Install Planning


#1

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


#2

On 12/14/2012 12:19 PM, 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.

Yes, this is what we do.

Is there any way to reliably sync the data between servers?

We don’t. A site has data that is specific to the site. Data is loaded
into Chef from Git, so Git is always the source of truth, and Chef
should be able to be blown away on the management node in the site and
reloaded easily from Git. This gets us out of the sync’ing data game,
and enables us to use source control for handling configuration change
management.

Best,
-jay


#3

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” markpimentel22@gmail.com 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


#4

Thanks for the help!

On Fri, Dec 14, 2012 at 12:36 PM, Adam Jacob adam@opscode.com 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” markpimentel22@gmail.com 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


Thanks,

Mark


#5

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 | sascha.bates@gmail.com | 612 850 0444 |
sascha.bates@skype | sascha_bates@yahoo |
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” markpimentel22@gmail.com 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