Dan Prince e32663b1fe Add missing Ironic monitoring_subscription
These got dropped in the service flattening patches.

Change-Id: Id0f5da6be5bd4f9c12ea9a2dfd18e64ace35f451
2019-01-11 09:53:49 -05:00
..
2018-12-19 13:04:08 -05:00
2018-12-18 10:41:15 -05:00
2018-12-13 08:12:36 -07:00
2018-12-14 13:13:40 -05:00
2018-12-14 07:45:24 +01:00
2018-12-13 10:25:09 -05:00

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)