- Patrick Debois has been involved in DevOps since 2009, organizing the first Europe DevOps conference in 2010 and speaking at many events.
- He works as a freelance consultant and has contributed to open source projects involving virtualization, configuration management, and DevOps.
- The document discusses various DevOps practices, tools, methodologies, maturity levels, and debates such as the role of DevOps certification and job titles. It promotes an upcoming 5th anniversary DevOps conference in Ghent, Belgium in October 2014.
Serena DevOps Drive In - Patrick Debois Live on DevOps: 5 Years in, what does the future hold? (slides)
1.
2.
3. 5 years
of
Devops
Patrick Debois
Thursday 28 August 14
4. Organizer Since 2009 Europe Organizer 2010
First Europe Training 2010
Speaker
Monitoring Chapter Technical Reviewer Co-Author Veewee / Sahara / Mccloud
Freelance consultant http://github.com/jedi4ever
Engineer
Mass Interactions for Big Audiences
Libvirt - Fog
Blog: http://jedi.be/blog - Twitter: @patrickdebois - #devops
Thursday 28 August 14
5. devops for networks
promise theory
Devops cookbook
A #devops
meme Map
devops enterprise
hiring devops
empathy
obama devops
hangops
more Deming
monitoringlove
infracoders
v-shaped people
@devopsborat
more devopsdays
Devops Café
Devops Certification
Trademark attempt
noops
choose your
own adventure
Devops Weekly
devops is a scam
Devopsdays Ghent 2009
10 deploys a day - Velocity
Continuous Delivery
CAMS
KanbanOps
Gartner
451 group
# devops
company
acquisitions
rugged devops
Phoenix Project
antifragility
Lean Startup
Agile
Infrastructure as code
Cloud
Cloud
4 steps to Epiphany
opsschool
itskeptic
myopic devops
lordcope blogpost “what is devops”
in search of incertainty
Thursday 28 August 14
9. Area 1: Extend delivery
to production
DEV OPS
Area 2: Extend operations
feedback to project
Area 4: Embed Operations
knowledge into Project
Area 3: Embed Project
knowledge into Operations
http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/
Thursday 28 August 14
10. “Layers per Area”
Think ‘tags’ of things you do in an area
Tools Can you ‘technically’
do it
Process Should you do it
People
Will you do it
(culture)
Area X
Thursday 28 August 14
11. “Area Maturity Level”
a way to quantify
your progress
http://groups.google.com/group/devops/browse_frm/thread/f3de603a4cea493e?scoring=d&
Thursday 28 August 14
12. CMMI - Maturity Levels (Process centric)
Initial Unpredictable
poorly controlled and reactive
Managed Focused on project, often
and reactive
Defined Focused on organization and
proactive
Quantitatively Managed Measured and controlled
Optimizing Focus on
Improvement
Thursday 28 August 14
13. Alternative Maturity Levels
(cfr. Continuous Integration Model)
Intro Using Source Control ...
Novice Builds Triggered by
Commit ...
Intermediate Automated Deployment
to Testing ...
Advanced Automated Functional
Testing ...
Insane Continuous Deployment
to Prod ...
http://blogs.urbancode.com/continuous-integration/continuous-integration-maturity-model/
Thursday 28 August 14
14. Name Area
Provision dev/test and
prod from the same src
DEV delivery to Prod
Embed Project
knowledge
Embed Operations
knowledge
feedback from Prod OPS
Layer Tools Level Intro
Practice: Use a configuration mangement system like chef/puppet to provision
dev,test and prod from the same source
Pattern: Automation, reuse of code
Principles: By reusing the code it gets tested more && often
more frequent/earlier feedback
Thursday 28 August 14
15. Different places where we can improve
Production
Dev, Test, QA
Business EndUser
Components (architecture)
People (process)
http://devopsdays.org/blog/2010/05/16/the-panel-experiment-and-ignite-devops/
Andrew
Schaefer
Thursday 28 August 14