23. Puppet Users Scaled from 0 to over 10,000 servers in 2
months without training 287 servers per SysAdmin vs. 19 for BMC
BladeLogic Over 50,000 systems managed by Puppet Deploy 1,800
machines in 2 hours vs. 25 machines per day with HP Opsware
Financial Entertainment Technology Defense Web Mobile Phone
Company
53. Seek the pain Image from
http://www.flickr.com/photos/pagedooley/2147718252/sizes/l/
54. Solve the simple problems
55. Add the infrastructure features you always wanted
56. Think like Puppet thinks
Resources, not text snippets or lines added to files
What resources are you managing?
How are they related to each other?
57. Replace Shell Scripts with Resources Becomes: This:
58. Relationships matter but are often implicit Package Service
Service should restart when configuration changes 30 Configuration
30 Configuration should get modifed after package installation
59. Explicit Relationships
60. Relationships provide ordering and notification
61. Classes document Intent
62. Organize files into modules
63. Provide platform abstraction Debian Red Hat
64. Portability and Naming
65. Roles
66. Puppet Enterprise
67. REPORTING Detail of node status to pinpoint specific issues
High-level status of nodes for instant visibility Time-based
display for insight into rate of change
68. Cloud Provisioning VMware Amazon AWS
69. RESOURCE BROWSING Choose nodes to clone to ensure
consistency Preview the impact before you clone nodes Browse for
managed nodes in your infrastructure
70. COMPLIANCE Accept or reject changes to update your baseline
See specific differences between node configurations
71. ORCHESTRATION Find out the status of each node group and
its last Puppet run
72. ORCHESTRATION Resources currently under Puppet management
Current set of managed nodes