Michele Baldessari 176b30649b Give the OVN DBS service a separate Vip ... This change (with its dependent reviews) creates a separate VIP for the OVN DBS service. A more detailed explanation can be found in https://bugs.launchpad.net/tripleo/+bug/1841811. The short explanation is that the OVN DBS HA service puts some additional constraints on the VIP it uses and that is problematic when that VIP is used by other services (e.g. a change in OVN DBS master will move the VIP and will also reset all mysql connections. It also prevents us splitting OVN DBS from where haproxy runs). Tested as follows: A) Deployed a mster environment with this review and all its dependencies and correctly obtained an OVN DBS service with its own Vip and the OVN services (controller/metadata) pointing to this separate Vip B) Deployed a master environment as is and then applied this review + dependencies and observed that a redeploy correctly created a new VIP, reconfigured the services to point to the new VIP and that the old obsolete constraints created around the per-network VIP were removed Closes-Bug: #1841811 Depends-On: Ic62b0fbc0fee40638811a5cd77a5dc5a4d82acf5 Change-Id: I620e37117c26b5b51bf9e1eda91daeb00fdf0f43		2019-09-23 13:05:39 +00:00
..
ovn-controller-container-puppet.yaml	Revert Add OvnDbInternal to EndpointMap and use it for ovn_db_host	2019-09-12 11:55:59 +00:00
ovn-dbs-container-puppet.yaml	Correct SELinux type for host openvswitch logs	2019-09-05 14:02:24 +02:00
ovn-dbs-pacemaker-puppet.yaml	Give the OVN DBS service a separate Vip	2019-09-23 13:05:39 +00:00
ovn-metadata-container-puppet.yaml	Revert Add OvnDbInternal to EndpointMap and use it for ovn_db_host	2019-09-12 11:55:59 +00:00