<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 5-2-2014 7:43, Sahina Bose wrote:<br>
</div>
<blockquote cite="mid:52F1DD96.601@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 02/03/2014 07:18 PM, Juan Pablo
Lorier wrote:<br>
</div>
<blockquote cite="mid:52EF9E1A.6030702@gmail.com" type="cite">
<pre wrap="">Hi,
I've created my first wiki page and I'd like someone to review it and
tell me if there's something that need to be changed (besides it does
not have any style yet)
The URL is
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ovirt.org/oVirt_Wiki:How_to_change_Gluster%27s_network_interface">http://www.ovirt.org/oVirt_Wiki:How_to_change_Gluster%27s_network_interface</a>
Regards,
</pre>
</blockquote>
<br>
Firstly, thanks for putting this information up!<br>
<br>
Some comments -<br>
<br>
1. when you use different IP addresses for engine -to -gluster
host (say IP1) and gluster -to -gluster communication (say IP2),
operations from ovirt engine like add brick or remove brick would
fail (as brick is tried to be added with IP1 which gluster does
not understand)<br>
<br>
To work around this, it is better to use a FQDN both for
registering the host with engine and also to peer probe the host
from gluster CLI.<br>
You could have multiple IP addresses on the host resolve to the
same FQDN. <br>
<br>
</blockquote>
That is how I use it in my test setup. 2 storage nodes which have an
entry in their hosts file with a different IP (172.1.1.1/2) then
what engine has or gets from DNS (split dns).<br>
So engine knows storage1 by ip 192.168.1.1 and on the storage
network storage1 is known by 172.1.1.1. You'll need to replicate the
hosts file to all storage/virt hosts that you have and all need 2
interfaces, one for storage and one for ovirtmgmt. You can use
engine to create gluster volumes because engine will use the
hostname and send the command to the storage where the hostname
resolves to the storage network.<br>
<br>
There is a post/blog on gluster.org (Joe Julian??) that uses
iptables to achieve the same trick but I like the dns one better.<br>
<br>
Joop<br>
<br>
</body>
</html>