openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
54,307 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Balazs Gibizer 15b9e81d37 Simplfy test setup for TestNovaMigrations* tests 
The NoDBTestCase base class does a lot of env setup that is not needed
for these tests. As we have issues with these tests (see bug 1823251)
this patch tries to decrease the complexity of them to help the
troubleshooting.

Change-Id: I46fafa470b9d378d96c0f364e9b487742bf58cb2
Related-Bug: #1823251
 		2019-06-03 14:02:34 +02:00
api-guide/source [Trivial doc change] Admin can overwrite the locked_reason of an owner 2019-05-14 19:04:08 +00:00
api-ref/source Merge "Block swap volume on volumes with >1 rw attachment" 2019-05-30 17:47:10 +00:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Remove zeromq from getting started with compute docs 2019-05-30 12:00:00 -04:00
etc/nova Remove 'etc/nova/cells.json' 2019-05-20 16:11:49 +01:00
gate Pass --nic when creating servers in evacuate integration test script 2019-04-01 09:58:01 -04:00
nova Simplfy test setup for TestNovaMigrations* tests 2019-06-03 14:02:34 +02:00
playbooks/legacy Merge "Set [quota]count_usage_from_placement = True in nova-next" 2019-05-30 20:39:56 +00:00
releasenotes Merge "Count instances from mappings and cores/ram from placement" 2019-05-30 20:39:43 +00:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00: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
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Skip novnc tests in multi-cell job until bug 1830417 is fixed 2019-05-24 14:23:05 -04:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Hacking N362: Don't abbrev/alias privsep import 2019-04-04 20:42:43 +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 Move selective patching of open() to nova.test for reuse 2019-05-25 02:49:40 +00:00
requirements.txt Blacklist python-cinderclient 4.0.0 2019-05-30 09:30:24 +08:00
setup.cfg Update Python 3 test runtimes for Train 2019-05-09 17:35:43 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Move selective patching of open() to nova.test for reuse 2019-05-25 02:49:40 +00:00
tox.ini Delete the placement code 2019-04-28 20:06:15 +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: