Open Stack

Bartosz,

It is obviously possible to install zabbix on the master nodes and put it
under pacemaker control. But it seems very strange for me to monitor
something with software located on the nodes that you are monitoring.

On Tue, Nov 25, 2014 at 4:21 PM, Bartosz Kupidura <bkupidura at mirantis.com>
wrote:

> Hello All,
>
> Im working on Zabbix implementation which include HA support.
>
> Zabbix server should be deployed on all controllers in HA mode.
>
> Currently we have dedicated role 'zabbix-server', which does not support
> more
> than one zabbix-server. Instead of this we will move monitoring solution
> (zabbix),
> as an additional component.
>
> We will introduce additional role 'zabbix-monitoring', assigned to all
> servers with
> lowest priority in serializer (run puppet after every other roles) when
> zabbix is
> enabled.
> 'Zabbix-monitoring' role will be assigned automatically.
>
> When zabbix component is enabled, we will install zabbix-server on all
> controllers
> in active-backup mode (pacemaker+haproxy).
>
> In next stage, we can allow users to deploy zabbix-server on dedicated
> node OR
> on controllers for performance reasons.
> But for now we should force zabbix-server to be deployed on controllers.
>
> BP is in initial phase, but code is ready and working with Fuel 5.1.
> Now im checking if it works with master.
>
> Any comments are welcome!
>
> BP link: https://blueprints.launchpad.net/fuel/+spec/zabbix-ha
>
> Best Regards,
> Bartosz Kupidura
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141125/eb3fd91b/attachment.html>