openstack/neutron
Code Issues Proposed changes

Improve release notes for dvr fixes

Browse Source 
Change-Id: Ida1165add974207a4ea25696d26e1daae7914288
Related-bug: #1456073
This commit is contained in:
Armando Migliaccio 2016-03-15 07:31:39 -07:00 committed by Brian Haley
parent 2413ab2979
commit ccbef43f5b
1 changed files with 10 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
releasenotes/notes/dvr-support-live-migration-b818b12bd9cbb518.yaml
View File

@ -1,22 +1,14 @@
--- ---
prelude: > prelude: >
Fix DVR support for service port live migration. Improve DVR's resiliency during Nova VM live
migration events.
fixes: fixes:
- Create DVR routers pro-actively on the destination - Create DVR router namespaces pro-actively on the
node for migrating dvr service port. destination node during live migration events. This
- If the DVR service port has associated floatingip, helps minimize packet loss to floating IP traffic.
then the floatingip namespace would be created on
the destination node.
issues: issues:
- Right now we do not have status update notification - More synchronization between Nova and Neutron is needed
for L3 networks into Nova for nova to take necessary to properly handle live migration failures on either
action on failure to create the L3 networks. side. For instance, if live migration is reverted or
So we do not report back failure and will be handled canceled, some dangling Neutron resources may be left
in next release. In this case there might be a delay on the destination host.
in creating the routers and fip namespace after the
DVR service port migrates.
- If the nova reverts or cancels the live migration
after it informs the neutron and before it migrates
the dvr service port, then we do not cleanup the router
and fip namespace that was created on the destination
node.