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> > To: 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?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
