[openstack-dev] [Ironic] Command structure for OSC plugin
Dmitry Tantsur
dtantsur at redhat.com
Mon Aug 24 15:56:36 UTC 2015
On 08/24/2015 05:41 PM, Jay Pipes wrote:
> On 08/24/2015 08:03 AM, Brad P. Crochet wrote:
>> I am working on extending the current set of patches that implement
>> the OSC plugin for Ironic. I would like some discussion/guidance about
>> a couple of command structures.
>>
>> Currently provisioning state is set via 'openstack baremetal set
>> --provision-state [active|deleted|rebuild|inspect|provide|manage]
>> $NODE'
>>
>> dtantsur suggests it be top-level a command (which I concur)
>> 'openstack baremetal [active|delete|rebuild|inspect|provide|manage]
>> $NODE'
>>
>> Question there is does that make sense?
>
> I prefer the current CLI command structure.
>
> `openstack baremetal active $NODE` does not make grammatical sense.
>
> `openstack baremetal activate $NODE` would make more sense, but I
> actually think the original is easier.
As it is now it's a bit hard to understand what "openstack baremetal
set" command actually does, as it corresponds to 2 API's (and I hope it
won't also do node updating, will it?)
>
> Best,
> -jay
>
> __________________________________________________________________________
> 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
More information about the OpenStack-dev
mailing list