OpenStack Compute (Nova)
Go to file
Balazs Gibizer 23d3b8fbc9 Remove global state from the FakeDriver
The virt driver FakeDriver used in both the functional and in the unit
test used a global state to configure the host and node names the driver
reports. This was hard to use when more then one compute service is started.
Also global state is dangerous.

It turned out that only a set of unit tests are using multiple nodes per
compute the rest of the tests can simply use host=<hostname>,
nodes=[<hostname>] setup.

So this removes the global state.

On stable/stein:
* Changes in functional/regressions/test_bug_1764556.py just removes the
  usage of the global state as that test was backported before the patch
  being backported was introduced

* Changes in functional/regressions/test_bug_1839560.py is a re-backport
  of If822509e906d5094f13a8700b2b9ed3c40580431 adapted to the current
  patch.

Related-Bug: #1859766

Change-Id: I2cf2fcbaebc706f897ce5dfbff47d32117064f9c
(cherry picked from commit b5666fb492)
2020-01-17 16:04:46 +01:00
api-guide/source Documentation for bandwidth support 2019-03-18 11:24:56 +01:00
api-ref/source Block deleting compute services with in-progress migrations 2019-11-25 11:11:13 -05:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Remove global state from the FakeDriver 2020-01-17 16:04:46 +01:00
etc/nova Add oslo.privsep to config-generator list 2019-03-01 16:43:21 +00:00
gate Remove redundant call to get/create default security group 2019-11-05 23:39:10 +00:00
nova Remove global state from the FakeDriver 2020-01-17 16:04:46 +01:00
playbooks/legacy [stable-only] Disable cinder-backup service in nova-next job 2019-11-27 11:04:44 +00:00
releasenotes Merge "Block deleting compute services with in-progress migrations" into stable/stein 2019-12-09 23:12:02 +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 Zuul v3: use devstack-plugin-nfs-tempest-full 2019-12-19 14:25:43 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Remove descriptions of nonexistent hacking rules 2019-09-03 02:15:41 +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 Added openssh-client into bindep 2019-10-29 07:02:35 +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: