3. Agenda
9:00am – DevOps, Continuous Delivery, Automation
Tim Marston, MidVision
9:15am – From DevOps to Operations Science
Christopher Brown, Opscode
`
9:30am – Applying DevOps: What does DevOps mean in the real
world?
John O’Donovan, FT
9:45am – DevOps at Scale: Things we Learned
Sam Pointer, OpsUnit
10:00am – Q&A
5. About Me
• Agile-aware since 2003
• Previously at Red Hat and mongoDB
• Currently leading alliances for MidVision
6. Defining DevOps
Wikipedia:
“DevOps is a software development method that stresses communication, collaboration and
integration between software developers and information technology (IT) professionals.”
(http://en.wikipedia.org/wiki/DevOps)
IBM:
“An enterprise capability for continuous software delivery that enables clients to seize market
opportunities and reduce time to customer feedback.” (http://ibm.co/18lOu3v)
12. DevOps Natives
“In software development, adoption of DevOps practices is a given,
at least in startups. The same should be true in legacy shops as
well.”
(http://gigaom.com/2013/08/28/for-some-devops-is-nothing-new/)
13. DevOps and Automation
DevOps
(Philosophy)
Continuous Delivery
(Practice)
ARA
(Tools)
Application Release Automation
a.k.a. Deployment Automation
“The process of packaging and deploying
an application or update of an application
from development, across various
environments, and ultimately to production”
14. Why ARA makes sense
Faster
• No Manual or script-based processes
• Faster deployments through whole lifecycle
• More resource time for value-creation
Safer
• Eliminate configuration-related errors
• Workflow-scheduling
• Audit & compliance controls
Hinweis der Redaktion
1960s Japan.W. Edwards Deming influences Japanese manufacturing, in particular ToyotaThe Deming Cycle
This was the formal birth of the Agile movement.
Meanwhile, in 2004, AWS was born.
The spread of agile methods through development and QA teams MeetsThe availability of highly agile infrastructure
There is an emergence of ‘DevOps’ as a skill, reminiscent of ‘Agile’ in the early noughties. It is a cultural change within an organisation, removing the silo barriers between Development and Operations. Establishing a DevOps practice can be a risky move, unless it is intended as an isolated pilot or PoC of the concept.There is no such thing as a ‘DevOps solution’, we’ll come back to that in a couple of slides’ time.
DevOps natives are not burdened with legacy infrastructure, and as market innovators are more open to the risk of change.Lessons can be learned by established companies from the experiences of these companies, though.
In Agile, as with DevOps, there are layers to the system. In an Agile world, there are methods (Scrum, XP etc.) beneath which exist the Practices (TDD, Continuous Integration) beneath which exist the tools (JUnit, CruiseControl etc.)DevOps hasn’t yet evolved a distinct layer of methodologies, but we can expect that these will emerge as intellectual empires are built.
So whether or not you are committed to implementing a DevOps approach.