tripleo-heat-templates/puppet/compute-config.yaml
Steven Hardy 54a0286106 Move role deployment steps into puppet/post.yaml
To enable steps to be aligned between roles, we need to define
dependencies between the steps, which is only possible if we
move the steps out of distinct nested stacks so we can use
depends_on to serialized the steps for all roles.

Note that we may be able to further refactor later to remove the
per-role -config.yaml nested stacks as well.

Change-Id: Ia2ea559e8eeb64763908f75705e3728ee90b5744
Partially-Implements: blueprint custom-roles
2016-09-09 11:04:12 +01:00

39 lines
1.0 KiB
YAML

heat_template_version: 2015-04-30
description: >
A software config which runs manifests/overcloud_compute.pp
parameters:
ConfigDebug:
default: false
description: Whether to run config management (e.g. Puppet) in debug mode.
type: boolean
StepConfig:
type: string
description: Config manifests that will be used to step through the deployment.
default: ''
resources:
ComputePuppetConfigImpl:
type: OS::Heat::SoftwareConfig
properties:
group: puppet
options:
enable_debug: {get_param: ConfigDebug}
enable_hiera: True
enable_facter: False
modulepath: /etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules
outputs:
- name: result
config:
list_join:
- ''
- - get_file: manifests/overcloud_compute.pp
- {get_param: StepConfig}
outputs:
OS::stack_id:
description: The software config which runs overcloud_controller.pp
value: {get_resource: ComputePuppetConfigImpl}