On 13/10/15 16:46, Fox, Kevin M wrote: > lb's use the term pools too. A little more specific might be good. > > Thanks, > Kevin > ------------------------------------------------------------------------ > *From:* Victoria Martínez de la Cruz [victo...@vmartinezdelacruz.com] > *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 > > 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 -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 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 > > > First and foremost, I'm sorry for not attending the last meeting. > > I just read the logs from the meeting and I'd like to raise my > concerns with the above. I think it's very confusing for users to have > a non-namespaced command. > > For example, what's a pool-flavor? Is it related to Nova's flavors? Is > it something related to some network pools? etc. > > I understand that one of the concerns is that things like `openstack > message message post` wouldn't look good but I think that the project > namespace could match the service catalog (will let folks for OSC > confirm/deny this). > > Some examples: > > $ openstack messaging post > $ openstack messaging flavor create > $ openstack messaging pool add > > etc > > Does the above make sense? > Flavio > > > > Best, > > Victoria > > 2015-10-10 10:10 GMT-03:00 Shifali Agrawal > <shaifali.agrawa...@gmail.com > <mailto:shaifali.agrawa...@gmail.com>>: > > All right, thanks for responses, will code accordingly :) > > On Wed, Oct 7, 2015 at 9:31 PM, Doug Hellmann > <d...@doughellmann.com <mailto:d...@doughellmann.com>> > 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 might even be good to change "flavor" to "server > flavor" (keeping > flavor as a backwards-compatible alias, of course). > Doug > > > > 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 > > > > > > > > From: Shifali Agrawal <shaifali.agrawa...@gmail.com > <mailto:shaifali.agrawa...@gmail.com>> > > To: openstack-dev@lists.openstack.org > <mailto:openstack-dev@lists.openstack.org> > > Date: 2015/10/06 03:40 PM > > Subject: [openstack-dev] > [Zaqar][cli][openstack-client] conflict > in nova > > 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 > flavor > > 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 > `message` > > word, and all new commands will be implement so that > they work only > with > > `message` word. > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org > <mailto:openstack-dev-requ...@lists.openstack.org>? > subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > @flaper87 > Flavio Percoco > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
As does designate - and we will have pool flavors in a future release. - Graham __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
