Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up
for free
Cookbook Reusability
someara
October 02, 2014
Technology
0
140
Cookbook Reusability
Chef Summit 2014
someara
October 02, 2014
Tweet
Share
More Decks by someara
See All by someara
someara
0
92
someara
0
170
someara
1
170
someara
2
230
someara
2
480
someara
3
460
someara
2
350
someara
2
230
someara
10
6k
Other Decks in Technology
See All in Technology
ihcomega56
1
440
soracom
0
510
mamix1116
3
390
viva_tweet_x
1
360
hanacchi
0
140
pohjus
0
3.3k
mmarukaw
0
1.8k
line_developers
PRO
0
170
kotatsu360
2
830
you
0
270
kaedemalu
0
310
yuzutas0
8
2.8k
Featured
See All Featured
colly
188
14k
frogandcode
128
20k
sferik
610
54k
jrom
116
7.2k
swwweet
206
6.9k
nonsquared
81
3.4k
tanoku
258
24k
wjessup
339
16k
moore
125
21k
gr2m
83
11k
holman
288
130k
shlominoach
176
7.5k
Transcript
Cookbook Reusability! Chef Community Summit 2014
Sean OMeara! someara@getchef.com! @someara
whoami
A Year in Review
Diversification
7zip! apache2! ark! application*! couchdb! Imagemagick! java
logrotate! mercurial! munin! nagios! nginx! ntp! openvpn
pacman! postgresql! python! reprepro! rabbitmq! runit! supervisor
selinux! tmux! varnish ! wordpress!
Supermarket https://www.flickr.com/photos/mobilestreetlife/10885044043
• Escaped the tyranny of JIRA! • Moved to Github
Issues! • Automated CLA checking! • OSS Artifact Repository
Rewrites
2009 0.5.2 Chef Vagrant ChefSpec 0.1.0 0.0.2 Minitest-Chef Berkshelf Test
Kitchen 2010 0.9.0 2011 0.10.0 2012 10.12.0 1.0.0 0.2.0 1.0.0 0.7.0 1.0.0 2013 2014 1.0.0 2.0.0 1.0.0 2.0.0 1.4.0 11.0.0 12.0.0 1.6.5 3.0.0 3.0.0 1.2.2 ServerSpec ChefDK 0.0.1 2.0.0 0.2.2 TDI Capability 0.8.0
yum! yum-*! jenkins! mysql! httpd
The Evolution of a Chef Cookbook
Stage 1 - Paradise https://www.flickr.com/photos/nattu/1385100375/
None
test / repair test / repair test / repair
Easy to read Easy to grok Easy to test }
Stage 2 - if statements
logic compiled into resource collection
Resource DSL } Just Ruby }
Resource DSL } Just Ruby } }Chef
Stage 3 - Crazytown https://www.flickr.com/photos/kwl/4595324641
None
wat
Why?
Reusable is useful
Cross-platform is useful
We desire useful things
Platform idioms are hard
Keeping the Dream Alive https://www.flickr.com/photos/kalexanderson/7014655351/
Most people just write their own cookbooks from scratch
I really really really want reusable cross-platform cookbooks
Lessons Learned
Attributes are routinely abused https://www.flickr.com/photos/jabberwocky381/2828863789
None
Attributes are an interface
Attributes are tunable knobs
None
You probably just want a variable
None
Or even a method
None
Using an attribute to track state during a Chef run
causes tears and sorrow
Prefer resource parameters
None
None
Primitives are more useful than opinionated policy
“They’re Just Resources”! ! LWRP is Googleable
Zoom out a level! ! Think about services and runtimes,
not files and processes
Singleton resources are good but confusing. Possibly even dangerous.! !
Multiple instance support is better! ! Cross-platform resources are best
None
BDD / TDD yields high quality cookbooks https://www.flickr.com/photos/glenirah/4376553184
Test Kitchen! ServerSpec / Minitest / Bats! ChefSpec
2009 0.5.2 Chef Vagrant ChefSpec 0.1.0 0.0.2 Minitest-Chef Berkshelf Test
Kitchen 2010 0.9.0 2011 0.10.0 2012 10.12.0 1.0.0 0.2.0 1.0.0 0.7.0 1.0.0 2013 2014 1.0.0 2.0.0 1.0.0 2.0.0 1.4.0 11.0.0 12.0.0 1.6.5 3.0.0 3.0.0 1.2.2 ServerSpec ChefDK 0.0.1 2.0.0 0.2.2 This Slide Again 0.8.0
Full test coverage is tedious
Full test coverage is totally worth it
Let users bring their own configurations
It is better to add to a resource_collection than to
monkey patch it
Configuration files are the brains of a service
Manage minimal configuration to get a service running
Offload further configuration to the user
conf.d is your friend
Hide everything else inside a resource
Add resource parameters when appropriate
None
None
Cross-platform cookbooks are hard https://www.flickr.com/photos/glenirah/4376553184
Cross-platform resources are even harder
They can be done!
Create a resource
None
Create a provider
None
Subclass platform providers
None
None
None
None
None
Set provider default for platforms
None
Do Repeat Yourself
Some resources are often the duplicated across providers
That’s fine. It’s the pattern as a whole that’s important
Maximize for grokability
People will be reading your code for the first time
during operations work
Init systems are annoying
Using a service resource usually requires file or template resources
in addition to service[thingd]
Debconf! Docker! LaunchD! Runit! SMF! Simple! SystemD! Sysvinit! Upstart! Windows
Services
Subclassing is awesome
None
Customize before recipe compilation
Going Forward
Cookbooks that ship resource primitives
More examples to copy
More breaking backwards compatibility (sorry)
Providers implemented with Docker containers (why not?)
chef-metal
Tell me what you think
Please don’t hurt me =)
None