[chef] RE: Re: Cookbook Architecture


Chronological Thread 
  • From: "Nguyen, Dang" < >
  • To: " " < >
  • Subject: [chef] RE: Re: Cookbook Architecture
  • Date: Wed, 17 Oct 2012 08:11:17 -0700
  • Accept-language: en-US
  • Acceptlanguage: en-US

My team uses the same methodology as John.


From: John Martinez
Sent: Wed, Oct 17, 2012 07:53 AM
To:
Subject: [chef] Re: Cookbook Architecture

We do separate versions of cookbooks and define what versions to use
in environments. Package versions are node attributes.

So, the latter.

-john

On Oct 17, 2012, at 7:48 AM, " " < > wrote:

> Hi Chefs,
>
> We have come across this design pattern many times when building out our
> cookbooks and can't quite decide which makes the most sense. Do you write your
> cookbook such that the latest version of the cookbook can install any version
> of the application it is installing/configuring or do you create separate
> versions of the cookbook for each version of the cookbook (i.e. each cookbook
> version installs only one version of the software)? The Opscode cookbooks seem
> to go with the first strategy but we have found we can make simpler cookbooks
> by going with the second strategy.
>
> Any thoughts?



Archive powered by MHonArc 2.6.16.

§