Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Controlled Evolution with Puppet and AWS

199 views

Published on

Webinar From 11/16/16 on Puppet integration with AWS for cloud computing.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Controlled Evolution with Puppet and AWS

  1. 1. Controlled Evolution with AWS & Puppet
  2. 2. Speakers 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
  3. 3. Speakers 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
  4. 4. Every company is a software company.
  5. 5. It feels like a breaking point.
  6. 6. Change is necessary.
  7. 7. We help great companies: Become great software companies Deliver fantastic experiences to their users Provide better software, faster And do it simply, at scale and securely
  8. 8. 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
  9. 9. Define with a common 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
  10. 10. 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
  11. 11. Cloud Management with Puppet Adopt, unify and manage cloud environments
  12. 12. Supporting heterogeneous infrastructure
  13. 13. Cloud adoption drives business 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%
  14. 14. Automation in the cloud Native tools don’t work Manual approaches / scripts are problematic Misconfiguration creates risk = Risk $ one-off
  15. 15. Puppet/aws module $ one-off
  16. 16. AWS Herd Management $ one-off
  17. 17. Introduction 17 ● 15 years experience in banking technology ● Particularly interested in hands on transformation of operating models.
  18. 18. What was the problem we were trying to solve? 18 Reduce manual effort and IT bureaucracy that is error prone, slowing us down and costing us money.
  19. 19. Our setup 19 Github Application Code Puppet Modules TeamCity Application & Container Build Puppet Master Configuration Management Artifactory Application & Container Store Application Server Application Environment Puppet R10K Release Management and Change Management
  20. 20. 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. 20
  21. 21. Standard puppet approach 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
  22. 22. Our experience with Puppet 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
  23. 23. 23 Reduction in manual effort 90% Team Development Effort 12% 600% Change Deployment Frequency Measurable results
  24. 24. But what about provisioning? 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 ?
  25. 25. Our AWS POC 25 Github Application Code 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
  26. 26. What did we discover ● 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. 26
  27. 27. Getting started with cloud was easy because we already automated with Puppet. 27
  28. 28. It will scale because we already automated with Puppet. 28
  29. 29. Potential stumbling blocks to 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. 29
  30. 30. Questions?
  31. 31. Read up on AWS-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?

×