History

Zuul 4d617a85ed Merge "Allow ssh from all for undercloud"		2019-01-21 16:10:16 +00:00
..
aodh	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
cinder	flatten cinder service configuration	2019-01-18 08:55:26 -05:00
docker	Move docker into deployment directory	2019-01-09 22:58:50 +00:00
glance	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
heat	flatten the heat service configurations	2019-01-13 10:03:55 -05:00
ironic	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
keepalived	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
keystone	Drop duplicate keystone logging group parameter	2019-01-16 10:01:50 -05:00
memcached	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
podman	Move podman into deployment directory	2018-12-17 11:37:19 +00:00
sahara	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01:00
snmp	Snmp - Use net_cidr_map for firewall rules	2019-01-06 18:21:54 +01:00
sshd	Allow ssh from all for undercloud	2019-01-18 11:14:12 -07:00
time	flatten time service configuration	2018-12-18 10:41:15 -05:00
timesync	Fix service naming conventions	2018-12-13 08:12:36 -07:00
tripleo-firewall	implement default ssh-from-ctlplane rule via hiera	2018-12-19 07:59:28 -07:00
tripleo-packages	flatten tripleo-packages service configuration	2018-12-19 09:24:49 -05:00
tuned	flatten tuned service configuration	2018-12-14 13:13:40 -05:00
zaqar	Ensure logs folder is created in prep hosts tasks.	2019-01-18 09:28:56 +01: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)