Successfully reported this slideshow.
Your SlideShare is downloading. ×

Puppet and the Model-Driven Infrastructure

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 70 Ad

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Advertisement

Similar to Puppet and the Model-Driven Infrastructure (20)

Recently uploaded (20)

Advertisement

Puppet and the Model-Driven Infrastructure

  1. Puppet and our Model- driven future Luke Kanies luke@reductivelabs.com Founder, Reductive Labs Portland, Oregon USA
  2. A bit about Puppet
  3. You pull the strings, Puppet does the work
  4. 0 SSH
  5. “...at Google we're currently using Puppet to manage close to 6,000 Macs, and it's likely our deployment will expand dramatically beyond that....”
  6. Written in Ruby
  7. Why does Puppet exist?
  8. Embarrassment
  9. Fear
  10. Somebody has to do something, and it's just incredibly pathetic that it has to be us. -- Jerry Garcia
  11. Why didn’t someone else make it?
  12. Sysadmins do too much Image from http://flickr.com/photos/shirleytwofeathers/2068713495/
  13. Speciation Image from http://flickr.com/photos/kenskritters/2128853769/
  14. Sysadmins know too much
  15. An Analogy Programming SysAdmin Low-level, commands Assembly non-portable and files Abstract, C* Resources portable * For small values of abstract
  16. Virtualization and the cloud
  17. Hardware Provisioning Deployment Old Days Cloud Days 0H 100H 200H 300H 400H
  18. Dell Hardware Provisioning Deployment Old Days Cloud Days 0H 100H 200H 300H 400H
  19. Dell Hardware Provisioning Deployment Old Days Cloud Days 0H 100H 200H 300H 400H You
  20. “We’re here for your sysadmins”
  21. Would your boss pick:
  22. Would your boss pick: • The current service quality at a lower price?
  23. Would your boss pick: • The current service quality at a lower price? • A higher service quality at the current price?
  24. Let’s talk about you
  25. Some questions
  26. Some questions • How many of you have written software to manage computers?
  27. Some questions • How many of you have written software to manage computers? • How many have published this software?
  28. Developer Sysadmin
  29. Three people Developer Sysadmin
  30. Puppet allows you to bridge that gap Image from http://www.flickr.com/photos/patrick-smith-photography/2969769911/sizes/o/
  31. Either you can manage many machines with little effort
  32. Either you can manage many machines with little effort Or you can’t
  33. Puppet and model- driven administration
  34. Resource Abstraction Layer (RAL)
  35. Do you really care how rpm works?
  36. Resource Providers 23 package types Users in NetInfo, useradd, pw Builtin support for RHEL, OS X, Solaris, Debian, Ubuntu, Gentoo, SuSE, FreeBSD, and more
  37. Resources are specified in code
  38. Code is compiled into a catalog
  39. The client gets a catalog, not code
  40. Least Privilege is in the house
  41. If it’s not in the catalog, it’s not managed
  42. If it’s not in the catalog, it can’t affect the system
  43. "Exec[createrepo-PM-RHEL5-noarch]" Compiled Catalogs "Yumrepo[PM-RHEL5-x86_64]" are a DAG "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]"
  44. Is this file being managed by Puppet?
  45. Which services will I need to restart if I edit this file?
  46. Who requires this package?
  47. Classes are modeled
  48. Code or Data?
  49. Perspective Shift
  50. Functional Areas • Specification and validation system • Auditing and application engine
  51. Code Catalog Compiler Transaction Report
  52. Data and Artifacts • Configurations and code • Compiled Catalogs • Transaction Reports • etc.
  53. Compile Apply Code Catalog Report
  54. So?
  55. Caching
  56. Integration
  57. Actual Future
  58. Simple Tools
  59. Which resources are being managed
  60. Validation prior to shipping
  61. Compile Apply Code Catalog Report
  62. CMDB Compile Apply Code Catalog Report
  63. CMDB Compile Apply Code Catalog Report LDAP
  64. Policy CMDB Compliance Compile Apply Code Catalog Report LDAP
  65. Policy CMDB Compliance Compile Apply Code Catalog Report LDAP CMDB
  66. Policy CMDB Remedy Compliance Compile Apply Code Catalog Report LDAP CMDB
  67. Policy CMDB Remedy Compliance Compile Apply Code Catalog Report LDAP CMDB Nagios
  68. Resource/Event Correlation
  69. Questio

Editor's Notes























  • Firefighter? Architect? Developer? Tape-changer? All of the above?
  • These are house finches, reminding one of the finches Darwin observed in the Galapagos. I want to cause sysadmin speciation.


  • * 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?












  • Do you have any computers?














  • rpm/apt/etc becomes packages
    /etc/hosts becomes hosts
    useradd/netinfo, etc. becomes users
    /etc/init.d/smf/launchd/daemontools becomes services


  • This is shareable, releasable code.
    Classes are analogous with tags




















  • This is shareable, releasable code.
    Classes are analogous with tags










































×