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.
Now, a customer facing this corruption can recover the master, as described in our documentation [1]. 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? As a first attempt, I filed a blueprint, proposing to separate /var/log [2]. Thanks, Fabrizio. [1] http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting <http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting> [2] https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master <https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master> > On 21 Nov 2014, at 12:01, Matthew Mosesohn <mmoses...@mirantis.com> wrote: > > I'm okay with Sensu or Monit, just as long as the results of > monitoring can be represented in a web UI and has a configurable > option for email alerting. Tight integration with Fuel Web is a > nice-to-have (via AMQP perhaps), but anything that can solve our > out-of-disk scenario is ideal. I did my best to tune our logging and > logs rotation, but monitoring is the most sensible approach. > > -Matthew > > On Fri, Nov 21, 2014 at 12:21 PM, Przemyslaw Kaminski > <pkamin...@mirantis.com> wrote: >> BTW, there's also Monit >> >> http://mmonit.com/monit/ >> >> (though it's in C) that looks quite nice. Some config examples: >> >> http://omgitsmgp.com/2013/09/07/a-monit-primer/ >> >> P. >> >> On 11/20/2014 09:13 PM, Dmitriy Shulyak wrote: >> >> Guys, maybe we can use existing software, for example Sensu [1]? >> Maybe i am wrong, but i dont like the idea to start writing our "small" >> monitoring applications.. >> Also something well designed and extendable can be reused for statistic >> collector >> >> >> 1. https://github.com/sensu >> >> On Wed, Nov 12, 2014 at 12:47 PM, Tomasz Napierala <tnapier...@mirantis.com> >> wrote: >>> >>> >>> On 06 Nov 2014, at 12:20, Przemyslaw Kaminski <pkamin...@mirantis.com> >>> wrote: >>> >>>> I didn't mean a robust monitoring system, just something simpler. >>>> Notifications is a good idea for FuelWeb. >>> >>> I’m all for that, but if we add it, we need to document ways to clean up >>> space. >>> We could also add some kind of simple job to remove rotated logs, obsolete >>> spanshots, etc., but this is out of scope for 6.0 I guess. >>> >>> Regards, >>> -- >>> Tomasz 'Zen' Napierala >>> Sr. OpenStack Engineer >>> tnapier...@mirantis.com >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev