RETIRED, Common scheduler for OpenStack
faace205a0
Instead of a hard-coded MANIFEST.in to list non-code files to be included in the tarball, use the setuptools-git plugin to ensure that every file that's in git will wind up in the tarball. The only things needed in MANIFEST.in now are files that are generated as part of the sdist run. Change-Id: I76df685d58f7b56977d859e8df92e845f450b3e4 |
||
---|---|---|
bin | ||
doc | ||
nova | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
Authors | ||
babel.cfg | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
tox.ini |
The Choose Your Own Adventure README for Nova
You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://nova.openstack.org
To dissect it in detail: visit http://github.com/openstack/nova
To taunt it with its weaknesses: use http://bugs.launchpad.net/nova
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING
To cry over its PEP-8 problems: http://jenkins.openstack.org/job/gate-nova-pep8/violations