Status: In Progress
Affects Version/s: None
Fix Version/s: Neon
FIPs for Octavia VIPs (octavia-fips)
An Octavia VIP is a neutron port that is not bound to any VM and is therefor not added to br-int. The VM containing the active haproxy sends gratuitous ARPs for the VIP's IP and ODL intercepts those and programs flows to forward VM traffic to the VMs port. Note that this is my understanding of how this all works, I have not validated it, the opener of this bug confirms that it works.
The ODL code responsible for configuring the FIP association flows on OVS currently relies on a southbound openflow port that corresponds to the neutron FIP port. The only real reason this is required is so that ODL can decide which switch should get the flows. See FloatingIPListener#createNATFlowEntries. In the case of the VIP port, there is no corresponding southbound port so the flows never get configured.
|75248,7||Add dp-id to ARP notifications||master||genius||Status: MERGED||+2||+1|
|75281,16||FIP support for Octavia VIPs||master||netvirt||Status: MERGED||+2||+1|
|76132,4||Spec for Fip support for Octavia Vips||master||netvirt||Status: MERGED||+2||+1|
|76296,2||Add dp-id to ARP notifications||stable/oxygen||genius||Status: MERGED||+2||+1|
|76303,3||FIP support for Octavia VIPs||stable/oxygen||netvirt||Status: MERGED||+2||+1|
|76603,1||Add dp-id to ARP notifications||stable/fluorine||genius||Status: MERGED||+2||+1|
|76606,2||FIP support for Octavia VIPs||stable/fluorine||netvirt||Status: MERGED||+2||+1|