Zabbix should be located on the separate nodes

Bug #1581693 reported by Andrey Epifanov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel Plugins
Confirmed
Critical
Unassigned
Nominated for 6.1 by Andrey Epifanov
Nominated for 7.0 by Andrey Epifanov
Nominated for 8.0 by Andrey Epifanov
Nominated for 9.0 by Andrey Epifanov
Nominated for Trunk by Andrey Epifanov

Bug Description

MOS: 6.1/7.0/8.0
Plugins: Zabbix

Zabbix is placed on the controllers and therefore consumes resources(cpu/disk size/db size) and can impact on the cloud stability.
I would strongly recommend to move it out on the separate nodes since(restrict to deploy on controllers and use OpenStack DB) it is not a critical component of cloud and to reduce its impact on critical services.

The same issues:
https://bugs.launchpad.net/fuel-plugins/+bug/1531834

Changed in fuel-plugins:
status: New → Confirmed
importance: Undecided → High
tags: added: customer found support
tags: removed: customer found
tags: added: customer-found
Revision history for this message
Simon Pasquier (simon-pasquier) wrote :

I understand your point but IMO this is a more a feature request than a bug.

Changed in fuel-plugins:
importance: High → Wishlist
tags: added: ct1
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Simon, having amount of customers, whos production was broken with this issue, I'd suggest plugins team will start working on it immediately and for all previous versions too.

Revision history for this message
Roman Rufanov (rrufanov) wrote :

Customer found issue on 6.1 resulting in cloud down situation. Please resolve and backport. Please provide instruction how to move Zabbix out of controllers in exiting environments.

Changed in fuel-plugins:
importance: Wishlist → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.