<div dir="ltr"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 31, 2018 at 3:08 PM, Juan Antonio Osorio Robles <span dir="ltr"><<a href="mailto:jaosorior@redhat.com" target="_blank">jaosorior@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF">
    <p>Logging is a topic that I think should get more love on the
      TripleO side.<br>
    </p><span class="gmail-">
    <br>
    <div class="gmail-m_5046470707256441310moz-cite-prefix">On 08/24/2018 12:17 PM, Juan Badia
      Payno wrote:<br>
    </div>
    <blockquote type="cite">
      
      <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></span>
    Wes, do you have an opinion about this? I think it would be a good
    idea to avoid these types of regressions.<span class="gmail-"><br>
    <blockquote type="cite">
      <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></span>
    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></div></blockquote><div>I'm creating the google spreadsheet [4] to track the status of the fluentd logging from pike to master. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
    <blockquote type="cite"><span class="gmail-">
      <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" target="_blank">https://review.openstack.org/<wbr>594836</a></div>
          <div>[2] <a href="https://review.openstack.org/594838" target="_blank">https://review.openstack.org/<wbr>594838</a></div>
          <div>[3] <a href="https://review.openstack.org/594840" target="_blank">https://review.openstack.org/<wbr>594840</a></div></div></div></span></blockquote></div></blockquote><div>[4] <span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://docs.google.com/spreadsheets/d/1Keh_hBYGb92rXV3VN44oPR6eGnX9LnTpcadWfMO8dZs/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1Keh_hBYGb92rXV3VN44oPR6eGnX9LnTpcadWfMO8dZs/edit?usp=sharing</a></span><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"> </span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><blockquote type="cite"><span class="gmail-"><div dir="ltr"><div>
        </div>
        <div><br>
        </div>
        <div>
        </div>
      </div>
      <br>
      <fieldset class="gmail-m_5046470707256441310mimeAttachmentHeader"></fieldset>
      <br>
      </span><span class="gmail-"><pre>______________________________<wbr>______________________________<wbr>______________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="gmail-m_5046470707256441310moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a>
<a class="gmail-m_5046470707256441310moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a>
</pre>
    </span></blockquote>
    <br>
  </div>

<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px;padding:0px"><span style="margin:0px;padding:0px">Juan</span> <span style="margin:0px;padding:0px">Badia Payno</span></p><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px;padding:0px"></p><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px;padding:0px"><span style="margin:0px;padding:0px">Software Engineer</span> </span><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px"></span><br style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px;padding:0px"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px;padding:0px">Red Hat <span style="margin:0px;padding:0px">EMEA ENG Openstack Infrastructure</span></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><br></td></tr></tbody></table></div></div></div></div></div></div></div>
</div></div></div>