openstack/manila
Code Issues Proposed changes

Merge "doc: document the non-standard export semantics of Ganesha"

Browse Source
This commit is contained in:
Jenkins 2015-12-09 16:43:50 +00:00 committed by Gerrit Code Review
commit a47e2c9004
2 changed files with 31 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
doc/source/devref/ganesha.rst
View File

@ -185,6 +185,35 @@ Known Restrictions
- The library does not support network segmented multi-tenancy model but
instead works over a flat network, where the tenants share a network.
.. _ganesha_known_issues
Known Issues
------------
- The export location for shares of a driver that uses the Ganesha Library
will be of the format ``<ganesha-server>:/share-<share-id>``. However,
this is incomplete information, because it pertains only to NFSv3
access, which is partially broken. NFSv4 mounts work well but the
actual NFSv4 export paths differ from the above. In detail:
- The export location is usable only for NFSv3 mounts.
- The export location works only for the first access
rule that's added for the given share. Tenants that
should be allowed to access according to a further
access rule will be refused (cf.
https://bugs.launchpad.net/manila/+bug/1513061).
- The share is, however, exported through NFSv4, just
on paths that differ from the one indicated by
the export location, namely at:
``<ganesha-server>:/share-<share-id>--<access-id>``,
where ``<access-id>`` ranges over the ID-s of access
rules of the share (and the export with ``<access-id>``
is accessible according to the access rule of that ID).
- NFSv4 access also works with pseudofs. That is, the
tenant can do a v4 mount of``<ganesha-server>:/`` and
access the shares allowed for her at the respective
``share-<share-id>--<access-id>`` subdirectories.
The :mod:`manila.share.drivers.ganesha` Module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

@ -81,7 +81,8 @@ back to key based authentication, using the key specified by
one of the OpenSSH-style default key locations (*~/.ssh/id_{r,d,ecd}sa*).
For further (non driver specific) configuration of Ganesha, see
:doc:`ganesha`.
:doc:`ganesha`. It is recommended to consult with :doc:`ganesha`:
:ref:`ganesha_known_issues` too.
Layouts have also their set of parameters, see :ref:`glusterfs_layouts` about
that.