openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
58,310 Commits 9 Branches 84 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Balazs Gibizer a634103b15 libvirt: allow querying devices from the persistent domain 
This patch adds from_persistent_config kwargs to get_interface_by_cfg()
and get_disk() so that the caller can specify which domain config the
devices is read from. Currently, if there was both a live domain and a
persistent domain then nova only reads from the live domain. In a later
patch during device detach these calls will be used to detach from the
persistent domain separately from the live domain.

Change-Id: I86153d31b02e6b74b42d53a6800297cbd0e5cbb4
Related-Bug: #1882521
 		2021-02-22 16:05:20 +01:00
api-guide/source Cyborg shelve/unshelve support 2021-01-15 03:21:17 +00:00
api-ref/source Merge "api-ref: Add notes about volume attach and detach being async" 2021-01-20 17:54:42 +00:00
devstack Revert "nova-multi-cell: Skip test_cold_migrate_unshelved_instance" 2020-12-17 10:24:27 +00:00
doc docs: Move the LibvirtDistroSupportMatrix wiki page into our docs 2021-02-01 14:33:15 +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 libvirt: allow querying devices from the persistent domain 2021-02-22 16:05:20 +01:00
playbooks Restart glance after updating policy in job 2021-01-29 16:16:24 -08:00
releasenotes Merge "glance: Remove [glance]/allowed_direct_url_schemes" 2021-02-06 01:10:07 +00: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 zuul: Mark nova-lvm as voting 2021-02-02 10:23:37 +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 Reuse code from oslo lib for JSON policy migration 2021-01-14 22:41:33 +00:00
mypy-files.txt libvirt: Define and emit DeviceRemovedEvent and DeviceRemovalFailedEvent 2021-02-22 11:05:15 +01:00
requirements.txt Reuse code from oslo lib for JSON policy migration 2021-01-14 22:41:33 +00: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 tox: Enable parallel docs build 2021-01-27 16:46:21 +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: