1. DevOps
WHY SHOULD WE CARE?

2. AGENDA
ABOUT TODAY
WHY ARE WE HERE TODAY?
CULTURE
AUTOMATION
MEASUREMENT
SHARING
THE END GOAL!
DEVOPS

3. WHAT (NOT) TO EXPECT
Ready to launch
Discussions about tooling
Financial statements
Awareness about DevOps
A seed for a collaborative future
Conversationstarter
ABOUT TODAY

4. He works for operations
He is happy when everything is
“up and running”
He loves stability
He knows about scripts
He runs the infrastructure
Meet Wim

5. He works as a developer
He is happy when he can deliver
new stuff
He loves agility
He know how to write software
He uses the infrastructure
Meet Tim

6. WHY ARE WE HERE TODAY?

7. THE PROBLEM
Deploying a New Application
Friday evening at 16u59
DEV: Finished, going home.
PM: Put this code live, here’s a tarball… NOW!
OPS: What database? Security? Backups?
High Avalability? Scalability? Who’s on call?

8. 10 Days into production

9. 10 +1 Days into production

10. Managing, Tuning & Configuring
THE PROBLEM

11. Production Passwords
THE PROBLEM

12. Security
THE PROBLEM

13. Worked fine in Dev, Ops problem now
THE PROBLEM

14. We need a new Server and we need it fast, like yesterday
Oh yea and we want super specifications and admin rights!
THE PROBLEM
Resources

15. THE PROBLEM
Shadow IT

16. THE PROBLEM
PRODUCTION ENVIRONMENT

17. ENOUGH!
ISN’T THERE A BETTER WAY?

18. DevOps
THERE IS A BETTER WAY…
It’s not about the tools
It’s about change
It’s about the people

19. [X] a new tool
[X] a new team
[X] something you can create overnight
[X] strict rules or tools or a definition
[X] something new
DevOps is not

20. DevOps is about
[v] Culture
[v] Automation
[v] Measurement
[v] Sharing

21. Company confidential – Do not distribute without notice ©AE 2014 n 21
WHERE HAPPINESS STARTS!
TURNING POINT

22. Try to understand each other!
What blocks the other one?
What can you do about it?
Never them or they, use US or WE instead!
[v] Culture

23. - Assemble a team
- Talk to the business people
- Define the work
- Find your constrains
- Put an electric fence around
production environment

24. Goal
Highly effective team

25. The First Way: The way of the Flow
Create One Step Environments
[ ] Automation

26. THE WORKFLOW
Create One Step Environments

27. CREATE A COOKBOOK

28. "Automated tests transform fear into boredom.“
– Eran Messeri, Google
“You build it, you run it.”
– Werner Vogels, CTO, Amazon

29. GOALS FOR THE FIRST WAY:
ü Creating single repository for code and environments
ü Consistent Dev, Test and Production environments,
all properly built before deployment begins
ü Features being deployed daily without catastrophic failures
ü Decreased lead time
ü Faster cycle time

30. CLOUDBURSTING
When you run out of your computing resources in your internal
data center, you “burst” the additional workload to an external
cloud on an on-demand basis

31. [v] Measurement
The Second Way: Feedback

32. The Second Way is about
creating the right to left feedback loops.
The goal of almost any process improvement
initiative is to shorten and amplify feedback loops
so necessary corrections can be continually made.

33. “As a developer, there has never been a more
satisfying point in my career than when I wrote
the code, I pushed the button to deploy it,
I watched the metrics to see if it actually worked
in production, and fixed it if it broke.”
– Tim Tischler
Director of Operations Engr,
Nike, Inc.

34. DEVELOPERS ACTUALLY LOOK AT HE LOGS!
Dev Guy Ops Guy Steve B.

35. GOALS FOR THE SECOND WAY:
ü Defects and security issues getting fixed faster than ever
ü Disciplined automated testing enabling many simultaneous
small, agile teams to work productively
ü All groups communicating and coordinating better
ü Everybody is getting more work done

36. [v] Sharing
The Third Way:
Continual Experimentation & Learning

37. BREAK THINGS EARLY AND OFTEN
“Do painful things more frequently, so you can
make it less painful… We don’t get pushback
from Dev, because they know it makes rollouts
smoother.”
– Adrian Cockcroft,
Former Architect, Netflix
(Now Technology Fellow,
Battery Ventures)

38. The Third Way is about creating a culture where
continual experimentation, taking risks and learning from
failure; and understanding that repetition and practice is
the prerequisite to mastery.
Experimentation and taking risks are what ensures that we
keep pushing to improve.

39. INJECT FAILURES OFTEN
Design each distributed system to expect and tolerate
failure from other systems on which it depends.
GOALS FOR THE THIRD WAY:

40. PETS AND CATTLE

42. YOU DON’T CHOOSE CHAOS MONKEY, CHAOS MONKEY CHOOSES YOU

43. SUMMARY

45. Remember
- Focus on the product first. Then the people we need to build the product.
Group them into a team and let them find their own way together.
- A fully autonomous team; no blockers or barriers to communication
- Capabilityand contribution is important, job titles are not
- Build, Deploy and Test the entire service with one command

47. Management must move from
approver to enabler.
BUT…

48. Who Is Doing DevOps?
Google, Amazon, Netflix, Etsy, Spotify, Twitter, Facebook …
CSC, IBM, CA, SAP, HP, Microsoft, Red Hat …
GE Capital, Nationwide, BNP Paribas, BNY Mellon,
World Bank, Paychex, Intuit …
The Gap, Nordstrom, Macy’s, Williams-Sonoma, Target …
General Motors, Northrop Grumman, LEGO, Bosche …
UK Government, US Department of Homeland Security …
Kansas State University…

50. The End goal
§ Improve business operational efficiency
§ Accelerate application development

51. A bit of history…
Devops is not a plan, it’s a reaction