Quick question - is there a way to test a new version of a cookbook with the same name, without breaking existing servers already provisioned?
For example, say I have a tomcat cookbook that’s working, but I wanted to try a different one…but I don’t want to mess all the existing boxes up.
Is this possible? I’m using Chef 0.10.
Thanks.
-Matt
Yes, have a look at Environments in Chef 0.10. You can specify which
versions of a cookbook ought to be used in each environment. In your
case, you can have the old version of a cookbook in your "production"
environment, and the new one in your “testing” environment.
http://wiki.opscode.com/display/chef/Environments
Ringo
You could use environments for this. For production hardcode versions of
cookbooks. And testing environment might use the latest versions.
On Jun 27, 2011 3:42 PM, "Matthew Drobnak" mdrobnak@ringleaderdigital.com
wrote:
Quick question - is there a way to test a new version of a cookbook with
the same name, without breaking existing servers already provisioned?For example, say I have a tomcat cookbook that's working, but I wanted to
try a different one...but I don't want to mess all the existing boxes up.Is this possible? I'm using Chef 0.10.
Thanks.
-Matt
That's kind of what I figured. Thanks everyone.
Where is this set again? I know I saw it, but I can't remember where.
-Matt
On Jun 27, 2011, at 7:58 AM, Денис Барышев wrote:
You could use environments for this. For production hardcode versions of cookbooks. And testing environment might use the latest versions.
On Jun 27, 2011 3:42 PM, "Matthew Drobnak" <mdrobnak@ringleaderdigital.commailto:mdrobnak@ringleaderdigital.com> wrote:
Quick question - is there a way to test a new version of a cookbook with the same name, without breaking existing servers already provisioned?
For example, say I have a tomcat cookbook that's working, but I wanted to try a different one...but I don't want to mess all the existing boxes up.
Is this possible? I'm using Chef 0.10.
Thanks.
-Matt
Hi.
Check out these links, they'll show you how to pin cookbook versions down.
http://wiki.opscode.com/display/chef/Environments
-s
On Mon, Jun 27, 2011 at 8:02 AM, Matthew Drobnak
mdrobnak@ringleaderdigital.com wrote:
That's kind of what I figured. Thanks everyone.
Where is this set again? I know I saw it, but I can't remember where.
-Matt
On Jun 27, 2011, at 7:58 AM, Денис Барышев wrote:You could use environments for this. For production hardcode versions of
cookbooks. And testing environment might use the latest versions.On Jun 27, 2011 3:42 PM, "Matthew Drobnak" mdrobnak@ringleaderdigital.com
wrote:Quick question - is there a way to test a new version of a cookbook with
the same name, without breaking existing servers already provisioned?For example, say I have a tomcat cookbook that's working, but I wanted to
try a different one...but I don't want to mess all the existing boxes up.Is this possible? I'm using Chef 0.10.
Thanks.
-Matt