openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
53,848 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Balazs Gibizer c38a821902 Fix exception type in test_boot_reschedule_fill_provider_mapping_raises 
After Iecbee518444bd282ce5f6fd019db41a322f76a83 merged the
test_boot_reschedule_fill_provider_mapping_raises does not simulate a
possible scenario as ConsumerAllocationRetrievalFailed cannot be
raised from _fill_provider_mapping any more.

The fault this functional test reporduces still exists just with
different exception types. So this patch changes the exception type
to a valid one that is still raised by _fill_provider_mapping.

Change-Id: I79cf44aafccb1bc6b13a3109c5a98215811bd04d
Related-Bug: #1819460
(cherry picked from commit fd3b86d1c3)
 		2019-05-07 15:35:25 +02:00
api-guide/source Documentation for bandwidth support 2019-03-18 11:24:56 +01:00
api-ref/source api-ref: Add description for BDM volume_size 2019-03-13 16:17:20 +00:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Merge "Eventlet monkey patching should be as early as possible" into stable/stein 2019-05-04 22:49:35 +00:00
etc/nova Add oslo.privsep to config-generator list 2019-03-01 16:43:21 +00:00
gate update gate test for removal of force evacuate 2019-03-08 16:31:31 +00:00
nova Fix exception type in test_boot_reschedule_fill_provider_mapping_raises 2019-05-07 15:35:25 +02:00
playbooks/legacy OpenDev Migration Patch 2019-04-19 19:47:27 +00:00
releasenotes Merge "Fix links to neutron QoS minimum bandwidth doc" 2019-03-21 16:41:35 +00:00
tools Make Xen code py3-compatible 2018-08-10 20:04:19 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Remove Placement API reference 2018-11-28 03:38:41 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:47:27 +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 OpenDev Migration Patch 2019-04-19 19:47:27 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Document how to make tests log at DEBUG level 2019-02-13 20:46:01 +00: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: modernise links 2018-03-24 20:27:11 +08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
lower-constraints.txt Merge "Require python-ironicclient>=2.7.0" 2019-03-22 02:55:13 +00:00
requirements.txt Merge "Convert driver supported capabilities to compute node provider traits" 2019-03-05 09:50:12 +00:00
setup.cfg Update mailinglist from dev to discuss 2018-12-05 09:44:35 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Require python-ironicclient>=2.7.0 2019-03-12 15:10:11 -04:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/stein 2019-03-22 03:50:05 +00: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: