Unable to setup static act/sby SI mode via Heat
Bug #1674408 reported by
amit surana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Won't Fix
|
High
|
Naveen N | |||
R3.1 |
Fix Committed
|
High
|
Naveen N | |||
R3.2 |
Fix Committed
|
High
|
Naveen N | |||
R4.0 |
Fix Committed
|
High
|
Naveen N | |||
Trunk |
Fix Committed
|
High
|
Naveen N |
Bug Description
If the VNF is not participating in any act/standy protocol like vrrp, then the same can be achieved by doing both of these steps:
(a) Statically set the LP of the VNF VMIs. Active VMI is set to LP 200 and backup is set to 100.
(b) Set service instance IP mode to active-standby.
With the service-instance ha-mode flag deprecated in 3.1/3.2, and because the service-instance IP is created dynamically after the service is instantiated, there is no way to set its service_instance_ip mode purely via HEAT/automation.
Either the ha_mode flag should be made available or agent should be able to export the correct route based on just the LP setting (ignoring the service-instance ip mode).
tags: | removed: config ui |
To post a comment you must log in.
Agent code will be fixed to ignore service-instance IP mode and advertise the vmi with higher LP.