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/keepalived/cluster/instance/stacklight_log_vip.yml b/keepalived/cluster/instance/stacklight_log_vip.yml
index caa6754..1a36121 100644
--- a/keepalived/cluster/instance/stacklight_log_vip.yml
+++ b/keepalived/cluster/instance/stacklight_log_vip.yml
@@ -3,6 +3,8 @@
classes:
- service.keepalived.support
parameters:
+ _param:
+ keepalived_stacklight_log_vip_priority: 101
keepalived:
cluster:
enabled: true
@@ -12,4 +14,4 @@
password: ${_param:keepalived_stacklight_log_vip_password}
interface: ${_param:keepalived_stacklight_log_vip_interface}
virtual_router_id: 110
- priority: 101
+ priority: ${_param:keepalived_stacklight_log_vip_priority}