OpenStack Compute (Nova)
Go to file
Alexandre Arents 9a0bc6e9cf Revert "nova-multi-cell: Skip test_cold_migrate_unshelved_instance"
This reverts commit c11f4e5336.

Test should work since change:
    I0b81282eba8238d8b64a67e38cf9d6392de1f85c

Conflicts:
        devstack/nova-multi-cell-blacklist.txt

NOTE(aarents): the confict is due to change
I95bc22f7d65454cd9e7b54a0e6d9516f2f204978
Disable qos resize tempest test for nova-multi-cell job

Change-Id: Ib953470cf0ccddfec5f253097ddd7f7f0eaf4883
2020-12-17 10:24:27 +00:00
api-guide/source Disable qos resize tempest test for nova-multi-cell job 2020-12-10 14:51:19 +01:00
api-ref/source Enhance simple usage API documentation 2020-12-07 17:38:37 -03:00
devstack Revert "nova-multi-cell: Skip test_cold_migrate_unshelved_instance" 2020-12-17 10:24:27 +00:00
doc Add a description in the PTL guide 2020-12-13 11:28:00 +00:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate Merge "Revert "Temporarily disable parts of heal port allocation test"" 2020-12-16 18:37:40 +00:00
nova Merge "Refactoring of functional.regression.test_bug_1702454" 2020-12-16 02:47:45 +00:00
playbooks nova-evacuate: Remove leftover playbook from standalone job 2020-12-07 20:26:29 +00:00
releasenotes Disable qos resize tempest test for nova-multi-cell job 2020-12-10 14:51:19 +01:00
roles nova-live-migration: Disable *all* virt services during negative tests 2020-11-27 13:35:42 +00:00
tools tools: Allow check-cherry-picks.sh to be disabled by an env var 2020-12-07 12:53:42 +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 "Revert "zuul: Skip test_attach_scsi_disk_with_config_drive in nova-ceph-multistore"" 2020-11-30 10:23:11 +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 lower-constraints: Bump packaging to 20.4 2020-12-07 16:09:49 +00:00
mypy-files.txt Add type hints to 'nova.virt.libvirt.utils' 2020-09-04 14:42:18 +01:00
requirements.txt Replace md5 with oslo version 2020-10-29 15:58:23 -04:00
setup.cfg Fix config option default value for sample config file 2020-11-25 00:05:08 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt [goal] Prepare for job migration to Ubuntu Focal (20.04) 2020-08-18 11:28:32 +00:00
tox.ini Remove outdated comment from tox.ini 2020-12-04 14:31:30 +01: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: