My suggestion is actually to not use Gluster currently for XenServer. A bug I filed about two years ago for using Gluster as a XenServer back-end was just fixed in 3.3. If you're going to use Gluster+Xen, use 3.3. As for NFS, make sure that you changed the NFS port to 2049 in the configuration and that should fix pretty much the front-end issues with Gluster and Xen. Justice -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Gerald Brandt Sent: Thursday, April 19, 2012 7:46 AM To: gluster-users Subject: Gluster 3.2.6 for XenServer Hi, I have Gluster 3.2.6 RPM's for Citrix XenServer 6.0. I've installed and mounted exports, but that's where I stopped. My issues are: 1. XenServer mounts the NFS servers SR subdirectory, not the export. Gluster won't do that. -- I can, apparently, mount the gluster export somewhere else, and then 'mount --bind' the subdir to the right place 2. I don't really know python, though I could fuddle my way through it, I guess. What I thought would be cool, was to modify the nfs.py mount script. If the 'Advanced Options' field contained the word gluster, then instead of an NFS mount happening, it would do the gluster mount. All the magic of the NFS mount would remain, and happen on the gluster one. Does this sound feasible? Is there anyone fluent in python that wants to help? Gerald _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
