[openstack-dev] [Zaqar][Horizon] UI for pools and flavors

Fei Long Wang feilong at catalyst.net.nz
Mon Oct 12 13:55:25 UTC 2015

On 12/10/15 20:36, Matthias Runge wrote:
> Hash: SHA256
> On 12/10/15 09:25, Flavio Percoco wrote:
>> On 10/10/15 21:07 +0530, Shifali Agrawal wrote:
>>> Greetings!
>>> I have prepared mock-ups[1],[2] 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[1] showing pools information by default and will
>>> show flavors if user click on flavors button present on top
>>> second menu bar.
>>> [1]: http://tinyurl.com/o2b9q6r [2]: http://tinyurl.com/pqwgwhl
>> I'm adding `[horizon]` to the subject to get more folks'
>> attention.
> 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....
> Matthias
> Version: GnuPG v2
> nHD0oAN5fxmAR0fqZH57n0T7et8Ocp+Xgp9aUD9roLPGlj9uFnLntMSHo9WIAzU9
> gq2fl0pgnmpMzwJ0yooAiMq4HXyJcG5UaY9xImTReTH4382x8j1OTVFvS+9ws+VU
> enK4S/2JW4Rvf6jpYGUcoNqtdmkFRLQohvu/K3V1Cg1Y+zMeYIQZxb4oZzcEOEyo
> 6E+DicR/4VVGi8gl0UGPkXSmm/jFaG8H3m5KTvTQr0PDd6l5ypwDXvZcRKQvPYmc
> c155EvjeXPByhm1jXpE6Cgv6NNROQFr+uRM1jKLF0Ss030XI7TSyMNYv9br6OVxi
> /SMlF+BG+FK26uwTc9Mf5D5mqTF6qgbPTLLu4vlqKa3JX0/y7Z8a7NoujzTKUBEl
> WAftY2ADAJE6Vb/1TEubujDIlKGBtoT/lGQUIJtj1t5VftfaNrZ1N2vMQ4P7c9hA
> W2EoRCTe6m8YbPPT3b3QFuuH2oecPECTiWcjEgRxp23ksnoFDkgjEGeM1+xNeQVV
> kfwfG4mcGP4lEUwPk2sdL/3xu16iUTMJURZdvkqI1FX3YfMwITjiY/jdqIwVwlNF
> 03XhFn1uloXyHSNRNNFXf85r3v4FDw9FWQCeCU5mqOzkdZZafhvdi2tUjkHniGsG
> =nLNP
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

More information about the OpenStack-dev mailing list