RETIRED, Common scheduler for OpenStack
Go to file
Monty Taylor efdd9c8c80 Update common setup code to latest.
This gets us up to date with common/setup.py and replaces custom nova
autodoc generation with the port of that code found in common.

Change-Id: I2a1c5d2c0fdcf40dbea50cc123b537adb068cdc2
2012-07-07 16:32:19 -05:00
bin Fix rpc import path in nova-novncproxy 2012-07-06 10:49:03 -07:00
doc Update common setup code to latest. 2012-07-07 16:32:19 -05:00
nova Update common setup code to latest. 2012-07-07 16:32:19 -05:00
.coveragerc Finalize tox config. 2012-06-07 12:15:42 -04:00
.gitignore Update common setup code to latest. 2012-07-07 16:32:19 -05:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Update common setup code to latest. 2012-07-07 16:32:19 -05:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
HACKING.rst Expand HACKING with commit message guidelines 2012-07-02 19:36:48 -07: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
openstack-common.conf Switch to common logging. 2012-07-02 15:57:09 -05:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
README.rst Flesh out the README file with a little more useful information 2012-06-29 17:11:10 +01:00
run_tests.sh Add PEP8 checks back for Dom0 plugins. 2012-06-28 22:57:24 +00:00
setup.cfg Finalize tox config. 2012-06-07 12:15:42 -04:00
setup.py Update common setup code to latest. 2012-07-07 16:32:19 -05:00
tox.ini Run hacking tests as part of the gate. 2012-07-02 08:50:41 -04: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

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 dicussion 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/

Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at:

http://wiki.openstack.org/GerritWorkflow

-- End of broadcast