Re: RFC: configuration via distributed database
On Tue, 6 Sep 2011 16:50:27 -0400
Jeff Darcy <jdarcy(a)redhat.com> wrote:
Kaleb deserves the credit for
pointing out that we already have a pretty good distributed database
available to us - GlusterFS itself, which already has some of the
distribution and self-healing features we need.
It is a clever idea if the chicken and egg problem gets resolved neatly.
But I'm just curious, did you guys think about using external
configuration management infrastructure, and if yes, what?
For example, we already rely on DNS (even if implicitly). How about
using the zone update feature to add-remove SRV records of servers
that have this "small private filesystem". They have port numbers.
Or, do not use private filesystem at all and roll our a Zookeeper
client (personally I hate both the complexity and verbosity of its API,
but I'm just asking).
Or, use rsyncd like in OpenStack (in Rackspace production really).
In short, I see what's approved but I wish to see what was rejected,
if you have the time to satisfy my curiosity.
When it starts up, hekafsd would go through [...]
Check whether this node is supposed to be a config-filesystem
server. If so, generate a simple server volfile and spin up an
instance of glusterfsd.
What does the "check" include, in more detail? Is there a seed
configuration file in /var/lib/hekafsd that "hfs_config init" creates?
-- Pete