This service is mapped to OS::Heat::None by default, but when enabled,
it uses external deploy tasks to create a new aggregate and zone in
Nova. All Compute nodes in the stack will be added to the zone by
default.
The zone name is the stack name by default, but can be overridden with
parameter values.
Change-Id: I0afb2265949f1222a86b350734e62da673e83aa9
Depends-On:I064f872e20537642880d5482cb9e0c2a801715ef
implements: blueprint split-controlplane-templates
This directory contains files that represent individual service
deployments, orchestration tools, and the configuration tools used to
deploy them.
Directory Structure
Each logical grouping of services will have a directory. Example:
'timesync'. Within this directory related timesync services would exist
to for example configure timesync services on baremetal or via
containers.
Filenaming conventions
As a convention each deployments service filename will reflect both
the deployment engine (baremetal, or containers) along with the config
tool used to deploy that service.
The convention is <service-name>-<engine>-<config
management tool>.
Examples:
deployment/aodh/aodh-api-container-puppet.yaml (containerized Aodh
service configured with Puppet)
deployment/aodh/aodh-api-container-ansible.yaml (containerized Aodh
service configured with Ansible)
deployment/timesync/chrony-baremetal-ansible.yaml (baremetal Chrony
service configured with Ansible)
deployment/timesync/chrony-baremetal-puppet.yaml (baremetal Chrony
service configured with Puppet)
0df81abe8e