OpenStack
> Operators
> Subject: Re: [Openstack-operators] New services disable reason
>
> Our install is still quite small and we take the risk of hitting that
> compute node whilst the service is starting, but we haven't actually
> encountered that yet (probably a user base s
ck-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] New services disable reason
Our install is still quite small and we take the risk of hitting that compute
node whilst the service is starting, but we haven't actually encountered that
yet (probably a user base size i
Our install is still quite small and we take the risk of hitting that
compute node whilst the service is starting, but we haven't actually
encountered that yet (probably a user base size issue) ...
IMHO, having a reason why stuff is disabled avoids hours of confusion and
trying to find the person
Hi,
as operators I would like to have your comments/suggestions on:
https://review.openstack.org/#/c/136645/1
With a large number of nodes several services are disabled because various
reasons (in our case mainly hardware interventions).
To help operations we use the "disable reason" as fast filt
