Devops@Runtime
22 Mai 2013
http://leon-rosenberg.net (@dvayanu)
Slide 2
Slide 2 text
Who am I?
• Leon Rosenberg - Architect, DevOps.
• 1997 - Started programming with Java.
• 2000 - Started building Portals.
• 2003 - Started anotheria.net.
• 2007 - Started MoSKito.
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
What is this about?
• Classic DevOps - Bring it Live!
• Runtime - Keep it Live!
• Getting there...
Slide 5
Slide 5 text
What CEO wants
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
DevOps
• “oh these developers don’t get it”
• “oh these ops guys don’t get it”
• devs inflict change, ops resist change
additional slide
Slide 9
Slide 9 text
Rollout
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
DevOps is to deployment what
agile is to software
development.
Slide 12
Slide 12 text
Automate
Slide 13
Slide 13 text
Tools
Maven + Jenkins + Bash
Slide 14
Slide 14 text
We rolled out!
• Are we done now?
• Or did it just start... ?
Slide 15
Slide 15 text
Business Value
• Development creates business value.
• Business value is rolled out.
• B(n) = B(n-1) + B(r).
• B(n-1) > B(r).
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
Production
Slide 18
Slide 18 text
Keep the coins falling
Slide 19
Slide 19 text
19
Problem finding and fixing
Availability Hosting needs
Cost per user
RAM/CPU Requirements
Service Level
BUGs
new features
architectural changes
Seasonal traffic Disaster recovery
Provider change
product pivots
new markets
Marketing campaigns
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
Best Monitoring Tool
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
How do I get to a
Common System State?
DevOps@Runtime!
Slide 25
Slide 25 text
Let’s give root to all
developers?!
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
Let’s build up a DevOps
Department?
Slide 28
Slide 28 text
It’s DEVops not OPSdev.
Slide 29
Slide 29 text
Do classic Dev and Op Roles
still exist?
Slide 30
Slide 30 text
DevOps Culture
Trust
Slide 31
Slide 31 text
Managers should:
Trust the developers.
Slide 32
Slide 32 text
Managers shouldn’t:
blame for fuckups.
Slide 33
Slide 33 text
Managers should:
Hire right developers.
Slide 34
Slide 34 text
Motivation?
• Money
• Fame and honour
• Self-fulfillment
• Passion
• Pride Professionalism
Slide 35
Slide 35 text
Managers should:
Hire right developers.
Slide 36
Slide 36 text
Ops should:
Trust the devs
Slide 37
Slide 37 text
Devs should:
trust the system
Slide 38
Slide 38 text
Trust The System?
• To trust the system you have to understand
the system.
• System behaves live different.
• Learn the system where it matters!
additional slide
Slide 39
Slide 39 text
Monitoring
Collect
Analyze
Inspect
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
Draw Pictures
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
Build history and learn what
changes
Every monday at 22:00 - 22:05
Slide 45
Slide 45 text
Don’t touch it!
Production
Slide 46
Slide 46 text
Fault Tolerance
Slide 47
Slide 47 text
Chaos Monkey
Slide 48
Slide 48 text
Load feedback
Slide 49
Slide 49 text
Test Restore not Backup
Slide 50
Slide 50 text
Clean logs
Slide 51
Slide 51 text
End 2 End Tests
Slide 52
Slide 52 text
...
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
DevOps
Slide 55
Slide 55 text
Contra
• Just another hype?
• Costs money?
• I need to learn puppet, chef, ...?
• Developers are not able/not willing... ?
• Sysadmin will manage it. Alone. Somehow.
Slide 56
Slide 56 text
What does DevOps bring to
the table that makes it unique?
Slide 57
Slide 57 text
DevOps is not the end of
road, it’s the road itself, and
each step on this road makes
your life easier.