Shared filesystem management project for OpenStack.
9157b8afb2
Use looser error code checking and add a verify after deny access so that the call will succeed whenever it can be confirmed that the access no longer exists. This fixes a variety of situations where previously a return code of 1 while attempting to remove access would cause the manila access rule to get stuck while the actual client access export was removed or never existed. Change-Id: Ie058a6185e3f5d91fb1cf232301eb0ac6ddcea7e Closes-Bug: #1651587 |
||
---|---|---|
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc | ||
install-guide/source | ||
manila | ||
manila_tempest_tests | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/Manila
- Developer docs: http://docs.openstack.org/developer/manila
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://github.com/openstack/manila.git
For developer information please see HACKING.rst
You can raise bugs here http://bugs.launchpad.net/manila