Good afternoon, I'm a user of glusterfs (and debian & ubuntu) and have some pointers which I hope will help move this bug along. The new glusterfs 3.1 series is substantially different from the 3.0 series, and although this package does include the new 3.1 series code, I believe it still provides the old 3.0 series initial configuration & initscript. I think this is why the gluster command does not work. What follows is a quick run-through of the major differences in 3.1 which would need to be addressed in the package to enable the new gluster command features, followed by a note about one solution I've come up with.
In glusterfs 3.1 there is a new "management daemon," called glusterd, which handles creation of volfiles and management of the glusterfsd (brick export) daemons. The new glusterd executable is actually just a symlink, /usr/sbin/glusterd -> /usr/sbin/glusterfsd. There is also a new initscript provided in the 3.1 series source tarball (glusterfs-3.1.3/extras/init.d/glusterd-Debian) which, when placed in /etc/init.d/glusterd, starts & stops the new glusterd daemon. Managing the glusterfsd daemon directly with /etc/init.d/glusterfs-server is no longer appropriate, since that is now handled through the gluster command with 'volume start' & 'volume stop'. The new glusterd daemon requires a specific volfile, /etc/glusterfs/glusterd.vol, to get going, which is also included in the glusterfs 3.1 source tarball (glusterfs-3.1.3/doc/glusterd.vol.) Once the new glusterd management daemon is running, the 'gluster' command (elastic volume manager) should work as one expects. A couple more notes about volfiles in 3.1... volfiles are now created, modified, and distributed to clients entirely automatically by the new glusterd management daemon, which stores them under /etc/glusterd/vols. Clients (using the new /sbin/mount.glusterfs script) will retrieve the volfile from a server, and receive any subsequent changes made to the volume through the gluster command automatically. Except for the glusterd management volfile, /etc/glusterfs/glusterd.vol, I believe no other files are needed in /etc/glusterfs with 3.1 when using the new management daemon as it stores generated configuration files under /etc/glusterd. Also, for what it's worth, I've made some changes to the Debian Sid source package for glusterfs 3.1.3 which enable the new gluster command functionality. I've put a derived source package with my modifications in an Ubuntu Launchpad PPA, mainly for my own use, but of course everyone is welcome to it. This is the first Debian package I've ever made, and I welcome any feedback about it. I think my modified source package will build on Debian Sid, but haven't tried it. Furthermore, due to the major changes in glusterfs 3.1, it may break existing systems if you try to upgrade to it, so take caution. My modified glusterfs-3.1.3 source package is available in the PPA here: https://launchpad.net/~semiosis/+archive/ppa<https://launchpad.net/%7Esemiosis/+archive/ppa> Hope this helps. Thank you, -louis zuckerman
