[Gluster-devel] Glusterd: A New Hope

Jeff Darcy jdarcy at redhat.com
Sun Mar 24 23:03:07 UTC 2013

On 03/24/2013 04:43 AM, Stephan von Krawczynski wrote:
> So the automated distribution of the vol-files does not help
> the majority at all.

It's not just about distribution of volfiles.  It's also about ensuring
their consistency across many servers and clients, and handling dynamic
updates.  For dynamic configuration changes without reboots or even
remounts, you either need glusterd or you need to reinvent a good
portion of it.  Even you should be able to appreciate the value of that,
since dynamic configuration speeds the tuning process.  Then there are a
whole bunch of other features that I mentioned in my last reply, which
you should read this time before rushing to give the broken record
another spin.

> you just
> said you cannot solve this by yourself and want to drop it on external
> know-how

Nobody said anything of the sort.  We *can* solve it for ourselves, but
there's no reason we should expend our own resources to solve the parts
of the problem that are already well solved elsewhere.  There's no
question that there will still be plenty of domain-specific
functionality left for us to deal with ourselves.  Leveraging other
projects is just basic software-engineering good sense, as it allows us
to devote more resources to enhancements in other areas - including
those you've said need improvement.  Reinventing the wheel would be
stupid, and forcing each user to reinvent their own would be worse.

More information about the Gluster-devel mailing list