Leon Rosenberg is an architect and DevOps expert who has been programming since 1997 and building portals since 2000. This document discusses DevOps and keeping applications live at runtime. It addresses how development creates business value but that value must be rolled out. It emphasizes automating deployment processes, using tools like Maven, Jenkins and Bash. It stresses the importance of a DevOps culture with trust between developers and operations and hiring the right developers. It also discusses monitoring, understanding production systems, and using techniques like chaos monkey testing to build reliability.

1. Devops@Runtime
22 Mai 2013
http://leon-rosenberg.net (@dvayanu)

2. Who am I?
• Leon Rosenberg - Architect, DevOps.
• 1997 - Started programming with Java.
• 2000 - Started building Portals.
• 2003 - Started anotheria.net.
• 2007 - Started MoSKito.

4. What is this about?
• Classic DevOps - Bring it Live!
• Runtime - Keep it Live!
• Getting there...

5. What CEO wants

8. DevOps
• “oh these developers don’t get it”
• “oh these ops guys don’t get it”
• devs inflict change, ops resist change
additional slide

9. Rollout

11. DevOps is to deployment what
agile is to software
development.

12. Automate

13. Tools
Maven + Jenkins + Bash

14. We rolled out!
• Are we done now?
• Or did it just start... ?

15. BusinessValue
• Development creates business value.
• Business value is rolled out.
• B(n) = B(n-1) + B(r).
• B(n-1) > B(r).

17. Production

18. Keep the coins falling

19. 19
Problem finding and fixing
Availability Hosting needs
Cost per user
RAM/CPU RequirementsService Level
BUGs
new features
architectural changes
Seasonal traffic Disaster recovery
Provider change
product pivotsnew markets
Marketing campaigns

22. Best Monitoring Tool

24. How do I get to a
Common System State?
DevOps@Runtime!

25. Let’s give root to all
developers?!

27. Let’s build up a DevOps
Department?

28. It’s DEVops not OPSdev.

29. Do classic Dev and Op Roles
still exist?

30. DevOps Culture
Trust

31. Managers should:
Trust the developers.

32. Managers shouldn’t:
blame for fuckups.

33. Managers should:
Hire right developers.

34. Motivation?
• Money
• Fame and honour
• Self-fulfillment
• Passion
• Pride Professionalism

35. Managers should:
Hire right developers.

36. Ops should:
Trust the devs

37. Devs should:
trust the system

38. 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

39. Monitoring
Collect
Analyze
Inspect

41. Draw Pictures

44. Build history and learn what
changes
Every monday at 22:00 - 22:05

45. Don’t touch it!
Production

46. Fault Tolerance

47. Chaos Monkey

48. Load feedback

49. Test Restore not Backup

50. Clean logs

51. End 2 End Tests

52. ...

54. DevOps

55. Contra
• Just another hype?
• Costs money?
• I need to learn puppet, chef, ...?
• Developers are not able/not willing... ?
• Sysadmin will manage it. Alone. Somehow.

56. What does DevOps bring to
the table that makes it unique?

57. DevOps is not the end of
road, it’s the road itself, and
each step on this road makes
your life easier.

59. Thanx
• http://devopsreactions.tumblr.com/