openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
57,370 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
c7c48c6f52
Go to file
Elod Illes c7c48c6f52 Fix cherry-pick check for merge patch 
Cherry-pick check script validates the proposed patch's commit message.
If a patch is not on top of the given branch then Zuul rebases it to
the top and the patch becomes a merge patch. In this case the script
validates the merge patch's commit message instead of the original
patch's commit message and fails.

This fix selects the parent of the patch if it is a merge patch.

Change-Id: I8e4e5afc773d53dee9c1c24951bb07a45ddc2f1a
2020-06-26 20:31:20 +02:00
api-guide/source Fix pygments_style 2020-05-20 21:56:41 +02:00
api-ref/source Fix pygments_style 2020-05-20 21:56:41 +02:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Merge "Update interop repo link" 2020-06-26 17:40:35 +00:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate nova-live-migration: Only stop n-cpu and q-agt during evacuation testing 2020-03-21 17:08:47 +00:00
nova Merge "Make libvirt able to trigger a backend image copy when needed" 2020-06-26 13:42:26 +00:00
playbooks Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
releasenotes Merge "Make libvirt able to trigger a backend image copy when needed" 2020-06-26 13:42:26 +00:00
roles Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
tools Fix cherry-pick check for merge patch 2020-06-26 20:31:20 +02: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: Make devstack-plugin-ceph-tempest-py3 a voting check job again 2020-05-26 09:44:21 +01:00
bindep.txt Merge "Add missing test bindep on openssl" 2020-06-21 02:01:16 +00:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Remove hacking rules for python 2/3 compatibility 2020-06-17 08:19:13 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt Merge "Cap jsonschema 3.2.0 as the minimal version" 2020-06-24 01:54:33 +00:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
mypy-files.txt libvirt: Add typing information 2020-06-19 10:47:59 +01:00
README.rst Start README.rst with a better title 2019-11-19 17:29:28 +01:00
requirements.txt Merge "Cap jsonschema 3.2.0 as the minimal version" 2020-06-24 01:54:33 +00:00
setup.cfg tox: Integrate mypy 2020-05-15 15:59:53 +01:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Bump hacking min version to 3.1.0 2020-05-19 08:09:43 +08:00
tox.ini Remove hacking rules for python 2/3 compatibility 2020-06-17 08:19:13 +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, 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: