[chef] Re: Re: 2 environments on one machine

[Arnold Krille < >]

Hi,

On Wed, 14 Aug 2013 09:55:39 -0700 "steve ." 
<
 >
wrote:
> A Chef node can only be in one environment at a time.
> 
> Here are the options I can think of, in ascending order of complexity:
> * Spin up another machine.  (Hey, we're ordering by complexity, not
> cost...)

You may reduce complexity by running one of the chef-clients (and their
resources) inside an lxc-container.
Or define two lxc containers on the host (via chef:-), one for PROD
with its chef-"node" and one for UAT.

> * Move your per-environment logic into roles, data bags or an
> application cookbook.  Roles and data bags won't let you constrain
> cookbook versions, though.

This gets messy on the chef-side.

> * Run two Chef clients/nodes on the same host.  You'll need to pay
> special attention to all of your cookbooks to ensure that they either
> don't share any resources or, if they absolutely _have_ to share
> resources, that they agree on the state of those resources.
> Otherwise the conflicting resources will toggle back and forth
> between the state that production wants it and the state that UAT
> wants it.

This gets messy (and unreproducible) on the client-side.

Since I started using the pxe-dust cookbook, I would just fire up
another vm with like 2 minutes of work (have to tell the dhcp-server
and libvirt about the new vm) and while the base installs, define the
machine in chef and then do something else until the machine is ready
to serve...

Have fun,

Arnold

Attachment: signature.asc
Description: PGP signature