f873e31f58
This strategy is to be used for the execution of deployment steps so
that tasks run on all hosts (up to # of workers) freely without locking
at each task. This is closer to what we had when Heat drove the
deployments as each of the software deployments would execute
simultaneously on all nodes at the same time.
This strategy does two important things for us:
1) Hosts execute their tasks freely with no dependencies on the other
hosts that are running the same tasks
2) Failures on any given host will not stop future tasks from
executing on other hosts, but will cause the overall playbook
execution to stop at the end of the "PLAY".
These specific things are how the previous deployment executed when Heat
was the driver of deployment actions. The nodes would fetch their list
of actions, execute and report back to status. Heat would fail the
deployment if any of the hosts failed to execute their work however a
failure on one host did not impact the other hosts. The TripleO
deployment framework already has the step concept in itself to allow
for the individual steps (1 through 5) to execute in a parallael on all
hosts at the same time. At the end of the "PLAY", ansible waits for all
nodes to complete before proceeding on to the next "PLAY". So Step 1 is
a "PLAY" followed by Step 2. If a failure occurs during Step 1 on any
host, we would not proceed to the Step 2 play.
Change-Id: Id921ed48a948211b9a90def4a4667d015ec11d2f
Team and repository tags
TripleO Ansible
TripleO Ansible project repository. Contains Ansible playbooks, roles, and plugins for use with TripleO.
Documentation for the project can be found at: https://docs.openstack.org/tripleo-ansible/latest/
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/tripleo-ansible/
The project source code repository is located at: https://opendev.org/openstack/tripleo-ansible/
The project home is at: https://launchpad.net/tripleo
The project bug tracker is located at: https://bugs.launchpad.net/tripleo