nova/releasenotes/notes/sriov-live-migration-0311dfb7102a48db.yaml
Sean Mooney d966ffabc3 libvirt: auto detach/attach sriov ports on migration
- This patch detaches all directmode sriov interfaces before calculating
  the updated xml for the destination immediately before starting the migration.
- This change modifies post_live_migration_at_destination to check
  if an instance has all interfecs defined in the guest xml and attaches
  the missing sriov interfaces if they are not present.
- This change adds a release note for the sriov live migration feature.
- This change extends the base virt driver interface with a new method
  rollback_live_migration_at_source and invokes it from
  rollback_live_migration in the compute manager.

Change-Id: Ib61913d9d6ef6148170963463bb71c13f4272c5d
Implements: blueprint libvirt-neutron-sriov-livemigration
2019-04-26 11:11:40 +01:00

26 lines
1.4 KiB
YAML

---
features:
- |
In this release SR-IOV live migration support is added to the libvirt
virt driver for Neutron interfaces. Neutron SR-IOV interfaces can be
grouped into two categories, direct mode interfaces and indirect.
Direct mode SR-IOV interfaces are directly attached to the guest and
exposed to the guest OS. Indirect mode SR-IOV interfaces have a software
interface such as a macvtap between the guest and the SR-IOV device.
This feature enables transparent live migration for instances with
indirect mode SR-IOV devices. As there is no generic way to copy
hardware state during a live migration, direct mode migration is not
transparent to the guest. For direct mode interfaces, we mimic the
workflow already in place for suspend and resume. For instance with
SR-IOV devices, we detach the direct mode interfaces before migration
and re-attach them after the migration. As a result, instances
with direct mode SR-IOV port will lose network connectivity during a
migration unless a bond with a live migratable interface is created
within the guest.
upgrade:
- |
The Libvirt SR-IOV migration feature intoduced in this release requires
both the source and destination node to support the feature. As a result
it will be automatically disabled until the conductor and compute nodes
have been upgraded.