Cédric Jeanneret c9adaaeb2f Flatten rabbitmq service - step 2
Now that we could get rid of the puppet dedicated definitions,
we can move the docker/* rabbitmq related stuff to the final
location, and correct the paths and some nits.

Change-Id: I47ca1e303bd38642200ccb7f6823bcd06cd00255
2019-02-06 12:50:51 +01:00
..
2019-02-01 10:02:10 -05:00
2019-01-22 14:09:02 -07:00
2019-01-29 08:08:06 -05:00
2019-02-01 10:01:32 -05:00
2019-01-22 13:21:13 -07:00
2019-02-01 10:00:25 -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-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)