Balazs Gibizer
56f29b3e4a
During creating or moving of an instance with qos SRIOV port the PCI device claim on the destination compute needs to be restricted to select PCI VFs from the same PF where the bandwidth for the qos port is allocated from. This is achieved by updating the spec part of the InstancePCIRequest with the device name of the PF by calling update_pci_request_spec_with_allocated_interface_name(). Until now such update of the instance object was directly persisted by the call. During code review it was came up that the instance.save() in the util is not appropriate as the caller has a lot more context to decide when to persist the changes. The original eager instance.save was introduced when support added to the server create flow. Now I realized that the need for such save was due to a mistake in the original ResourceTracker.instance_claim() call that loads the InstancePCIRequest from the DB instead of using the requests through the passed in instance object. By removing the extra DB call the need for eagerly persisting the PCI spec update is also removed. It turned out that both the server create code path and every server move code paths eventually persist the instance object either during at the end of the claim process or in case of live migration in the post_live_migration_at_destination compute manager call. This means that the code now can be simplified. Especially the live migration cases. In the live migrate abort case we don't need to roll back the eagerly persisted PCI change as now such change is only persisted at the end of the migration but still we need to refresh pci_requests field of the instance object during the rollback as that field might be stale, containing dest host related PCI information. Also in case of rescheduling during live migrate if the rescheduling failed the PCI change needed to be rolled back to the source host by a specific code. But now those change are never persisted until the migration finishes so this rollback code can be removed too. Change-Id: Ied8f96b4e67f79498519931cb6b35dad5288bbb8 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/