On 13/08/2013, at 12:05 PM, Kaushal M wrote: > Hi all, > We recently had a mailing list discussion about the current problems > with peer identification and handling multiple networks. This proposal > is regarding better identification of peers. > > Currently, the way we identify peers is not consistent all through the > gluster code. We use uuids internally and hostnames externally. This > setup works pretty well when all the peers are on a single network, > have one address, and are referred to in all the gluster commands with > same address. But once we start mixing up addresses in the commands > (ip, shortnames, fqdn) and bring in multiple networks we have > problems. > > The problems were discussed in the following mailing list threads and > some solutions were proposed. > - How do we identify peers? [1] > - RFC - "Connection Groups" concept [2] > > The solution to the multi-network problem is dependent on the solution > to the peer identification problem. So it'll be good to target fixing > the peer identification problem asap, ie. in 3.5 , and take up the > networks problem later. > > Thoughts? Sounds like a really good idea to me. :) Do you want to discuss potential implementation ideas here, or write up a Feature Page first, or ? Regards and best wishes, Justin Clift > - Kaushal > > -- > [1] http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00067.html > [2] http://lists.gnu.org/archive/html/gluster-devel/2013-06/msg00069.html > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > https://lists.nongnu.org/mailman/listinfo/gluster-devel -- Open Source and Standards @ Red Hat twitter.com/realjustinclift
