openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
54,167 Commits 9 Branches 81 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Ghanshyam Mann b05bf09b2d Make greande jobs n-v for EM and oldest stable 
As discussed in ML thread[1], we are going to
make grenade jobs as non voting for all EM stable and
oldest stable. grenade jobs are failing not and it might take
time to fix those if we are able to fix. Once it jobs are
working depends on project team, they can bring them back to
voting or keep non-voting.

If those jobs are failing consistently and no one is fixing them
then removing those n-v jobs in future also fine.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015499.html

StableOnly

Depends-On: https://review.opendev.org/#/c/737384/
Depends-On: https://review.opendev.org/#/c/737826/

Change-Id: I4e03295548af5272a02ca81162fcd685c7986470
 		2020-06-24 15:42:47 +00: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 Merge "Fix os-keypairs pagination links" into stable/stein 2020-03-13 00:53:43 +00:00
etc/nova Add oslo.privsep to config-generator list 2019-03-01 16:43:21 +00:00
gate nova-live-migration: Ensure subnode is fenced during evacuation testing 2020-03-23 10:22:33 +00:00
nova Add functional test for bug 1550919 2020-06-02 15:02:42 +01:00
playbooks/legacy [stable-only] Disable cinder-backup service in nova-next job 2019-11-27 11:04:44 +00:00
releasenotes Merge "Reject boot request for unsupported images" into stable/stein 2020-04-24 17:06:50 +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 Make greande jobs n-v for EM and oldest stable 2020-06-24 15:42:47 +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 Use placement stable version for functional job 2020-04-15 10:25:57 -05: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: