In the same spirit as change I1f07272499b419079466cf9f395fb04a082099bd
we want to rerun all pacemaker _init_bundles all the time. For a few main
reasons:
1) We will eventually support scaling-up roles that contain pacemaker-managed services and we need to rerun _init_bundles so that
pacemaker properties are created for the newly added nodes.
2) When you replace a controller the pacemaker properties will be
recreated for the newly added node.
3) We need to create appropriate iptables rules whenever we add a
service to an existing deployment.
We do this by adding the DeployIdentifier to the environment so that
paunch will retrigger a run at every redeploy.
Reviewed: https:/ /review. openstack. org/567821 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=a0dfc6c0c69 4091eae195d4090 a63e339f3daa39
Committed: https:/
Submitter: Zuul
Branch: master
commit a0dfc6c0c694091 eae195d4090a63e 339f3daa39
Author: Michele Baldessari <email address hidden>
Date: Fri May 11 12:12:32 2018 +0200
rerun *_init_bundles all the time
In the same spirit as change I1f07272499b419 079466cf9f395fb 04a082099bd
pacemaker- managed services and we need to rerun _init_bundles so that
we want to rerun all pacemaker _init_bundles all the time. For a few main
reasons:
1) We will eventually support scaling-up roles that contain
pacemaker properties are created for the newly added nodes.
2) When you replace a controller the pacemaker properties will be
recreated for the newly added node.
3) We need to create appropriate iptables rules whenever we add a
service to an existing deployment.
We do this by adding the DeployIdentifier to the environment so that
paunch will retrigger a run at every redeploy.
Partial-Bug: #1775196 c7f4abc269b61b2 868bfbc9272
Change-Id: Ifd48d74507609f