openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
44,247 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
4a237c02e4
Go to file
Matt Riedemann 4a237c02e4 Use liberty-eol tag for liberty release notes 
reno doesn't currently handle missing branches so we need
to use the liberty-eol tag to fix the release note job in
the gate now that origin/stable/liberty is gone.

reno will eventually check for the -eol tag when a stable
branch isn't found in:

I41ab682f081e7fd39ea534b7e2180c2109ca34ef

Change-Id: Ie54f69f5c1f91a3781c876f035fe9ed838e11c08
2016-12-14 11:38:20 -05:00
api-guide/source docs: cleanup wording for 'SOFT_DELETED' in api-guide 2016-11-28 11:51:00 -05:00
api-ref/source api-ref: Fix 'id' (attachment_id) parameters 2016-12-13 06:18:05 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Add RC file for excluding tempest tests for LVM job 2016-05-17 10:25:45 -04:00
doc Merge "Some improvement to the process doc" 2016-12-12 16:10:01 +00:00
etc/nova Add CORS filter to versions pipeline 2016-12-02 11:44:09 -05:00
nova Merge "Move tags validation code to json schema" 2016-12-14 14:46:48 +00:00
plugins/xenserver Add a hacking rule for string interpolation at logging 2016-10-11 08:39:48 +00:00
releasenotes Use liberty-eol tag for liberty release notes 2016-12-14 11:38:20 -05:00
tools Merge "Add Apache 2.0 license to source file" 2016-10-10 12:38:13 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore doc: Integrate oslo_policy.sphinxpolicygen 2016-10-20 10:31:01 +01: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
.testr.conf [placement] Adjust the name of the gabbi tests 2016-09-20 19:14:44 +00:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst hacking: Use uuidutils or uuidsentinel to generate UUID 2016-11-29 11:49:24 +05:30
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst Refresh README and its docs links 2016-08-08 10:26:08 +01:00
requirements.txt Make RPCFixture support multiple connections 2016-12-07 06:53:57 -08:00
run_tests.sh Add description on how to run ./run_test.sh -8 2016-01-11 13:17:04 +00:00
setup.cfg Remove deprecated nova-all binary 2016-10-12 10:02:17 -07:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2016-12-05 09:57:19 +00:00
tests-py3.txt Merge "Port virt.xenapi.client.test_session to Python 3" 2016-12-12 17:20:56 +00:00
tox.ini Merge "Corrects the type of a base64 encoded string" 2016-12-13 23:03:13 +00:00

README.rst

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 and OpenStack Ironic.

OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

API

To learn how to use Nova's API, consult the documentation available online at:

http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/

For more information on OpenStack APIs, SDKs and CLIs, please see:

http://www.openstack.org/appdev/ http://developer.openstack.org/

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, please read:

http://docs.openstack.org/developer/nova/feature_classification.html

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:

http://bugs.launchpad.net/nova

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:

http://docs.openstack.org/developer/nova/