<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">The proposed monitoring options make sense, since the Fuel master has nothing yet, but I would like to ressurect this thread to see if we can discuss some strategies in order to avoid the /var/log fillup with consequent docker containers corruption.</div><div class=""><br class=""></div><div class="">Now, a customer facing this corruption can recover the master, as described in our documentation [1].</div><div class="">Of course, if we could avoid the problem at all, it would be even better. So, do we have a strategy in progress on this?</div><div class=""><br class=""></div><div class="">As a first attempt, I filed a blueprint, proposing to separate /var/log [2]. </div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Fabrizio.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting" class="">http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting</a></div><div class="">[2] <a href="https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master" class="">https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master</a> </div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On 21 Nov 2014, at 12:01, Matthew Mosesohn <<a href="mailto:mmosesohn@mirantis.com" class="">mmosesohn@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I'm okay with Sensu or Monit, just as long as the results of<br class="">monitoring can be represented in a web UI and has a configurable<br class="">option for email alerting. Tight integration with Fuel Web is a<br class="">nice-to-have (via AMQP perhaps), but anything that can solve our<br class="">out-of-disk scenario is ideal. I did my best to tune our logging and<br class="">logs rotation, but monitoring is the most sensible approach.<br class=""><br class="">-Matthew<br class=""><br class="">On Fri, Nov 21, 2014 at 12:21 PM, Przemyslaw Kaminski<br class=""><<a href="mailto:pkaminski@mirantis.com" class="">pkaminski@mirantis.com</a>> wrote:<br class=""><blockquote type="cite" class="">BTW, there's also Monit<br class=""><br class=""><a href="http://mmonit.com/monit/" class="">http://mmonit.com/monit/</a><br class=""><br class="">(though it's in C) that looks quite nice. Some config examples:<br class=""><br class="">http://omgitsmgp.com/2013/09/07/a-monit-primer/<br class=""><br class="">P.<br class=""><br class="">On 11/20/2014 09:13 PM, Dmitriy Shulyak wrote:<br class=""><br class="">Guys, maybe we can use existing software, for example Sensu [1]?<br class="">Maybe i am wrong, but i dont like the idea to start writing our "small"<br class="">monitoring applications..<br class="">Also something well designed and extendable can be reused for statistic<br class="">collector<br class=""><br class=""><br class="">1. https://github.com/sensu<br class=""><br class="">On Wed, Nov 12, 2014 at 12:47 PM, Tomasz Napierala <tnapierala@mirantis.com><br class="">wrote:<br class=""><blockquote type="cite" class=""><br class=""><br class="">On 06 Nov 2014, at 12:20, Przemyslaw Kaminski <pkaminski@mirantis.com><br class="">wrote:<br class=""><br class=""><blockquote type="cite" class="">I didn't mean a robust monitoring system, just something simpler.<br class="">Notifications is a good idea for FuelWeb.<br class=""></blockquote><br class="">I’m all for that, but if we add it, we need to document ways to clean up<br class="">space.<br class="">We could also add some kind of simple job to remove rotated logs, obsolete<br class="">spanshots, etc., but this is out of scope for 6.0 I guess.<br class=""><br class="">Regards,<br class="">--<br class="">Tomasz 'Zen' Napierala<br class="">Sr. OpenStack Engineer<br class="">tnapierala@mirantis.com<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">OpenStack-dev mailing list<br class="">OpenStack-dev@lists.openstack.org<br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></blockquote><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">OpenStack-dev mailing list<br class="">OpenStack-dev@lists.openstack.org<br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">OpenStack-dev mailing list<br class="">OpenStack-dev@lists.openstack.org<br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""><br class=""></blockquote><br class="">_______________________________________________<br class="">OpenStack-dev mailing list<br class=""><a href="mailto:OpenStack-dev@lists.openstack.org" class="">OpenStack-dev@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></div></blockquote></div><br class=""></body></html>