openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
54,646 Commits 9 Branches 81 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Matt Riedemann cee072b962 Convert nova-next to a zuul v3 job 
For the most part this should be a pretty straight-forward
port of the run.yaml. The most complicated thing is executing
the post_test_hook.sh script. For that, a new post-run playbook
and role are added.

The relative path to devstack scripts in post_test_hook.sh itself
had to drop the 'new' directory since we are no longer executing
the script through devstack-gate anymore the 'new' path does not
exist.

Change-Id: Ie3dc90862c895a8bd9bff4511a16254945f45478
 		2019-07-23 11:32:35 -04:00
api-guide/source Merge "docs: Rework all things metadata'y" 2019-06-23 09:13:08 +00:00
api-ref/source api-ref: Fix a broken link 2019-07-05 13:24:18 +09:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc doc: Fix a parameter of NotificationPublisher 2019-07-10 16:13:51 +09:00
etc/nova Merge "Summarize output of sample configuration generator" 2019-06-16 07:30:03 +00:00
gate Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
nova Merge "libvirt: Remove unreachable native QEMU iSCSI initiator config code" 2019-07-10 17:32:48 +00:00
playbooks Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
releasenotes Merge "Add placement request pre-filter compute_status_filter" 2019-07-09 17:31:47 +00:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04: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 Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -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 Merge "Set COMPUTE_STATUS_DISABLED trait from update_provider_tree flow" 2019-07-07 00:57:45 +00:00
requirements.txt Merge "Set COMPUTE_STATUS_DISABLED trait from update_provider_tree flow" 2019-07-07 00:57:45 +00: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 Merge "Exclude broken ironicclient versions 2.7.1" 2019-06-03 19:44:11 +00:00
tox.ini hacking: Resolve W605 (invalid escape sequence) 2019-06-24 14:24:06 -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: