<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Fuelers,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">As Simon said, we already have a log centralisation solution for MOS delivered as a Fuel plugins known as StackLight / LMA toolset. And so objectively, there is no need to have log management in Nailgun anymore. To go one step further we suggested several times to have a StackLight agent installed on the Fuel master node to also collect and centralise those logs. There is a little bit of a chicken and egg problem to resolve but I think it is worth a try to have that nailed down in the roadmap for Fuel 10.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Cheers</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"> - Patrick </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"> </div><p class="airmail_on">On 11 March 2016 at 10:07:28, Simon Pasquier (<a href="mailto:spasquier@mirantis.com">spasquier@mirantis.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">
<div>Hello Roman,<br>
<br></div>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Mar 11, 2016 at 9:57 AM, Roman
Prykhodchenko <span dir="ltr"><<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</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">
Fuelers,<br>
<br>
I remember we’ve discussing this topic in our couloirs before but
I’d like to bring that discussion to a more official format.<br>
<br>
Let me state a few reasons to do this:<br>
<br>
- Log management code in Nailgun is overcomplicated<br>
- Working with logs on big scale deployments is barely possible
given the current representation<br>
- Due to overcomplexity and ineffectiveness of the code we always
get recurring bugs like [1]. That eats tons of time to
resolve.<br>
- There are much better specialized tools, say Logstash [2], that
can deal with logs much more effectively.<br>
<br>
<br>
There may be more reasons bus I think even the already mentioned
ones are enough to think about the following proposal:<br>
<br>
- Remove Logs tab from Fuel Web UI<br>
- Remove logs support from Nailgun<br>
- Create mechanism that allows to configure different log
management software, say Logstash, Loggly, etc </blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- Choose a default software to install and provide a plugin for it
from the box<br></blockquote>
<div><br>
<div>This is what the LMA/StackLight plugins [1][2] are meant for.
No need to develop anything new.<br>
<br></div>
<div>And I'm +1 with the removal of log management from Fuel. As
you said, it can't scale...<br></div>
<div><br>
[1] <a href="http://fuel-plugin-lma-collector.readthedocs.org/en/latest/">http://fuel-plugin-lma-collector.readthedocs.org/en/latest/</a><br>
[2] <a href="http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/">
http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/</a><br>
</div>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
References<br>
1. <a href="https://bugs.launchpad.net/fuel/+bug/1553170" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1553170</a><br>
2. <a href="https://www.elastic.co/products/logstash" rel="noreferrer" target="_blank">https://www.elastic.co/products/logstash</a><br>
<br>
<br>
- romcheg<br>
<br>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote>
</div>
<br></div>
</div>
</div>
</div>
__________________________________________________________________________
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<br></div></div></span></blockquote></body></html>