[openstack-dev] [Fuel] fuel master monitoring

Fox, Kevin M Kevin.Fox at pnnl.gov
Mon Nov 24 19:36:48 UTC 2014

One of the selling points of tripleo is to reuse as much as possible from the cloud, to make it easier to deploy. While monasca may be more complicated, if it ends up being a component everyone learns, then its not as bad as needing to learn two different monitoring technologies. You could say the same thing cobbler vs ironic. the whole Ironic stack is much more complicated. But for an openstack admin, its easier since a lot of existing knowlege applies. Just something to consider.


From: Tomasz Napierala
Sent: Monday, November 24, 2014 6:42:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Fuel] fuel master monitoring

> On 24 Nov 2014, at 11:09, Sergii Golovatiuk <sgolovatiuk at mirantis.com> wrote:
> Hi,
> monasca looks overcomplicated for the purposes we need. Also it requires Kafka which is Java based transport protocol.
> I am proposing Sensu. It's architecture is tiny and elegant. Also it uses rabbitmq as transport so we won't need to introduce new protocol.

Do we really need such complicated stuff? Sensu is huge project, and it's footprint is quite large. Monit can alert using scripts, can we use it instead of API?

Tomasz 'Zen' Napierala
Sr. OpenStack Engineer
tnapierala at mirantis.com

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141124/27cfcc92/attachment.html>

More information about the OpenStack-dev mailing list