[openstack-dev] [Zaqar][Horizon] UI for pools and flavors
shaifali.agrawal09 at gmail.com
Tue Oct 13 11:10:02 UTC 2015
Thanks for the responses.
While discussion on IRC with Zaqar developers flwag(Fei Long Wang )
mentioned that we need to focus on queues and subscriptions as well along
with pools and flavor, for the first iteration lets have queues and pools
Adding links here, ,  of updated mock-ups, please let me know your
views for them, what more information we should add in queues grid? Should
we provide users a UI to decide maximum number of messages a queue can hold?
[Create Pool]: http://tinyurl.com/nh9df6m
On Mon, Oct 12, 2015 at 7:40 PM, Fei Long Wang <feilong at catalyst.net.nz>
> On 12/10/15 20:36, Matthias Runge wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> On 12/10/15 09:25, Flavio Percoco wrote:
>>> On 10/10/15 21:07 +0530, Shifali Agrawal wrote:
>>>> I have prepared mock-ups, to build Zaqar UI, at present
>>>> focusing only to bring pools and flavors on dashboard. Sharing
>>>> two mock-ups for same purpose - allowing all operations related
>>>> to them(CRUD).
>>>> It will be great to know the views of zaqar developers/users if
>>>> the design is satisfactory to them or they want some amendments.
>>>> Also let me know if any information of pools/flavors is missing
>>>> and need to be added.
>>>> In first mockup showing pools information by default and will
>>>> show flavors if user click on flavors button present on top
>>>> second menu bar.
>>>> : http://tinyurl.com/o2b9q6r : http://tinyurl.com/pqwgwhl
>>> I'm adding `[horizon]` to the subject to get more folks'
>>> Thank you for bringing this up!
>> maybe it's necessary to give a brief context for those mockups?
> +1 For now, it would be nice if we can figure out where to hold the source
> code, a new dashboard project or in Horizon.
>> What does a pool here?
> A pool is like a container to organize queues/messages. Admin can create
> many different pools based on their capabilities.
>> why is a pool weighted (or how)
> When there are many pools, the pool with higher weight will be selected to
> be posted messages.
>> and isn't a
>> pools and a pool group somehow the same?
> Pool group is most like a group/container for group to organize groups.
>> If you have pools, what is the intention of flavors then?
> Admin can create flavor based on pool group's capabilities. Then user can
> create queue based on pool group to leverage the advantage of the pool
> group. For example, there are two pool groups. One named 'fast storage'
> which contains pools: pool_A and pool_B, one named 'reliable storage' which
> contains pool_C and pool_D, then admin can create a flavor named
> 'fast_storage'. When user created a new queue and set the flavor with
> 'fast_storage', then the messages posted to the queue will be stored in
> pool_A and pool_B.
>> Just to ask the obvious questions here....
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>> -----END PGP SIGNATURE-----
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Cheers & Best regards,
> Fei Long Wang (王飞龙)
> Senior Cloud Software Engineer
> Tel: +64-48032246
> Email: flwang at catalyst.net.nz
> Catalyst IT Limited
> Level 6, Catalyst House, 150 Willis Street, Wellington
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev