Split out BootstrapNode SoftwareConfig

This patch splits out the BootstrapNode config
such that alternate implementation (puppet for example)
can implement their own SoftwareConfig's via a nested stack.

This is controlled by the standard overcloud heat environment.

For os-apply-config deployments the implementation should work the
same as before.

For puppet deployments the implementation uses hiera metadata
to configure bootstrap_nodeid.

Change-Id: I691a9d7c474866038a5d47beab295899b5479d03

1 files changed, 21 insertions, 0 deletions

diff --git a/bootstrap-config.yaml b/bootstrap-config.yaml
new file mode 100644
index 00000000..14ecc005
--- /dev/null
+++ b/bootstrap-config.yaml
@@ -0,0 +1,21 @@
+heat_template_version: 2014-10-16
+description: 'Bootstrap Config'
+
+parameters:
+  bootstrap_nodeid:
+    type: string
+
+resources:
+
+  BootstrapNodeConfigImpl:
+    type: OS::Heat::StructuredConfig
+    properties:
+      config:
+        bootstrap_host:
+          bootstrap_nodeid: {get_param: bootstrap_nodeid}
+
+outputs:
+  config_id:
+    description: The ID of the BootstrapNodeConfigImpl resource.
+    value:
+      {get_resource: BootstrapNodeConfigImpl}