Adrian Chiris
fd8fdc9345
This patch, builds on previous patches and enables
Live migration with SR-IOV indirect ports.
Prior to this change migration would have either:
- Failed with instance running on the source node.
- Failed with two VMs booted on both source and destination
nodes, VM state is set to migrating, duplicate MACs on
source and destination node and improper PCI resource claiming.
This scenario is observed in the case of macvtap port type and
neutron does not support multiple port binding API extension.
With very little, non user friendly information in the log.
Conductor Changes:
- Allow live migration only with VIF related PCI devices to allow
properly claiming PCI resources on the destination node.
With this change live migration with generic flavor based
PCI passthrough devices will not be supported due to libvirt and
qemu constraint.
- Add a check to allow live migration with VIF related PCI allocation
only when neutron supports multiple ports binding API extension
and compute nodes are up to date.
- update the migrating VIF with the correct profile when binding the
ports on the destination host, this will allow proper binding against
the destination host and ensure VIF will be plugged correctly by Nova.
Compute Changes:
- Create VIFMigrateData for all VIFs in
check_can_live_migrate_destination()
- For every VIF that contains a PCI device in its profile
claim a PCI device on the destination node using the matching
InstancePCIRequest of the instance being migrated.
- Update the relevant VIFMigrateData profile with the newly
claimed PCI device.
- Free PCI devices on source and allocate on destination upon
a successful migration or free claimed PCI devices on destination
upon failure.
NeutronV2 Changes:
- Don't update binding profile with PCI devices if migration type is
live-migration as the profile was already updated when an inactive
port binding was created during bind_ports_to_host() call
from conductor.
Note: This builds on multiple ports binding API.
Change-Id: I734cc01dce13f9e75a16639faf890ddb1661b7eb
Partial-Implement: blueprint libvirt-neutron-sriov-livemigration
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/nova.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
OpenStack Nova
==============
OpenStack Nova provides a cloud computing fabric controller, supporting a wide
variety of compute technologies, including: libvirt (KVM, Xen, LXC and more),
Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
---
To learn how to use Nova's API, consult the documentation available online at:
- `Compute API Guide <https://developer.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://developer.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
In the unfortunate event that bugs are discovered, they should be reported to
the appropriate bug tracker. If you obtained the software from a 3rd party
operating system vendor, it is often wise to use their own bug tracker for
reporting problems. In all other cases use the master OpenStack bug tracker,
available at:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
Developers
----------
For information on how to contribute to Nova, please see the contents of the
CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst
file, and pass all unit tests.
Further developer focused documentation is available at:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
Other Information
-----------------
During each `Summit`_ and `Project Team Gathering`_, we agree on what the whole
community wants to focus on for the upcoming release. The plans for nova can
be found at:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/