Michele Baldessari 79eddd1552 Be able to know when we are running inside a minor update workflow ... With this change we add an ansible variable called 'tripleo_minor_update' set to true only during the update_steps_playbook which get run during a minor update. Then inside common/deploy-steps-tasks when starting containers with paunch we export this 'tripleo_minor_update' ansible variable and push it inside the 'TRIPLEO_MINOR_UPDATE' environment variable. Inside change Id1d671506d3ec827bc311b47d9363952e1239ce3 we will then use the env variable and export it to the restart_bundles in order to detect if we're inside a minor update workflow (as opposed to a redeploy - aka stack update). The testing that has been done is described in the above change. Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com> Related-Bug: #1823849 NB: Cherry-pick not 100% clean due to missing Ia630f08f553bd53656c76e5c8059f15d314a17c0 and other missing reviews Change-Id: Ib3562adbd83f7162c2aeb450329b7cc4ab200fc2 (cherry picked from commit 7133394c35)		2019-04-09 12:04:44 +02:00
..
deploy-steps-tasks.yaml	Be able to know when we are running inside a minor update workflow	2019-04-09 12:04:44 +02:00
deploy-steps.j2	Be able to know when we are running inside a minor update workflow	2019-04-09 12:04:44 +02:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00
services.yaml	Move cellv2 discovery from control plane services to compute services	2019-03-06 11:01:33 +05:30