[chef] Re: Re: Re: To Freeze or Not to Freeze

[Pete Cheslock < >]

I missed Curtis's original reply but we use Berks upload.  Which if i'm remembering correctly will freeze by default.

On Wed, May 14, 2014 at 11:39 AM, Andrew Gross < " target="_blank"> > wrote:

I use the same style as David.  The workflow is managed mostly using `knife-spork`. To deploy a cookbook to an environment we use a command similar to https://gist.github.com/andrewgross/b6612087007ba437cd69

NOTE: We actually use 2 different Chef Servers, one for production and one for staging, but the workflow remains largely the same.

On Tue, May 13, 2014 at 9:56 AM, Stewart, Curtis < " target="_blank"> > wrote:

Thanks for the reply, Pete!

Is your upload/freeze process done manually via ‘knife-cookbook-upload —freeze”?  Or do you use something like Berkshelf or knife-spork for cookbook uploading?

Curtis Stewart

Consultant

m 217.390.5067

Skype cstewart8710

" target="_blank">

www.momentumsi.com

 

Cloud Migration - Architecture - DevOps - Big Data - App Dev

On May 13, 2014, at 8:38 AM, Pete Cheslock < " target="_blank"> > wrote:

I would freeze on every upload by default.  I would not want a cookbook with the same version but with a change get uploaded to the server and break something. We use pinned versions in our environment files so that ensure that environment must change for the change to be applied.  

-Pete

On May 13, 2014, at 9:32 AM, "Stewart, Curtis" < " target="_blank"> > wrote:

How do most folks determine when a cookbook should be frozen?  Or even whether or not to freeze them at all.  Is it once a cookbook is used in a deployment?  Or, is it every time a cookbook is uploaded to the server?

Thanks,

Curtis

Curtis Stewart

Consultant

m 217.390.5067

Skype cstewart8710

" target="_blank">

www.momentumsi.com

 

<80BB855A-341B-44CC-8CD6-44C237EBA7A5[5].png>

Cloud Migration - Architecture - DevOps - Big Data - App Dev