This is a talk I gave at the Lean, Agile and Systems Thinking conference in Melbourne, July 2012.
http://www.lastconference.com/
Covering DevOps as a movement. Ideas behind continuous delivery and a sample implementation covering some of those principles in practise using Puppet and Amazon Web Services.
6. Devops is not something you
build, it’s something you do
#devops
7. “Some people get stuck on the word ‘devops’, thinking
that it’s just about development and operations
working together.
Systems thinking advises us to optimize the whole;
therefore devops must apply to the whole
organization, not only the part between development
and operations.”
— Patrick Debois
11. “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
27. Puppet is IT automation software that helps system
administrators manage infrastructure
throughout its lifecycle, from
provisioning and configuration
to patch management and compliance.
33. AWS CloudFormation gives developers
and systems administrators an easy way to
create and manage a collection of
related AWS resources.
34. 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
58. “I do believe that complexity is the enemy.
Until we better understand complexity, our
chances of building better IT systems is
limited. The first thing we must understand
about complexity is that not all complexity is
equal. And the complexity on which most
people focus is probably the least complex
complexity of all.”
Roger Sessions
http://simplearchitectures.blogspot.com/2009/03/cancer-of-complexity.html
Editor's Notes
Bulleted list for the talk. Highlight as we progress
DevOps
Start by mapping how your organization delivers, who is involved, how do changes get promoted downstream, etcCollect metrics: lead time, process time, %CAThis will tell you where your constraints are in your delivery process. Remember that the reason uat is slow might be because of something done in coding (a completely different step)Find the bottlenecks, improve them, iterateThis is about continuous improvement. You are never done.
I’m only going to talk about the part from coding to release. Now that might not be the constraint in your process. It might be how you manage requirements and ideas. You should look at your highest priority constraints first.Let’s assume your constraint is in here (yellow boxes). How do you improve the delivery process.
to everyone in delivery process: dev, tester, dba, sysadmin, ba, etcfrom: compilation, unit tests, functional tests, integration tests, performance tests, etcfast feedback turns out to be the secret. When you achieve that you start winning.
Improve Feedback speeds. Testing is covered elsewhere. Dev-Ops side of things.
Bulleted list for the talk. Highlight as we progress
Application Diagram
Time to CI. Be good to your team. Integrate often. Fail fast.
Puppet uses a declarative, model-based approach to IT automation.
Switch to terminal Review the time of the job. Switch to AWS console. Check the instances. Ssh into the box. Cat the puppet log.
Switch to Go. Explain the pipeline.
Switch to terminal Review the time of the job. Switch to AWS console. Check the instances. Ssh into the box. Cat the puppet log.
Switch to terminal Review the time of the job. Switch to AWS console. Check the instances. Ssh into the box. Cat the puppet log.
Improve Feedback speeds. Testing is covered elsewhere. Dev-Ops side of things.