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

Shifali Agrawal shaifali.agrawal09 at gmail.com
Tue Oct 13 20:58:03 UTC 2015

On Tue, Oct 13, 2015 at 12:05 PM, Flavio Percoco <flavio at redhat.com> 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 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?

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:

$ keystone user-create
$ heat event-list

This will create a separate namespace for the project and also will solve
the issue of `openstack messaging message post`.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151014/94c42ff1/attachment.html>

More information about the OpenStack-dev mailing list