OpenStack Compute (Nova)
Go to file
Dan Smith d1a8ffc408 Move resource provider staticmethods to proxies
Because of bugs in stub_out(), if we use staticmethods combined
with the db_api context managers, we'll break those methods when
the stubs are removed. There is a fix in the queue, but it's going
to be weeks before we can use it. This adds staticmethod proxy
jumps to work around the problem like we're doing for the flavor
code right now. That keeps the tests and other code the way we want
it to look, and we can move the meat back into the staticmethods once
the bug is fixed.

The following patch will be stub_out-ing relevant bits, so fix this
first to keep that diff smaller.

Change-Id: I2015ac25500f7f6960f4916a4249bb711b157b9b
2016-03-31 21:41:28 +00:00
api-guide/source Removes some redundant words 2016-03-25 09:10:36 +07:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Update cells blacklist regex for test_server_basic_ops 2016-03-27 19:31:32 -04:00
doc Merge "Remove auto generated module api documentation" 2016-03-18 21:07:05 +00:00
etc/nova Add os-brick rootwrap filter for privsep 2016-03-15 21:08:08 +00:00
nova Move resource provider staticmethods to proxies 2016-03-31 21:41:28 +00:00
plugins/xenserver Merge "plugins/xenserver: Resolve PEP8 issues" 2016-03-10 14:27:09 +00:00
releasenotes config options: Remove 'wsgi_' prefix from opts 2016-03-25 13:19:19 +00:00
tools Merge "Add a tool for reserving migration placeholders during release time" 2016-02-10 19:48:44 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Merge "Add reno for release notes management" 2015-11-13 16:24:51 +00: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 tox -e functional 2014-11-12 15:31:06 -05: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
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Removes some redundant words 2016-03-25 09:10:36 +07: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
openstack-common.conf Use imageutils from oslo.utils 2016-02-16 18:34:43 +08:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
requirements.txt Updated from global requirements 2016-03-05 20:48:35 +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 Remove auto generated module api documentation 2016-03-18 07:18:07 -04:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2016-02-08 02:42:24 +00:00
tests-py3.txt Blacklist TestOSAPIFixture.test_responds_to_version in python3 2016-03-18 12:36:32 +00:00
tox.ini Error on API Guide warnings 2016-03-17 07:57:23 +01:00

OpenStack Nova README

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.

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.

Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.

To keep updated with new developments in the OpenStack project follow @openstack on Twitter.

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

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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 wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:

https://git.openstack.org/cgit/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast