Pacemaker maintenance mode for the duration of Puppet run on update
authorSteven Hardy <shardy@redhat.com>
Fri, 13 Nov 2015 11:18:50 +0000 (11:18 +0000)
committerJiri Stransky <jistr@redhat.com>
Mon, 14 Dec 2015 13:24:13 +0000 (14:24 +0100)
commitea1294fe9b11029edab719e8bf558733226b3fd4
treead104cd5ccf8e14ae8f3be445a87c9d46d4aa8d4
parent5a6907f2b829f34daa5f2d9d9cd69de35a1b9c56
Pacemaker maintenance mode for the duration of Puppet run on update

This enables pacemaker maintenantce mode when running Puppet on stack
update. Puppet can try to restart some overcloud services, which
pacemaker tries to prevent, and this can result in a failed Puppet run.

At the end of the puppet run, certain pacemaker resources are restarted
in an additional SoftwareDeployment to make sure that any config changes
have been fully applied. This is only done on stack updates (when
UpdateIdentifier is set to something), because the assumption is that on
stack create services already come up with the correct config.

(Change I9556085424fa3008d7f596578b58e7c33a336f75 has been squashed into
this one.)

Change-Id: I4d40358c511fc1f95b78a859e943082aaea17899
Co-Authored-By: Jiri Stransky <jistr@redhat.com>
Co-Authored-By: James Slagle <jslagle@redhat.com>
environments/puppet-pacemaker.yaml
extraconfig/tasks/noop.yaml [new file with mode: 0644]
extraconfig/tasks/pacemaker_resource_restart.sh [new file with mode: 0755]
extraconfig/tasks/post_puppet_pacemaker.yaml [new file with mode: 0644]
extraconfig/tasks/pre_puppet_pacemaker.yaml [new file with mode: 0644]
overcloud-resource-registry-puppet.yaml
overcloud.yaml
puppet/all-nodes-config.yaml
puppet/controller-post.yaml