Shared filesystem management project for OpenStack.
993e7489fa
Switch to BaseTestCase as base class for all Manila test classes. This BaseTestCase class automatically uses the following fixtures: * fixtures.FakeLogger (only if needed) * fixtures.NestedTempfile * fixtures.TempHomeDir so we don't have to explicit add them to our constructor. Change-Id: I336d024f7008f5300e1882fa960a8e32439a9a70 |
||
---|---|---|
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