Let the bgp_plugin to query floating IP bgp next_hop
When a dvr floating IP is associated to a port, the bgp plugin
`floatingip_update_callback` will immediately send a notification
`start_route_advertisements` to DR agent, there is a new floating
IP bgp route.
But this bgp route is not correct, its next_hop is set to dvr router
snat gateway IP address. And then after `periodic_interval` seconds,
the DR agent will resync that DVR fip route with new next_hop to the
correct FIP namespace fg-device IP address.
This patch will let the bgp_plugin to handle the floating IP bgp route
next_hop query.
Reviewed: https:/ /review. openstack. org/372310 /git.openstack. org/cgit/ openstack/ neutron- dynamic- routing/ commit/ ?id=0980985b2f3 590f60b4726a541 9680a1d70f9ead
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0980985b2f3590f 60b4726a5419680 a1d70f9ead
Author: LIU Yulong <email address hidden>
Date: Mon Sep 19 11:29:04 2016 +0800
Let the bgp_plugin to query floating IP bgp next_hop
When a dvr floating IP is associated to a port, the bgp plugin _update_ callback` will immediately send a notification route_advertise ments` to DR agent, there is a new floating
`floatingip
`start_
IP bgp route.
But this bgp route is not correct, its next_hop is set to dvr router
snat gateway IP address. And then after `periodic_interval` seconds,
the DR agent will resync that DVR fip route with new next_hop to the
correct FIP namespace fg-device IP address.
This patch will let the bgp_plugin to handle the floating IP bgp route
next_hop query.
Change-Id: Ic6bb7f4263c6e2 da315178be2ed04 1eb7020c905
Closes-bug: #1615919