openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
19,194 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Mark McLoughlin 706a137005 Use oslo-config-2013.1b4 
The cfg API is now available via the oslo-config library, so switch to
it and remove the copied-and-pasted version.

Add the 2013.1b4 tarball to tools/pip-requires - this will be changed
to 'oslo-config>=2013.1' when oslo-config is published to pypi. This
will happen in time for grizzly final.

Add dependency_links to setup.py so that oslo-config can be installed
from the tarball URL specified in pip-requires.

Remove the 'deps = pep8==1.3.3' from tox.ini as it means all the other
deps get installed with easy_install which can't install oslo-config
from the URL.

Make tools/hacking.py include oslo in IMPORT_EXCEPTIONS like it already
does for paste. It turns out imp.find_module() doesn't correct handle
namespace packages.

Retain dummy cfg.py file until keystoneclient middleware has been
updated (I18c450174277c8e2d15ed93879da6cd92074c27a).

Change-Id: I4815aeb8a9341a31a250e920157f15ee15cfc5bc
 		2013-02-19 21:16:32 -08:00
bin Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc Default SG rules for the Security Group "Default" 2013-02-19 01:50:51 +00:00
etc/nova Merge "Added a service heartbeat driver using Memcached." 2013-02-20 02:56:56 +00:00
nova Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00
plugins/xenserver Harmonize PEP8 checking between tox and run_tests.sh 2013-02-15 00:39:58 +00:00
smoketests Removed print stmts in test cases 2013-01-29 12:55:14 -05:00
tools Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00
.coveragerc Update .coveragerc 2013-02-06 16:47:06 +02:00
.gitignore Ignore auto-generated files by lintstack 2013-01-17 17:27:09 -05:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add the missing replacement text in devref doc. 2012-12-14 09:47:32 +08:00
.testr.conf Invert test stream capture logic for debugging. 2013-01-07 11:03:30 -08:00
CONTRIBUTING.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
HACKING.rst Module import style checking changes 2013-02-13 17:05:09 +01:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
README.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
run_tests.sh Make pep8 tests run inside virtualenv 2013-02-16 20:50:14 +01:00
setup.cfg Use testr to run nova unittests. 2012-12-14 14:22:20 -08:00
setup.py Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00
tox.ini Use oslo-config-2013.1b4 2013-02-19 21:16:32 -08:00

README.rst

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

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:

http://github.com/openstack/nova

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

https://lists.launchpad.net/openstack/

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://nova.openstack.org/

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

-- End of broadcast