[chef] Re: Decomposed Chef Server install

[Noah Kantrowitz < >]

On Sep 24, 2015, at 2:20 AM, Ameir A. 
<
 >
 wrote:

> Hello,
> 
> We're currently running Chef Server with the monolithic installer, with 
> everything running on one node; the only exception is that the bookshelf is 
> backed by S3.
> 
> I've been asked to investigate resiliency, and in that effort, would like 
> to split Chef Server up by its individual components, and offload what I 
> can to managed services (like Redis And Postgres on Elasticache and RDS, 
> respectively).
> 
> I found the following image, with a breakdown of the different components:
> https://docs.chef.io/_images/chef_server_ha.svg
> 
> Suppose I were to split each component into its own Docker container (which 
> isn't what I'm set on, necessarily, but for the sake of discussion); how 
> would I do so?  Is it possible via the RPM/DEB packages to just install 
> individual components?  Also, is it safe to assume that all state is 
> present solely in Redis, Postgres, and Solr (and the bookshelf, of course)?
> 
> Any insight would be well-appreciated.

The general way the Chef HA packages do this IIRC is to install the whole 
omnibus package on each node but disable services that aren't needed there so 
the DB machines turn off erchef/nginx/bifrost/etc and vice versa. This can be 
done via the chef-server.rb config file.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail