Zabbix not deployed on existing nodes

[Claude Durocher]

Environment:

Fuel 5.1 community deployed on Ubuntu.

Problem:

If Zabbix is deployed after the 'original environment deployment', existing nodes are not monitored by Zabbix. New nodes will be added correctly to Zabbix however.

Expected behaviour:

-documentation should reflect this fact
-there should be a documented way to add existing nodes to Zabbix

[Tomasz 'Zen' Napierala (tzn)]

This is indeed missing, thank you for reporting

[Vladimir Kuklin (vkuklin)]

This issue is related to granular deployment - we can trigger zabbix role installation again after we implement granular deployment and separate zabbix-agent tasks

[Vladimir Kuklin (vkuklin)]

No as we have zabbix roles installed separately, let's run these tasks after we add zabbix-server - reassigning it to python team

[Oleksiy Molchanov (omolchanov)]

I am passing it to Zabbix team, as they owns this plugin.

[Dmitry Pyzhov (dpyzhov)]

Zabbix has been moved to plugin. And in 7.0 we have a https://blueprints.launchpad.net/fuel/+spec/role-as-a-plugin feature. So this bug can be fixed on the plugin side.

[Piotr Misiak (piotr-misiak)]

In 6.1 and in 7.0, plugin framework do not allow to enable plugin in an already deployed environment so your use case in invalid for the Zabbix plugin.