[openstack-dev] [Fuel] fuel master monitoring

Jay Pipes jaypipes at gmail.com
Wed Nov 26 18:15:48 UTC 2014


On 11/26/2014 11:54 AM, Sergii Golovatiuk wrote:
> Jay,
>
> Fuel uses watchdog service for container to restart it in case of
> issues. We have the same problem with containers when disk is full

I see. I guess I don't quite understand why Zabbix isn't just used for 
everything -- after all, the puppet manifests already exist for it and 
are used for monitoring other things apparently.

-jay

> On Wed, Nov 26, 2014 at 4:39 PM, Jay Pipes <jaypipes at gmail.com
> <mailto:jaypipes at gmail.com>> wrote:
>
>     On 11/26/2014 10:22 AM, Przemyslaw Kaminski wrote:
>
>         We want to monitor Fuel master node while Zabbix is only on
>         slave nodes
>         and not on master. The monitoring service is supposed to be
>         installed on
>         Fuel master host (not inside a Docker container) and provide
>         basic info
>         about free disk space, etc.
>
>
>     Why not use the same thing for monitoring the Fuel master host as we
>     do for the docker containers/cluster?
>
>
>         P.
>
>         On 11/26/2014 02:58 PM, Jay Pipes wrote:
>
>             On 11/26/2014 08:18 AM, Fox, Kevin M wrote:
>
>                 So then in the end, there will be 3 monitoring systems
>                 to learn,
>                 configure, and debug? Monasca for cloud users, zabbix
>                 for most of the
>                 physical systems, and sensu or monit "to be small"?
>
>                 Seems very complicated.
>
>                 If not just monasca, why not the zabbix thats already
>                 being deployed?
>
>
>             Yes, I had the same thoughts... why not just use zabbix
>             since it's
>             used already?
>
>             Best,
>             -jay
>
>             _________________________________________________
>             OpenStack-dev mailing list
>             OpenStack-dev at lists.openstack.__org
>             <mailto:OpenStack-dev at lists.openstack.org>
>             http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev
>             <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>         _________________________________________________
>         OpenStack-dev mailing list
>         OpenStack-dev at lists.openstack.__org
>         <mailto:OpenStack-dev at lists.openstack.org>
>         http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev
>         <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>     _________________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.__org
>     <mailto:OpenStack-dev at lists.openstack.org>
>     http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



More information about the OpenStack-dev mailing list