[chef-dev] Re: Re: Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes

[Noah Kantrowitz < >]

On Mar 27, 2012, at 1:04 AM, Ringo De Smet wrote:

> 
> 
> On 22 March 2012 23:28, Peter Donald 
> <
 >
>  wrote:
> 
> It seems like this is an attempt to jury-rig something onto the chef
> model rather than changing the model. It seems like the use case is
> actually adhoc execution of commands/resource installation using the
> chef syntax? If so why not add the ability to distribute a one-shot
> command to chef clients when needed. Then these application deploys
> and/or apt-get upgrades or whatever could be run through this system
> and regular infrastructure maintenance can continue to use the
> existing approach. I think trying to merge the two approaches may lead
> to a bit of complexity when adopting chef.
> 
> Tools to perform one-shot commands over a set of machines:
> * http://rundeck.org/
> * http://docs.puppetlabs.com/mcollective/
> 
> The latter can read Chef or Ohai metadata.
> 
> No need to change Chef for that.

An application deploy is never a single command anymore, it is complex set of 
SCM repos and config files at the very least.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail