By default, the Nagios dashboard is now exposed on the public network.
To change this configuration, the deployer will have to assign the
'infrastructure_alerting_ui' role to another network using Fuel netwowrk
templates.
DocImpact
Change-Id: I2e6bf12dc530af18a048c61adbb8da07c1156810
This change makes sure that Pacemaker is reconfigured on the nodes that
are already deployed when the environment is scaled up. We use the
'update_required' stanza to enforce that the nodes already deployed are
updated in the same run than the new nodes. The 'reexecute_on' stanza
doesn't guarantee that.
Change-Id: Id8ea87616fa3c9026462a41711732285624d9533
Closes-Bug: #1536533
Once the plugin deployment has completed, it uses the Fuel API to
register the Nagios URL. The end-users will get the information in
the Fuel UI.
This change also introduces the use of the primary role since only one
node should be responsible for notifying the Fuel API.
Change-Id: Ie5c2495b5bcbce4aec3d5dd2cae247884b231efe
This change configures a VIP address in the management subnet. It also
deploys a Corosync/Pacemaker cluster which is needed for the VIP
fail-over.
Change-Id: I13055ff714dffb893284f9163d3c501ded8b5e74
Implements: blueprint nagios-high-availability
Andreas Jaeger