Upgrade to Pro — share decks privately, control downloads, hide ads and more …

What is DevOps and why should I care?

mattrogish
November 01, 2014

What is DevOps and why should I care?

Why should you care about devops? Then, how to not mess it up once you do care.

mattrogish

November 01, 2014
Tweet

More Decks by mattrogish

Other Decks in Programming

Transcript

  1. What Is DevOps & Why Should I Care? @MattRogish matt.rogish@gmail.com

  2. About Me • Programmer (Ruby on Rails), DBA, CTO •

    Consultant • Founder • CTO RailsMachine.com / ReactiveOps
  3. Do I Need Ops?

  4. None
  5. YES

  6. YES*

  7. None
  8. None
  9. None
  10. None
  11. How Not To Do It

  12. Traditional Dev Handoff

  13. None
  14. None
  15. The New Dev Operator?

  16. None
  17. pg_dump: SQL command failed pg_dump: Error message from server: ERROR:

    canceling statement due to conflict with recovery DETAIL: User query might have needed to see row versions that must be removed. FATAL: database system identifier differs between the primary and standby FATAL: the database system is starting up
  18. None
  19. So What is DevOps?

  20. The Ops Trinity Availability Performance Security Happy App Users

  21. Matt Rogish “DevOps is a philosophical and cultural movement to

    transform Ops from a Cost Center to a Profit Center, acting as a force-multiplier for Product Development.”
  22. What Does This Mean?

  23. The New Ops Role • Provide tools and support to

    developers • Ops Trinity Evangelists • Infrastructure Experts
  24. Tools and Support • Graphing, Logging, Display • Continuous Integration

    & 
 Deployment • Feature Flags, Reporting • Automation
  25. Ops Trinity Evangelists • Availability • Performance • Security

  26. Infrastructure Experts • DBAs • System Automation • Network Admins

    • Platform Admins
  27. How to DevOp?

  28. Who is your 007?

  29. Starting Out • Create slack time for important improvement projects

    • Keep batch sizes small and the planning horizon short (e.g., weeks, not months) • Keep prioritizing higher “the system of work” over “doing work” • Need Redundancy to Avoid Burnout
  30. Stuff to do while small • Lean All The Things

    • Automation in the Small • Make Informed Tradeoffs
  31. While growing • Increase Test Confidence • Automate All The

    Things • Continuous Product
 Delivery
  32. At Scale • Dedicated Ops Teams 
 or Outsource •

    Flexible Infrastructure • Lean UX, Lean DevOps 
 -> Lean Product
  33. Tools of the Trade

  34. Graphing, Stats • statsd, graphite • elasticsearch, logstash, kibana

  35. Cloud Automation • terraform, packer • puppet, chef • ansible,

    salt
  36. Cloud Infrastructure • Xen • OpenStack/CloudStack • Docker, CoreOS

  37. None
  38. How to DevOp? @MattRogish matt.rogish@gmail.com