[chef] Re: Re: Re: Re: Re: More on Cookbook Design Patterns


Chronological Thread 
  • From: Lamont Granquist < >
  • To:
  • Cc: , Jay Perry < >
  • Subject: [chef] Re: Re: Re: Re: Re: More on Cookbook Design Patterns
  • Date: Thu, 03 Apr 2014 10:04:22 -0700

On Thu Apr  3 08:33:44 2014, Tom Duffield wrote:
In your acme_tomcat cookbook you could have a recipes that handle
Acme, Co specific tomcat user implementation (acme_tomcat::users),
security (acme_tomcat::security), or monitoring
(acme_tomcat::monitoring).

yeah, i do like this model.

then your base role includes the appropriate recipes to give you LWRPs for adding users and setting up monitoring, and you get good locality so that your tomcat config isn't scattered across separate security, monitoring and users cookbooks. its appropriate to extract this stuff because its just not base role stuff, its all about what it means to be a generic tomcat server in your infrastructure. ideally acme_tomcat would then expose LWRPs that you'd then use in recipes for application instances.






Archive powered by MHonArc 2.6.16.

§