[Gluster-devel] RFC - "Connection Groups" concept

Justin Clift jclift at redhat.com
Wed Jun 26 09:25:40 UTC 2013


On 26/06/2013, at 9:28 AM, Stephan von Krawczynski wrote:
<snip>
>> This is an idea that's been on my mind for a while, to overcome a
>> fundamental problem Gluster has with some network common topologies.
>> (thanks to Niels de Vos for letting me bounce ideas off him btw)
>> 
>> Most corp places I've worked have multiple network interfaces on their
>> storage boxes, each for a specific purpose (eg backup interface, client
>> interface, general connectivity interface, and more).
>> 
>> At present Gluster can't really make use of this kind of topology
>> effectively.  Having some interfaces only for client traffic, other
>> interfaces for peer replication traffic just isn't how it's designed.
>> 
>> To address this, we could introduce "connection groups".
>> [...]
>> Thoughts? :)
>> 
>> Regards and best wishes,
>> 
>> Justin Clift
> 
> Dear Justin,
> 
> it was pretty easy to use such an infrastructure in times of glusterfs 2.X
> where an admin had true control over the ongoing with a _config file_. Since
> the whole 3.X mess started really nothing was improved besides the automatic
> self-heal. The network part has become unusable in terms of controlling what
> is really going on and where.

Interesting point.  I barely remember 2.x from the brief times I was trying
that out (before I joined Red Hat). :)

That being said, the "controlled" approach (my wording) in 3.x is here to
stay, so let's fix its weaknesses.

What do you reckon about of the general concept in my email? ;>

Regards and best wishes,

Justin Clift

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift





More information about the Gluster-devel mailing list