Comment 11 for bug 1583694

After analyzing both the options, if HA or VRRP applications are not accepting the delaying in migrating from on FIP namespace to another namespace, then we should probably go back to the centralized model for the ports that are unbound.

So here is my proposal. We come up with a "neutron.conf" configuration option of "dvr_unbound_port_fip_use_cvr=True". If this option is configured, this will override any default behavior of the L3 agent and neutron server behavior for the DVR routers and will try to configure the Floatingip's for these unbound ports within the 'SNAT_namespace'. So those VMs that are associated with the unbound allowed_address_pair port or any other port that is unbound will have to send the traffic from their node to the network_node and the floatingip translation will happen within the snat_namespace similar to the CVR.

Any GARP update messages that are sent out from the VMs through the keepalived will reach the SNAT namespace and the traffic will get forwarded to the respective router interfaces.

The disadvantage of this is feature is we loose the distributed nature of the floatingip and make the agent job more complex.

Please let me know your thoughts.