<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Jul 23, 2015 3:41 PM, "Timo Schaepe" <<a href="mailto:info@timoschaepe.de">info@timoschaepe.de</a>> wrote:<br>
><br>
> Hey guys,<br>
><br>
> we are trying to use gluster 3.6.4 in a cloud environment. Creating the gluster itself is not a problem. Mounting the created vol from a machine in the cloud infrastructure is not a problem. But when I am trying to mount the created gluster vol from an external machine it fails. In the log files of the client I can see that gluster is annoucing the bricks with the cloud infrastructure internal ips, which are not accessible from outside of the cloud. When I change the internal ips to the public domain names in /var/lib/glusterd/gv0.tcp-fuse.vol on every cluster host it works seamless. I definitely think that this is not the recommended way to solve this problem. Of course it breaks, if I add another bricks to the gluster.<br>
><br>
> Is there a possibility to change the annouced ip adresses?<br>
> Or is there another way to solve this problem?<br>
Probably in that case its better to peer probe using public domain name instead of internal IP?<br>
><br>
> Thanks,<br>
><br>
> Timo<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</p>