Balazs Gibizer
5f63ada309
This patch adds extra functional test coverage for live migration with qos ports. It covers live migration with target host specified and re-schedule success and failure cases. There are two non test code changes. 1) In the check_can_live_migrate_destination compute manager method CONF.host was used to determine the destination host. This was replaced with self.host. This change result in identical data in a production environment. But during the functional test the CONF object is global for every compute servers running in the environment. This causes that when the above call runs on host2 the CONF.host is already set to host3 as that host was started later in the test. Fortunately self.host is set on the compute manage during the compute startup so it is correct in the functional test env too. It is unfortunate that we have to change non test code to make the test code work but the global CONF variable is a hard problem to resolve. 2) The InstancePCIRequest is saved in the LiveMigrationTask as the task updates the request for each host it tries to move the instance. If non of the destination supports the migration then the rollback() of the task will restore the InstancePCIRequest to its original value as the instance will remain on the source host. Change-Id: I351399f02d4d3b3e958a62fe37380577f3056d0d blueprint: support-move-ops-with-qos-ports-ussuri
==============
OpenStack Nova
==============
.. 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 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://docs.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://docs.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/