c56cdc8dda
This adds support for an Instance HA deployment option which evacuates VMs after a compute node failure. To enable this feature just add -e environments/compute-instanceha.yaml and make sure the compute nodes have the OS::TripleO::Services::ComputeInstanceHA and the OS::TripleO::Services::PacemakerRemote services added to it. Testing has been done as follows: 1) Deploy an overcloud with Instance HA 2) Create a VM on the overcloud 3) Crash a compute node 4) Observe that the nova evacuate resource agent initiates the nova evacuation: Nov 29 10:39:49 localhost NovaEvacuate(nova-evacuate)[32253]: NOTICE: Initiating evacuation of overcloud-novacompute-0.localdomain with fence_evacuate Nov 29 10:39:57 localhost NovaEvacuate(nova-evacuate)[32253]: NOTICE: Completed evacuation of overcloud-novacompute-0.localdomain 5) Observe the VM having been started on the functional compute node A documentation patch will follow explaining the whole mechanism more in detail. blueprint instance-ha Depends-On: I4d1908242e9513a225d2b1da06ed4ee769ee10f7 Change-Id: If6c7d6c56eca96bd64ac5936036d119bd9ec6226
10 lines
363 B
YAML
10 lines
363 B
YAML
# An environment which enables instance HA
|
|
# Needs to be combined with environments/puppet-pacemaker.yaml
|
|
# The ComputeInstanceHA *and* PacemakerRemote services need to be added
|
|
# to your Compute role
|
|
resource_registry:
|
|
OS::TripleO::Services::ComputeInstanceHA: ../puppet/services/pacemaker/compute-instanceha.yaml
|
|
|
|
parameter_defaults:
|
|
EnableInstanceHA: true
|