DevOps

47,953 views

Published on

Published in: Technology
10 Comments
92 Likes
Statistics
Notes
No Downloads
Views
Total views
47,953
On SlideShare
0
From Embeds
0
Number of Embeds
1,319
Actions
Shares
0
Downloads
2,388
Comments
10
Likes
92
Embeds 0
No embeds

No notes for slide
  • Problem is engrained into usDevelopment-centric folks tend to come from a mindset where change is the thing that they are paid to accomplish. The business depends on them to respond to changing needs. Because of this relationship, they are often incentivized to create as much change as possible.Operations folks tend to come from a mindset where change is the enemy.  The business depends on them to keep the lights on and deliver the services that make the business money today. Operations is motivated to resist change as it undermines stability and reliability. How many times have we heard the statistic that 80% of all downtime is due to those self-inflicted wounds known as changes?as it undermines stability and reliability - Ops are keeping them from deliveringChangeCulture
  • DevOps has been broken down into four categories.CAMS, which I am going to go into detail.
  • Culture is created from these differences between dev and opsDevelopment Complete is not Live, Production, Make-Us-Millions
  • AKA less human error16mins/day over 30 people = 250days/year
  • DevOps

    1. DevOps<br />@matthew_jones<br />mjones@itree.com.au<br />
    2. Dev or Ops?<br />6 Days after a successful deployment, the server experiences high load.<br />
    3. Dev or Ops?<br />There is an issue with the build server.<br />Code isn’t building.<br />
    4. Dev or Ops?<br />Software is deployed to the test environment.<br />You can’t login to the application.<br />
    5. Dev vs. Ops<br />
    6. “It works on my machine...”<br />
    7. “It’s not the server, it’s your code.”<br />
    8. What is the role of Dev and Ops?<br />
    9. What are the roles of Devs and Ops?<br />Dev<br />Create change<br />Add or modify features<br />Ops<br />Create stability<br />Create or enhance services<br />
    10. What are the roles of Devs and Ops?<br />Dev<br />Create change<br />Add or modify features<br />Ops<br />Create stability<br />Create or enhance services<br />
    11. We Have A Problem...<br />
    12. The Problem<br /><ul><li>Disconnect between the groups
    13. Results in conflict and inefficiencies
    14. Devs don’t deploy consistent software
    15. Ops are motivated to resist change
    16. Development process is Agile
    17. Operations process is Static</li></li></ul><li>And we are missing the point of it all...<br />
    18. We are all here to ENABLE business<br />
    19. So What’s All This Change?<br />
    20. Change<br />Is required for business<br />Doesn’t mean outages<br />Should be exploited and not feared<br />
    21. Change shouldn’t mean fire fighting<br />
    22. DevOps To The Rescue!<br />
    23. What is DevOps?<br />“DevOps is an approach to bridge the gap between agile software development and operations” – agileweboperations.com<br />Collaborative Mindset of Devs and Ops<br />It’s what Agile is to software development<br />C.A.M.S.<br />
    24. Culture<br />
    25. Culture<br />Relationships<br />Engage early, engage often<br />Bust Silos TM<br />Be open<br />Stop finger pointing<br />Eradicate “last-mile syndrome”<br />
    26. Culture<br />Communication<br />Talk is cheap (get out of your chair)<br />Involve each other in core processes and decisions<br />Ask Questions<br />Don’t say “no”<br />Invite everyone to stand-ups and retrospectives<br />
    27. Automation<br />
    28. Automation<br />Machines are really good at doing the same task over and over<br />Consistent and Known State<br />Fast and Efficient<br />5 mins/day = 2.6 days/year<br />
    29. Automation<br />What can be automated?<br />Builds<br />Deployments<br />Testings<br />Monitoring<br />Self-healing<br />System rollouts<br />System configuration<br />
    30. Metrics<br />
    31. Metrics<br />Capture, learn, improve.  <br />Assists in:<br />Capacity Planning<br />Trend Analysis<br />Fault Finding<br />Simple as saving Tomcat access info<br />Plotted on a graph over time<br />
    32. Metrics<br />
    33. Sharing<br />
    34. Sharing<br />Share Ideas<br />Share Metrics<br />Ops: Give devs shell access<br />Devs: See what technology can be leveraged<br />
    35. DevOps Lifecycle<br />
    36. Before<br /><ul><li>Talk about functional requirements
    37. Talk about non-functional requirements
    38. Security
    39. Backups
    40. Availability
    41. Upgradeability
    42. Configuration Mgmt
    43. Monitoring
    44. Logging
    45. Metrics</li></li></ul><li>During<br />Communication<br />Source Control<br />Automate Builds<br />Automate Tests<br />Automate Deployments (Dev, Test and Prod)<br />Collate App and System Metrics<br />
    46. After<br />Release<br />Retrospective Meetings<br />Continue to Run Tests<br />Monitor Applications and Systems<br />Issues (Yes, they do happen)<br />Post Mortem Meetings<br />
    47. What are we doing?<br />
    48. Puppet<br />
    49. Automated System Admin 101<br />
    50. Automated System Admin 101<br />Puppet Lives Here<br />
    51. Configuration Management Tool<br />Open Source (FTW!)<br />Infrastructure Is Code<br />Confidence of System State<br />Lather, Rinse, Repeat...<br />Puppet<br />
    52. nodedefault {<br />includesudo<br />includentp<br />includessh<br />}<br />nodeproject-dev01inheritsdefault {<br />include jdk6<br />include tomcat55<br />include fonts<br />}<br />nodeproject-test01inheritsdefault {<br />include jdk6<br />include tomcat6<br />include fonts<br />}<br />
    53. classsudo {<br />package { ["sudo"]:<br />ensure => latest,<br /> }<br />file { "/etc/sudoers":<br />owner => root,<br />group => root,<br />mode => 440,<br />source => "puppet:///files/sudo/sudoers",<br />require => Package["sudo"];<br /> }<br />}<br />
    54. Autobahn<br />
    55. Autobahn<br />Continuous Deployment Tool<br />Developed In-House<br />Automates Deployment Process<br />Grabs Builds from Hudson<br />Deploys to App Server<br />
    56. Autobahn<br />
    57. Summary<br /><ul><li>Bust Silos TM
    58. Culture
    59. Automation
    60. Metrics
    61. Sharing
    62. Ask yourself “Is my work creating business value?”</li></li></ul><li>More Info?<br /><ul><li>Podcasts
    63. DevOps Cafe
    64. Agile Executive
    65. Presentations
    66. Velocity
    67. DevOps Days
    68. Other
    69. Twitter: #devops
    70. Google Groups: agile-system-administration, devops</li></li></ul><li>Question Time<br />

    ×