Steven Hardy 87b16ddbfc run docker_puppet_tasks on any role ... Currently this assumes all tasks will run on the primary controller but because of composable roles, that may not be the case. An example is if you deploy keystone on any role other than the role tagged primary e.g Controller by default, we don't create any of the users/endpoints because the tasks aren't written to the role unless keystone actually runs there. Conflicts: common/deploy-steps-tasks.yaml Closes-Bug: #1792613 Change-Id: Ib6efd03584c95ed4ab997f614aa3178b01877b8c (cherry picked from commit a0a09d29aa)		2019-02-11 09:57:57 +00:00
..
deploy-steps-tasks.yaml	run docker_puppet_tasks on any role	2019-02-11 09:57:57 +00:00
deploy-steps.j2	Stop upgrade if a task on one node fails	2018-11-27 15:16:28 +01:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00
services.yaml	run docker_puppet_tasks on any role	2019-02-11 09:57:57 +00:00