the seven habits of highly effective puppet users - puppetconf 2014

Seven Habits of Highly Effective Puppet Users

David Danzilio @djdanzilio

1

$(whoami)

2

What’s talk this about?

A collection of observations of high performing Puppet users

Habits?

What’s a habit?

“[A habit is] an acquired behavior pattern regularly followed until it has become almost involuntary”

Habits are hard

You don’t think about habits

Seven Habits• Think like a software developer

• Treat Puppet like code

• Stop, drop, and design

• Test all the things

• Continuous integration and deployment

• Make nice with Ruby

• Get involved


Habit #1 Think like a software developer

14Habit 1: Think like a software developer


You’re not a system administrator anymore



You’re a software developer



System Administration ≠

Software Development



Why did we think this would be easy?!



Puppet is easy because it’s a DSL


FALSEFALSE


We just made it easy to write bad code



You can’t expect people to be good at something they’ve never done


I’m a doctor, not an engineer.I’m a doctor, not an engineer.24


Software engineering is a mature discipline



This is particularly important in Puppet 4



Habit #2 Treat Puppet like code

27Habit 2: Treat Puppet like code


Stop thinking of Puppet as just configuration data



Infrastructure as CODE



Infrastructure as

CODE30Habit 2: Treat Puppet like code


Version Control



Documentation



README



Inline documentation



Refactoring



Code Review



Style



puppet-lint



Habit #3 Stop, drop, and design

46Habit 3: Stop, drop, and design


Software needs to be designed



Separation of Concerns



Package, File, Service



Roles and Profiles



Identify Interfaces



What information does your module need?



Where does that information come from?



Where does that information need to go?



Public and Private classes



Data Separation



Data in your Puppet code is bad



Hiera



params



Module data



Stability



Identify a stable feature set



Semantic Versioning



Simplicity



UNIX Philosophy



Focus on your module’s core functionality



Hooks



class jabberd ( ... $manage_package = true, $manage_repository = false, $manage_service = true, ... ) {

...

}



Write modules as if they’re going to be open sourced



Habit #4 Test all the things

71Habit 4: Create a culture of testing


The toolchain has improved dramatically



Testing has become relatively inexpensive



Your infrastructure is too important to not test



How?



puppet-syntax



rspec-puppet



describe ‘myclass’ do it { should compile.with_all_deps } end



beaker


Seven Habits of Highly Effective Puppet Users 82Habit 4: Create a culture of testing

kitchen-ci


serverspec



describe package('httpd') do it { should be_installed } end

describe service('httpd') do it { should be_enabled } it { should be_running } end

describe port(80) do it { should be_listening } end



Why test Puppet?



Complexity



Test first!



Make your tests count



it do should contain_file(‘/etc/ssh/sshd_config’).with({ ‘ensure’ => ‘present’, ‘owner’ => ‘root’, ‘group’ => ‘root’, ‘mode’ => ‘0644’, }) end



context ‘with port => 2222’ do let(:params) {{ :port => ‘2222’ }}

it do should contain_file(‘/etc/ssh/sshd_config’).with_content( %r{Port 2222} ) end end



Habit #5 Continuous Integration and

Deployment

93Habit 5: Continuous integration and deployment


Build a pipeline



Automated testing



Unit Tests



Integration Tests



Acceptance tests



Test under real world conditions



Puppet versions



Operating System versions



Ruby versions



Dependency versions



Automated deployment



librarian-puppet, r10k, MCollective, Capistrano



Habit #6 Make nice with Ruby

109Habit 6: Make nice with Ruby


Puppet is Ruby



Get over it



Why?



rake



rspec



bundler



guard



Custom Types, Providers, and Facts



If you want to do anything advanced



Habit #7 Get involved

121Habit 7: Get involved


Puppet is rapidly evolving



Your experience is valuable



Share your modules



Speak at conferences



Answer questions



Blog about it


Questions?

Thank you!

David Danzilio@djdanzilio

http://blog.danzilio.net

Image Credits

• http://simpsons.wikia.com/wiki/File:Homer-simpson-brain,1280x800,18857.jpg • https://dcarchives.files.wordpress.com/2014/06/habit-change-1964-mcphee-priller.jpg • http://www.quickmeme.com/meme/3plfef • http://www.quickmeme.com/Bad-Habit-Bruce • http://www.mememaker.net/static/images/templates/747303.jpg • http://knowyourmeme.com/photos/230191-wtf-is-this-shit • http://programmerryangosling.tumblr.com/image/22790837971 • http://www.quickmeme.com/img/d3/d36ad81bae0a8d69cd91f81065d8b0a19d9dfc1b63753093992282d6aa8b35dd.jpg • http://www.avatar3trailer.com/gangnam-style/gangnam_style_psy_05.jpg • http://www.troll.me/images/pissed-off-obama/refactor-your-fucking-code.jpg • http://www.globalnerdy.com/2011/05/30/ruby-foo/ • http://www.quickmeme.com/meme/3twnp6 • http://smashingboxes.com/ideas/beginners-guide-to-test-driven-development-tdd • http://www.pythian.com/blog/service-reliability-how-systems-administration-is-evolving-part-one/ • http://www.troll.me/2012/03/07/uncategorized/dont-worry-guys-i-got-programmer-cred/ • http://www.savthecoder.com/blog/saturday-meme-5-futurama-fry-tests-his-new-method • http://www.quickmeme.com/meme/3uc80p/ • http://i.qkme.me/3tde6j.jpg • http://i.qkme.me/3sekdw.jpg • http://www.quickmeme.com/meme/3sm9k1?id=229466593 • http://i.ytimg.com/vi/HUSSKWWg-0c/maxresdefault.jpg • http://blog.15five.com/wp-content/uploads/2013/09/Hypnosis_for_bad_habits_nyc.jpg • http://www.keepcalm-o-matic.co.uk/p/keep-calm-and-rtfm-27/

the seven habits of highly effective puppet users - puppetconf 2014

Technology

effective puppet users

puppet code

treat puppet

effective puppet users

effective puppet users

effective puppet users

effective puppet users

effective puppet users