Upgrade to Pro — share decks privately, control downloads, hide ads and more …

What's In This Cookbook?

What's In This Cookbook?

or, How do I know what I’m eating?

An Ignite that touches on Opscode Chef's Cookbooks, and an attempt to help describe a Cookbook Versioning Policy (CVP).

Mike Fiedler

June 06, 2013
Tweet

More Decks by Mike Fiedler

Other Decks in Technology

Transcript

  1. What’s In This Cookbook? or, How do I know what

    I’m eating? Thursday, June 6, 13
  2. Mike Fiedler Operations Datadog.com Twitter: @mikefiedler GitHub: @miketheman Ops School

    Chef-Community Roller Derby Ref Skydiver ©Alex Erde Thursday, June 6, 13
  3. It starts with... • good intentions • roll your own

    code • open source a solution • desire to release goodness frequently Thursday, June 6, 13
  4. Bring on Versions! RHEL 6.0 2010-11-09 RHEL 6.1 2011-05-19 RHEL

    6.2 2011-12-06 RHEL 6.3 2012-06-20 RHEL 6.4 2013-02-21 Flickr: Alan Dayley Thursday, June 6, 13
  5. X.Y.Z apache 2.2.0 2.2.23 2.4.3 postgresql 9.0.13 9.1 9.1.9 9.2.4

    python 2.6.6 2.6.8 2.7.5 Thursday, June 6, 13
  6. Enter CVP Cookbook Versioning Policy: Sane Versioning for Chef Cookbooks

    http://chef-community.github.io/cvp/ Mad props to Kevin Christen! Thursday, June 6, 13
  7. Public API • External interfaces • Names other recipes may

    be using • Libraries, Providers & Resources • Templates used via Providers Thursday, June 6, 13
  8. Minor Versions • Adding non-breaking features • New recipe, resource,

    provider • New attribute w/default value • Relaxing constraints Thursday, June 6, 13
  9. Mike’s Version Theory • Don’t break stuff • Don’t surprise

    others • Breaking something? Be LOUD! • Use similar practices for internal code Thursday, June 6, 13
  10. Speak to me about: Chef DevOps OpsSchool Automation Wine Skydiving

    Roller Derby #HugOps Thursday, June 6, 13