Cédric Jeanneret 9a36edb320 Ensure we get rsyslog state, even in "--check" mode
Introduced with Ia615ac07d0c559deb65e307bb6254127e989794d, an issue
can be hit when deploy is launched with dry-run mode.

Change-Id: I5851dc7820fdcc4f5790980d94b81622ce3b0c8d
Related-Bug: #1823841
2019-04-09 08:06:12 +02:00
..
2019-03-28 08:24:40 -04:00
2019-03-18 14:49:28 -04:00
2019-01-29 08:08:06 -05:00
2019-04-08 12:03:49 +00:00
2019-02-15 12:53:15 -07:00
2019-01-22 13:21:13 -07: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)