[Rdo-list] Disabling and enabling OpenStack

Kaul, Yaniv Yaniv.Kaul at emc.com
Fri Nov 7 11:25:21 UTC 2014


> -----Original Message-----
> From: Lars Kellogg-Stedman [mailto:lars at redhat.com]
> Sent: Friday, November 07, 2014 12:26 PM
> To: Kaul, Yaniv
> Cc: rdo-list at redhat.com
> Subject: Re: [Rdo-list] Disabling and enabling OpenStack
> 
> On Wed, Nov 05, 2014 at 06:39:18AM -0500, Kaul, Yaniv wrote:
> > This was fine and dandy, but now:
> > 1. I can't stop the openstack services:
> > [root at lgdrm1499 ~]# openstack-service list |xargs openstack-service
> > stop Too few arguments.
> 
> "openstack-service list" and other commands only operated on "enabled"
> services (because you would not want to start services that were disabled).
> When you disable a service, that means you can no longer operate on it with
> the openstack-service command.
> 
> In your situation, I would do this:

Thanks, I've managed.
I find the functionality half-baked. If you have a disable, it's only natural you want an enable action. And you do expect it to work.

You also expect 'stop' to work on active service, regardless if they are enabled or disabled (in my case, I've disabled before stopping them).
I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1161501 to track the issue.

Lastly, I've mentioned but not filed a bug - on secondary compute nodes, openstack-utils RPM is not installed (Packstack-based installation), making stopping/starting the openstack related services a bit different than on the controller node.
Y.

> 
>   openstack-service list > /etc/openstack-services
>   openstack-service stop
>   xargs systemctl disable < /etc/openstack-services
> 
> And then when you want to start things back up:
> 
>   xargs systemctl enable < /etc/openstack-services
>   openstack-service start
> 
> --
> Lars Kellogg-Stedman <lars at redhat.com> | larsks @ {freenode,twitter,github}
> Cloud Engineering / OpenStack          | http://blog.oddbit.com/





More information about the dev mailing list