Designing for DevOps

Building an operations team that is designed to maximize happiness is a rare opportunity; usually the features of DevOps are added piece by piece into an organization, it can be a slow and ad hoc process. New Relic is fortunate to be building our operations team from the ground up with DevOps in mind.

This opportunity allows us to select and grow with intention and purpose. We’ll be sharing everything about our experience, from what we look for during hiring through the processes we put in place. We’ll discuss the tools we use, the culture we are building and the pitfalls we didn’t see coming.

Every team is unique, so we cannot give you a roadmap to success but we’re happy to share our mistakes and successes as we build an operations team that makes happiness a priority.

Transcript

1. Designing for DevOps
5. Vehicles for land or air that carry the dedication to efficiency, getting along on little power, that is the hallmark of soaring!
6. @amateurhuman
8. THIS IS OUR STORY.
9. Collector Beacon RPM Pinger WWW END-USER OUR CUSTOMER NEW RELIC
10. 60 Billion metrics / Day 623 THOUSAND APPS
11. 2,081,321,280 HTTP REQUESTS
12. 2 OpS*
13. Growing Pains
14. DO NOT WANT.
15. racking boxes is not A FEATURE.
16. Putting out Fires? Not A Feature.
17. AVAILABILITY SCALABILITY
18. AVAILABILITY SCALABILITY
19. ENGINEER NOT ADMINISTER
20. HACKERS over rackers.
21. Generalists
22. Tool Builders
23. DEVELOPERS Developers developers
24. BE DELIBERATE.
25. MATURITY
26. MATURITY UNDERSTANDABILITY
27. MATURITY UNDERSTANDABILITY INTEGRATEABLE
28. MATURITY UNDERSTANDABILITY INTEGRATEABLE EASILY ABSTRACTED
29. OPS SHOULD BE INTERESTING NOT EXCITING.
30. Continuous Deployment
31. Continuous Deployment Feature flags
32. Continuous Deployment Feature flags RESILIENCE
33. OUR TOOLS TELL US SOMETHING ABOUT OUR Culture.
35. Optimize for discovery
37. Yes, WE’RE HIRING newrelic.com/Jobs Yes, You should try it newrelic.com/puppetconf Chris Kelly / @amateurhuman