Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-19 Thread Shifali Agrawal
Thanks for the awesome feedback :) I got the point of not using project name, thanks Dean for explaining it so well. We will move ahead as per Monty's suggestion. On Wed, Oct 14, 2015 at 3:13 PM, Sean Dague wrote: > On 10/12/2015 07:55 PM, Dean Troyer wrote: > > On Mon, Oct 12,

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-14 Thread Flavio Percoco
On 13/10/15 18:27 -0400, Monty Taylor wrote: On 10/13/2015 05:15 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal > wrote: All above make sense, just one thing, how about using word "zaqar"

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-14 Thread Sean Dague
On 10/12/2015 07:55 PM, Dean Troyer wrote: > On Mon, Oct 12, 2015 at 5:25 PM, Victoria Martínez de la Cruz > > > wrote: > > So, this commands would look like > > openstack pool-flavor create > openstack

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Flavio Percoco
On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote: HI all, 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

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Victoria Martínez de la Cruz
Fair enough, +1 to Flavio's suggestion Thanks all, Victoria 2015-10-13 3:35 GMT-03:00 Flavio Percoco : > On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote: > >> HI all, >> >> Thanks for your feedback. We discussed this topic in this week weekly >> meeting >> and we

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Fox, Kevin M
questions) Subject: Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor Fair enough, +1 to Flavio's suggestion Thanks all, Victoria 2015-10-13 3:35 GMT-03:00 Flavio Percoco <fla...@redhat.com<mailto:fla...@redhat.com>>: On 12/10/15 19:25 -03

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Hayes, Graham
> *Sent:* Tuesday, October 13, 2015 5:28 AM > *To:* Flavio Percoco; OpenStack Development Mailing List (not for usage > questions) > *Subject:* Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in > nova flavor and zaqar flavor > > Fair enough, +1 to Flavio's suggestion &

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Shifali Agrawal
On Tue, Oct 13, 2015 at 12:05 PM, Flavio Percoco wrote: > On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote: > >> HI all, >> >> Thanks for your feedback. We discussed this topic in this week weekly >> meeting >> and we came to the conclusion that it would be better

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Dean Troyer
On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal < shaifali.agrawa...@gmail.com> wrote: > All above make sense, just one thing, how about using word "zaqar" > instead of messaging? That is what all other projects are doing, for > example: > These are the old project-specific CLIs, note that the

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Steve Baker
On 14/10/15 10:15, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal > wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other projects

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Monty Taylor
On 10/13/2015 05:15 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal > wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-12 Thread Victoria Martínez de la Cruz
HI all, 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

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-12 Thread Dean Troyer
On Mon, Oct 12, 2015 at 5:25 PM, Victoria Martínez de la Cruz < victo...@vmartinezdelacruz.com> wrote: > 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 > I

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-10 Thread Shifali Agrawal
All right, thanks for responses, will code accordingly :) On Wed, Oct 7, 2015 at 9:31 PM, Doug Hellmann wrote: > 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

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-07 Thread Doug Hellmann
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). Doug > > I'm in the

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-06 Thread Steve Martinelli
Using `message flavor` works for me, and having two words is just fine. 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 the collisions in the future. Thanks, Steve Martinelli OpenStack Keystone Core