tripleo-heat-templates/puppet/bootstrap-config.yaml
Steven Hardy b1ae63bb11 Remove NO_SIGNAL from ControllerBootstrapNodeDeployment
We need to be sure the boostrap node data has been propagated to the
cluster before proceeding with configuration, because
ControllerNodesPostDeployment consumes the data put in place by this
and depends_on for serialization, which is essentially meaningless when
combined with NO_SIGNAL.

Change-Id: I73a1e5a2cda4c79f457bfbd9ce2836dc5c1902cc
2015-06-03 16:30:53 +02:00

29 lines
669 B
YAML

heat_template_version: 2015-04-30
description: 'Bootstrap Config Puppet'
parameters:
bootstrap_nodeid:
type: string
bootstrap_nodeid_ip:
type: string
resources:
BootstrapNodeConfigImpl:
type: OS::Heat::StructuredConfig
properties:
group: os-apply-config
config:
hiera:
datafiles:
bootstrap_node:
mapped_data:
bootstrap_nodeid: {get_param: bootstrap_nodeid}
bootstrap_nodeid_ip: {get_param: bootstrap_nodeid_ip}
outputs:
config_id:
description: The ID of the BootstrapNodeConfigImpl resource.
value:
{get_resource: BootstrapNodeConfigImpl}