[openstack-dev] [designate][osc] new sub commands - how should they be named?
reedip banerjee
reedip14 at gmail.com
Wed Apr 6 23:14:52 UTC 2016
Hi Graham,
Service is somewhat a pretty common word and would have been used by
several components. But the distinguishing point between Keystone,
Designate, Nova et.al . would be the component ( in this case , dns) to
which the subcommand belongs to.
Also, the below commands make more sense.
> openstack dns service list
> openstack dns service show
You can continue with these options IMHO.
On Wed, Apr 6, 2016 at 8:23 PM, Morgan Fainberg <morgan.fainberg at gmail.com>
wrote:
>
>
> On Wed, Apr 6, 2016 at 7:44 AM, Sheel Rana Insaan <ranasheel2000 at gmail.com
> > wrote:
>
>> Hey Graham,
>>
>> I just added service for block storage, we have named these
>> openstack volume service list/enable/disable.
>>
>> Same protocol is used for nova as well previosly.
>>
>> Hope this will help.
>>
>> Regards,
>> Sheel Rana
>> On Apr 6, 2016 7:54 PM, "Hayes, Graham" <graham.hayes at hpe.com> wrote:
>>
>>> On 06/04/2016 15:20, Qiming Teng wrote:
>>> > On Wed, Apr 06, 2016 at 01:59:29PM +0000, Hayes, Graham wrote:
>>> >> Designate is adding support for viewing the status of the various
>>> >> services that are running.
>>> >>
>>> >> We have added support to our openstack client plugin, but were looking
>>> >> for guidance / advices on what the actual commands should be.
>>> >>
>>> >> We have implemented it in [1] as "dns service list" and
>>> >> "dns service show" - but this is name-spacing the command.
>>> > do you mean?
>>> >
>>> > openstack dns service list
>>> > openstack dns service show
>>>
>>> sorry, yes - I just included the sub commands.
>>>
>>> >
>>> >> Is there an alternative? "service" is already taken by keystone, and
>>> if
>>> >> we take "service-status" (or other generic term) it will most likely
>>> >> conflict when nova / cinder / heat / others add support of their
>>> service
>>> >> listings to OSC.
>>> >>
>>> >> What is the protocol here? First to grab it wins?
>>> >>
>>> >> Thanks
>>> >>
>>> >> - Graham
>>> >>
>>> >> 1 - https://review.openstack.org/284103
>>> >>
>>>
>>
> I think the offered options make a lot of sense:
>
> openstack dns service list
> openstack dns service show
>
>
> I would encourage continued use of the namespacing like this for future
> subcommands where possible (as it seems cinder and nova are already on
> track to do).
>
> --Morgan
>
>
> __________________________________________________________________________
> 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
>
>
--
Thanks and Regards,
Reedip Banerjee
IRC: reedip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160407/a9c1b8c5/attachment.html>
More information about the OpenStack-dev
mailing list