The shift to cloud-based services has dramatically altered the IT landscape as we know it. Enterprise infrastructure borders have expanded beyond the firewall and now include hosted applications and infrastructure hosted in public and private clouds. Puppet helps DevOps teams meet their common objectives, creating a seamless IT infrastructure across departments, reducing cost and increasing productivity.This training section will cover deploying cloud infrastructure automatically using Puppet, an open source configuration management and automation tool.The session will cover the following topics: Configuring Puppet and Puppetmaster Resource Types and the Resource Abstration Layer Virtual Resources, Exported Resources and Stored ConfigsSpeaker BioLuke founded Puppet and Puppet Labs in 2005 out of fear and desperation, with the goal of producing better operations tools and changing how we manage systems. He has been publishing and speaking on his work in system administration since 1997, focusing on development since 2001. He has developed and published multiple simple sysadmin tools and contributed to established products like Cfengine, and has presented on Puppet and other tools around the world, including at OSCON, LISA, Linux.Conf.au, and FOSS.in. His work with Puppet has been an important part of DevOps and delivering on the promise of cloud computing.
Citation preview
1.
Luke Kanies
Founder of Puppet
Founder and CEO, Puppet Labs
Configuration Management, Clouds, and Puppet
2. The IT Situation
3. Absolutely critical
4. Gatekeepers
5. Bad tools
6. Calcification
7. DevOps
8. 2001: Agile Manifesto
9. Individuals and interactions over processes and tools
10. Working software over comprehensive documentation
11. Customer collaboration over contract negotiation
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