After a migration clean up the floating ip on the source host
When a VM is migrated that has a floating IP associated, the L3
agent on the source host should be notified when the migration
is over. If the router on the source host is not going to be
removed (there are other ports using it) then we should nofity
that the floating IP needs to be cleaned up.
Change-Id: Iad6fbad06cdd33380ef536e6360fd90375ed380d
Closes-bug: #1585165
(cherry picked from commit a1f06fd707ffe663e09f2675316257c8dc528d47)
Reviewed: https:/ /review. openstack. org/328464 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=83ca27f52ae 994660eb9cb9cd0 40dc409b417452
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 83ca27f52ae9946 60eb9cb9cd040dc 409b417452
Author: rossella <email address hidden>
Date: Wed Jun 8 17:18:51 2016 +0200
After a migration clean up the floating ip on the source host
When a VM is migrated that has a floating IP associated, the L3
agent on the source host should be notified when the migration
is over. If the router on the source host is not going to be
removed (there are other ports using it) then we should nofity
that the floating IP needs to be cleaned up.
Change-Id: Iad6fbad06cdd33 380ef536e6360fd 90375ed380d 3e09f2675316257 c8dc528d47)
Closes-bug: #1585165
(cherry picked from commit a1f06fd707ffe66