tripleo-heat-templates/deployment/pacemaker
Damien Ciabrini 164fac75a0 minor update: only migrate HA VIP away when needed
When update tasks runs in a HA controller node, pacemaker is
stopped, along with all HA resources hosted on the node. If
any VIP is hosted on that node, it is moved to another node
prior to stopping pacemaker to limit service downtime.

If the HA controller node doesn't manage VIP (no HAProxy) or
the control plane only has 1 node, there is no need to try and
move VIP away before stopping pacemaker.

Tested on a 1-node HA control plane, and also on a control
plane with external balancer (no HAproxy service, thus no VIP
managed in pacemaker). The dedicated ansible task no longer
tries to move VIP if it doesn't need to.

Closes-Bug: #1892570
Change-Id: Id9b9c413ee37dcda422e69ebef4aca81e4877156
2020-08-22 11:11:19 +02:00
..
clustercheck-container-puppet.yaml Deprecate EnablePaunch and remove Paunch support 2020-06-03 17:53:40 +00:00
compute-instanceha-baremetal-puppet.yaml Use absolute name to include puppet classes 2020-04-11 08:13:23 +09:00
ovn-dbs-baremetal-puppet.yaml Use absolute name to include puppet classes 2020-04-11 08:13:23 +09:00
pacemaker-baremetal-puppet.yaml minor update: only migrate HA VIP away when needed 2020-08-22 11:11:19 +02:00
pacemaker-remote-baremetal-puppet.yaml pcmk_remote FFU support for Instance HA 2020-08-12 17:09:41 +02:00