- From: Adam Jacob <
>
- To:
- Subject: [chef] Re: High availability for chef
- Date: Tue, 5 Jul 2011 10:42:10 -0700
On Mon, Jul 4, 2011 at 7:30 AM,
<
>
wrote:
>
As we move configuration of more critical components to our chef server, we
>
need to implement some sort of high availability solution for our chef
>
server.
>
>
Any one has experience in that matter ?
>
>
a) Is replication of couchdb, solr index viable ? or
It depends on what level of HA you require. For both CouchDB and Solr,
you can handle this with DRBD and passive failover for what is usually
sub-second takeover on failure - this is also good for things like
cookbook uploads (stick /var/chef on the DRBD drives.)
You can also make each component HA on their own, using the mechanisms
the upstream recommends - Replication in both cases you list above.
>
b) it is more simple to just re-create the database from source code
>
of cookbook, roles and databags ? in that case how to make sure that we
>
don´t have to re-register each node
You likely want to be keeping an active replica (either with app
replication or disk-level replication) for your failover - this helps
in DR, but that's what backups are for.
Best,
Adam
--
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E:
Archive powered by MHonArc 2.6.16.