Download as PDF, PPTX
![( How GitHub Writes Puppet augeas { 'my.cnf/performance': context => '/files/etc/mysql/my.cnf/mysqld', changes => [ # automatic dump/restore 'set innodb_auto_lru_dump 18000', # innodb "set innodb_buffer_pool_size ${innodb_buffer_pool_size}", 'set innodb_log_file_size 256M', 'set innodb_log_buffer_size 8M', 'set innodb_lazy_drop_table 1', ], require => Percona::Server[$::fqdn] }](https://image.slidesharecdn.com/puppet-at-github-puppetconf-2013-130823164329-phpapp02/75/Puppet-at-GitHub-PuppetConf-2013-95-2048.jpg)
Uploaded byPuppet
Puppet at GitHub - PuppetConf 2013
The document discusses the state and future of Puppet at GitHub. It describes how GitHub has been using Puppet for over 5 years to manage over 600 nodes, open sourcing many Puppet modules. It also outlines best practices for writing, testing, and deploying Puppet code used at GitHub, including tools like Puppet Lint, RSpec Puppet, and continuous integration/deployment. The future of Puppet at GitHub includes upgrading to Puppet 3.x and Ruby 2.0, integrating more with PuppetDB and their GPanel configuration tool, and potentially using MCollective.
Puppet at GitHub - PuppetConf 2013
- 1.
- 2. @wfarr GitHub Operations Known Aliases: King ofKebabs The Chairman Mr. Caremad !
- 3. The State ofPuppet at GitHub "
- 4. " The Stateof Puppet at GitHub github/boxen
- 5. " The Stateof Puppet at GitHub ~1.5 years old
- 6. " The Stateof Puppet at GitHub open-sourced ~7 months ago
- 7. " The Stateof Puppet at GitHub ~240 open-source puppet modules
- 8. " The Stateof Puppet at GitHub puppet 3.latest
- 9. " The Stateof Puppet at GitHub supports ruby 1.8.7, 1.9.3, 2.0.0
- 10. " The Stateof Puppet at GitHub hiera
- 11. " The Stateof Puppet at GitHub OS X
- 12. " The Stateof Puppet at GitHub Linux support in-progress
- 13. " The Stateof Puppet at GitHub # tomorrow @ 2:20pm
- 14. " The Stateof Puppet at GitHub github/puppet
- 15. " The Stateof Puppet at GitHub $
- 16. " The Stateof Puppet at GitHub ~5 years old
- 17. " The Stateof Puppet at GitHub 0.24.x — 2.7.x
- 18. " The Stateof Puppet at GitHub 121 modules
- 19. " The Stateof Puppet at GitHub ~280k lines of code
- 20. " The Stateof Puppet at GitHub every single employee has commit access
- 21. " The Stateof Puppet at GitHub 15.5k commits to master past 12 months
- 22. " The Stateof Puppet at GitHub by 86 contributors
- 23. " The Stateof Puppet at GitHub % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %
- 24. " The Stateof Puppet at GitHub % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % 42.5%
- 25. " The Stateof Puppet at GitHub % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % now with ops taken out
- 26. " The Stateof Puppet at GitHub 0 100 200 300 400 2012-08-25 2012-10-20 2012-12-15 2013-02-09 2013-04-06 2013-06-01 2013-07-27 commits on master per week, last 12 months
- 27. " The Stateof Puppet at GitHub 0 1000 2000 3000 4000 total commits by author past year
- 28. " The Stateof Puppet at GitHub 0 175 350 525 700 total commits by author past year, except ops
- 29. " The Stateof Puppet at GitHub 0 175 350 525 700 total commits by authors with >10 commits, past year, except ops
- 30. " The Stateof Puppet at GitHub single puppetmaster
- 31. " The Stateof Puppet at GitHub rubygems
- 32. " The Stateof Puppet at GitHub ruby 1.8.7
- 33. " The Stateof Puppet at GitHub unicorn
- 34. " The Stateof Puppet at GitHub puppet 2.7.latest
- 35. " The Stateof Puppet at GitHub ~600 nodes
- 36. " The Stateof Puppet at GitHub run hourly via crond
- 37. " The Stateof Puppet at GitHub puppetdb
- 38. " The Stateof Puppet at GitHub nagiosdb
- 39. " The Stateof Puppet at GitHub "yo puppetdb, gimme all your nagios::object::* resources so I can update this nagios config"
- 40. " The Stateof Puppet at GitHub filtergendb
- 41. " The Stateof Puppet at GitHub "yo puppetdb, gimme all the filtergen::rule resources I would realize so I can update this filtergen config"
- 42. " The Stateof Puppet at GitHub ⚡ puppetdb ⚡
- 43. " The Stateof Puppet at GitHub as it turns out, an api call is faster than running puppet on a host
- 44. " The Stateof Puppet at GitHub gpanel
- 45. " The Stateof Puppet at GitHub "Imagine Puppet Dashboard meets Razor and went on a weekend trip to the beach with the Heroku API and drank epic amounts of blue drink"
- 46. " The Stateof Puppet at GitHub aka we reinvented our own, smaller version of Foreman
- 47. " The Stateof Puppet at GitHub inventory
- 48. " The Stateof Puppet at GitHub
- 49. " The Stateof Puppet at GitHub
- 50. " The Stateof Puppet at GitHub app configuration
- 51. " The Stateof Puppet at GitHub
- 52. " The Stateof Puppet at GitHub versioning of configuration values
- 53. " The Stateof Puppet at GitHub Create nil => 1 Update 1 => 2 Delete 2 => nil
- 54. " The Stateof Puppet at GitHub let's make credential rolling less awful
- 55. " The Stateof Puppet at GitHub provisioning
- 56. " The Stateof Puppet at GitHub provisioning is typically awful
- 57. " The Stateof Puppet at GitHub we sprinkled in some ChatOps
- 58. " The Stateof Puppet at GitHub
- 59. " The Stateof Puppet at GitHub a little bit later...
- 60. " The Stateof Puppet at GitHub <MACHINE>
- 61. " The Stateof Puppet at GitHub enc
- 62. " The Stateof Puppet at GitHub we have the dumbest ENC out there
- 63. " The Stateof Puppet at GitHub ⋆
- 64. " The Stateof Puppet at GitHub # /usr/local/sbin/fetch_gpanel_enc fe1.rs.github.com --- parameters: gpanel_cabinet: D20-13 gpanel_enabled: true gpanel_monitored: false
- 65. " The Stateof Puppet at GitHub we never specify classes via the ENC
- 66. " The Stateof Puppet at GitHub any variables we pass through are prefixed with gpanel_
- 67. How GitHub writesPuppet (
- 68. ( How GitHubWrites Puppet rodjek/puppet-lint
- 69. ( How GitHubWrites Puppet
- 70. ( How GitHubWrites Puppet if you aren't using puppet-lint to audit your puppet codebase, you are doing it wrong
- 71. ( How GitHubWrites Puppet puppet-lint enforces the Puppet Labs style guide
- 72. ( How GitHubWrites Puppet puppet-lint can even fix a ton of linter errors for you
- 73. ( How GitHubWrites Puppet put it in a pre-commit hook
- 74. ( How GitHubWrites Puppet $ git commit -am "can't lint this" modules/github/manifests/role/redis.pp: syntax ok modules/github/manifests/role/redis.pp - WARNING: => is not properly aligned on line 118 1 errors found, aborting commit.
- 75. ( How GitHubWrites Puppet and then buy rodjek a beer
- 76. ( How GitHubWrites Puppet rodjek/rspec-puppet
- 77. ( How GitHubWrites Puppet
- 78. ( How GitHubWrites Puppet if you aren't writing tests for your puppet code before running it on a server, you are doing it wrong
- 79. ( How GitHubWrites Puppet use whatever framework/library
- 80. ( How GitHubWrites Puppet rspec-puppet just happens to be a pretty good one
- 81. ( How GitHubWrites Puppet put it in a pre-commit hook
- 82. ( How GitHubWrites Puppet $ git commit -am "tests dont pass but whatever lol" 1) Expected redis::server would include class "more_than_a_single_c_thread" 1 failures encountered, aborting commit.
- 83. ( How GitHubWrites Puppet and then buy rodjek another beer
- 84. ( How GitHubWrites Puppet node definitions
- 85. ( How GitHubWrites Puppet we don't use an ENC to describe node classes
- 86. ( How GitHubWrites Puppet node /^github-redisd+/ { class { 'github::role::polling_redis': enabled => $::gpanel_enabled, environment => $::gpanel_environment, private_ipv4 => $::ipaddress, } }
- 87. ( How GitHubWrites Puppet abstractions all the way down
- 88. ( How GitHubWrites Puppet treat your site classes as cascades down to your dist classes
- 89. ( How GitHubWrites Puppet class redis::server( # params ) { class { 'redis::config': ... } -> class { 'redis::package': ... } ~> class { 'redis::service': ... } }
- 90. ( How GitHubWrites Puppet class github::redis( # params ) inherits github::defaults { $memory = $environment ? { 'stg' => '2G', default => $half_memory_gb } class { 'redis::server': ... } }
- 91. ( How GitHubWrites Puppet class github::role::polling_redis( # params ) { class { 'github::redis': # overrides based on specific node } }
- 92. ( How GitHubWrites Puppet augeas
- 93. ( How GitHubWrites Puppet you know what's not awesome?
- 94. ( How GitHubWrites Puppet an erb template that requires your class to take 52876423 parameters so you can configure every possible value in my.cnf
- 95. ( How GitHubWrites Puppet augeas { 'my.cnf/performance': context => '/files/etc/mysql/my.cnf/mysqld', changes => [ # automatic dump/restore 'set innodb_auto_lru_dump 18000', # innodb "set innodb_buffer_pool_size ${innodb_buffer_pool_size}", 'set innodb_log_file_size 256M', 'set innodb_log_buffer_size 8M', 'set innodb_lazy_drop_table 1', ], require => Percona::Server[$::fqdn] }
- 96. ( How GitHubWrites Puppet it can seem complex and scary
- 97. ( How GitHubWrites Puppet it is an amazing tool
- 98. How GitHub shipsPuppet )
- 99. ) How GitHubShips Puppet continuous integration
- 100. ) How GitHubShips Puppet commit gets pushed
- 101. ) How GitHubShips Puppet jenkins runs the test suite
- 102. ) How GitHubShips Puppet status gets posted back to GitHub.com
- 103. ) How GitHubShips Puppet tmm1/test-queue
- 104. ) How GitHubShips Puppet
- 105. ) How GitHubShips Puppet remembers how to better parallelize tests
- 106. ) How GitHubShips Puppet continuous deployment
- 107. ) How GitHubShips Puppet tests passed for commit, Hubot auto-deploys
- 108. ) How GitHubShips Puppet branch deploy everything
- 109. ) How GitHubShips Puppet a lot of shops have a few environments
- 110. ) How GitHubShips Puppet testing staging production
- 111. ) How GitHubShips Puppet currently we have 181 environments
- 112. ) How GitHubShips Puppet that's not the same as 181 nodes not running production
- 113. ) How GitHubShips Puppet we only have 5 of those
- 114. ) How GitHubShips Puppet Hubot automatically merges the master branch before allowing any branch to deploy
- 115. ) How GitHubShips Puppet ChatOps
- 116. ) How GitHubShips Puppet 202 employees 100% access to Puppet 100% trust
- 117. ) How GitHubShips Puppet the list of roles you'd never think would touch production puppet webkit developer core git developers core ruby developers svn developers search developer frontend designers windows developers mac developers support enterprise sales
- 118. ) How GitHubShips Puppet every puppet run happens in chat
- 119. ) How GitHubShips Puppet all puppet output goes to chat
- 120. ) How GitHubShips Puppet everyone can see everything
- 121. ) How GitHubShips Puppet everyone can do anything
- 122. ) How GitHubShips Puppet hands-on learning, by accident
- 123. ) How GitHubShips Puppet eliminate disruptive questions
- 124. The Future ofPuppet at GitHub *
- 125. * The Futureof Puppet at GitHub puppet 3.x
- 126. * The Futureof Puppet at GitHub upgrading a large, old codebase from 2.7 to 3 is really painful
- 127. * The Futureof Puppet at GitHub we've been talking about it for a year
- 128. * The Futureof Puppet at GitHub we're still trying to push forward, but...
- 129. * The Futureof Puppet at GitHub helping maintain security fixes for 2.7
- 130. * The Futureof Puppet at GitHub goal is to be on 3.2 by end of year
- 131. * The Futureof Puppet at GitHub ruby 2.0
- 132. * The Futureof Puppet at GitHub moar faster rubby
- 133. * The Futureof Puppet at GitHub we get this for free when we move to 3
- 134. * The Futureof Puppet at GitHub mcollective
- 135. * The Futureof Puppet at GitHub aka the story of github/shell and the wonders of ssh in a for-loop
- 136. * The Futureof Puppet at GitHub there are a lot of cool things about mcollective
- 137. * The Futureof Puppet at GitHub I think it will be a part of our stack in the future
- 138. * The Futureof Puppet at GitHub but you can still go pretty damn far with bash and ssh
- 139. * The Futureof Puppet at GitHub even more puppetdb tooling
- 140. * The Futureof Puppet at GitHub waiting for multiple runs to converge exported resources is painful
- 141. * The Futureof Puppet at GitHub use the puppetdb API to skip all that
- 142. * The Futureof Puppet at GitHub even more gpanel integration
- 143. * The Futureof Puppet at GitHub "databags"
- 144. * The Futureof Puppet at GitHub "node search"
- 145. * The Futureof Puppet at GitHub steal good ideas from other tools
- 146.
- 147. "all software isterrible" — anyone who's worked with software long enough
- 148. "no software isbetter than no software" — rtomayko
- 149. the plumbing doesn'tmatter when all you care about is the porcelain
- 150. write some damnedgood porcelain
- 152.
- 153. HE'S NORMALLY NOT THISBLURRY
- 154. HE IS ALSONOT MY BROTHER, BUT YOU REALLY SHOULD BUY HIM A BEER
- 155. YOU SHOULD BUYTHIS MAN A LOT OF BEER
- 156.