openstack/tripleo-heat-templates
Code Issues Proposed changes
bcf80d474a
tripleo-heat-templates/deployment
History
Dan Prince bcf80d474a Add deployments/README.rst 
To help clarify current and future naming conventions in this directory.

Change-Id: Ib9d24f9844f5aecd47cdd6a47247562dce2092ee
Related-Blueprint: services-yaml-flattening
2018-12-13 10:25:09 -05:00
..
aodh upgrade: remove tasks that stop and disable services 2018-12-10 09:19:59 -05:00
timesync Specify multiple NtpServers by default 2018-12-04 08:31:55 -07:00
README.rst Add deployments/README.rst 2018-12-13 10:25:09 -05:00

README.rst

TripleO Deployments

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)