[chef] RE: Re: How to manage the configuration of chef server?

[Nico Kadel-Garcia < >]

I use ‘chef-solo’ from chefdk with a node configured for the chef server itself. Chefdk brings Berkshelf with it and saves compilation time for configuring Berkshelf the first time. Otherwise, bootstrapping the chef server itself can get nasty, especially if you make *any* mistakes, and especially if you ever have to rebuild the chef server from scratch.

 

 

Nico Kadel-Garcia

Lead DevOps Engineer

">

 

 

 

 

From: AJ Christensen [mailto:
Sent: Wednesday, January 28, 2015 9:40 PM
To:
Subject: [chef] Re: How to manage the configuration of chef server?

 

chef client registered itself, running the chef-server cookbook + any other firewall/management related cfg mgmt you need to run on your c.server boxen.

 

cheers,

 

--aj

 

On Thu, Jan 29, 2015 at 3:38 PM, Greg Barker < " target="_blank"> > wrote:

I wrote a little recipe to upgrade glibc for CVE-2015-0235 and it was easy enough to patch all my nodes. But now I'm wondering, how should I run this recipe on my Chef Server?

I had originally provisioned my Chef Server using a little fabric script that installs chef, git clones my chef repo, and runs chef-solo. I haven't had to run a converge on it since but now it's got me thinking, how do you guys handle config management of the Chef Server? How do you provision your initial Chef Server?

Thanks!
Greg