RETIRED, Common scheduler for OpenStack
Go to file
Joe Gordon b1de4523f3 Do not run pylint by default
pylint creates some files, and leaves git in a detached HEAD.

pylint can still be run via 'tox -epylint'

Change-Id: Ic0193f2488f1c6eb4a9f0fabbe24ac9869239890
2012-08-28 15:14:11 -07:00
bin Implement project specific flavors API 2012-08-27 23:45:05 +08:00
doc Add two prereq pkgs to nova devref env guide 2012-08-23 09:18:34 +10:00
nova Merge "Fixes backwards compatible rpc schedule_run" 2012-08-28 02:26:07 +00:00
.coveragerc Finalize tox config. 2012-06-07 12:15:42 -04:00
.gitignore Ignoring *.sw[op] files 2012-08-16 20:40:20 -03:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Update .mailmap 2012-08-25 18:24:04 +09:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
HACKING.rst OpenStack capitalization added to HACKING.rst 2012-08-17 15:59:32 -05: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 Add the plugin framework from common; use and test. 2012-07-15 16:25:26 -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 Merge "Disable I18N in Nova's test suites" 2012-08-20 07:53:47 +00:00
setup.cfg Finalize tox config. 2012-06-07 12:15:42 -04:00
setup.py Merge "Refactor instance_usage_audit. Add audit tasklog." 2012-07-11 17:06:42 +00:00
tox.ini Do not run pylint by default 2012-08-28 15:14:11 -07: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