<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>+1 as well, for the same reasons. I also added by +1 to the review. Thanks!</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Alex Leonhardt <<a href="mailto:aleonhardt.py@gmail.com">aleonhardt.py@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, January 15, 2015 at 1:02 AM<br>
<span style="font-weight:bold">To: </span>Belmiro Moreira <<a href="mailto:moreira.belmiro.email.lists@gmail.com">moreira.belmiro.email.lists@gmail.com</a>>, OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-operators] New services disable reason<br>
</div>
<div><br>
</div>
<div>
<div>
<p dir="ltr">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) ...</p>
<p dir="ltr">IMHO, having a reason why stuff is disabled avoids hours of confusion and trying to find the person who 'did it'.</p>
<p dir="ltr">In terms of keeping track, I'd have thought that the dashboard admin panel can show you service states and I'd expect a disabled service to say 'disabled', but again we don't even use this feature at the moment.</p>
<p dir="ltr">+1 from me :)</p>
<p dir="ltr">Alex<br>
</p>
<br>
<div class="gmail_quote">On Wed, 14 Jan 2015 19:34 Belmiro Moreira <<a href="mailto:moreira.belmiro.email.lists@gmail.com">moreira.belmiro.email.lists@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,
<div>as operators I would like to have your comments/suggestions on:</div>
<div><a href="https://review.openstack.org/#/c/136645/1" target="_blank">https://review.openstack.org/#/c/136645/1</a><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>With a large number of nodes several services are disabled because various reasons (in our case mainly hardware interventions). </div>
<div>To help operations we use the "disable reason" as fast filter to identify why the service is disabled.</div>
<div><br>
</div>
<div>At same time, we add several new nodes (nova-compute) per week. </div>
</div>
<div>At CERN to avoid adding a service when the daemon starts for the first time nova is configured with:</div>
<div>enable_new_services=False</div>
<div>This is great, however no "disable reason" is set. </div>
<div>For us having services disabled with no reason specified creates additional checks. </div>
<div><br>
</div>
<div>How are others keeping track of disabled services?</div>
<div><br>
</div>
<div><br>
</div>
<div>Belmiro</div>
<div>---</div>
<div>CERN</div>
</div>
______________________________<u></u>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-operators</a><br>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>