<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Logging is a topic that I think should get more love on the
TripleO side.<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/24/2018 12:17 PM, Juan Badia
Payno wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKnAgae0uW1Ut2hEGqULeEhWNradZHCZAZL-+nyRym+zgy7Zjw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>
<div>Recently, I did a little test regarding fluentd logging
on the gates master[1], queens[2], pike [3]. I don't like
the status of it, I'm still working on them, but basically
there are quite a lot of misconfigured logs and some
services that they are not configured at all.</div>
<div><br>
</div>
<div>I think we need to put some effort on the logging. The
purpose of this email is to point out that we need to do a
little effort on the task.</div>
<div><br>
</div>
<div>First of all, I think we need to enable fluentd on all
the scenarios, as it is on the tests [1][2][3] commented on
the beginning of the email. Once everything is ok and some
automatic test regarding logging is done they can be
disabled.</div>
</div>
</div>
</blockquote>
Wes, do you have an opinion about this? I think it would be a good
idea to avoid these types of regressions.<br>
<blockquote type="cite"
cite="mid:CAKnAgae0uW1Ut2hEGqULeEhWNradZHCZAZL-+nyRym+zgy7Zjw@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>I'd love not to create a new bug for every
misconfigured/unconfigured service, but if requested to grab
more attention on it, I will open it.</div>
</div>
</div>
</blockquote>
One bug to fix all this is fine, but we do need a public place to
track all the work that needs to be done. Lets reference that place
on the bug. Could be Trello or an etherpad, or whatever you want,
it's up to you.<br>
<blockquote type="cite"
cite="mid:CAKnAgae0uW1Ut2hEGqULeEhWNradZHCZAZL-+nyRym+zgy7Zjw@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>The plan I have in mind is something like:</div>
<div> * Make an initial picture of what the fluentd/log status
is (from pike upwards).</div>
<div> * Fix all misconfigured services. (designate,...)</div>
<div> * Add the non-configured services. (manila,...)</div>
<div> * Add an automated check to find a possible
unconfigured/misconfigured problem.</div>
<div><br>
</div>
<div>Any comments, doubts or questions are welcome</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Juan</div>
<div><br>
</div>
<div>[1] <a href="https://review.openstack.org/594836"
moz-do-not-send="true">https://review.openstack.org/594836</a></div>
<div>[2] <a href="https://review.openstack.org/594838"
moz-do-not-send="true">https://review.openstack.org/594838</a></div>
<div>[3] <a href="https://review.openstack.org/594840"
moz-do-not-send="true">https://review.openstack.org/594840</a></div>
</div>
<div><br>
</div>
<div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>