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
Reviewed: https:/ /review. opendev. org/669847 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=176b30649b1 8f14818480ba3b6 a76cfcf9f3aa26
Committed: https:/
Submitter: Zuul
Branch: master
commit 176b30649b18f14 818480ba3b6a76c fcf9f3aa26
Author: Michele Baldessari <email address hidden>
Date: Wed Jul 24 08:57:36 2019 +0200
Give the OVN DBS service a separate Vip
This change (with its dependent reviews) creates a separate VIP for the OVN DBS /bugs.launchpad .net/tripleo/ +bug/1841811.
service. A more detailed explanation can be found in https:/
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: /metadata) pointing to this separate Vip
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
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: Ic62b0fbc0fee40 638811a5cd77a5d c5a4d82acf5 b51bf9e1eda91da eb00fdf0f43
Change-Id: I620e37117c26b5