[chef] Re: Re: Re: Chef 11 in production


Chronological Thread 
  • From: Anton K < >
  • To:
  • Subject: [chef] Re: Re: Re: Chef 11 in production
  • Date: Fri, 19 Apr 2013 09:14:44 +0300

Thank you for the answers. I've started to use chef-server(11) in a production, but still using chef-client 10.24.0 at the workstation and nodes, because of memory leak problems with 11.4.0.



On Tue, Apr 16, 2013 at 11:45 PM, steve . < " target="_blank"> > wrote:
We haven't formally discussed this at work, but I think our upgrade plan will look something like this:

Once we get our mitts on the equivalent Private Chef version and install it in testing, we'll get people to test their cookbooks off the test endpoint.  (We're looking forward to it, though -- knife-lastrun bombed out our older Chef 10.x server through some bizarre bug that had nodes running many node.save()s per Chef run and freaked out Solr.  We're hoping this goes away once the back-end switches to Postgres -- knife-lastrun's nice to have, IMO.)  With the new version on our test endpoint, we can run our repos through our test framework until they all turn green again.  Then we'll know we're ready to roll it out to our thousands of production nodes..



On Tue, Apr 16, 2013 at 1:11 PM, Bryan McLellan < " target="_blank"> > wrote:
On Tue, Apr 16, 2013 at 8:37 AM,  < " target="_blank"> > wrote:
> I am new in a Chef's community. Does anyone use already Chef 11.x in
> production? Is it stable for production?

Yes.

Cycle Computing was an early adopter of Chef 11:
http://www.opscode.com/case-studies/opscode-case-study-cycle-computing.pdf

As well as Facebook:
http://www.opscode.com/press-releases/facebook-likes-opscode-and-private-chef/

And those were a couple of months ago. As John noted, it is in
production all over the place now.

Bryan





Archive powered by MHonArc 2.6.16.

§