DVR:Fix _notify_l3_agent_new_port for proper arp update
Now with notifications coming from ml2 plugin on port create
and port update, it is worth fixing the existing _notify_
l3_agent_new_port for proper arp update and router scheduling.
Previously we have been sending arp update and calling router
scheduling for every update notification for service ports,
but now we can take necessary action only when required, since
the fix to update the arp and router scheduling was recently
done by sending the port info for every new port created.
When _notify_l3_agent_port_update is triggered, we check if the
original port host binding exists and if there is a change in
host binding with respect to the new port, then we go ahead and
reschedule the router on the new host and flush the arp entry.
Reviewed: https:/ /review. openstack. org/253685 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=b223452e68f a8629cb67826bb8 ae3ac612e0b859
Committed: https:/
Submitter: Jenkins
Branch: master
commit b223452e68fa862 9cb67826bb8ae3a c612e0b859
Author: Swaminathan Vasudevan <email address hidden>
Date: Fri Dec 4 11:58:57 2015 -0800
DVR:Fix _notify_ l3_agent_ new_port for proper arp update
Now with notifications coming from ml2 plugin on port create agent_new_ port for proper arp update and router scheduling.
and port update, it is worth fixing the existing _notify_
l3_
Previously we have been sending arp update and calling router
scheduling for every update notification for service ports,
but now we can take necessary action only when required, since
the fix to update the arp and router scheduling was recently
done by sending the port info for every new port created.
When _notify_ l3_agent_ port_update is triggered, we check if the
original port host binding exists and if there is a change in
host binding with respect to the new port, then we go ahead and
reschedule the router on the new host and flush the arp entry.
Related-Bug: #1524020
Change-Id: Ifda623d5413b72 bf80f38fba5c12a 05a88bb7de5