Fix conflict between OpenStack and Telemetry VIP
In production deployments, OpenStack and Telemetry VIP addresses are
located on different clusters. This isn't the case here which leads to
duplicate entries for the same address in the keepalived configuration.
This change fixes this problem by allocating a new address for the
Telemetry cluster.
Change-Id: I663b93995f4426fa5d828cb135e1da57d0e320ca
diff --git a/classes/cluster/virtual-mcp11-contrail/openstack/control.yml b/classes/cluster/virtual-mcp11-contrail/openstack/control.yml
index 8ad024a..2887191 100755
--- a/classes/cluster/virtual-mcp11-contrail/openstack/control.yml
+++ b/classes/cluster/virtual-mcp11-contrail/openstack/control.yml
@@ -45,6 +45,7 @@
parameters:
_param:
keepalived_vip_interface: ens4
+ keepalived_openstack_telemetry_vip_address: 172.16.10.252
cluster_vip_address: ${_param:openstack_control_address}
cluster_local_address: ${_param:single_address}
cluster_node01_hostname: ctl01