DevOps Days MSP 2017

Transcript

1. Sys Admins, DevOps, SRE! Oh My!
2. ✨ @to_emoji
3. Hello, I’m @bryanl
4. FinTech Startup
6. 0 55 110 165 220 Age in Years
7. This is a journey not a destination
8. So, there’s DevOps…
9. … and then there is DevOps in the enterprise
10. Ok, Bryan… I’m intrigued
11. 1. DevOps team
12. 2. DevOps as a means to tackle a regulatory hurdle
13. 3. DevOps as a way to remain Agile
14. Why does it have to be this way?
15. PEOPLE (you don’t believe me? think of any thing in your life that’s hard. dig a little and find out that PEOPLE are the problem)
16. Corporate Communication 101
17. Small Team
18. Larger Team
19. Multiple Teams
20. Multiple lines of business with multiple teams
21. “My problems are the most important kinds of problems”
22. Developers only cause pain
23. I digress
24. It isn’t all bad
25. How do you know you are headed down the wrong path?
26. How do you know you are headed down the wrong path?
27. How do you know you are headed down the hard path?
28. 1. DevOps teams The HARD path
29. 2. Optimization of process over people The HARD path
30. 3. Developers not participating in the DevOps process The HARD path
32. 4. You have a DevSecOps group The HARD path
33. So the enterprise sounds like a horrible place…
34. … but it isn’t
35. Why does Bryan work for an enterprise? •People •Diversity •Challenge
36. DevOps path for the neophyte
37. Sys Admin
38. Run Service X
39. Run Service Y
40. Scales by growth
41. Dev Ops
42. Provide Tools As a Service (TaaS)
43. In support of the Agile process
44. Site Reliability Engineer (SRE)
45. Engineer first
46. “How do I do more with less?”
47. SRE is DevOps DevOps is SRE
48. What should you know?
49. Linux
50. More specifically…
51. bash
52. but remember, “scripting isn’t automation”
53. How networking works
54. How system services work
55. Tools of the space
56. Empathy
57. What would you say you do here?
58. Continuous Integration
59. Generate an artifact
60. Continuous Deployment
61. Monitoring
62. We are beyond Nagios
63. Long term trends
64. Time based comparisons
65. Alerts
66. Visibility
67. Logging
68. How can you be more effective?
69. Promote collaboration
70. Embrace your tooling and fill the gaps
71. It’s all about scale
72. Embrace simplicity
73. Documentation is Paramount
74. Documentation is Paramount • Who • What • When • Where • Why • How
75. You should be involved in every phase of a system’s design and development
76. Your focus is automation over more hands on keyboards
77. You scale solutions with engineering instead more people
78. Required reading
83. 1. One less step
84. 2. You are the 10x
85. 3. You work with computers. Learn a programming language
86. AppOps A practical implementation of the DevOps practice
88. AppOps distilled • Continuous Integration • Continuous Deployment • Logging • Metrics • Error Handling
89. AppOps distilled (2017 edition) • Continuous Integration • Continuous Deployment • Logging • Metrics • Tracing • Error Handling
90. At a certain point, you aren’t a beginner any more
91. Remember One less step?
92. Make it one less step for others
93. Your application teams own business logic you own…
94. @peterbourgon
95. The power of words, technology, and empathy
96. –Bryan Liles We are the keepers We keep it up We keep on the pager We keep it going
97. We are people and people ain’t perfect
98. We acknowledge this fact by building tools
99. The problem with tools is we become our tools
100. • Gophers • Pythonistas • Rubyists • Perl Rabble Rousers
101. Don’t fall for the team trap
102. Teams imply competition
103. It isn’t us versus them
104. It’s all of us for the betterment of all of us
105. It’ll hurt, but progress is possible
106. We invoke empathy to solve problems for our users