[chef] Re: Re: Install Planning

[Sascha Bates < >]

We have a CI job that manages the code in the Chef Server. After passing 
linting, syntax and cookbook tests and converging on test nodes, we have 
a sync job that makes sure everything that should be in the Chef Servers 
is there and anything that shouldn't gets deleted. That helps with the 
mystery knife syndrome too (people knifing in quick fixes and not 
commiting).

Sascha


Sascha Bates | 
  | 612 850 0444 | 

  | 
  |
On 12/14/12 11:36 AM, Adam Jacob wrote:
> We recommend the same. Don't sync between datacenters - when you need to,
> it's easy enough to build tooling that talks to N environments (either for
> search aggregation, knife ssh enhancements, etc.)
>
> Adam
>
> On 12/14/12 9:19 AM, "Mark Pimentel" 
> <
>  >
>  wrote:
>
> > Could anyone provide some insight as to the best way to manage chef in a
> > multisite environment.
> >
> >
> > The desire seems to be to have a chef server local to each datacenter.
> >
> >
> > Is there any way to reliably sync the data between servers?
> >
> >
> > Or have one "master" that gets updates from all other servers?
> >
> >
> > What are the pitfalls in deploying chef this way?
> >
> >
> > --
> > Thanks,
> >
> > Mark