1. DevOps @matthew_jones mjones@itree.com.au

2. Dev or Ops? 6 Days after a successful deployment, the server experiences high load.

3. Dev or Ops? There is an issue with the build server. Code isn’t building.

4. Dev or Ops? Software is deployed to the test environment. You can’t login to the application.

5. Dev vs. Ops

6. “It works on my machine...”

7. “It’s not the server, it’s your code.”

8. What is the role of Dev and Ops?

9. What are the roles of Devs and Ops? Dev Create change Add or modify features Ops Create stability Create or enhance services

10. What are the roles of Devs and Ops? Dev Create change Add or modify features Ops Create stability Create or enhance services

11. We Have A Problem...

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

18. We are all here to ENABLE business

19. So What’s All This Change?

20. Change Is required for business Doesn’t mean outages Should be exploited and not feared

21. Change shouldn’t mean fire fighting

22. DevOps To The Rescue!

23. What is DevOps? “DevOps is an approach to bridge the gap between agile software development and operations” – agileweboperations.com Collaborative Mindset of Devs and Ops It’s what Agile is to software development C.A.M.S.

24. Culture

25. Culture Relationships Engage early, engage often Bust Silos TM Be open Stop finger pointing Eradicate “last-mile syndrome”

26. Culture Communication Talk is cheap (get out of your chair) Involve each other in core processes and decisions Ask Questions Don’t say “no” Invite everyone to stand-ups and retrospectives

27. Automation

28. Automation Machines are really good at doing the same task over and over Consistent and Known State Fast and Efficient 5 mins/day = 2.6 days/year

29. Automation What can be automated? Builds Deployments Testings Monitoring Self-healing System rollouts System configuration

30. Metrics

31. Metrics Capture, learn, improve. Assists in: Capacity Planning Trend Analysis Fault Finding Simple as saving Tomcat access info Plotted on a graph over time

32. Metrics

33. Sharing

34. Sharing Share Ideas Share Metrics Ops: Give devs shell access Devs: See what technology can be leveraged

35. DevOps Lifecycle

37. Talk about non-functional requirements

38. Security

39. Backups

40. Availability

41. Upgradeability

42. Configuration Mgmt

43. Monitoring

44. Logging

46. After Release Retrospective Meetings Continue to Run Tests Monitor Applications and Systems Issues (Yes, they do happen) Post Mortem Meetings

47. What are we doing?

48. Puppet

49. Automated System Admin 101

50. Automated System Admin 101 Puppet Lives Here

51. Configuration Management Tool Open Source (FTW!) Infrastructure Is Code Confidence of System State Lather, Rinse, Repeat... Puppet

52. nodedefault { includesudo includentp includessh } nodeproject-dev01inheritsdefault { include jdk6 include tomcat55 include fonts } nodeproject-test01inheritsdefault { include jdk6 include tomcat6 include fonts }

53. classsudo { package { ["sudo"]: ensure => latest, } file { "/etc/sudoers": owner => root, group => root, mode => 440, source => "puppet:///files/sudo/sudoers", require => Package["sudo"]; } }

54. Autobahn

55. Autobahn Continuous Deployment Tool Developed In-House Automates Deployment Process Grabs Builds from Hudson Deploys to App Server

56. Autobahn

58. Culture

59. Automation

60. Metrics

61. Sharing

63. DevOps Cafe

64. Agile Executive

65. Presentations

66. Velocity

67. DevOps Days

68. Other

69. Twitter: #devops