OpenStack Compute (Nova)
Go to file
Artom Lifshitz 00f1d4757e Update SRIOV port pci_slot when unshelving
There are a few things we need to do to make that work:

* Always set the PCIRequest's requester_id. Previously, this was only
  done for resource requests. The requester_id is the port UUID, so we
  can use that to correlate which port to update with which pci_slot
  (in the case of multiple SRIOV ports per instance).

  This has the side effect of making the fix work only for instances
  created *after* this patch has been applied. It's not ideal, but
  there does not appear to be a better way.

* Call setup_networks_on_host() within the instance_claim context.
  This means the instance's pci_devices are updated when we call it,
  allowing us to get the pci_slot information from them.

With the two previous changes in place, we can figure out the port's
new pci_slot in _update_port_binding_for_instance().

Closes: bug 1851545
Change-Id: Icfa8c1d6e84eab758af6223a2870078685584aaa
2021-04-23 10:07:04 -04:00
api-guide/source Support interface attach with QoS ports 2021-02-11 16:43:17 +01:00
api-ref/source trivial: fix word duplication in api ref 2021-03-22 09:22:39 +01:00
devstack Revert "nova-multi-cell: Skip test_cold_migrate_unshelved_instance" 2020-12-17 10:24:27 +00:00
doc docs: Populate "See Also" section with meaningful links 2021-04-13 17:22:24 +01:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
nova Update SRIOV port pci_slot when unshelving 2021-04-23 10:07:04 -04:00
playbooks Make nova-ceph-multistore use policy.yaml 2021-03-10 07:35:24 -08:00
releasenotes Update SRIOV port pci_slot when unshelving 2021-04-23 10:07:04 -04:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools Add generate schemas tool 2021-01-18 16:27:00 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore tox: Integrate mypy 2020-05-15 15:59:53 +01:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.pre-commit-config.yaml Switch to hacking 2.x 2020-01-17 11:30:40 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Merge "nova-next: Drop NOVA_USE_SERVICE_TOKEN as it is now True by default" 2021-04-11 10:23:16 +00:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add a hacking rule for assert_has_calls 2020-09-28 23:08:15 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst docs: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
bindep.txt bindep: Install python3 and python3-devel on CentOS 8 and Fedora 2020-10-03 13:20:21 +01:00
lower-constraints.txt Bumping min os-brick ver to 4.3.1 2021-03-29 17:36:12 +01:00
mypy-files.txt nova-manage: Add libvirt get_machine_type command 2021-03-03 14:03:49 +00:00
requirements.txt Bumping min os-brick ver to 4.3.1 2021-03-29 17:36:12 +01:00
setup.cfg setup.cfg: Resolve warning 2021-03-09 12:49:50 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt use psycopg2 binary instead of source package 2021-01-14 18:12:04 +00:00
tox.ini tox: Add passenv DISABLE_CHERRY_PICK_CHECK to pep8 2021-02-17 11:23:49 +00:00

README.rst

OpenStack Nova

image

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, 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:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

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:

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:

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: