Hmmm... but given that glusters fuse client is posix compliant, can't you just create a single volume and use a customized umask setup on user-named subdirectories in that volume to mimic this behaviour?
On Jul 2, 2013, at 7:25 PM, Joshua Hawn <[email protected]> wrote: > I've been looking into using Gluster to replace a system that we currently > use for storing data for several thousand users. With our current networked > file system, each user can create volumes and only that user has access to > their volumes with authentication. > > I see that Gluster also offers a username/password auth system, which is > great, but there are several issues about it that bother me: > > [1] Currently all the authentication related information is passed > un-encrypted over the network from client to server. > [2] Currently each volume is managed as a separate process on the server. > > [1] is a major security issue for me and [2] is a major scalablity issue. > > Are either of these issues going to be fixed in the next release or are there > any alternatives that Gluster offers? Also, is the authentication layer only > used by the Gluster FUSE client or is it possible with NFS or CIFS? > > I've also wondered if Gluster can support authentication on a sub-directory > level? If not, how complicated would it be to modify the source code to > enable it? This would enable us to go around the one-process-per-volume issue. > _______________________________________________ > Gluster-users mailing list > [email protected] > http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
