Hide Forgot
A customer has requested a feature where when client gets a client vol file from server process, the vol file should have the appropriate IP addresses (depending on which interface the client connects to) - Can we do anything about this? If client resolved the domain name to correct IP addresses it will work as expected but stew mentioned that maintaining DNS entires will be painful for him. This is something we have not discussed at Gluster.
(In reply to comment #0) > A customer has requested a feature where when client gets a client vol file > from > server process, the vol file should have the appropriate IP addresses > (depending on which interface the client connects to) - Can we do > anything about this? If client resolved the domain name to correct IP > addresses it will work as expected but stew mentioned that maintaining > DNS entires will be painful for him. This is something we have not discussed at > Gluster. Krishna can you explain further about this feature. Is it about "volfile" during the fetch-spec should resolve the hostnames to their respective IP's? Its quite confusing. Thanks
The storage servers have 3 IP addresses for the box (for 3 separate physical interfaces). Say IP1 IP2 IP3. Now clients connecting from IP2 network should fetch the client volfile from the server and the volume file should have remote-host as IP2 and not IP1 (if not it will say "no route to host"). The customer requested us to handle such a setup. We can solve this at the platform level by maintaining separate volume files for each IP address. Or we can solve it at the FS level by making remote-host accept a list of comma separated IP addresses in the volume definition (so it will act like DNS round robin) Bala knows about this as he was also in the customer visit. Let me reassign this to Avati as it looks like it will be much simpler if we handle this situation at the FS level. Avati, can you take a look? > Krishna can you explain further about this feature. > > Is it about "volfile" during the fetch-spec should resolve the hostnames to > their respective IP's? > > Its quite confusing. > > Thanks
Just had a call with the customer. He mentioned that the feature is low priority.
We can have multiple volume files per interface/ip like volume.ip1.vol volume.ip2.vol volume.ip3.vol one can decide which interface to connect by choosing one of the below commands # mount -t glusterfs host:/volume.ip1 /mnt/glusterfs # mount -t glusterfs host:/volume.ip2 /mnt/glusterfs # mount -t glusterfs host:/volume.ip2 /mnt/glusterfs This is achievable in all of 3.1.x series will be working for all future releases also. Hence closing it as fixed.