[Bugs] [Bug 1285126] GlusterFS NFS does not implement an all_squash volume setting

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1285126

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |FutureFeature, Triaged
                 CC|                            |eruby at knowledgematters.net,
                   |                            |ndevos at redhat.com
          Component|cli                         |protocol
            Version|3.7.6                       |mainline
              Flags|                            |needinfo?(eruby at knowledgema
                   |                            |tters.net)

Red Hat Bugzilla <bugzilla at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Doc Type|Bug Fix                     |Enhancement



--- Comment #1 from Niels de Vos <ndevos at redhat.com> ---
Advanced configuration options for uid/gid squashing is available through
NFS-Ganesha. Only very little work is put into Gluster/NFS, NFS-Ganesha will
become the preferred NFS-server in the future. If you rely on this
functionality, you probably should give NFS-Ganesha with FSAL_GLUSTER a try.

---

The server.*-squash options are not NFS specific, they are usable for FUSE
mounts and libgfapi access as well.

It probably makes sense to provide a server.all-squash option that makes all
access to the volume done through the anonymous user/group (anonuid/anongid).
However, the server.root-squash is volume wide option, and can only be turned
on/off. It might be more useful to have a server.all-squash option that checks
for the IP-address instead of an all-or-nothing switch.

Earl, could you explain a little about the expected feature and config options
that you would like to see?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.