<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Great to see some interest on trying to improve the log!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">+1 on the “no valid host found”, this one should be at the very top of the to-be-fixed list.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Very difficult to troubleshoot filters in lab testing (let alone in production) as there can be many of them. This will get worst with more NFV optimization filters with so many combinations it gets really
complex to debug when a VM cannot be launched with NFV optimized flavors. With the scheduler filtering engine, there should be a systematic way to log the reason for not finding a valid host - at the very least the error should display which filter failed
as an ERROR (and not as DEBUG).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">We really need to avoid deploying with DEBUG log level but unfortunately this is the only way to troubleshoot. Too many debug-level logs are for development debug (meaning pretty much useless in any circumstances
– developer forgot to remove before commit of the feature), many errors that should be logged as ERROR but have been logged as DEBUG only.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> Alec<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Mikhail Medvedev <mihailmed@gmail.com><br>
<b>Date: </b>Tuesday, January 9, 2018 at 9:16 AM<br>
<b>To: </b>Piotr Bielak <piotr.bielak@corp.ovh.com><br>
<b>Cc: </b>"openstack-operators@lists.openstack.org" <openstack-operators@lists.openstack.org><br>
<b>Subject: </b>Re: [Openstack-operators] [openstack-operators][nova] Verbosity of nova scheduler<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
On Tue, Jan 9, 2018 at 8:18 AM, Piotr Bielak <<a href="mailto:piotr.bielak@corp.ovh.com">piotr.bielak@corp.ovh.com</a>> wrote:<br>
> Hi! I'm conducting some research about the nova scheduler logs<br>
> verbosity. Did you ever encounter any situation, where you didn't feel<br>
> satisfied with the amount or quality of the logs (at any log level).<br>
> It is known that the nova-scheduler produces hardly any logs at INFO<br>
> level. What are your experiences with the nova-scheduler in production<br>
> environments? What would you like to see in the logs, what isn't printed<br>
> at the moment (maybe some expected log format)?<br>
<br>
I am supporting a couple of OpenStack dev clouds and I found in order to solve most operational problems faster I need DEBUG enabled everywhere. In case of scheduler, "No valid host was found" was untractable without the debug messages (as of Mitaka). I need
to know what filter ate all the hosts and what values it used for calculations as a minimum.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">><br>
> Thanks for any help and advice,<br>
> Piotr Bielak<br>
><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">---<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Mikhail Medvedev (mmedvede)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">IBM<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>