Continuous Delivery in the Cloud
2 likes1,563 views
This document summarizes a workshop about DevOps practices like continuous integration, infrastructure as code, and automated deployment. It discusses: 1. Using continuous integration to automatically build and test code changes. 2. Defining infrastructure using configuration files to enable consistent and automated environments from development to production. 3. Automating deployment through tools that rebuild servers from code and data to enable rapid, repeatable releases with minimal downtime. The document provides examples using tools like Puppet, AWS CloudFormation, and auto-scaling groups to demonstrate these practices in action for a sample Twitter application. It emphasizes speeding up the cycle from code to production to get faster feedback.
![Cloud Formation Template
…
…
"Resources" : {
"Ec2Instance" : {
"Type" : "AWS::EC2::Instance",
"Properties" : {
"InstanceType" : "c1.medium",
"SecurityGroups" : [ { "Ref" : "InstanceSecurityGroup" } ],
"KeyName" : { "Ref" : "KeyName" },
"ImageId" : { "Fn::FindInMap" : [ "RegionMap", { "Ref" : "AWS::Region" }, "AMI" ]},
"UserData": { "Ref": "BootScript" }
}
},
…
…](https://image.slidesharecdn.com/cdinthecloudawssummit-120516010109-phpapp02/85/Continuous-Delivery-in-the-Cloud-42-320.jpg)
Continuous Delivery in the Cloud
- 5. BIG IDEAS
- 7. What are we talking about?
- 8. Agenda Ideas behind this workshop Ideas in practice Continuous integration System integration Production deployment Summary Questions
- 12. consistency from development to production accidental necessary >> inconsistency inconsistency deployment process environment configuration testing tools
- 13. Automation
- 14. Rebuild from code + data
- 16. Disk CPU Network Memory
- 18. Dev Ops Ops Dev
- 19. In short.
- 20. 1 2 3 Infrastructure Automate DevOps as code
- 21. continuous delivery small feature chunks time software always production ready releases tied to business needs, not IT constraints minimize the lead time from idea to live concept to cash
- 22. Agenda Ideas behind this workshop Ideas in practice Continuous integration System integration Production deployment Summary Questions
- 23. Sample Application for #AWS Tweets Sample App
- 25. WebApp Java/JVM Executable War ~ 30 lines of code Unix Service Native Packaging/RPM
- 26. Lets see this working
- 28. I win with Continuous Integration
- 29. while (true) { if (change checked into vcs) then build & test sleep 60 }
- 30. aws-twitter-feed repository while (true) { if (change checked into vcs) then build & test sleep 60 } RPM
- 33. Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to patch management and compliance.
- 34. Puppet definition for our GO machine
- 36. Don’t make the Version Control Sad
- 37. github.com/nigelfds/configuration- master Puppet definitions and AWS scripts
- 38. To keep things moving, lets kick it off
- 39. S3 Bucket Self Configured Puppet & AWS Build scripts Server Packaged Scripts Cloud Formation APIs Create Machine Behind the scenes Nigel’s Laptop
- 40. AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources.
- 41. Once deployed, you can modify and update the AWS resources in a controlled and predictable way allowing you to version control your AWS infrastructure in the same way as you version control your software
- 42. Cloud Formation Template … … "Resources" : { "Ec2Instance" : { "Type" : "AWS::EC2::Instance", "Properties" : { "InstanceType" : "c1.medium", "SecurityGroups" : [ { "Ref" : "InstanceSecurityGroup" } ], "KeyName" : { "Ref" : "KeyName" }, "ImageId" : { "Fn::FindInMap" : [ "RegionMap", { "Ref" : "AWS::Region" }, "AMI" ]}, "UserData": { "Ref": "BootScript" } } }, … …
- 43. Creating the stack with CloudFormation Name of the stack Create the stack Self configuration scripts (Invokes Puppet)
- 44. Lets see how we’re doing
- 47. Puppet definition for our GO machine Server Monitoring
- 48. In Short
- 49. Packaging for the target ( Using PMs) Continuous Integration (Using ) Declarative Env. Conf. (Using ) Infrastructure as Code (Using )
- 50. Agenda Ideas behind this workshop Ideas in practice Continuous integration System integration Production deployment Summary Questions
- 51. Everything works by itself
- 52. But they need to work together
- 53. Bring in the conductor =
- 54. Complex !
- 55. How does this look in
- 57. Self Configured GO Server App Server Cloud Formation APIs Behind the scenes
- 58. Creating the AMI Create an AMI from the running instace Save a reference to the Image Id Delete the running instance
- 59. Lets see this on AWS
- 60. Snapshot -> AMIs are awesome
- 61. Boot Test QA = Speed Prod Instances
- 62. Agenda Ideas behind this workshop Ideas in practice Continuous integration System integration Production deployment Summary Questions
- 63. To keep things moving, lets kick it off
- 64. ELB Remove ZERO DOWNTIME ! ID-1 ID-2 Autoscaling Terminate Instance APP APP ID-1 ID-2 V2.0 V1.0 V2.0 V1.0 ID-3 ID-1 ID-2 ID-4
- 65. Lets see this working
- 66. Agenda Ideas behind this workshop Ideas in practice Continuous integration System integration Production deployment Summary Questions
- 67. 1 2 3 Infrastructure Automate DevOps as code
- 68. Thank you and …
- 69. “How? By fast, automated of your on the production readiness feedback applications every time there is a change whether code, infrastructure, configuration or database ” Jez Humble Author Continuous Delivery
- 70. Ps. We’re hiring ;-)