<p dir="ltr">+1 to remove logs from Fuel UI in Fuel Newton.<br>
In Fuel Mitaka we'd need to put a deprecation warning somewhere.</p>
<br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 11, 2016, 04:57 Patrick Petit <<a href="mailto:ppetit@mirantis.com">ppetit@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <p>On 11 March 2016 at 12:51:40, Igor Kalnitsky (<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>) wrote:</p> <div><blockquote type="cite" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span><div><div></div><div>Patrick,<span> </span><br><br>Sorry, but I meant another question. I thought that LMA plugin should<span> </span><br>be installed in some environment before we can start use it. Is this a<span> </span><br>case? If so, it means we can't use for master node until some<span> </span><br>environment is deployed.<span> </span></div></div></span></blockquote></div></div><div style="word-wrap:break-word"><p>Right. This is the chicken and egg problem I mentioned earlier...</p><p>But this is not a “problem” specific to Fuel. My take on this is is that ops management tooling (logging, monitoring) should be installed off-band before any OpenStack deployment. In fact, in real-world usage, we frequently get asks to have the monitoring and logging services of StackLight installed permanently for multi-enviroments. And so, one approach would be to make Stacklight backend services the first bits of software installed by Fuel (if not already there), then reconfigure Fuel to hook into those services and only then, enter into the regular OpenStack provisioning mode.</p></div><div style="word-wrap:break-word"><div><blockquote type="cite" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span><div><div><br><br>On Fri, Mar 11, 2016 at 12:52 PM, Patrick Petit <<a href="mailto:ppetit@mirantis.com" target="_blank">ppetit@mirantis.com</a>> wrote:<span> </span><br>><span> </span><br>> On 11 March 2016 at 11:34:32, Igor Kalnitsky (<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>)<span> </span><br>> wrote:<span> </span><br>><span> </span><br>> Hey Roman,<span> </span><br>><span> </span><br>> Thank you for bringing this up. +1 from my side, especially taking<span> </span><br>> into account the patch where we tried to solve logrotated logs problem<span> </span><br>> [1]. It's complex and unsupportable, as well as already existed<span> </span><br>> logview code in Nailgun.<span> </span><br>><span> </span><br>> Patrick, Simon,<span> </span><br>><span> </span><br>> Does LMA plugin support logs from master node? Or it's designed to<span> </span><br>> watch environment's logs?<span> </span><br>><span> </span><br>> No it’s not designed specifically for environment logs. Can be adapted to<span> </span><br>> any log format.<span> </span><br>><span> </span><br>> Would just need to write a parser like you would with logstach when logs are<span> </span><br>> not standard.<span> </span><br>><span> </span><br>> Patrick<span> </span><br>><span> </span><br>><span> </span><br>><span> </span><br>> Thanks,<span> </span><br>> Igor<span> </span><br>><span> </span><br>><span> </span><br>> [1]: <a href="https://review.openstack.org/#/c/243240/" target="_blank">https://review.openstack.org/#/c/243240/</a><span> </span><br>><span> </span><br>> On Fri, Mar 11, 2016 at 11:53 AM, Patrick Petit <<a href="mailto:ppetit@mirantis.com" target="_blank">ppetit@mirantis.com</a>> wrote:<span> </span><br>>> Fuelers,<span> </span><br>>><span> </span><br>>> As Simon said, we already have a log centralisation solution for MOS<span> </span><br>>> delivered as a Fuel plugins known as StackLight / LMA toolset. And so<span> </span><br>>> objectively, there is no need to have log management in Nailgun anymore.<span> </span><br>>> To<span> </span><br>>> go one step further we suggested several times to have a StackLight agent<span> </span><br>>> installed on the Fuel master node to also collect and centralise those<span> </span><br>>> logs.<span> </span><br>>> There is a little bit of a chicken and egg problem to resolve but I think<span> </span><br>>> it<span> </span><br>>> is worth a try to have that nailed down in the roadmap for Fuel 10.<span> </span><br>>> Cheers<span> </span><br>>> - Patrick<span> </span><br>>><span> </span><br>>><span> </span><br>>> On 11 March 2016 at 10:07:28, Simon Pasquier (<a href="mailto:spasquier@mirantis.com" target="_blank">spasquier@mirantis.com</a>)<span> </span><br>>> wrote:<span> </span><br>>><span> </span><br>>> Hello Roman,<span> </span><br>>><span> </span><br>>> On Fri, Mar 11, 2016 at 9:57 AM, Roman Prykhodchenko <<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a>><span> </span><br>>> wrote:<span> </span><br>>>><span> </span><br>>>> Fuelers,<span> </span><br>>>><span> </span><br>>>> I remember we’ve discussing this topic in our couloirs before but I’d<span> </span><br>>>> like<span> </span><br>>>> to bring that discussion to a more official format.<span> </span><br>>>><span> </span><br>>>> Let me state a few reasons to do this:<span> </span><br>>>><span> </span><br>>>> - Log management code in Nailgun is overcomplicated<span> </span><br>>>> - Working with logs on big scale deployments is barely possible given the<span> </span><br>>>> current representation<span> </span><br>>>> - Due to overcomplexity and ineffectiveness of the code we always get<span> </span><br>>>> recurring bugs like [1]. That eats tons of time to resolve.<span> </span><br>>>> - There are much better specialized tools, say Logstash [2], that can<span> </span><br>>>> deal<span> </span><br>>>> with logs much more effectively.<span> </span><br>>>><span> </span><br>>>><span> </span><br>>>> There may be more reasons bus I think even the already mentioned ones are<span> </span><br>>>> enough to think about the following proposal:<span> </span><br>>>><span> </span><br>>>> - Remove Logs tab from Fuel Web UI<span> </span><br>>>> - Remove logs support from Nailgun<span> </span><br>>>> - Create mechanism that allows to configure different log management<span> </span><br>>>> software, say Logstash, Loggly, etc<span> </span><br>>>><span> </span><br>>>> - Choose a default software to install and provide a plugin for it from<span> </span><br>>>> the box<span> </span><br>>><span> </span><br>>><span> </span><br>>> This is what the LMA/StackLight plugins [1][2] are meant for. No need to<span> </span><br>>> develop anything new.<span> </span><br>>><span> </span><br>>> And I'm +1 with the removal of log management from Fuel. As you said, it<span> </span><br>>> can't scale...<span> </span><br>>><span> </span><br>>> [1] <a href="http://fuel-plugin-lma-collector.readthedocs.org/en/latest/" target="_blank">http://fuel-plugin-lma-collector.readthedocs.org/en/latest/</a><span> </span><br>>> [2] <a href="http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/" target="_blank">http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/</a><span> </span><br>>><span> </span><br>>><span> </span><br>>>><span> </span><br>>>><span> </span><br>>>><span> </span><br>>>> References<span> </span><br>>>> 1. <a href="https://bugs.launchpad.net/fuel/+bug/1553170" target="_blank">https://bugs.launchpad.net/fuel/+bug/1553170</a><span> </span><br>>>> 2. <a href="https://www.elastic.co/products/logstash" target="_blank">https://www.elastic.co/products/logstash</a><span> </span><br>>>><span> </span><br>>>><span> </span><br>>>> - romcheg<span> </span><br>>>><span> </span><br>>>><span> </span><br>>>> __________________________________________________________________________<span> </span><br>>>> OpenStack Development Mailing List (not for usage questions)<span> </span><br>>>> Unsubscribe:<span> </span><br>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><span> </span><br>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span> </span><br>>>><span> </span><br>>><span> </span><br>>> __________________________________________________________________________<span> </span><br>>> OpenStack Development Mailing List (not for usage questions)<span> </span><br>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><span> </span><br>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span> </span><br>>><span> </span><br>>><span> </span><br>>> __________________________________________________________________________<span> </span><br>>> OpenStack Development Mailing List (not for usage questions)<span> </span><br>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><span> </span><br>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span> </span><br>>><span> </span><br>><span> </span><br>> __________________________________________________________________________<span> </span><br>> OpenStack Development Mailing List (not for usage questions)<span> </span><br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><span> </span><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span> </span><br></div></div></span></blockquote></div></div>__________________________________________________________________________<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>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>