[chef] Re: Decomposed Chef Server install

[Bryant Lippert < >]

Hi Ameir,

Here's Chef's documentation on how to do an HA installation on AWS: http://docs.chef.io/install_server_ha_aws.html

Could you do it via docker, sure. There are a number of different approaches you could take. I would suggest looking into the backup and restoration of your existing chef server: https://docs.chef.io/server_backup_restore.html After this I would suggest green-fielding an HA solution, and transferring your data to that implementation, if that's the route that you decide to take.

Best,

Bryant

On Thu, Sep 24, 2015 at 4:20 AM, Ameir A. < " target="_blank"> > 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.

Thanks,
Ameir

--

Bryant Lippert

Raindance 

" target="_blank">

M 302-465-4326