Downloaded 14 times
Systems building-systems-a-puppet-story-19133
- 1. Systems Building Systems APuppet Story
- 3. What is Puppet? LanguageParser Client/Server Resource Abstraction A few other things...
- 4.
- 5.
- 6. What is asysadmin?
- 7.
- 8. Do tools have tosuck?
- 9.
- 10. Everything the Same EverythingDistinct
- 11.
- 12. Don’t look atme... I wasn’t the last one to touch it...
- 13. SSH Cfengine ?
- 14.
- 15. SSH Cfengine ?
- 16. SSH Cfengine ?
- 17. You can eithereasily manage complex systems at scale...
- 18. You can eithereasily manage complex systems at scale... Or you can’t...
- 19. Who’s using Puppet? “...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....”
- 20.
- 21. People are finallyfiguring out puppet and how it gets you to the pub by 4pm. Note that I've been at this pub since 2pm. -- Jorge Castro
- 22. Enter Puppet... Configuration Is Declarative Code Semantics Matter Reproducible Shareable Maintainable Extensible
- 23. Developer Sysadmin
- 24. Three people Developer Sysadmin
- 25. An Analogy Programming SysAdmin Low-level, commands Assembly non-portable and files Abstract, C* Resources portable * For small values of abstract
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32. Portable 23 package types Users in NetInfo, useradd, pw Support for Debian, Ubuntu, Red Hat, Solaris, OS X, Gentoo, SuSE, FreeBSD, and more
- 33.
- 34.
- 35.
- 38.
- 39. Configuration should Package get modified after package installation Configuration
- 40. Configuration should Package get modified after package installation Service should restart Configuration when configuration changes Service
- 43.
- 44.
- 45. Idempotence... Describes theproperty of operations in mathematics and computer science which yield the same result after the operation is applied multiple times.
- 49.
- 50. Code Puppetmasterd puppetd puppetd OS X in the puppetd cloud Linux
- 51.
- 52. Every Client: Retrieve resource catalog from central server
- 53. Every Client: Retrieve resource catalog from central server Determine resource order
- 54. Every Client: Retrieve resource catalog from central server Determine resource order Check each resource in turn, fixing if necessary
- 55. Every Client: Retrieve resource catalog from central server Determine resource order Check each resource in turn, fixing if necessary Rinse and repeat, every 30 minutes
- 56.
- 57. Every Resource: Retrieve current state (e.g., by querying dpkg db or doing a stat)
- 58. Every Resource: Retrieve current state (e.g., by querying dpkg db or doing a stat) Compare to desired state
- 59. Every Resource: Retrieve current state (e.g., by querying dpkg db or doing a stat) Compare to desired state Fix, if necessary (or just log)
- 64.
- 66.