OpenStack resource provider inventory allocation service
Go to file
Monty Taylor 277d3a862d Finish AUTHORS transition.
The code to generate the authors file from the git changelog has been in the
tree and running for a few weeks now. Somehow the removal of the authors
test and and the MANIFEST.in file were wrong though. This should clean that
up.

Fixes bug 920757.

Change-Id: I66c388c1c81804f8dabc52b5ee25c7f394921e11
2012-07-05 09:11:37 -05:00
doc Removes RST documentation and moves it to openstack-manuals 2012-04-30 12:45:48 -05:00
nova Modifies ec2/cloud to be able to use Cinder 2012-07-03 12:00:40 -07:00
.coveragerc Finalize tox config. 2012-06-07 12:15:42 -04:00
.gitignore Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04: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
README.rst Flesh out the README file with a little more useful information 2012-06-29 17:11:10 +01:00
setup.cfg Finalize tox config. 2012-06-07 12:15:42 -04:00
setup.py Merge "Use setuptools-git plugin for MANIFEST." 2012-06-28 21:38:53 +00: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