Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
What is DevOps?
Book Extract / Summary
Mike Loukides O’ Reilly
The NoOps Debate
• Adrian Cockcroft’s article about NoOps at Netflix
• Ignited a controversy that has been smouldering for...
BOFH (“Bastard Operator from Hell”)
• serves as a reminder of those days, when disasters happen and
operations fire fight ...
O’Reilly’s Velocity Conference
Infrastructure as Code
• If you’re going to do operations reliably, you need to make it
reproducible and programmatic
Autonomous Correction
• software to detect a misbehaving EC2 instance automatically, destroy
the bad instance, spin up a n...
modern applications, running in the
cloud, still need to be resilient
James Urquhart
Operations doesn’t go away
it becomes part of the development
Not an uber developer,
• who understands big data,
• web performance optimization,
• application middleware,
• fault toler...
Cooperation not isolation
cooperate and collaborate with the developers who create the applications.
… movement informally known as “DevOps.”
Amazon’s EBS outage 2013 - NetFlix
• demonstrates how the nature of “operations” has changed
• Netflix, knew how to design...
that the best thing about the EBS outage
was that his guys weren’t running around
like crazy trying to fix things
JD Long ...
The bonding needs to be fluid, but that’s
precisely the point.
The task — providing a solid, stable application for custom...
Operations is crucial to success,
• but operations can only succeed to the extent that it collaborates
with developers and...
Its not about fire fighting but eliminating
fires
it’s important not to divorce developers
from the consequences of their work
since the fires are frequently set by their
c...
Pin Pointing Rather than finger-pointing
post-mortems that try to figure out the causality of an outage is old world
So What is DevOps
• interminable up-front planning,
• “minimum viable product,”
• continuous integration,
• continuous dep...
PERL
• no sysadmin worth his salt came without a portfolio of Perl
• Perl was designed as a programming language for autom...
Puppet and Chef
• automate configuration,
• every machine has an identical software configuration
• running the right serv...
Vagrant
• ensure that all your virtual machines are constructed identically from
the start
ChaosMonkey?
• randomly kills instances and services within the application.
• Resilience embedded Operations
DTrace
• provide insight into almost every aspect of system behavior;
• 1 big challenges facing modern operations groups i...
EMT training sessions are essential for
operations staff so that they understood how
to handle themselves and communicate ...
Ending thoughts
• Hadoop cluster to monitor the Hadoop cluster
• Operations in change groups are playing a huge role in th...
Sincere Thanks to Mike Loukides &
O’Reilly Media
Vishwanath Ramdas
This is a book summary extract for wiki reference
Upcoming SlideShare
Loading in …5
×

DevOps 201607

190 views

Published on

My read and summarization of the booklet on devops by mike loukides from O Reilly, great read for starters.. a good reference on automation, inreastructure as code

Published in: Internet
  • Be the first to comment

DevOps 201607

  1. 1. What is DevOps? Book Extract / Summary Mike Loukides O’ Reilly
  2. 2. The NoOps Debate • Adrian Cockcroft’s article about NoOps at Netflix • Ignited a controversy that has been smouldering for sometime . • John Allspaw’s gave a detailed response to Adrian’s article • The Key here is not semantics and vocabulary but concepts and principles that help better operations and provide resilient services
  3. 3. BOFH (“Bastard Operator from Hell”) • serves as a reminder of those days, when disasters happen and operations fire fight and blame game is on.. • Being told “We need 125 servers online ASAP, and there’s no time to automate it is a recipe for disaster.” - Sascha Bates
  4. 4. O’Reilly’s Velocity Conference
  5. 5. Infrastructure as Code • If you’re going to do operations reliably, you need to make it reproducible and programmatic
  6. 6. Autonomous Correction • software to detect a misbehaving EC2 instance automatically, destroy the bad instance, spin up a new one, and configure it, all without interrupting service.
  7. 7. modern applications, running in the cloud, still need to be resilient James Urquhart
  8. 8. Operations doesn’t go away it becomes part of the development
  9. 9. Not an uber developer, • who understands big data, • web performance optimization, • application middleware, • fault tolerance in a massively distributed environment, • we need operations specialists on the development teams.
  10. 10. Cooperation not isolation cooperate and collaborate with the developers who create the applications.
  11. 11. … movement informally known as “DevOps.”
  12. 12. Amazon’s EBS outage 2013 - NetFlix • demonstrates how the nature of “operations” has changed • Netflix, knew how to design for reliability; • they understood resilience, • spreading data across zones. • resilience was a property of the application, • EBS was down but Netflix’s ChaosMonkey ensured resilience
  13. 13. that the best thing about the EBS outage was that his guys weren’t running around like crazy trying to fix things JD Long tweet
  14. 14. The bonding needs to be fluid, but that’s precisely the point. The task — providing a solid, stable application for customers — is the same.
  15. 15. Operations is crucial to success, • but operations can only succeed to the extent that it collaborates with developers and participates in the development of applications that can monitor and heal themselves.
  16. 16. Its not about fire fighting but eliminating fires
  17. 17. it’s important not to divorce developers from the consequences of their work since the fires are frequently set by their code. Allspaw points out
  18. 18. Pin Pointing Rather than finger-pointing post-mortems that try to figure out the causality of an outage is old world
  19. 19. So What is DevOps • interminable up-front planning, • “minimum viable product,” • continuous integration, • continuous deployment.  The Tool Set
  20. 20. PERL • no sysadmin worth his salt came without a portfolio of Perl • Perl was designed as a programming language for automating system administration. I
  21. 21. Puppet and Chef • automate configuration, • every machine has an identical software configuration • running the right services.
  22. 22. Vagrant • ensure that all your virtual machines are constructed identically from the start
  23. 23. ChaosMonkey? • randomly kills instances and services within the application. • Resilience embedded Operations
  24. 24. DTrace • provide insight into almost every aspect of system behavior; • 1 big challenges facing modern operations groups is developing analytic tools and metrics that can take advantage of the data that’s available to predict failures
  25. 25. EMT training sessions are essential for operations staff so that they understood how to handle themselves and communicate with each other in an emergency Jesse Robbins
  26. 26. Ending thoughts • Hadoop cluster to monitor the Hadoop cluster • Operations in change groups are playing a huge role in the deployment of new, more efficient protocols for the web, like SPDY. • Lot of our “best practices” for TCP tuning were developed in the days of ISDN and 56 Kbps analog modems, and haven’t been adapted to the reality of Gigabit Ethernet, OC48* fiber,
  27. 27. Sincere Thanks to Mike Loukides & O’Reilly Media Vishwanath Ramdas This is a book summary extract for wiki reference

×