- From: "Durfee, Bernie (GE Global Research)" <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Re: Chef-Solo to Chef-Zero
- Date: Tue, 2 Sep 2014 21:52:52 +0000
- Accept-language: en-US
Thanks Mathias!
I like this and am going to use it. But from what I understand chef-solo
is going to be replaced at some point by chef-client running in local mode.
Are there plans to get chef-runner working with chef-client local mode?
Bernie
On 9/2/14, 5:15 PM, "Mathias Lafeldt"
<
>
wrote:
>
That's exactly the workflow chef-runner was made for:
>
>
https://github.com/mlafeldt/chef-runner
>
>
The tools prepares all cookbooks locally using e.g. Berkshelf, uploads
>
them to the server via rsync (very fast), and finally runs Chef Solo.
>
>
-Mathias
>
>
>
On Tue, Sep 2, 2014 at 11:12 PM, Daniel DeLeo
>
<
>
>
wrote:
>
> On Tuesday, September 2, 2014 at 2:07 PM, Durfee, Bernie (GE Global
>
>Research) wrote:
>
>> A common workflow I use isŠ
>
>>
>
>> 1. Change my cookbook
>
>> 2. Run Œberks package¹ to build a complete tarball of my cookbook with
>
>>all dependencies
>
>> 3. SCP to a server
>
>> 4. Run Œsudo chef-solo -o ³recipe[my-fancy-cookbook::default]" -r
>
>>cookbooks-1409688848.tar.gz¹ to test the cookbook
>
>> 5. Repeat
>
>>
>
>> Is this workflow possible with chef-client in local mode? Can I pass
>
>>chef-client a tarball that was created by the Œberks package¹ command?
>
>>
>
>> Thanks!
>
>
>
> You¹d probably use `berks vendor` to get your cookbook set into a
>
>directory and rsync that over instead of shipping a tar archive. You¹d
>
>have the same basic flow, slightly different commands.
>
>
>
> --
>
> Daniel DeLeo
>
>
>
>
>
>
Archive powered by MHonArc 2.6.16.