
Many services currently set an `is_bootstrap_node` fact, meaning they override each other's results when the fact is being set. As long as the fact doesn't belong into a particular step but it's executed on every step, nothing bad happens, as the correct is_bootstrap_node setting directly precedes any service upgrade tasks. However, we intend to put the fact setting into step 0 in change Ib04b051e8f4275e06be0cafa81e2111c9cced9b7 and at that point the name collision would break upgrades (only one service would "win" in setting the is_bootstrap_node fact). This patch changes the is_bootstrap_node facts in upgrade_tasks to use per-service naming. Note that fast_forward_upgrade_tasks use their own is_boostrap_node logic. We've uncovered some weirdness there while looking into the is_boostrap_node issue, but the fix is not a low hanging fruit and likely we'll be completely redoing the FFU tasks for Q->T upgrade. So the FFU tasks are left alone for now. Change-Id: I9c585d3cb282b7e4eb0bacb3cf6909e04a9a495e Closes-Bug: #1810408
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)