Getting Started with Puppet (v2)

A second take at getting started with Puppet. This covers Who, What, Where, When, Why, and sometimes How.

Transcript

1. 2014 Presented by Getting Started With Puppet Michael Stahnke Director of Engineering Services Puppet Labs @stahnma
3. Presented by Why What How Who Worst Practices Summary
5. Presented by
29. Presented by
30. Presented by
43. Presented by List of first things that come online
50. Presented by Though shall not run rsh or rlogin.
65. Presented by Who does the work?
66. Presented by Who does gets the benefit?
67. Presented by Inventory Service - using inventory service - noop - the RAL - facter and facter extensions
68. Presented by What could possibly be more interesting?
69. Presented by For every 25 percent increase in problem complexity, there is a 100 percent increase in solution complexity. Robert L. Glass: Facts and Fallacies of Software Engineering
70. Presented by there is no such thing as an “automatic” factory, but merely degrees of automation.
71. Presented by XKCD comic Fallacies of automation * I can automate that * I don’t have to know specifics * Automation leads to unemployment * Documented behavior
72. Presented by Watch out for these traps: * Auto/auto * Not a time savings * Not delivering value * Not sustainable (too complex)
74. Presented by what are the first things you do when a system comes online? What are the first things you do when a switch comes online?
75. Presented by Some Real Puppet Tips Manifest Ordering Data Input Control You don’t need to know ruby Monitoring/Feedback loop Testing
76. Presented by Event Inspector Facter Inventory service queries the RAL Noop usage Audit/tech controls
80. Presented by Automation Definition (n): Automating comes from the roots auto- meaning self, and mating, meaning screwing
104. Presented by Worst Practices High Value slide 1