fe675be832
Changes: - replaced direct usage of sychronized func from lockutils with local wrapper, that provides prefix; - 'lock_path' is not provided anymore as hardcode, defined 'lock_path' in config is expected; - added MANILA_LOCK_PATH to devstack plugin, to be able to set path before installation. Change-Id: I6518df0a6d32f1021b19a48f928f9ec8b00140b2 Closes-Bug: #1347915 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc/manila | ||
manila | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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