tripleo-heat-templates/puppet/services/services.yaml
Dan Prince 0bcf693a73 Configure ControllerServices via resource chains
This patch wires in a new for Mitaka Heat feature
that allows us to dynamically include a set of nested
stacks representing individual services via a Heat resource chain.
Follow on patches will use this interface to decompose the controller
role into isolated services.

Co-Authored-By: Steve Hardy <shardy@redhat.com>
Depends-On: If510abe260ea7852dfe2d1f7f92b529979483068
Change-Id: I84c97a76159704c2d6c963bc4b26e365764b1366
2016-03-31 16:09:17 -04:00

41 lines
1.1 KiB
YAML

heat_template_version: 2016-04-08
description: >
Utility stack to convert an array of services into a set of combined
role configs.
parameters:
Services:
default: []
description: |
List nested stack service templates.
type: comma_delimited_list
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
MysqlVirtualIPUri:
default: ''
type: string
description: The URI virtual IP for the MySQL service.
resources:
ServiceChain:
type: OS::Heat::ResourceChain
properties:
resources: {get_param: Services}
concurrent: true
resource_properties:
EndpointMap: {get_param: EndpointMap}
MysqlVirtualIPUri: {get_param: MysqlVirtualIPUri}
outputs:
config_settings:
description: Configuration settings.
value: {map_merge: {get_attr: [ServiceChain, role_data, config_settings]}}
step_config:
description: Step configuration.
value: {list_join: ["\n", {get_attr: [ServiceChain, role_data, step_config]}]}