Emilien Macchi 72aa2dfc0a Create deployment/deprecated directory
It's not easy to find which services are deprecated, so let's create a
directory: deployment/deprecated and put the services in there.

This patch:
- creates the directory and a README
- moves already deprecated services into that directory
- update all references to these services to point to the right files

Change-Id: Id6c927d9c0db024875032f04228047d029c0696d
2019-02-20 16:57:58 -05: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-15 12:53:15 -07: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)