×
Copy
Open
Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Testing Cookbooks
Slide 2
Slide 2 text
Sean OMeara!
[email protected]
! @someara
Slide 3
Slide 3 text
whoami
Slide 4
Slide 4 text
Writing Cookbooks
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
Are we done?
Slide 9
Slide 9 text
Testing Cookbooks
Slide 10
Slide 10 text
Slightly more involved.
Slide 11
Slide 11 text
The Basics http://www.flickr.com/photos/jronaldlee/5295169486/
Slide 12
Slide 12 text
Run the recipe See what happens
Slide 13
Slide 13 text
Manual techniques Automated techniques
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
CLI IS BETTER
Slide 17
Slide 17 text
ChefDK
Slide 18
Slide 18 text
Our toolchain is in Ruby
Slide 19
Slide 19 text
Standard Ruby dev setups are tricky to install
Slide 20
Slide 20 text
System Ruby! RVM! chruby
Slide 21
Slide 21 text
cd project ; bundle install
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
Put the code in the can.
Slide 25
Slide 25 text
OMNIBUS ChefDK! ! Stable toolchain in an Omnibus installer
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
Ruby! Chef! Test Kitchen! kitchen-vagrant! Berkshelf! Foodcritic! Rubocop! ChefSpec
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
Converge Testing
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
CaaP! vs! IaaP
Slide 33
Slide 33 text
Cookbook as a Project! vs! Infrastructure as a Project
Slide 34
Slide 34 text
no chef-repo
Slide 35
Slide 35 text
battery not included
Slide 36
Slide 36 text
kitchen-vagrant! kitchen-docker! kitchen-ec2! kitchen-rackspace! kitchen-gce! kitchen-digitalocean! kitchen-openstack! kitchen-bluebox! kitchen-joyent! kitchen-lxc also available
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
Integration Testing ttps://www.flickr.com/photos/kitsa_sakurako/439652830
Slide 48
Slide 48 text
Test that a set of resources have achieved their combined goal
Slide 49
Slide 49 text
{ testable intent
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
Test Kitchen runs integration tests out of band of Chef
Slide 53
Slide 53 text
It does this with bussers
Slide 54
Slide 54 text
Bats! Serverspec! Minitest! Cucumber
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
suite busser
Slide 57
Slide 57 text
No content
Slide 58
Slide 58 text
No content
Slide 59
Slide 59 text
kitchen test! ! kitchen converge! kitchen verify! kitchen destroy
Slide 60
Slide 60 text
test tear down
Slide 61
Slide 61 text
Style Testing
Slide 62
Slide 62 text
No content
Slide 63
Slide 63 text
Ruby level style enforcement
Slide 64
Slide 64 text
No content
Slide 65
Slide 65 text
No content
Slide 66
Slide 66 text
No content
Slide 67
Slide 67 text
No content
Slide 68
Slide 68 text
No content
Slide 69
Slide 69 text
No content
Slide 70
Slide 70 text
single quotes space after comma no trailing whitespace
Slide 71
Slide 71 text
No content
Slide 72
Slide 72 text
No content
Slide 73
Slide 73 text
Chef level style enforcement
Slide 74
Slide 74 text
No content
Slide 75
Slide 75 text
No content
Slide 76
Slide 76 text
No content
Slide 77
Slide 77 text
No content
Slide 78
Slide 78 text
No content
Slide 79
Slide 79 text
http://www.flickr.com/photos/40389360@N00/2428706650/ Regression Testing
Slide 80
Slide 80 text
ChefSpec makes assertions about compiled resource collections
Slide 81
Slide 81 text
No content
Slide 82
Slide 82 text
No content
Slide 83
Slide 83 text
No content
Slide 84
Slide 84 text
No content
Slide 85
Slide 85 text
No content
Slide 86
Slide 86 text
REFERENCE SLIDE
Slide 87
Slide 87 text
No content
Slide 88
Slide 88 text
No content
Slide 89
Slide 89 text
No content
Slide 90
Slide 90 text
https://github.com/opscode-cookbooks/yum https://github.com/opscode-cookbooks/mysql Reference Cookbooks https://github.com/opscode-cookbooks/jenkins https://github.com/opscode-cookbooks/yum-epel
Slide 91
Slide 91 text
Cookbook Dependencies
Slide 92
Slide 92 text
Often, a cookbook will depend on another
Slide 93
Slide 93 text
include_recipe ‘another_cookbook::recipe’! ! OR! ! consume a resource shipped in another_cookbook
Slide 94
Slide 94 text
For example
Slide 95
Slide 95 text
No content
Slide 96
Slide 96 text
No content
Slide 97
Slide 97 text
not in core Chef
Slide 98
Slide 98 text
ships in mysql cookbook
Slide 99
Slide 99 text
No content
Slide 100
Slide 100 text
No content
Slide 101
Slide 101 text
Dependencies suck and you don’t want to manage them manually.
Slide 102
Slide 102 text
No content
Slide 103
Slide 103 text
Berkshelf is bundler for Chef cookbooks
Slide 104
Slide 104 text
No content
Slide 105
Slide 105 text
your chef-server here
Slide 106
Slide 106 text
No content
Slide 107
Slide 107 text
Bundler installs dependencies into your local gem cache
Slide 108
Slide 108 text
Berkshelf installs dependencies into your local cookbook cache
Slide 109
Slide 109 text
No content
Slide 110
Slide 110 text
No content
Slide 111
Slide 111 text
No content
Slide 112
Slide 112 text
No content
Slide 113
Slide 113 text
No content
Slide 114
Slide 114 text
No content
Slide 115
Slide 115 text
needs moar ServerSpec
Slide 116
Slide 116 text
Continuous Integration
Slide 117
Slide 117 text
This is all driven from the command line
Slide 118
Slide 118 text
Which makes it super easy to wire into CI systems
Slide 119
Slide 119 text
CI should watch version control for commits
Slide 120
Slide 120 text
Polling! vs! Notifications
Slide 121
Slide 121 text
I ran out of slides!