tripleo-heat-templates/deployment/rabbitmq
Jiri Stransky d4db2fa532 Force re-run of pacemaker bundle init containers during upgrade-scaleup
We need to recreate the *_init_bundle containers during the staged
upgrade (upgrade-scaleup), because the init containers will e.g. set
the correct replica count for the bundle as we're scaling up from 1 to
3 controllers.

The init containers wouldn't get re-run/recreated automatically on
upgrade-scaleup because none of their input would change. The
DeploymentIdentifier is set by the `openstack upgrade prepare` command
and applied during upgrade with `--limit controller-0`. Then later
when we run `--limit controller-0,controller-1`, the
DeploymentIdentifier value does not change from the perspective of
controller-0, so we have to explicitly remove the bundle init
containers to force re-running them.

Change-Id: I93c6d7292f37529735e24286f4076634aa4fe6a5
Partial-Bug: #1831690
2019-08-13 13:59:44 +02:00
..
rabbitmq-container-puppet.yaml Force removal of docker container in tripleo-docker-rm. 2019-07-19 12:37:35 +00:00
rabbitmq-messaging-notify-container-puppet.yaml Force removal of docker container in tripleo-docker-rm. 2019-07-19 12:37:35 +00:00
rabbitmq-messaging-notify-pacemaker-puppet.yaml Force re-run of pacemaker bundle init containers during upgrade-scaleup 2019-08-13 13:59:44 +02:00
rabbitmq-messaging-notify-shared-puppet.yaml Move containers-common.yaml into deployment 2019-04-14 18:15:12 -04:00
rabbitmq-messaging-pacemaker-puppet.yaml Force re-run of pacemaker bundle init containers during upgrade-scaleup 2019-08-13 13:59:44 +02:00
rabbitmq-messaging-rpc-container-puppet.yaml Force removal of docker container in tripleo-docker-rm. 2019-07-19 12:37:35 +00:00
rabbitmq-messaging-rpc-pacemaker-puppet.yaml Force re-run of pacemaker bundle init containers during upgrade-scaleup 2019-08-13 13:59:44 +02:00