diff options
| author |   Michele Baldessari <michele@acksyn.org> | 2017-02-28 16:37:07 +0100 |
|---|---|---|
| committer |   Emilien Macchi <emilien@redhat.com> | 2017-03-02 12:38:24 +0000 |
| commit | 16c4cd610da54138ea2c29516023670d8ad19a75 (patch) | |
| tree | 891fda40a8a6eed0a72420d89f97550d8cf5156e /firstboot/userdata_example.yaml | |
| parent | 34caceed84675663f553f4da9191eb0710cc0c70 (diff) | |
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
(cherry picked from commit 41514d0cd603194fecb327f96995c60a9fe6e67a)
Diffstat (limited to 'firstboot/userdata_example.yaml')
0 files changed, 0 insertions, 0 deletions