openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
50,594 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Stephen Finucane 6d7646be53 [stable-only] Fix sphinx doc job 
This is a combination of 2 commits to fix gate failure due to recent
failure of build-sphinx-docs-job since python 2 was replaced in it to
python 3.

1. tox: Make everything work with Python 3

Nothing too fancy here except that we've to work around a really ugly
side-effect of blockdiag.

Conflicts:
  tox.ini

Change-Id: Ibd32d30aacae65702d0ccbdb8a02b1667ec4e8ee
(cherry picked from commit b862f6ff35)

2. Python 3 fix for sphinx doc

In Python 3, dict methods dict.keys() return “views” instead of lists.
Therefore, the code:

    impls = sorted(matrix.targets.keys())
    impls.sort()

should be replaced by:

    impls = sorted(matrix.targets.keys())

to be Python 3 compatible.

Change-Id: I50477b0ac43adff9e9b0220bd7c48d6ebb6471b3
(cherry picked from commit 8ca01a3abb)
 		2022-02-22 16:58:15 +01:00
api-guide/source Merge "Update links in documents" 2018-02-08 01:29:29 +00:00
api-ref/source Block deleting compute services with in-progress migrations 2020-02-12 16:21:13 +00:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Skip more rebuild tests for cells v1 job 2018-09-26 09:07:30 -04:00
doc [stable-only] Fix sphinx doc job 2022-02-22 16:58:15 +01:00
etc/nova Move remaining uses of parted to privsep. 2018-01-24 22:26:36 +00:00
gate move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
nova Merge "[neutron] Get only ID and name of the SGs from Neutron" into stable/queens 2021-09-11 14:12:20 +00:00
placement-api-ref/source [placement] Add status and links fields to version document at / 2020-09-11 14:15:54 +01:00
playbooks/legacy Fix nova-grenade-live-migration run book for opendev migration 2019-04-26 15:17:21 -04:00
releasenotes Update pci stat pools based on PCI device changes 2021-05-25 16:15:52 +05:30
tools Follow up for cherry-pick check for merge patch 2020-11-02 20:48:04 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Fix test runner config issues with os-testr 1.0.0 2017-09-13 17:11:57 -04:00
.gitreview OpenDev Migration Patch 2019-04-19 19:46:53 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml zuul: remove legacy-tempest-dsvm-neutron-dvr-multinode-full 2020-07-23 15:34:56 +02:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst doc: fix link to creating unit tests in contributor guide 2017-11-14 11:22:43 -05: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 doc: Rework README to reflect new doc URLs 2017-08-03 16:06:08 -04:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Bindep does not catch missing libpcre3-dev on Ubuntu 2018-02-13 16:53:16 -05:00
requirements.txt Updated from global requirements 2018-02-01 07:20:35 +00:00
setup.cfg Deprecate the IronicHostManager 2017-11-28 15:23:48 -05:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt [stable-only] Cap bandit to 1.6.2 2020-12-16 15:41:30 +01:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini [stable-only] Fix sphinx doc job 2022-02-22 16:58:15 +01:00

README.rst

Team and repository tags

image

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:

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: