b29a0e553f
A share managed in HSP could have some access rules that are not in Manila. Trying to add a rule that already exists in backend results in an error. Also, rules in backend that names are not "share_id + ip" can't be deleted. Additionally, if this share has a rule only in backend and not in Manila, trying to delete it would fail, because HSP doesn't allow delete share when it still has rules. Fix it by adding a check in update access when rules already exist in backend. Check for access rule name in backend when denying access. And cleaning all rules from backend before deleting a share to ensure that it has no children in HSP. Change-Id: I0c8ee5c47efe22f004692022dd952f301d669b06 Closes-Bug: #1620756
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