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.
12. consistency from development to
production
accidental necessary
>> inconsistency
inconsistency
deployment process
environment configuration
testing tools
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
33. Puppet is IT automation software that helps system
administrators manage infrastructure
throughout its lifecycle, from
provisioning and configuration
to patch management and compliance.
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
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