OpenStack Compute (Nova)
Go to file
Sean Dague 15b392a67b Don't print to stdout when executing hacking checks
The way the hacking tests _run_check works, it ends up evaluating
python code in a context where all of our stdout capture has been
undone. The pep8 check_all method *also* prints out the errors found,
not only accumulating them for later. We can patch out the method
doing that to keep this from leaking through the test output, which
only causes confusion.

Change-Id: I9be4801352c4977504d95123d01bcbe309f22347
2016-09-22 08:32:04 -04:00
api-guide/source Merge "Fix a typo from ID to Id" 2016-09-21 03:04:47 +00:00
api-ref/source [api-ref] Correct parameter type 2016-09-20 17:20:37 +07: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 trivial: Rewrap guide at 79 characters 2016-09-21 11:32:17 +01:00
etc/nova Add bigswitch command to compute rootwrap filters 2016-09-02 14:01:38 -02:30
nova Don't print to stdout when executing hacking checks 2016-09-22 08:32:04 -04:00
plugins/xenserver Merge "XenAPI: resolve the fetch_bandwidth failure" 2016-09-20 19:43:15 +00:00
releasenotes Merge "Add a new release note" 2016-09-19 18:04:06 +00:00
tools Remove locals() for formatting strings. 2016-08-22 17:32:38 +07:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Ignore generated merged policy files 2016-08-31 08:54:25 -07: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 Add initial framing of placement API 2016-07-29 10:31:36 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Remove hacking check [N347] for config options. 2016-08-11 14:23:21 +02: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 Refresh README and its docs links 2016-08-08 10:26:08 +01:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
requirements.txt Updated from global requirements 2016-09-21 07:31:10 +00:00
run_tests.sh Add description on how to run ./run_test.sh -8 2016-01-11 13:17:04 +00:00
setup.cfg Merge "Adds nova-policy-check cmd" 2016-09-01 17:56:56 +00:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Move wsgi-intercept to test-requirements.txt 2016-09-20 14:17:54 -04:00
tests-py3.txt Remove nova/api/validator.py 2016-08-16 09:52:29 +00:00
tox.ini Revert "tox: Don't create '.pyc' files" 2016-09-14 10:45:44 +01: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/