3238e547a6
This change combines the previous puppet and docker files into a single file that performs the docker service installation and configuration for the horizon service. With this patch the baremetal version of each respective horizon service has been removed. Change-Id: I132465a32cd9f5e094ed184a92549d6521ad4e64 Related-Blueprint: services-yaml-flattening |
||
---|---|---|
.. | ||
aodh | ||
cinder | ||
congress | ||
database | ||
docker | ||
etcd | ||
glance | ||
haproxy | ||
heat | ||
horizon | ||
ironic | ||
iscsid | ||
keepalived | ||
kernel | ||
keystone | ||
login-defs | ||
memcached | ||
mistral | ||
multipathd | ||
neutron | ||
panko | ||
podman | ||
sahara | ||
securetty | ||
selinux | ||
snmp | ||
sshd | ||
swift | ||
tacker | ||
time | ||
timesync | ||
tripleo-firewall | ||
tripleo-packages | ||
tuned | ||
zaqar | ||
README.rst |
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)