[chef] Re: Re: Chef server as a chef-client on itself ok?

[Ranjib Dey < >]

same here. Chef server is a chef client  too. some time the higher precedence environments control the lower precedence environments chef server,

e.g. prod chef -server  -> chef client to itself

staging chef server -> chef client to itself

ops chef server -> chef client to staging . Ops is the environment where all chef testing happens, the ops chef server has a CD (continuous deployment) recipe, which erase the chef server, and restore all chef artifacts (nodes, clients, cookbooks , databags etc) from git repo & backup. This enables us to test the whole backup restore mechanism, as well as ensures we dont have dangling cookbooks (not checked inside repo, not present in Berksfile, but still present in chef server),

best
ranjib

On Tue, Oct 8, 2013 at 12:00 PM, Mike < " target="_blank"> > wrote:

We do that. It's a machine that we're managing, and this way all the logic needed to build a Chef Server (and the components of such) are stored in Chef code.

-M

On Tue, Oct 8, 2013 at 2:57 PM, Eric Feldhusen < " target="_blank"> > wrote:

Any reason I shouldn't have the Chef server be a client on itself?  I have a couple of recipes that we roll out to all servers, like a NRPE configuration for monitoring by Nagios and specific user accounts. 

Eric Feldhusen