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
cstewart@momentumsi.commailto:cstewart@momentumsi.com
www.momentumsi.comhttp://www.momentumsi.com/
[cid:71466434-A311-4F82-BC03-F7D6BA0FA526]http://www.momentumsi.com/http://www.momentumsi.com/
Cloud Migration - Architecture - DevOps - Big Data - App Dev
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" cstewart@momentumsi.com 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
cstewart@momentumsi.com
www.momentumsi.com
<80BB855A-341B-44CC-8CD6-44C237EBA7A5[5].png>
Cloud Migration - Architecture - DevOps - Big Data - App Dev
We freeze them the moment they are uploaded to the Chef Server, and use
environment files to pin versions allowing us to promote a frozen cookbook
up through our environments.
On Tue, May 13, 2014 at 9:38 AM, Pete Cheslock petecheslock@gmail.comwrote:
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" cstewart@momentumsi.com
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
cstewart@momentumsi.com
www.momentumsi.com
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
cstewart@momentumsi.commailto:cstewart@momentumsi.com
www.momentumsi.comhttp://www.momentumsi.com/
[cid:71466434-A311-4F82-BC03-F7D6BA0FA526]http://www.momentumsi.com/http://www.momentumsi.com/
Cloud Migration - Architecture - DevOps - Big Data - App Dev
On May 13, 2014, at 8:38 AM, Pete Cheslock <petecheslock@gmail.commailto:petecheslock@gmail.com> 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” <cstewart@momentumsi.commailto:cstewart@momentumsi.com> 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
cstewart@momentumsi.commailto:cstewart@momentumsi.com
www.momentumsi.comhttp://www.momentumsi.com/
<80BB855A-341B-44CC-8CD6-44C237EBA7A5[5].png>http://www.momentumsi.com/http://www.momentumsi.com/
Cloud Migration - Architecture - DevOps - Big Data - App Dev
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 deploy_cookbook.sh · GitHub
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 cstewart@momentumsi.comwrote:
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
cstewart@momentumsi.com
www.momentumsi.com
On May 13, 2014, at 8:38 AM, Pete Cheslock petecheslock@gmail.com
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" cstewart@momentumsi.com
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
cstewart@momentumsi.com
www.momentumsi.com
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 andrew@yipit.com 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 deploy_cookbook.sh · GitHub
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 cstewart@momentumsi.comwrote:
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
cstewart@momentumsi.com
www.momentumsi.com
On May 13, 2014, at 8:38 AM, Pete Cheslock petecheslock@gmail.com
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" cstewart@momentumsi.com
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
cstewart@momentumsi.com
www.momentumsi.com
Yes, berks behavior is to freeze by default.
On Wed, May 14, 2014 at 10:41 AM, Pete Cheslock petecheslock@gmail.comwrote:
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 andrew@yipit.com 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 deploy_cookbook.sh · GitHub
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 <cstewart@momentumsi.com
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
cstewart@momentumsi.com
www.momentumsi.com
On May 13, 2014, at 8:38 AM, Pete Cheslock petecheslock@gmail.com
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" cstewart@momentumsi.com
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
cstewart@momentumsi.com
www.momentumsi.com