[chef] Re: Re: Re: Chef Solo experience / best practices?

[Jeremy Voorhis < >]

Ben Rockwood actually covers some of them on some of them in the video above.

Testing and development with Vagrant is a great reason to use and support chef-solo. Using chef-solo at a larger scale, lets you remove the dependency on chef-server and have more flexibility with your chef runs, but you lose the benefits of using knife for provisioning, and chef-server for inventory and node search.

Hope that helps,

Jeremy Voorhis

On Fri, Nov 2, 2012 at 2:06 PM, Jens Skott < " target="_blank"> > wrote:

As a chef newbe I have only read about chef-solo some, what are the advantages of running chef-solo vs the chef server version? 

Sent from my iPad

On 2 nov 2012, at 18:21, Jeremy Voorhis < " target="_blank"> > wrote:

Thanks Jeff,

The talk coincided with a few things I've heard about cookbook distribution (HTTP with ACLs) and chef-solo execution, and there's lots to think about here.

On Fri, Nov 2, 2012 at 7:33 AM, Jeff Blaine < " target="_blank"> > wrote:

On 11/1/2012 8:03 PM, Jeremy Voorhis wrote:

Ohai,

I'd like to know if anyone has had success using chef-solo for a
multi-node production deployment. I've heard and read reports of using
it with MCollective a couple years ago, but haven't heard much since.

Ben Rockwood uses it at Joyent.

http://www.youtube.com/watch?v=he7vxhm6v64