Open Stack

On 05/25/2017 10:20 AM, Zhenguo Niu wrote:
> hi all,

Hi!

> 
> I'm from the Mogan team, we chose the same keyward 'baremetal' when implementing 
> a OSC plugin [1]. As we think the baremetal command is representative of a 
> baremetal resource, not a service, so it makes sense for different projects to 
> share the top level resource name that OpenStack can provide.

We do not "own" the word "baremetal", so nothing prevents you from using it. 
However, in my experience:
1. This does confuse users, as they expect "openstack baremetal" to be a prefix 
belonging to Ironic.
2. Collisions may happen. We had two collisions with TripleO already, one 
resulted in us killing a TripleO command abruptly.

> 
> The commands we have implemented are listed below, seems there's no collision 
> with Ironic presently, and Ironic doesn't manage such resources.
> 
> * openstack baremetal server <action> <args>
> * openstack bareemtal flavor <action> <args>
> * openstack baremetal keypair <action> <args>
> * openstack baremetal availability zone <action> <args>

Ironic does not have any notion of either of these, so it should be fine.

I'm still a bit on a -1 side because of potential users confusion. I wonder how 
can we send a message across that prefixes do not designate a specific project, 
but are rather just part of a "sentence". I'm specifically worried about 
confusing "baremetal server" of Mogan with "baremetal node" of Ironic. For many 
people these can be synonyms.

> 
> So, we'd like to ask if our CLI pattern is allowed before we release the client.
> 
> Thanks in advance!
> 
> 
> [1] https://github.com/openstack/python-moganclient
> 
> -- 
> Best Regards,
> Zhenguo Niu
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>