58b99bf5ee
During the upgrad of pacemaker managed services there is a temporary tagging of the existing container image to the newly image we are going to upgrade to. The input during this taggins is the container image id, in contrast to what is passed during deploy tasks, which is the image name with its tag. For that reason, we can't pull the image in these cases otherwise the role will fail as it can't find an image to pull from a container image id. Change-Id: I4fdd3a05465fa0318b4ec5c079d59f4dd80fa9f2 Closes-Bug: #1814104 |
||
|---|---|---|
| .. | ||
| aodh | ||
| cinder | ||
| congress | ||
| database | ||
| docker | ||
| etcd | ||
| glance | ||
| haproxy | ||
| heat | ||
| ironic | ||
| iscsid | ||
| keepalived | ||
| kernel | ||
| keystone | ||
| login-defs | ||
| manila | ||
| memcached | ||
| mistral | ||
| multipathd | ||
| neutron | ||
| nova | ||
| panko | ||
| podman | ||
| rabbitmq | ||
| 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)