tripleo-heat-templates/deployment/heat
Carlos Camacho 8a9e8ae528 Stop services for unupgraded controllers
Before we start services on upgraded bootstrap
controller (usually controller-0), we need to
stop services on unupgraded controllers
(usually controller-1 and controller-2).

Also we need to move the mysql data transfer
to the step 2 as we need to first stop the
services.

Depends-On: I3c0580893aed5bda46d9104ffcee0f00cbabd9ee
Change-Id: Ib4af5b4a92b3b516b8e2fc1ae12c8d5abe40327f
(cherry picked from commit 08d1156fcc)
2019-07-16 15:24:04 +02:00
..
heat-api-cfn-container-puppet.yaml Stop services for unupgraded controllers 2019-07-16 15:24:04 +02:00
heat-api-cloudwatch-disabled-puppet.yaml flatten the heat service configurations 2019-01-13 10:03:55 -05:00
heat-api-container-puppet.yaml Stop services for unupgraded controllers 2019-07-16 15:24:04 +02:00
heat-base-puppet.yaml Deprecate messaging params replaced by global oslo params 2019-03-28 12:13:07 -06:00
heat-engine-container-puppet.yaml Stop services for unupgraded controllers 2019-07-16 15:24:04 +02:00