[openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor
Victoria Martínez de la Cruz
victoria at vmartinezdelacruz.com
Mon Oct 12 22:25:40 UTC 2015
Thanks for your feedback. We discussed this topic in this week weekly
meeting and we came to the conclusion that it would be better to use
"pool-flavor" instead of creating a namespace for Zaqar only (by prefixing
everything with the "message" key).
So, this commands would look like
openstack pool-flavor create
openstack pool-flavor get
openstack pool-flavor delete
openstack pool-flavor update
openstack pool-flavor list
2015-10-10 10:10 GMT-03:00 Shifali Agrawal <shaifali.agrawal09 at gmail.com>:
> All right, thanks for responses, will code accordingly :)
> On Wed, Oct 7, 2015 at 9:31 PM, Doug Hellmann <doug at doughellmann.com>
>> Excerpts from Steve Martinelli's message of 2015-10-06 16:09:32 -0400:
>> > Using `message flavor` works for me, and having two words is just fine.
>> It might even be good to change "flavor" to "server flavor" (keeping
>> flavor as a backwards-compatible alias, of course).
>> > I'm in the process of collecting all of the existing "object" works are
>> > putting them online, there's a lot of them. Hopefully this will reduce
>> > collisions in the future.
>> > Thanks,
>> > Steve Martinelli
>> > OpenStack Keystone Core
>> > From: Shifali Agrawal <shaifali.agrawal09 at gmail.com>
>> > To: openstack-dev at lists.openstack.org
>> > Date: 2015/10/06 03:40 PM
>> > Subject: [openstack-dev] [Zaqar][cli][openstack-client] conflict in
>> > flavor and zaqar flavor
>> > Greetings,
>> > I am implementing cli commands for Zaqar flavors, the command should be
>> > like:
>> > "openstack flavor <create/update/delete>"
>> > But there is already same command present for Nova flavors. After
>> > discussing with Zaqar devs we thought to change all zaqar commands such
>> > that they include `message` word after openstack, thus above Zaqar
>> > command will become:
>> > "openstack message flavor <create/update/delete>"
>> > Does openstack-client devs have something to say for this? Or they also
>> > feel its good to move with adding `message` word to all Zaqar cli
>> > commands?
>> > Already existing Zaqar commands will work with get a deprecation
>> > message/warning and also I will implement them all to work with
>> > word, and all new commands will be implement so that they work only with
>> > `message` word.
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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