Only run the VIP creation code when enable_load_balancer is set to true
When we use an external loadbalancer we do not want neither haproxy nor
VIPs on our control plane, since they will be managed externally.
So a user will usually include something like the following template:
/usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml
or implement a similar set of parameters/resource mapping.
The main needed params are: EnableLoadBalancer set to false, the
noop-ing of the haproxy service via 'OS::TripleO::Services::HAproxy: OS::Heat::None'
and the hard-coding of the external VIPs via the *VirtualFixedIPs
parameters.
To make sure we do not create the OVNDbs VIP we will use
the listen_on_master_ip_only as the variable to
determine if an external loadbalancer is used:
- no -> external LB used
- yes -> pcmk+haproxy i.e. our own loadbalancer
We cannot use the enable_load_balancer hiera key that is normally
set by haproxy, because the haproxy service will be nooped.
NB: cherry-pick is not clean due to context
Related-Bug: #1864409
(cherry picked from commit 50c5e1e6a52798ecebd35c3a1892573ec454061b)
Reviewed: https:/ /review. opendev. org/727946 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=8cf3793626f 90c4a982cdf884f 83722cd1563337
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 8cf3793626f90c4 a982cdf884f8372 2cd1563337
Author: Michele Baldessari <email address hidden>
Date: Thu May 14 09:06:22 2020 +0200
Only run the VIP creation code when enable_ load_balancer is set to true
When we use an external loadbalancer we do not want neither haproxy nor
VIPs on our control plane, since they will be managed externally.
So a user will usually include something like the following template: share/openstack -tripleo- heat-templates/ environments/ external- loadbalancer- vip.yaml :Services: :HAproxy: OS::Heat::None'
/usr/
or implement a similar set of parameters/resource mapping.
The main needed params are: EnableLoadBalancer set to false, the
noop-ing of the haproxy service via 'OS::TripleO:
and the hard-coding of the external VIPs via the *VirtualFixedIPs
parameters.
To make sure we do not create the OVNDbs VIP we will use on_master_ ip_only as the variable to
the listen_
determine if an external loadbalancer is used:
- no -> external LB used
- yes -> pcmk+haproxy i.e. our own loadbalancer
We cannot use the enable_ load_balancer hiera key that is normally
set by haproxy, because the haproxy service will be nooped.
NB: cherry-pick is not clean due to context
Related-Bug: #1864409 cebd35c3a189257 3ec454061b)
(cherry picked from commit 50c5e1e6a52798e
Change-Id: Ie313c0410ed684 661aeea77158572 035ddfcfcd5