Portable infrastructure with puppet
- 1. Portable Infrastructu re with Puppet Luke Kanies Founder of Puppet project Founder and CEO of Puppet Labs
- 2. The state of Puppet
- 4. Puppet is changing quickly • Still plenty of features to add • Every day we learn, and every lesson brings a refactoring • Maturity brings its own design requirements • Connectiveness is a larger priority
- 5. Puppet is Pervasive Web Entertainment Technology Financial Defense
- 6. I promised some things last year
- 7. Puppet Camp 2009 Promises •1.0 •WebGUI •Modules
- 9. 0.2
- 10. 0 0.2
- 11. 1.0
- 12. 0 1.0
- 13. 2.6
- 14. Lots of refactoring, and a lot of features
- 15. Pure Ruby DSL
- 16. Class Parameters
- 17. Finished migration to REST Still working on publishing all of the formats and URLs
- 18. The single executable shift puppetmasterd puppet master puppetd puppet agent puppetca puppet cert ralsh puppet resource puppetdoc puppet doc
- 19. More informative reports Heavily trimmed
- 20. Exposing types and classes
- 21. Faster in many ways • Compiles are much faster • File serving is streamed (thanks Brice!) • Lots of small improvements
- 22. Relationship syntax
- 23. Hashes
- 24. Taught us a lot about how (not) to release
- 25. “Web GUI” Dashboard is growing and prospering
- 27. Reporting
- 28. Lots to come • Automatically detect optional and required parameters • Catalog and report correlation • Discovery • Harass Rein for more information!
- 29. Let’s go Back
- 30. Why does Puppet exist?
- 31. Embarrassment
- 32. Fear
- 33. A simple dream: That sysadmins could reuse code
- 34. Enable focus on the value-add Usually Ideally 0 25.0 50.0 75.0 100.0 Things you have to do Things you want to do
- 35. The Problem } • No standardization Every • 75% of IT budgets spent infrastructure to maintain existing systems starts from • Code changes with the scratch sysadmin
- 36. We needed a high-level language for
- 37. Shell scripts are assembly code Programmin SysAdmin g Low-level, non- Assembly perl/shell/etc portable, single-use Abstract, portable, C* Puppet reusable * For small values of abstract
- 38. So: The ultimate goal was code reuse
- 39. We’ve built a platform that can enable reuse
- 40. Now we just need to start sharing
- 41. Announcing: Puppet Forge http://forge.puppetlabs.com http://projects.puppetlabs.com/projects/ module-site
- 42. Share the modules you’ve created
- 43. Find modules others have
- 46. Minimum Viable Product (MVP)
- 47. It’s all about code reuse
- 48. Westheimer's Discovery: A couple of months in the laboratory can frequently save
- 49. Luke’s Corollary: A couple of months of development can frequently save a couple of hours on the internet.
- 50. Collaborate on existing code rather than
- 51. Or, start again and publish
- 52. A new forcing function in
- 53. Because there’s now a place for all that metadata: • Classes, definitions, nodes, etc. • Required and optional parameters • Versions • Dependencies
- 54. Drives further introspection in Puppet
- 55. We can add: • Portability information - ‘confine’ in classes and modules • Incompatibilities • “Tested on” information • Etc.
- 56. Pushes Dashboard to manage modules
- 57. Package-like behaviour in the modules
- 58. Fills out the product portfolio •The industry-leading open source automation platform Puppet •Supported with subscription Puppet •A graphical view into your Puppet infrastructure •A simplified interface for many configuration actions Dashboard •Collaborate with other IT administrators on Puppet content Puppet Forge •Access Puppet Labs supported modules
- 59. Any Question
Editor's Notes
- #34: The management layer has not yet been commoditized
- #36: * The assembly programmers fought the adoption of C * Fear for your career if you’re a bit too fond of assembly * It’s not about fewer people, it’s about higher quality and productivity * Are there more or fewer programmers today than in the days of assembly?