Michele Baldessari b0e7008196 standalone/overcloud: enable the HA deployment by default ... With the HA NG work having landed, the impact of pacemaker is reduced and only very few core services are being managed by pacemaker. Since the HA deployments work just fine with a single node, it makes little sense to use the non-ha deployment as default any longer (Also because downstream we do the default to the HA deployment by default and this keeps confusing users). This patch does the following : * Remove Keepalived services from all CI scenarios running it. * Make sure all HA services deployed in CI run with Pacemaker. * Remove non HA containers so Pacemaker can bootstrap the new containers safely. * Before removing mysql container, create the clustercheck user and grant correct permissions to avoid bootstrap issues later when galera is spawned. * Disable HA on the minor update job, it seems to not working fine if only one controller is deployed. Depends-On: https://review.opendev.org/#/c/718759 Change-Id: I0f61016df6a9f07971c5eab51cc9674a1458c66f		2020-04-09 21:27:02 +00:00
..
tests	standalone/overcloud: enable the HA deployment by default	2020-04-09 21:27:02 +00:00
__init__.py	Sample environment generator	2017-06-12 15:02:50 -05:00
environment_generator.py	Merge "Trim whitespace in multi-line env descriptions"	2019-04-16 05:28:25 +00:00