History

Zuul 0b5de70375 Merge "flatten snmp service configuration"		2018-12-30 00:34:39 +00:00
..
aodh	Merge "Fix service naming conventions"	2018-12-15 02:43:28 +00:00
glance	The monitoring_subscription was lost in translation	2018-12-21 23:42:51 +00:00
ironic	Flatten Ironic services configuration	2018-12-14 07:25:13 +01:00
keepalived	Flatten Keepalived service configuration	2018-12-13 10:26:26 -05:00
memcached	flatten memcached service configuration	2018-12-14 12:06:53 -05:00
podman	Move podman into deployment directory	2018-12-17 11:37:19 +00:00
snmp	flatten snmp service configuration	2018-12-14 13:09:34 -05:00
timesync	Fix service naming conventions	2018-12-13 08:12:36 -07:00
tripleo-firewall	flatten tripleo-firewall service configuration	2018-12-14 13:16:34 -05:00
tuned	flatten tuned service configuration	2018-12-14 13:13:40 -05: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)