• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
DevOps @ Runtime
 

DevOps @ Runtime

on

  • 386 views

DevOps@Runtime Talk I held at OOSE Training Center in Hamburg covers the runtime perspective of the DevOps Culture and how to get there

DevOps@Runtime Talk I held at OOSE Training Center in Hamburg covers the runtime perspective of the DevOps Culture and how to get there

Statistics

Views

Total Views
386
Views on SlideShare
344
Embed Views
42

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 42

http://www.oose.de 42

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    DevOps @ Runtime DevOps @ Runtime Presentation Transcript

    • Devops@Runtime22 Mai 2013http://leon-rosenberg.net (@dvayanu)
    • Who am I?• Leon Rosenberg - Architect, DevOps.• 1997 - Started programming with Java.• 2000 - Started building Portals.• 2003 - Started anotheria.net.• 2007 - Started MoSKito.
    • What is this about?• Classic DevOps - Bring it Live!• Runtime - Keep it Live!• Getting there...
    • What CEO wants
    • DevOps• “oh these developers don’t get it”• “oh these ops guys don’t get it”• devs inflict change, ops resist changeadditional slide
    • Rollout
    • DevOps is to deployment whatagile is to softwaredevelopment.
    • Automate
    • ToolsMaven + Jenkins + Bash
    • We rolled out!• Are we done now?• Or did it just start... ?
    • BusinessValue• Development creates business value.• Business value is rolled out.• B(n) = B(n-1) + B(r).• B(n-1) > B(r).
    • Production
    • Keep the coins falling
    • 19Problem finding and fixingAvailability Hosting needsCost per userRAM/CPU RequirementsService LevelBUGsnew featuresarchitectural changesSeasonal traffic Disaster recoveryProvider changeproduct pivotsnew marketsMarketing campaigns
    • Best Monitoring Tool
    • How do I get to aCommon System State?DevOps@Runtime!
    • Let’s give root to alldevelopers?!
    • Let’s build up a DevOpsDepartment?
    • It’s DEVops not OPSdev.
    • Do classic Dev and Op Rolesstill exist?
    • DevOps CultureTrust
    • Managers should:Trust the developers.
    • Managers shouldn’t:blame for fuckups.
    • Managers should:Hire right developers.
    • Motivation?• Money• Fame and honour• Self-fulfillment• Passion• Pride Professionalism
    • Managers should:Hire right developers.
    • Ops should:Trust the devs
    • Devs should:trust the system
    • Trust The System?• To trust the system you have to understandthe system.• System behaves live different.• Learn the system where it matters!additional slide
    • MonitoringCollectAnalyzeInspect
    • Draw Pictures
    • Build history and learn whatchangesEvery monday at 22:00 - 22:05
    • Don’t touch it!Production
    • Fault Tolerance
    • Chaos Monkey
    • Load feedback
    • Test Restore not Backup
    • Clean logs
    • End 2 End Tests
    • ...
    • DevOps
    • Contra• Just another hype?• Costs money?• I need to learn puppet, chef, ...?• Developers are not able/not willing... ?• Sysadmin will manage it. Alone. Somehow.
    • What does DevOps bring tothe table that makes it unique?
    • DevOps is not the end ofroad, it’s the road itself, andeach step on this road makesyour life easier.
    • Thanx• http://devopsreactions.tumblr.com/