openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
45,482 Commits 10 Branches 92 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
1a8453fd9b
Go to file
Rafael Folco 1a8453fd9b [placement] Raising http codes on old microversion 
Currently only HTTP 404 can be raised. This enables other HTTP status
to be raised if microversion does not match with the minimum required.
This is useful for new methods created to raise other http status code
for older placement microversions, like 405 HTTPMethodNotAllowed.

Change-Id: I2b684fcfd93fc70fe385a93346ee255279909489
2017-03-15 14:28:42 +00:00
api-guide/source Removes unnecessary utf-8 encoding 2016-12-20 10:27:01 +07:00
api-ref/source Merge "remove a TODO as all set for tags" 2017-03-10 22:51:34 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Skip test_stamp_pattern in cells v1 job 2017-02-14 10:25:24 -05:00
doc [placement] Raising http codes on old microversion 2017-03-15 14:28:42 +00:00
etc/nova Fix doc generation warnings 2017-02-24 17:43:08 +00:00
gate move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
nova [placement] Raising http codes on old microversion 2017-03-15 14:28:42 +00:00
plugins/xenserver XenAPI Remove useless files when use os-xenapi lib 2017-01-10 18:06:17 -08:00
releasenotes Typo fix in releasenotes: deprecate network options 2017-03-13 09:22:42 +00:00
tools Remove usage of config option verbose 2017-02-27 10:02:45 +08: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 Enable global hacking checks and removed local checks 2017-02-10 15:09:37 +01:00
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 Show team and repo badges on README 2016-11-25 13:55:29 +01:00
requirements.txt Updated from global requirements 2017-03-02 11:50:48 +00:00
setup.cfg Use Sphinx 1.5 warning-is-error 2017-03-03 18:52:56 +01:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Use flake8-import-order 2017-03-06 06:50:23 -08:00
tests-functional-py3.txt Remove invalid URL in gabbi tests 2017-01-17 21:10:45 +00:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini Use flake8-import-order 2017-03-06 06:50:23 -08: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 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/