Re: [openstack-dev] [designate][osc] new sub commands - how should they be named?

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. >

Re: [openstack-dev] [designate][osc] new sub commands - how should they be named?

On Wed, Apr 6, 2016 at 7:44 AM, Sheel Rana Insaan 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. > >

Re: [openstack-dev] [designate][osc] new sub commands - how should they be named?

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" wrote: > On

Re: [openstack-dev] [designate][osc] new sub commands - how should they be named?

On 06/04/2016 15:20, Qiming Teng wrote: > On Wed, Apr 06, 2016 at 01:59:29PM +, 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 /

Re: [openstack-dev] [designate][osc] new sub commands - how should they be named?

On Wed, Apr 06, 2016 at 01:59:29PM +, 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

[openstack-dev] [designate][osc] new sub commands - how should they be named?

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