Puppet camp europe 2011 hackability
•
1 like•1,361 views
Watch along with the video at https://www.youtube.com/watch?v=ag-bI5lr55s Luke Kanies, CEO and Founder of Puppet Labs, talks on "Making Puppet More Hackable" at PuppetCamp Europe '11, Amsterdam, Netherlands. Learn more: http://www.puppetlabs.com
More Related Content
What's hot
What's hot (7)
Viewers also liked
Viewers also liked (8)
Similar to Puppet camp europe 2011 hackability
Similar to Puppet camp europe 2011 hackability (20)
More from Puppet
More from Puppet (20)
Recently uploaded
Recently uploaded (20)
Puppet camp europe 2011 hackability
- 1. Wireless • Any “BvB Hotspot...” network • New browser page • User: bvbhotspot Password: berlag33 Friday, May 13, 2011
- 2. puppet labs Friday, May 13, 2011
- 3. Making Puppet More Hackable Luke Kanies luke@puppetlabs.com Friday, May 13, 2011
- 4. Question Authority Friday, May 13, 2011
- 5. Puppet Labs Friday, May 13, 2011
- 6. Puppet Labs • 40 employees Friday, May 13, 2011
- 7. Puppet Labs • 40 employees • Fantastic investors and board members Friday, May 13, 2011
- 8. Puppet Labs • 40 employees • Fantastic investors and board members • I’m still CEO Friday, May 13, 2011
- 9. Puppet 2.7 Friday, May 13, 2011
- 10. Apache License Friday, May 13, 2011
- 11. Faces Friday, May 13, 2011
- 12. Static Compiler Friday, May 13, 2011
- 13. Certificate API Friday, May 13, 2011
- 14. Deterministic Ordering For otherwise unrelated resources Friday, May 13, 2011
- 15. Enhanced Graph Management Friday, May 13, 2011
- 16. Puppet Enterprise Friday, May 13, 2011
- 17. Always based on full releases Friday, May 13, 2011
- 18. Looking for Partners Friday, May 13, 2011
- 19. PE 1.1 - 5/11 • MCollective • RHEL 4/5/6, SLES, Solaris Friday, May 13, 2011
- 20. PE 1.2 - 6/11 • Discovery • Provisioning Friday, May 13, 2011
- 21. Q3 • Full Windows support • 2.7 base • Change Lifecycle Management Friday, May 13, 2011
- 22. Faces, Hackability, and Marketing Friday, May 13, 2011
- 23. Puppet is different, but not in straightforward ways Friday, May 13, 2011
- 24. Awkward Friday, May 13, 2011
- 25. I wanted to tell The Story of Why Friday, May 13, 2011
- 26. A bit of history: Cfengine Friday, May 13, 2011
- 27. I had no control • Stuckwith whatever application logic it shipped with • Core components were mandatory Friday, May 13, 2011
- 28. Do Not Question • Why is this file here? • What requires this package? • What will happen if I change this file? • Do these classes conflict? Friday, May 13, 2011
- 29. Not Extensible Friday, May 13, 2011
- 30. “Puppet is Different” Friday, May 13, 2011
- 31. Easily extensible, everywhere A quick count shows 10 kinds of extensibility Friday, May 13, 2011
- 32. The Puppet world • Facts • Resources • Catalogs • Edges • Events Friday, May 13, 2011
- 33. Questions can be asked of every artifact • Is this file being managed? • What happens if I restart this service? • Who requires this package? • Did my service restart? • Were there any failures? Friday, May 13, 2011
- 34. Data > Code • Caching • Validation • Implementation Independence • Integration Friday, May 13, 2011
- 35. "Exec[createrepo-PM-RHEL5-noarch]" The Graph Matters "Yumrepo[PM-RHEL5-x86_64]" "Package[postgresql-server]" "Postgres::Role[puppet]" "Package[thttpd]" "File[/var/www/thttpd/html/yum-PM-RHEL5-x86_64]" "File[/var/www/thttpd/html/yum-PM-RHEL5-noarch]" "Exec[rsync-rpmdir-PM-RHEL5-x86_64]" "Exec[rsync-rpmdir-PM-RHEL5-noarch]" "Exec[createrepo-PM-RHEL5-x86_64]" "Yumrepo[PM-RHEL5-noarch]" Friday, May 13, 2011
- 36. An Aside: The Competition Friday, May 13, 2011
- 37. AFAIK, Puppet is the only tool that provides: • A complete list of every resource managed in your entire infrastructure • A complete list of every dependency in your entire infrastructure • A complete list of every single change that’s ever happened in your entire infrastructure • With full run simulation and inspection ...all in a queryable, storable, cacheable way Friday, May 13, 2011
- 38. Progress? •Declarative •Code runs on Cfengine client •Implicit •Imperative dependencies •Code runs on Chef client •Implicit dependencies •Declarative Puppet •Only data on clients, no code •Explicit dependencies Friday, May 13, 2011
- 39. How do we talk about this? Market this? Friday, May 13, 2011
- 40. “Puppet is Model-Driven” Friday, May 13, 2011
- 41. Procedural Code Catalog Compile Apply Report Friday, May 13, 2011
- 42. Model-driven Compile Apply Code Catalog Report It’s the artifacts that matter Friday, May 13, 2011
- 43. Policy CMDB Remedy Complian Compile Apply Code Catalog Report LDAP CMDB Nagios Friday, May 13, 2011
- 44. No one knows what ‘model driven’ means Friday, May 13, 2011
- 45. “Puppet is hackable” Props to Nick Fagerland Friday, May 13, 2011
- 46. But it wasn’t really true Friday, May 13, 2011
- 47. You could *program* it, but not hack it like a sysadmin would Friday, May 13, 2011
- 48. Really: Encapsulated, modular and data- driven Friday, May 13, 2011
- 49. Unfortunately the applications hard-code our logic • Download plugins • Upload Facts • Download Catalog • Apply Catalog • Send Report Friday, May 13, 2011
- 50. Other application world- views exist • Only update catalogs during maintenance windows • Push catalog updates • Send fact updates 10x as often as puppet runs • Combine multiple catalogs on the client side and run them together • Compile catalogs for hundreds of hosts and compare them • Manually view catalog diffs before deploying Friday, May 13, 2011
- 51. It doesn’t make sense to extend the core apps with this logic Friday, May 13, 2011
- 52. And doing it yourself is too hard with current tools Friday, May 13, 2011
- 53. So we should expose everything and let you build what you want Friday, May 13, 2011
- 54. Functions • Compiler • Transactions • Network • Indirector • Parser • RAL Friday, May 13, 2011
- 55. Data • Facts • Catalog • Reports • Resource Types (AST and RAL) • Nodes • Certificates Friday, May 13, 2011
- 56. Interfaces Friday, May 13, 2011
- 57. Puppet Faces Friday, May 13, 2011
- 58. A framework for exposing, combining, and extending core Puppet functions and data types Friday, May 13, 2011
- 59. A collection of Faces that does this in Ruby and on the CLI Friday, May 13, 2011
- 60. Good: It directly exposes Puppet internals in a hackable way Friday, May 13, 2011
- 61. Bad: It directly exposes Puppet internals Friday, May 13, 2011
- 62. Examples • puppet catalog find <host> • puppet facts upload • puppet certificate sign <host> • puppet file find <sum> Friday, May 13, 2011
- 63. Easily extensible • puppet config info <name> • puppet catalog select <host> <type> • puppet file diff <sum> <sum> • puppet node clean <name> • puppet catalog diff <host> <host> Friday, May 13, 2011
- 64. What we’re working on Friday, May 13, 2011
- 65. Team and Community Friday, May 13, 2011
- 66. Flattening the on-ramp Friday, May 13, 2011
- 67. Ad-hoc Tooling Friday, May 13, 2011
- 68. Cross-Node Applications Friday, May 13, 2011
- 69. Databases Friday, May 13, 2011
- 70. Change Lifecycle Friday, May 13, 2011
- 71. Questions? Friday, May 13, 2011