From ccbef43f5bd1f7c393d7ccc90e2ba79f42f3e1e6 Mon Sep 17 00:00:00 2001 From: Armando Migliaccio Date: Tue, 15 Mar 2016 07:31:39 -0700 Subject: [PATCH] Improve release notes for dvr fixes Change-Id: Ida1165add974207a4ea25696d26e1daae7914288 Related-bug: #1456073 --- ...pport-live-migration-b818b12bd9cbb518.yaml | 28 +++++++------------ 1 file changed, 10 insertions(+), 18 deletions(-) diff --git a/releasenotes/notes/dvr-support-live-migration-b818b12bd9cbb518.yaml b/releasenotes/notes/dvr-support-live-migration-b818b12bd9cbb518.yaml index d569276b39c..2f9958dadf9 100644 --- a/releasenotes/notes/dvr-support-live-migration-b818b12bd9cbb518.yaml +++ b/releasenotes/notes/dvr-support-live-migration-b818b12bd9cbb518.yaml @@ -1,22 +1,14 @@ --- prelude: > - Fix DVR support for service port live migration. + Improve DVR's resiliency during Nova VM live + migration events. fixes: - - Create DVR routers pro-actively on the destination - node for migrating dvr service port. - - If the DVR service port has associated floatingip, - then the floatingip namespace would be created on - the destination node. + - Create DVR router namespaces pro-actively on the + destination node during live migration events. This + helps minimize packet loss to floating IP traffic. issues: - - Right now we do not have status update notification - for L3 networks into Nova for nova to take necessary - action on failure to create the L3 networks. - So we do not report back failure and will be handled - in next release. In this case there might be a delay - 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. + - More synchronization between Nova and Neutron is needed + to properly handle live migration failures on either + side. For instance, if live migration is reverted or + canceled, some dangling Neutron resources may be left + on the destination host.