[chef] Re: Re: Multiple Chef Servers on Different Ports

[mark bradley < >]

Hi Bryan, that's pretty much what I thought but wanted to check my idea before starting to install and configure (and suffer debugging pains :) ). I'm not expecting *many* clients, fewer that 100, so I think I'll go with one each of couchdb and rabbitmq and use multiple databases and multiple queues.

I can't run 2 VMs, because:

a) I'm running in an EC2 instance and cannot further virtualize :)

b) I really simplified the question and have other environments (QA, UAT, etc.) in between DEV and PROD. I can't afford that many servers for this project.

Mark

On Fri, Mar 9, 2012 at 12:39 PM, Bryan McLellan < "> > wrote:

On Fri, Mar 9, 2012 at 11:58 AM, mark bradley < "> > wrote:
> I have several git repos to manage changes to different environments (say
> DEV + PROD). Is it pretty straight-forward to run chef-server on different
> ports and have the DEV clients connect to the DEV port and PROD to the PROD
> port? Will I need to configure different rabbitmq queues and couchdb
> database for each one?
>
> If any has pointers to docs (Google hasn't help here) or has experience
> doing this I'd appreciate it.

I'd start here: http://wiki.opscode.com/display/chef/Chef+Configuration+Settings

The trick is that you'll need to be running two of everything. You can
make decisions like two couchdb servers or one with two databases, and
two rabbitmq servers or one with multiple vhosts? Theoretically you
can set all this. If you do it, I'd love to hear your success. I'd
personally just run two VMs because it leaves you with a more standard
installation that is easier to scale.

Bryan