Downloaded 20 times
Uploaded byPuppet
Controlled Evolution with Puppet and AWS
- The document discusses how Puppet can be used to automate infrastructure provisioning and configuration management across cloud and on-premise environments. - It provides an example of how one company used Puppet to reduce manual effort by 90% and increase change deployment frequency by 600% while provisioning applications on AWS. - Key capabilities of Puppet that helped include defining infrastructure with a common language, gaining visibility into dependencies and changes, and intelligently orchestrating changes across environments.
More Related Content
Similar to Controlled Evolution with Puppet and AWS
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Controlled Evolution with Puppet and AWS
- 1. Controlled Evolution with AWS &Puppet 16 November 2016
- 2. Carl Caum: Sr.Technical Marketing Manager at Puppet Chris Barker: Principal Technical Solutions Engineer at Puppet Seamus Birch: Change Agent at one of Canada’s tier-one banks Speakers
- 3. Every company is asoftware company.
- 4. It feels like abreaking point.
- 5.
- 6. We help greatcompanies: Become great software companies Deliver fantastic experiences to their users Provide better software, faster And do it simply, at scale and securely
- 7. Automate for speed,reliability and security Define with a common language Gain situational awareness Orchestrate change intelligently Ensure security & compliance What’s needed to deliver and operate modern software simply, at scale and securely Across devices, through the stack
- 8. Define with acommon language ● Easy to read, understand, write & share ● Write once, use everywhere ● Testing built in ● No code clobbering ● Choose from thousands of free modules, backed by a vibrant ecosystem Standard way for teams to deliver and operate software Puppet code example
- 9. Gain situational awareness ●Real-time change visibility ● Unique dependency visualizations ● Continual drift monitoring and reporting ● Audit and compliance reporting ● Built-in, custom and 3rd party visualizations Know exactly what is going on with all your software Event inspection in Puppet Enterprise
- 10. Cloud Management with Puppet Adopt,unify and manage cloud environments
- 11.
- 12. Cloud adoption drivesbusiness of organizations believe cloud will help them improve their revenue Source: IDC “Don’t Get Left Behind: The Business Benefits of Achieving Greater Cloud Adoption,” Aug 2015 53%
- 13. Automation in thecloud Native tools don’t work Manual approaches / scripts are problematic Misconfiguration creates risk = Risk $ one-off
- 14.
- 15. AWS Herd Management $one-off
- 16. Introduction 16 ● 15 yearsexperience in banking technology ● Particularly interested in hands on transformation of operating models.
- 17. What was theproblem we were trying to solve? 17 Reduce manual effort and IT bureaucracy that is error prone, slowing us down and costing us money.
- 18. Our setup 18 Github Application Code PuppetModules TeamCity Application & Container Build Puppet Master Configuration Management Artifactory Application & Container Store Application Server Application Environment Puppet R10K Release Management and Change Management
- 19. Or first steps ●Built a community of developers on the platform. ● Focused on promoting continuous deployment rather than continuous integration. ● Obtained security risk assessments and approvals on the Puppet process as a software deployment mechanism. ● Heavily invested in getting the infrastructure teams to pick up puppet. ● Lucky enough to find an infrastructure team that could pick up the coding aspect. ● Worked with the release management and change control teams to add support to R10K to their service. ● Started with a pilot of 150 servers. 19
- 20. Standard puppet approach Provisioning Virtualenvironments ● Cloud ● Containers Application infrastructure SQL server ● Tomcat ● WebSphere ● IIS ● MySQL Core infrastructure Operating system ● NTP ● DNS ● SSH ● Firewall ● Users ● Groups Application orchestration Custom apps ● COTS ● Share services
- 21. Our experience withPuppet Provisioning Virtual environments ● Cloud ● Containers Application infrastructure SQL server ● Tomcat ● WebSphere ● IIS ● MySQL Core infrastructure Operating system ● NTP ● DNS ● SSH ● Firewall ● Users ● Groups Application orchestration Custom apps ● COTS ● Share services 1 2 3
- 22. 22 Reduction in manualeffort 90% Team Development Effort 12% 600% Change Deployment Frequency Measurable results
- 23. But what aboutprovisioning? Provisioning Virtual environments ● Cloud ● Containers Application infrastructure SQL server ● Tomcat ● WebSphere ● IIS ● MySQL Core infrastructure Operating system ● NTP ● DNS ● SSH ● Firewall ● Users ● Groups Application orchestration Custom apps ● COTS ● Share services 1 2 3 ?
- 24. Our AWS POC 24 Github ApplicationCode Puppet Modules TeamCity Application & Container Build Puppet Master Configuration Management Artifactory Application & Container Store Cloud Command and Control Keys Puppet R10K Release Management and Change Management VPC, Security, Firewall, Network etc ECS EC2 Instances Application RDS
- 25. What did wediscover ● We had a real life application deployed within a couple of weeks. ● We didn’t require any new processes to be created. ● There were no special approvals/waivers/exceptions to obtain. ● We didn’t need to change firewalls or modify our security posture. ● We reduced infrastructure costs to pennies in the dollar. 25
- 26. Getting started withcloud was easy because we already automated with Puppet. 26
- 27. It will scalebecause we already automated with Puppet. 27
- 28. Potential stumbling blocksto avoid ● Focus on automation, not on cloud as the objective. ● Don’t start with doing cloud manually, it will not scale and your cloud transformation will stall. ● The development team must have a mature approach to security. You must be 100% confident that when you ask a security consultant to review your setup, they will not find any vulnerabilities. ● You need to let go of the crutch that it is SSH/RDC. 28
- 29.
- 30. Read up onAWS-Based Node Lifecycle Management with Puppet in our white paper: bit.ly/AWSlifecycle Check out our AWS-supported module on the Puppet Forge, which provides the ability to manage AWS resources: forge.puppet.com/puppetlabs/aws Watch Chris Barker's PuppetConf 2016 talk, AWS Management & Puppet: What to do with cloud instances: bit.ly/puppetconf15barker What’s next?