openstack/tripleo-heat-templates
Code Issues Proposed changes
e32663b1fe
tripleo-heat-templates/deployment
History
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
..
aodh Merge "Fix service naming conventions" 2018-12-15 02:43:28 +00:00
docker Move docker into deployment directory 2019-01-09 22:58:50 +00:00
glance Merge "Bind mount /var/lib/iscsi in containers using iSCSI" 2019-01-08 03:44:36 +00:00
ironic Add missing Ironic monitoring_subscription 2019-01-11 09:53:49 -05:00
keepalived Flatten Keepalived service configuration 2018-12-13 10:26:26 -05:00
keystone Set keystone bind_host to both public and admin 2019-01-10 15:44:38 +00:00
memcached Memcached - Use net_cidr_map for firewall rules 2019-01-06 18:21:21 +01:00
podman Move podman into deployment directory 2018-12-17 11:37:19 +00:00
snmp Snmp - Use net_cidr_map for firewall rules 2019-01-06 18:21:54 +01:00
sshd flatten sshd service configuration 2018-12-19 13:04:08 -05: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 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
zaqar Flatten Zaqar service configuration 2018-12-14 07:45:24 +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)