d1722c4d2f
We have two types of share drivers. First type supports creation of share servers and second does not. Then, we have approach of "network plugin" for handling of networking and it is useful only with first type of share drivers. So, we should restrict instantiation of network plugins with second type of share drivers. It will allow us to remove unused dependencies for running some share drivers. Change-Id: Ib7d6a9ff1b6ce0d5d2bca350040363ea1461c419 Closes-Bug: #1417087 |
||
---|---|---|
bin | ||
contrib | ||
doc | ||
etc | ||
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/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