Shared filesystem management project for OpenStack.
13f0446ed5
Remove rootwrap code copied from oslo-incubator, make manila-rootwrap a console_script entrypoint pointing in oslo.rootwrap instead. Partially-implements blueprint use-common-code Change-Id: I519e8dec24dc9c48243af41dc0f423c05a0d92e2 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc/manila | ||
manila | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
The Choose Your Own Adventure README for Manila
You have come across an OpenStack shared filesystem service. It has identified itself as "Manila." It was abstracted from the Cinder project.
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 https://wiki.openstack.org/wiki/Manila
To dissect it in detail: visit http://github.com/stackforge/manila
To taunt it with its weaknesses: use http://bugs.launchpad.net/manila
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst
To cry over its pylint problems: http://jenkins.openstack.org/job/manila-pylint/violations