openstack
/
manila
Code Issues Proposed changes

glusterfs: document Gluster NFS misbehavior 

Gluster NFS does not disrupt pre-existing mounts
on access revocation.

Change-Id: Ie0a10a495acf78744bd534fc7ebb190c242036c0
Partial-Bug: #1506659
This commit is contained in:
Csaba Henk 2015-12-17 01:46:24 +01:00
parent 51069d5390
commit 7ffde21559
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/devref/glusterfs_driver.rst
View File

@ -181,6 +181,13 @@ Known Restrictions
currently created within a single GlusterFS volume of a GlusterFS storage
pool.
- The driver does not provide read-only access level for shares.
- Assume that share S is exported through Gluster NFS, and tenant machine T
has mounted S. If at this point access of T to S is revoked through
`access-deny`, the pre-existing mount will be still usable and T will still
be able to access the data in S as long as that mount is in place.
(This violates the principle *Access deny should always result
in immediate loss of access to the share*, see
http://lists.openstack.org/pipermail/openstack-dev/2015-July/069109.html.)
The :mod:`manila.share.drivers.glusterfs` Module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~