Interns What Is DevOps


Published on

Presentation at my company to all the Interns about What DevOps is to me and why I'm passionate about it.

NOTE: Liberally gathered stuffs from the internetz. If I did something wrong by doing so or by you let's chat. I want to work with you to make it better :)

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • I’m going to ask you right now to find something you are passionate about.
  • My name is Aaron Blythe, I’ve been here at Cerner for over 10 years.I have been passionate about many things in that time.I worked on PowerChart, I was the Quality Architect for the IP Development Organization where we focused on Root Cause Analysis at a time where client perception of Millennium Quality was very low.I co-created CernerCast, which was a tool to share ScreenCasts or Videos with other engineersI created a site where we could tracking and correllate every Windows crash that happened at a client site.I worked on one of our first Rails Apps here at Cerner. The Cerner Store.Now I want to share with you what I am currently passionate about.
  • I’m going to take a tangent for 3 minutes to Let Derek Sivers, creator of CD Baby explain to you what a movement is…
  • Where did the term come from? <click>Velocity Conference 2009 <click>Two Men from Flickr – Everyone familiar with Flickr?... Photo sharing site? Who has a Flickr account?One a Dev… John Allspaw <click>One an Ops… Paul Hammond <click>
  • John Allspaw and Paul Hammond (Flickr) “In the last week there were 67 deploys of 496 changes by 18 people” – Flickr Dev Blog, December 17th 2008.
  • The CFEngine project began in 1993 as an Open Source Projectauthor Mark Burgess (then a post-doctoral fellow of the Royal Society at Oslo University, NorwayLike many post-docs and PhD students, Burgess ended up with the task of managing Unix workstations, scripting and fixing problems for users manually. Scripting took too much time, the flavours of Unix were significantly different, and scripts had to be maintained for multiple platforms, drowning in exception logic.
  • We have memes
  • We have slogans
  • How does this apply to DevOps?So how many people recognize these characters? And I’m not just talking about Spock and Scotty, how many people recognize the traditional IT roles embedded in their behaviors.Metaphor Attribution – Andrew Shafer, now of Rackspace
  • Grey # Physical Nodes, Purple # Virtual Nodes
  • adjust their performance to the current conditionsresources and time are finiteSuccess is the ability to anticipate the changing shape of risk before damage occursfailure is simply the temporary or permanent absence of that.
  • With multi-tenantBig Data solutions we have an awesome opportunity in that when we fix or enhance, we fix or enhance for all – minimizing a lot of repetitive work. Remember we like to eliminate or automate repetitive work.However if we break for one client we also break for all or many. The stakes are high.
  • Chernobyl and Three Mile IslandWe can learn a lot from the Nuclear industry and the Air-plane industry for software. They have excellent monitoring that they have built over the years.Alert fatigue is a fairly consistent worry.
  • Does everyone know what infrastructure is?Very broad topic…
  • We are talking about problems that are costs for businesses.If you haven't been in this situation yet, and you continue to work in Software then you soon will be.I have lived on both sides of this line.The situation is some proprietary software that you are relying on has a bug that is very specific to the situation that you have.You can reproduce this every time.The developers of the system are sure that this could never be a problem.Further they have no in-house testing system that looks anything like what you have at your site as a client of theirs.
  • ESR – of the Cathedral and the Bazaar Predicted middleware and databases will remain more mixed open source and closed source after what he called the “Revolution”
  • Anyone know where the word “Engineer” comes from?
  • As Devs we cannot act like this.
  • Or this
  • And come on GumpySysAdmins, lighten up
  • And it shouldn’t only be the Ops walking out like this on a Good Day
  • This is what working together looks like.
  • So be passionate about something
  • Maybe you are not passionate about the same things that I am, but be passionate about something
  • Interns What Is DevOps

    1. 1. Question… • Have any of you installed software before? @ablythe
    2. 2. Passion @ablythe
    3. 3. What is DevOps? Aaron Blythe @ablythe
    4. 4. DevOps is a Movement What is a Movement? @ablythe
    5. 5. Where did the term come from? Dev Ops @ablythe
    6. 6. Velocity Conference 2009 “10+ Deploys Per Day” “Dev and Ops Cooperation at Flickr” See: @ablythe
    7. 7. But It Didn’t Start There – Just Gained Mindshare 1993 @ablythe
    8. 8. The Devops Movement is Gaining Momentum @ablythe
    9. 9. The Devops Movement is Gaining Momentum @ablythe
    10. 10. What is Devops? • DevOps is about the people • Dev – The Software Engineer • Ops – The System Engineer @ablythe
    11. 11. The players Dev Ops&
    12. 12. Meet Dev • Little bit weird • Sits closer to the boss • Thinks too hard Don’t hate the player …
    13. 13. Meet Ops • Pulls levers & turns knobs • Easily excited • Yells a lot in emergencies Why you be hatin ? ! ?
    14. 14. Why DevOps? – Explosive Growth1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 @ablythe
    15. 15. Why DevOps? – Distributed Architecture @ablythe
    16. 16. Racking Servers @ablythe
    17. 17. Why Devops? - Drive To Automate @ablythe
    18. 18. Devs - Continuous Integration Source Control Build Processor Artifact Repository @ablythe
    19. 19. Ops - Continuous Deployment Source Control Build Processor Artifact Repository Configuration Management Node Node Node Monitoring Troubleshoot @ablythe
    20. 20. Where Does the term “Engineer” Come From? @ablythe
    21. 21. Where Does the term “Engineer” Come From? @ablythe
    22. 22. Where Does the term “Engineer” Come From? @ablythe
    23. 23. Where Does the term “Engineer” Come From? @ablythe
    24. 24. Where Does the term “Engineer” Come From? @ablythe
    25. 25. Resilience Engineering @ablythe
    26. 26. Resilience Engineering • 'failure' is the result of the adaptations necessary to cope with the complexity of the real world • rather than a breakdown or malfunction @ablythe
    27. 27. Monitoring @ablythe
    28. 28. Engineering Meltdowns @ablythe
    29. 29. Infrastructure As Code @ablythe
    30. 30. Infrastructure is Complex @ablythe
    31. 31. Application See Node @ablythe
    32. 32. Application Application Database See Nodes @ablythe
    33. 33. Application App Databases See Nodes Grow @ablythe
    34. 34. App Servers App Databases See Nodes Grow @ablythe
    35. 35. App LB App Servers App Databases See Nodes Grow @ablythe
    36. 36. App LBs App Servers App Databases See Nodes Grow @ablythe
    37. 37. App LBs App Servers App DB Cache App DBs See Nodes Grow @ablythe
    38. 38. App LBs App Servers App DB Cache App DBs Infrastructures have topology @ablythe
    39. 39. Round Robin DNS App Servers App DB Cache App DBs Floating IP? Yours is a snowflake @ablythe
    40. 40. App LBs App Servers NoSQL DB slaves Cache DB Cache DBs Complexity increases quickly @ablythe
    41. 41. USA EUR AUS It increases globally... @ablythe
    42. 42. Roots in Open Source @ablythe
    43. 43. Open Source for Infrastructure • What I am not saying: – Open Source for all software – Open Source only (many of these suites/companies have Enterprise options). • I am saying: – When the core is open source you get "Linus' Law” – Since you are a developer, you can crack the code and just fix it. @ablythe
    44. 44. @ablythe
    45. 45. Open Source - Operating Systems Desktop Servers @ablythe
    46. 46. Open Source – Web Servers @ablythe
    47. 47. Open Source - Databases @ablythe
    48. 48. Big Data/NOSQL @ablythe
    49. 49. @ablythe
    50. 50. Open Source • So most of our stack is already open source on the web • What we provide as businesses is not this computer science framework, but business value @ablythe
    51. 51. DevOps - it is about the people @ablythe
    52. 52. @ablythe
    53. 53. @ablythe
    54. 54. @ablythe
    55. 55. @ablythe
    56. 56. @ablythe
    57. 57. @ablythe
    58. 58. @ablythe
    59. 59. Your Assignment • Install Ubuntu somewhere • Install Ruby (maybe through RVM) • Install rails • Run ‘rails new’ • Install vagrant/virtual box • Install chef-solo • Deploy your creation on Heroku • Send me a link on twitter @ablythe @ablythe