Bug 764850 (GLUSTER-3118)

Previous versions (3.0.x) of Gluster which allowed for using configuration files, enabled us to set up multiple listeners on multiple networks for a single brick.  So when a client on a specific network connected to the volume, it would have no trouble accessing the brick in its entirety.

The current versions (3.1.x, 3.2.x) do not appear to enable this capability, without hand editing the volume files.  This leads to a path where you either have to avoid ever using the management tools after initial configuration, or you have to give up this capability.  As we have customers dependent upon this functionality, this is problematic to say the least.  They are effectively stuck at 3.0.x for the duration of their usage unless this feature makes its way back in via the management tools.

What I would suggest is adding a brick-alias feature to re-enable this capability.  So you could have

   gluster volume VOLNAME add-brick-alias BRICK-NAME ALIAS

where ALIAS is either a DNS name or an IP address.  You could have similar functions of remove-brick-alias, disable-brick-alias, enable-brick-alias, modify-brick-alias, etc.

  Then when a client connects from a particular subnet, the information returned to it is relative to that specific subnet.  So if you have two distinct nets, a 10GbE private net and a 1GbE public net, building the Gluster volume on the 10GbE private net will exploit the 10GbE whenever possible.  But using the 1GbE with fuse clients will still be possible.

  This is needed in a number of cases where the NFS client is not an acceptable alternative.