Bug 1471839 - [RFE] Heat template for monitoring is restricted to 1 host
[RFE] Heat template for monitoring is restricted to 1 host
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
10.0 (Newton)
Unspecified Unspecified
medium Severity medium
: Upstream M1
: 13.0 (Queens)
Assigned To: Martin Magr
Leonid Natapov
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-17 10:15 EDT by Robin Cernin
Modified: 2018-03-15 09:09 EDT (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180103192339.d05b39d.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1714910 None None None 2017-09-04 05:18 EDT
OpenStack gerrit 495149 None None None 2017-08-18 06:43 EDT

  None (edit)
Description Robin Cernin 2017-07-17 10:15:05 EDT
TripleO affected templates:


We do not allow multiple servers to be specified in those environment files.

We are looking for MonitoringRabbitHost server redundancy.

Templates example:

  #### Sensu settings ####
  MonitoringRabbitPort: 5672
  MonitoringRabbitUserName: sensu
  MonitoringRabbitPassword: sensu
  MonitoringRabbitUseSSL: false
  MonitoringRabbitVhost: "/sensu"
Comment 1 Martin Magr 2017-07-19 04:56:20 EDT
Hey Robin, so affected template is /usr/share/openstack-tripleo-heat-templates/environments/monitoring-environment.yaml, correct? I'm asking because MonitoringRabbit* parameters are not part of collectd-environment.yaml or logging-environment.yaml. I'm gonna check if sensu puppet module supports multiple rabbitmq host already. If yes, the you should be able to provide multiple host already. If not, we will have to implement this feature. Please stay tuned.
Comment 2 Robin Cernin 2017-07-19 05:07:46 EDT
Hi, yes sorry ffix it in the monitoring-environment.yaml.
Comment 3 Martin Magr 2017-07-19 05:11:41 EDT
So bad new is that the currently used parameter is not supporting multiple RabbitMQ hosts. The good new is that there is rabbitmq_cluster parameter implemented already in the puppet module, so the change will be required only on the level of tripleo-heat-templates.
Comment 17 Leonid Natapov 2018-03-15 09:09:00 EDT
Was able to deploy with MonitoringRabbitCluster configuration.

Tested with 2 rabbit cluster nodes. Did sensu sanity with rabbit cluster. Looks ok.


Note You need to log in before you can comment on or make changes to this bug.