Fix priority parameters for VIP instances
Prior this change, all Keepalived instances (except for OpenStack VIP)
had the same priority which leads to unpredictable master elections.
Change-Id: Ifdc468b83f904b36489830678e550fc82c206985
diff --git a/reclass/storage/system/openstack_telemetry_cluster.yml b/reclass/storage/system/openstack_telemetry_cluster.yml
index d184fc9..986ed61 100644
--- a/reclass/storage/system/openstack_telemetry_cluster.yml
+++ b/reclass/storage/system/openstack_telemetry_cluster.yml
@@ -15,7 +15,7 @@
salt_master_host: ${_param:reclass_config_master}
linux_system_codename: trusty
single_address: ${_param:openstack_telemetry_node01_address}
- keepalived_vip_priority: 103
+ keepalived_openstack_telemetry_vip_priority: 103
openstack_telemetry_node02:
name: ${_param:openstack_telemetry_node02_hostname}
domain: ${_param:cluster_domain}
@@ -25,7 +25,7 @@
salt_master_host: ${_param:reclass_config_master}
linux_system_codename: trusty
single_address: ${_param:openstack_telemetry_node02_address}
- keepalived_vip_priority: 102
+ keepalived_openstack_telemetry_vip_priority: 102
openstack_telemetry_node03:
name: ${_param:openstack_telemetry_node03_hostname}
domain: ${_param:cluster_domain}
@@ -35,4 +35,4 @@
salt_master_host: ${_param:reclass_config_master}
linux_system_codename: trusty
single_address: ${_param:openstack_telemetry_node03_address}
- keepalived_vip_priority: 101
+ keepalived_openstack_telemetry_vip_priority: 101