[chef] Re: Re: Chef Server - How to do High Availability?

[Tetsu Soh < >]

Hello,

Yes. you can wait for Chef 11. Or check out what I did.

- Set up multiple chef servers under balancer. 
You cal also separate servers into different data centers

- Using BigCouch cluster instead of  CouchDB.  
BigCouch works well with current chef. And clustering it is not difficult. 

- Using GlusterFS to store cookbooks.
Chef server will store cookbooks in local disk. It will be a problem if you 
have more than one chef server under load balancer. So we use GlusterFS to 
sync cookbook storing.
(Performance is not a problem)

- Using  SolrCloud instead of Solr as search engine.
SolrCould is still under development. But current version is stable enough 
for production.

- RabbitMQ can also achieve HA by using mirror  queue and persistent topic.
But rabbitmq is not so critical you can just skip it.

That's all.
That what I'm doing in our production environment.
Hope it is helpful.

Regards

Tetsu

On Sep 8, 2012, at 2:07 AM, Seth Falcon 
<
 >
 wrote:

> On Sep 6, 2012, at 9:57 PM, Julian C. Dunn wrote:
>> I'm hoping that with Chef 11, the data is stored in just one place rather 
>> than needing to have a couchdump & cookbook cache that's synchronized.
> 
> In Chef 11 all Chef data except for cookbooks are stored in the DB 
> (Postgres or MySQL). Cookbook contents are stored separately on the 
> filesystem named by file content checksum. So you will still need to load 
> dumps of both data stores to restore a Chef server.
> 
> + seth