Shared filesystem management project for OpenStack.
76f8d3b948
Module 'lockutils' was released within 'oslo concurrency' lib and removed from oslo incubator. Use it from lib. Changes: - Removed local copy of 'lockutils' copied from incubator. - Config opt 'lock path' moved to separate config group 'oslo_concurrency'. Now it can be set for Devstack installation also by "OSLO_LOCK_PATH" env var. - Removed explicit usage of 'lockutils.synchronized' within Manila and reused it from manila.utils. Change-Id: I21257bc8c0a41dc1bb342deadbcf279c9f3b670d |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc | ||
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/openstack/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