We faced this problem at one customer place where the frontend management network was different (10.0.100.x), and backend network where glusterfs storage nodes talk to each other was different (10.0.200.x, on a higher speed network). Now, when I goto web interface, and create the volume, it creates glusterfs volume files (mainly the client volumes) with IP, instead of hostnames. Due to this, GlusterFS volume files need manual change in storage platform.. Resolving hostname to IP should not be done IMO, we can discuss more on making this option automated so that volumefiles support both the networks. I would like to tag this bug with 'major' severity, as we are getting more and more users who use it in above mentioned setup.. -Amar
(In reply to comment #0) > We faced this problem at one customer place where the frontend management > network was different (10.0.100.x), and backend network where glusterfs storage > nodes talk to each other was different (10.0.200.x, on a higher speed network). > Now, when I goto web interface, and create the volume, it creates glusterfs > volume files (mainly the client volumes) with IP, instead of hostnames. Due to > this, GlusterFS volume files need manual change in storage platform.. > > Resolving hostname to IP should not be done IMO, we can discuss more on making > this option automated so that volumefiles support both the networks. > > I would like to tag this bug with 'major' severity, as we are getting more and > more users who use it in above mentioned setup.. > > -Amar Amar, I would like to know does both networks carry same hostname?. This can be fixed with a one line in glusterfs-volgen. But i wanted to know how was the other network configured? and did they carry the same hostname? Supporting multiple hostnames for a single machine is a feature which should be implemented nevertheless. Regards Harshavardhana
(In reply to comment #1) > > I would like to know does both networks carry same hostname?. Actually, if its hostname, ppl can have each network's dns server resolve it to different IP (or even put it in /etc/hosts), so there is no change is required in volumefile. If it has hardcoded IP, we have to manually edit the volume file. _Amar
(In reply to comment #2) > (In reply to comment #1) > > > > I would like to know does both networks carry same hostname?. > > Actually, if its hostname, ppl can have each network's dns server resolve it to > different IP (or even put it in /etc/hosts), so there is no change is required > in volumefile. > > If it has hardcoded IP, we have to manually edit the volume file. > > _Amar But this is not possible through webUI right now to have multiple hostnames? i think?.
This can be fixed by just passing the hostname values rather than converting them into IP. This will go in 3.0.3 release
PATCH: http://patches.gluster.com/patch/2774 in master (Remove dns lookup issued for each hostnames.)
PATCH: http://patches.gluster.com/patch/2776 in release-2.0 (Remove dns lookup issued for each hostnames.)
PATCH: http://patches.gluster.com/patch/2775 in release-3.0 (Remove dns lookup issued for each hostnames.)