OpenStack Compute (Nova)
Go to file
Stephen Finucane 51d16adda6 mypy: Add type annotations to 'nova.pci'
The 'nova.pci' module is poorly understood and difficult to debug.
Start adding type hints to make this a little easier to parse and catch
dumb errors. Some code needs to be reworked to make 'mypy' happy, but
it's mostly just type annotations.

Note that because of how the 'nova.objects' module works, we need to
delay interpolation by using forward references, or expressing the type
as string literals to be resolved later [1].

[1] https://www.python.org/dev/peps/pep-0484/#forward-references

Change-Id: I2a609606806c6cabdf95d53339335f61743fc5b0
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
2021-04-26 18:06:21 +01:00
api-guide/source Trival change: spell error of Shelve 2021-04-07 02:10:19 +00:00
api-ref/source trivial: fix word duplication in api ref 2021-03-22 09:22:39 +01:00
devstack Switch to new rolevar for run-tempest role 2021-04-09 16:06:10 +00:00
doc Merge "docs: Correct typos in 'nova-manage db' docs" 2021-04-22 11:45:31 +00: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 mypy: Add type annotations to 'nova.pci' 2021-04-26 18:06:21 +01:00
playbooks [OVN] Explicitly set grenade job to ML2/OVS 2021-04-12 09:39:16 +01:00
releasenotes Replace blind retry with libvirt event waiting in detach 2021-04-18 10:24:08 +02: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 "Switch to new rolevar for run-tempest role" 2021-04-24 09:37:23 +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 mypy: Add type annotations to 'nova.pci' 2021-04-26 18:06:21 +01: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: