demystifying devops
TRANSCRIPT
The journey so far… D
evel
oper
s bu
ilt
and
ran
the
syst
ems
Developers built the systems
Operators ran the systems
Developers built the systems
Testers tested the systems
Sys Admin managed the systems
Operators ran the systems
???
Key changes… • From top-down predictive planning => team-driven
adaptive planning • From documentation-driven sequential phases =>
working software each iteration • From episodic delivery of all features => incremental
delivery of highest-value features • Dev + Test => One team / agile developers – Old Dev + Test capabilities => New Dev – Old Test + Dev capabilities => New Test
…and the problems ensued! Deployment was still a major risk
When deployed, software would invariably underperform
Changes were episodic, and way too risky
When problems were found, “Us Vs They” blame game
Time/cost to find issues was huge, to fix is even more
…
The Wall of Confusion: One Company, Two Mindsets…
http://www.olindata.com/blog/2014/01/what-devops http://dev2ops.org/wp-content/uploads/2010/02/WallOfConfusion.png
So, what is Devops? The term was coined by Patrick Debois in 2009. He wanted to extend Agile principles into sys admin and ops.
Enable collaboration between all teams involved in building, shipping and managing a feature
Developers don’t just focus on functionality. Performance and Reliability are just as important.
Operations don’t get involved only towards the end, but throughout the development lifecycle.
Tools might help, especially for large deployment, but culture comes tops.
DevOps Principles
Develop and test against production-like systems
Deploy with repeatable, reliable processes
Monitor and validate operational quality
Amplify feedback loops
DevOps for Dummies – Sanjeev Sharma
Success Factors
http://www.ca.com/us/lpg/ca-technology-exchange/what-smart-businesses-have-gained.aspx