openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
50,680 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
6efbed5e70
Go to file
Chris Dent 6efbed5e70 Fix link in placement contributor doc 
A todo in the contributor/placement.rst slipped through the review
cracks and meant a bad link to 'link to spec once it merges' is in the
docs. This fixes it with the correct link to the spec.

Change-Id: I13daf9576dcb1229409826b4c4eac28c8bb1e23f
2018-04-20 12:27:40 +01:00
api-guide/source Add config drive link to api-guide 2018-04-16 11:36:27 +08:00
api-ref/source Block deleting compute services which are hosting instances 2018-04-18 19:16:00 -04:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Cleanup tempest-dsvm-cells-rc blacklist 2018-03-15 09:31:24 -04:00
doc Fix link in placement contributor doc 2018-04-20 12:27:40 +01:00
etc/nova Convert users of tune2fs to privsep. 2018-02-28 07:14:51 +11:00
gate Make nova-manage db purge take --all-cells 2018-03-08 09:26:49 -08:00
nova Merge "Block deleting compute services which are hosting instances" 2018-04-20 05:55:36 +00:00
placement-api-ref/source [placement] Support forbidden traits in API 2018-04-13 19:24:08 +01:00
playbooks/legacy Use Queens UCA for nova-multiattach job 2018-04-12 16:07:52 -04:00
releasenotes Merge "Block deleting compute services which are hosting instances" 2018-04-20 05:55:36 +00:00
tools Finish stestr migration 2017-11-24 16:51:12 -05:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Fix test runner config issues with os-testr 1.0.0 2017-09-13 17:11:57 -04:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04: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 Use Queens UCA for nova-multiattach job 2018-04-12 16:07:52 -04: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
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Removed unnecessary parantheses in yield statements 2018-03-07 16:44:36 +09: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
requirements.txt uncap eventlet in nova 2018-04-11 21:35:49 +08:00
setup.cfg Follow the new PTI for document build 2018-03-16 14:39:36 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Updated from global requirements 2018-03-23 07:40:46 +00:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini Default to py3 for the pep8 tox env because it's stricter 2018-04-04 15:24:00 +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: