Sorry - re my previous post, I meant WITHOUT Fuse ... James Burnash, Unix Engineering T. 201-239-2248 [email protected] | www.knight.com
545 Washington Ave. | Jersey City, NJ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Burnash, James Sent: Friday, November 12, 2010 10:41 AM To: [email protected] Subject: Re: [Gluster-users] Exposing parts of a volume to specific clients? Mike - this will work - I've done it, as have many others on this list - but the fuse RPM will have to be installed on the clients, because they will only be able to access it as a fuse filesystem once it has been mounted via NFS. At least, that was my experience - anybody that has gotten it to work with FUSE please let us know how you did it. James Burnash, Unix Engineering -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mike Hanby Sent: Friday, November 12, 2010 10:25 AM To: [email protected] Subject: Re: [Gluster-users] Exposing parts of a volume to specific clients? So, to accomplish this right now I would need to disable the builtin NFS server, enable the OS NFS server, mount the Gluster file system and export as normal via /etc/exports? Just brainstorming here, Mike -----Original Message----- From: Shehjar Tikoo [mailto:[email protected]] Sent: Thursday, November 11, 2010 10:47 PM To: Mike Hanby Cc: [email protected] Subject: Re: [Gluster-users] Exposing parts of a volume to specific clients? Mike Hanby wrote: > Howdy, > > We have 18TB at our disposal to share via GlusterFS 3.1. My initial thought > was to create a single volume, comprised of 18 x 1TB bricks. The volume will > be used for user storage as well as storage for applications. > > Is there any way to create different exports for the various clients via NFS > and Gluster client? > > For example, the server used by our user base should be able to mount the > users directory on the gfs volume (nas-01:/gfs/users), where as the yum > repository server should only be able to mount nas-01:/gfs/repo > > Essentially, I only want to expose what's necessary for each client machine > to perform its roll. > > If this isn't possible directly within GlusterFS, I'm open to suggestions to > rethink my strategy. > Not possible yet. Its on the ToDo list. Thanks > Thanks, > > Mike > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
