<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Hi Folks,<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">I’d like to get some eyes on a bug I just filed:
<a href="https://bugs.launchpad.net/nova/+bug/1250049"><span style="color:#333333;text-decoration:none">https://bugs.launchpad.net/nova/+bug/1250049</span></a><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">A recent change (</span><a href="https://review.openstack.org/#/c/52189/9">https://review.openstack.org/#/c/52189/9</a><span class="apple-converted-space"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333"> </span></span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">)
introduced the automatic disable / re-enable of nova-compute when connection to libvirt is lost and recovered. The problem is that it doesn’t take any account of the fact that a cloud administrator may have other reasons for disabling a service, and always
put nova-compute back into an enabled state. <o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white;max-width: 45em;orphans: auto;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">The impact of this is pretty big for us – at any point in time we have a number of servers disabled for various operational reasons, and there are times when we need to restart libvirt
as part of a deployment. With this change in place all of those hosts are returned to an enabled state, and the reason that they were disabled is lost.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">While I like the concept that an error condition like this should disable the host from a scheduling perspective, I think it needs to be implemented as an additional form of disablement
(i.e a separate value kept in the ServiceGroup API), not an override of the current one.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">I’d like to propose that the current change is reverted as a priority, and a new approach then submitted as a second step that works alongside the current enable /disable reason.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Sorry for not catching this in the review stage – I didn’t notice this one at all.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:14.4pt;margin-left:0cm;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Phil<o:p></o:p></span></p>
</div>
</body>
</html>