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.
Closes-bug: #1585165
(cherry picked from commit a1f06fd707ffe663e09f2675316257c8dc528d47)
Reviewed: https:/ /review. openstack. org/329107 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=a6e020cc199 df0eafe7b4fdcd9 2fa74881d27dfa
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit a6e020cc199df0e afe7b4fdcd92fa7 4881d27dfa
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.
Closes-bug: #1585165 3e09f2675316257 c8dc528d47)
(cherry picked from commit a1f06fd707ffe66
Conflicts: db/l3_dvrschedu ler_db. py tests/unit/ scheduler/ test_l3_ agent_scheduler .py 380ef536e6360fd 90375ed380d
neutron/
neutron/
Change-Id: Iad6fbad06cdd33