<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 13, 2013 at 4:05 AM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
We recently had a mailing list discussion about the current problems<br>
with peer identification and handling multiple networks. This proposal<br>
is regarding better identification of peers.<br>
<br>
Currently, the way we identify peers is not consistent all through the<br>
gluster code. We use uuids internally and hostnames externally. This<br>
setup works pretty well when all the peers are on a single network,<br>
have one address, and are referred to in all the gluster commands with<br>
same address. But once we start mixing up addresses in the commands<br>
(ip, shortnames, fqdn) and bring in multiple networks we have<br>
problems.<br>
<br>
The problems were discussed in the following mailing list threads and<br>
some solutions were proposed.<br>
- How do we identify peers? [1]<br>
- RFC - "Connection Groups" concept [2]<br>
<br>
The solution to the multi-network problem is dependent on the solution<br>
to the peer identification problem. So it'll be good to target fixing<br>
the peer identification problem asap, ie. in 3.5 , and take up the<br>
networks problem later.<br>
<br>
Thoughts?<br></blockquote><div><br></div><div>Thanks for the proposal Kaushal. This is a welcome change. It will be great to have all internal identifiers for peers to happen through UUID and get translated into a host/IP at the most superficial layer. There are open issues around node crash + re-install with same IP (but new UUID) which needs to be addressed in this effort.</div>
<div><br></div><div>Avati</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Kaushal<br>
<br>
--<br>
[1] <a href="http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00067.html" target="_blank">http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00067.html</a><br>
[2] <a href="http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00069.html" target="_blank">http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00069.html</a><br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br>
<a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div></div>