Upgrades: fix up the rabbitmq HA mode like in new ocata deployments
authorMichele Baldessari <michele@acksyn.org>
Tue, 28 Feb 2017 15:37:07 +0000 (16:37 +0100)
committerMichele Baldessari <michele@acksyn.org>
Thu, 2 Mar 2017 07:46:54 +0000 (08:46 +0100)
commit41514d0cd603194fecb327f96995c60a9fe6e67a
tree52dcac77f66cd5355e7b09c5bf11038386a6ed63
parentb889a4b5b3be37ee1dabb60ddce519af84b15b22
Upgrades: fix up the rabbitmq HA mode like in new ocata deployments

In ocata we changed the rabbitmq ha policy to "ha-exactly" via the
following changes:
- tht: Iace6daf27a76cb8ef1050ada0de7ff1f530916c6
- puppet-tripleo: Ib62001c03e1e08f58cf0c6e0ba07a8879a584084

We took care of the upgrade path via I3a97505d2ae1ae27f3080ffe74c33fdabffd2420

With the move to the ansible-based composable upgrades we left this change out.
And now an upgraded environment has the following policy:
- Upgraded environment
Attributes: set_policy="ha-all ^(?!amq\.).* {"ha-mode":"all"}"

- New environment
Attributes: set_policy="ha-all ^(?!amq\.).* {"ha-mode":"exactly","ha-params":2}"

We need to add this pcs resource change to the our upgrade scripts.

Change-Id: I3c4113c207e9d0c45be43df7c2379ac26cb60692
Closes-Bug: #1668600
puppet/services/pacemaker/rabbitmq.yaml