Puppet: Split out controller pacemaker manifest

This patch adds support for using the Heat resource registry
so that end users can enable pacemaker. Using this approach
allows us to isolate all of the pacemaker logic for the
controller in a single template rather than use conditionals
for every service that must support it.

Change-Id: Ibefb80d0d8f98404133e4c31cf078d729b64dac3

1 files changed, 23 insertions, 0 deletions

diff --git a/puppet/controller-config-pacemaker.yaml b/puppet/controller-config-pacemaker.yaml
new file mode 100644
index 00000000..4cec83a2
--- /dev/null
+++ b/puppet/controller-config-pacemaker.yaml
@@ -0,0 +1,23 @@
+heat_template_version: 2014-10-16
+
+description: >
+  A software config which runs manifests/overcloud_controller_pacemaker.pp
+
+resources:
+
+  ControllerPuppetConfigImpl:
+    type: OS::Heat::SoftwareConfig
+    properties:
+      group: puppet
+      options:
+        enable_hiera: True
+        enable_facter: False
+      outputs:
+      - name: result
+      config:
+        get_file: manifests/overcloud_controller_pacemaker.pp
+
+outputs:
+  OS::stack_id:
+    description: The software config which runs overcloud_controller_pacemaker.pp
+    value: {get_resource: ControllerPuppetConfigImpl}