The document provides an overview of DevOps fundamentals and key events in the history and evolution of DevOps. It discusses the Agile Manifesto created in 2001 to promote lightweight software development processes. It then outlines the three main transformations required for DevOps - process, technology, and culture. Process transformation involves development and operations teams working together throughout the service lifecycle. Technology transformation relies on automation and infrastructure as code. Culture transformation requires high trust, collaboration, and collective ownership. The document also discusses continuous integration, validation, delivery, deployment, and improvement as DevOps principles.

1. DevOps Fundamentals
An introduction by Kiril Serebnik
January 2016

2. About myself
AND KEY EVENTS IN HISTORY OF DEVOPS

3. me

5. The tail-wagger

6. 2000

7. 2000
2001
Agile
Manifesto

8. 2000
2006
2001
Agile
Manifesto

9. 2006
2008
DevOps
Movement kick
started during
Agile
conference
2009
O’Reilly Velocity
conference was
dedicated to
DevOps
2010
First DevOps
Conference –
DevfOpsDays
Was held in the
US
2011
DevOps
Community
starts to
develop tools
like Vagrant,
Chef, Puppet
First DevOps
Job notice
appears in
media
2013
Flood of
DevOps related
books starts to
appear
2014
2015
2001
Agile
Manifesto
2000

10. On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen
people met to talk, ski, relax, and try to find common ground, and of course, to eat. What emerged was the
Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM,
Adaptive Software Development, Crystal Clear, Feature-Driven Development, Pragmatic Programming, and
others sympathetic to the need for an alternative to documentation driven, heavyweight software
development processes convened.

11. processes and toolsover
comprehensive documentationover
contract negotiationover
following a planover
http://agilemanifesto.org/
Sorry for awful background. This is the actual background for Agile Manifesto site

13. I
II
III

14. DevOps
transformation
PROCESS Transformation
TECHNOLOGY Transformation
CULTURE Transformation

15. PROCESS
• Operations and development
engineers participate together in the
entire service life-cycle from design
through to production support
• An incident command system is in
place where the development team is
involved in incident resolution
• Processes are re-engineered to be
more efficient, lean and repeatable
smooth the process of developing and
releasing code

16. TECHNOLOGY • DevOps technology improvements
place reliance on build, test and
release automation along with
orchestration across technologies and
integrated tool chains
• Infrastructure is treated as code
• The DevOps team delivers small
chunks of value to the developers
more often
• Recovery oriented computing – fail
forward
keeping the heart beating

17. CULTURE
• High trust, team culture
demonstrating effective, seamless
cross-functional collaboration and
open communications
• Demonstrated servant leadership –
enable and serve from the top down
• Established collective ownership
• Creativity is encouraged
collaboration mindset between
individuals

20. Continuous …
Everything
Don’t stop to improve any
PROCESS, SERVICE, PRODUCT

21. Continuous INTEGRATION
changes are immediately built, tested and
reported on when they are added to a larger
code base.
build
test
immediate feedback on system-wide
impact of local changes
gathered metrics show overall code quality
Continuous VALIDATION
fail
pass

22. Continuous VALIDATION
shared provider of both scheduled and
event-driven regression and performance
test suits
extreme visibility into the entire
architecture of a product both at component
and system-vide level
avoided failures, reduced testing and release
costs, picture of health of the product
on constant basis
Continuous DELIVERY
componen
t
component
fail
pass

23. Continuous DELIVERY
teams produce software in short cycles, ensuring
that the software may be reliably
conveyed for consistent, low-risk releases at
any time
releasing software faster and more
frequently
help organization to remain lean, agile and
innovative independently of its size
Continuous DEPLOYMENT
componen
t
component
release release

24. Continuous DEPLOYMENT
any piece of code written for a product instantly
brought to production following well
defined deployment route
consistently deploy code to production as
features are completed, and as soon as
they have met the release criteria
Continuous IMPROVEMENT
customer
customer
release release
always have a possibility to get a root cause
of unexpected failures in the system and
eliminate them

25. Continuous IMPROVEMENT
releasing software faster and more
frequently
organization remains lean, agile and
innovative no matter the size
customer
customer

26. integration validation delivery deployment improvement

27. minimize lead time, the time
elapsed between development writing
one new line of code and this new
code being used by live users, in
production
Integration
Validation
Delivery
Deployment
Improvement

31. Toolchain
Ultimate DevOps Bedrock

32. BI Monitoring Collaboration Continuous Integration
Build
Deployment
Release
Management
Repo Management
Security
Source
Code
Manage
ment
Logging
Config Management
Networking
Config Provisioning
Testing
Cloud IaaS
Databases
Micro Services
Provisioning

33. Collaboration Continuous Integration
Build Cloud IaaS
Databases
Deployment
Micro Services
Release
Management
Security
Source
Code
Manage
ment
Config Provisioning
Testing
BI Monitoring
Repo Management
Logging
Provisioning
Config Management
Networking

34. Cloud IaaS
Databases
Deployment
Micro Services
Release
Management
Security
BI Monitoring
Repo Management
Logging
Provisioning
Config Management
Collaboration Continuous Integration
Build
Source
Code
Manage
ment
Config Provisioning
Testing
Networking

35. BI Monitoring Collaboration Continuous Integration
Build
Deployment
Release
Management
Repo Management
Security
Source
Code
Manage
ment
Logging
Config Management
Networking
Config Provisioning
Testing
Cloud IaaS
Databases
Micro Services
Provisioning

36. Cloud IaaS
Databases
Deployment
Micro Services
Release
Management
Security
BI Monitoring
Repo Management
Logging
Provisioning
Config Management
Collaboration Continuous Integration
Build
Source
Code
Manage
ment
Config Provisioning
Testing
Networking

37. Cloud IaaS
Databases
Deployment
Micro Services
Release
Management
Security
BI Monitoring
Repo Management
Logging
Provisioning
Config Management
Build
Config Provisioning
Testing
Networking

38. Databases
Deployment
Release
Management
BI Monitoring
Logging
Provisioning
Build
Testing
Config Management
Config Provisioning

39. BI Monitoring Collaboration Continuous Integration
Build
Deployment
Release
Management
Repo Management
Security
Source
Code
Manage
ment
Logging
Config Management
Networking
Config Provisioning
Testing
Cloud IaaS
Databases
Micro Services
Provisioning

45. DEVOPS