PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazon & Andrew Popp, Servicechannel.com
•
0 likes•828 views
This document summarizes best practices for using Puppet configuration management in the AWS cloud. It describes ServiceChannel's journey from an on-premise infrastructure to migrating to AWS, including initial exploration of single EC2 instances and hybrid on-premise/AWS deployments. Key steps for deploying Puppet in AWS are discussed such as understanding AWS services, network configuration, enabling CloudTrail logging, and using IAM roles. The Puppet Labs AWS module is introduced for provisioning AWS resources through Puppet. Benefits seen from adopting DevOps practices like Puppet in AWS include faster deployment times, increased stability, and shorter recovery windows.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazon & Andrew Popp, Servicechannel.com
Similar to PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazon & Andrew Popp, Servicechannel.com (20)
More from Puppet
More from Puppet (20)
Recently uploaded
Recently uploaded (20)
PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazon & Andrew Popp, Servicechannel.com
- 1. Best Practices for Puppet in the Cloud Randall Hunt – AWS Tech Evangalist Andrew Popp – DevOps System Engineer (ServiceChannel)
- 2. Contents / Agenda Who is SC ? Moving into AWS Im in a Cloud Now … Whats Next ? Deploying Puppet in AWS Puppetlabs AWS Module 2Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All
- 3. ServiceChannel At a Glance Who is this guy, and what does this company do? 3
- 4. 4 Andrew Popp DevOps Systems Engineer @doctahpopp99
- 5. 5
- 6. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 6 200+ Employees around the globe 300+ Clients from many industries 50K+ Commercial contractors & suppliers 200K Locations under management 63 Countries using service daily 1.4Million Work orders processed per month
- 7. Where we started … 7
- 8. 8
- 9. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 9 • Dev Env • Single Server • IIS/MSSQL colo • Prod Env • 6 Servers (Web) • 1 DB Server • No Load balancers • No CI/CD • No Codebase No Cfg Mgmt !
- 10. Moving into AWS When the going gets tough … virtualize dat. 10
- 11. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 11 There is a road, no simple highway … • Exploration • Single function • Classic EC2 • No VPC • Hybrid Approach • Majority of Production Payload still on prem.
- 12. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 12
- 13. Somethings shaking, on Shakedown Street … Became … Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 13
- 14. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 14
- 15. AWS 2012 Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 15
- 16. So I'm in the cloud now This is awesome, but what's next ? 16
- 17. AWS Today Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 17 94 EC2 Nodes 62 ELBs 39 Cache Clusters DevOps Team 90 SQS Queues 500 SNS Queues 92 Dynamo DB tables
- 18. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 18 • Understand your Services • Know your Limits (API) • Decide on a Network Config (Region) • Available across AZ • VPC Architecture • Enable CloudTrail • Meta-data URI • User-Data • IAM Roles
- 19. Initial Network Deployment Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 19 • Single Region • Single VPC • Subnets Across AZ’s • NAT Instance • Security Group Inbound Rules • Route 53
- 21. Deploying Puppet in your VPC The beginning of great things … 21
- 22. Key Management Features • Puppet Architecture in Cloud (Prod/Testing) • EC2 Auto-Signing • EC2 Tags • Class creation and resource organization Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 22
- 23. Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 23 https://docs.puppet.com/puppet/latest/reference/ssl_attributes_extensions.html#puppet-specific-registered-ids
- 24. Puppetlabs-AWS Now were cooking w/ gas 24
- 25. DevOps Team Performance Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All 25 • Throughput • A deploy a day keeps the … • X Deploys per year. • Lead time for changes ~3 hours • We can do 60 min • Stability • Recovery • 1-2 hour range and its getting smaller … • Rate of failure • 15-20% • Increase of confidence
- 26. So What Happens If Hurricane Sandy Comes back ? 26