Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Beyond DevOps - How Netflix Bridges the Gap

Operating a massively scalable, constantly changing, distributed global service is a daunting task. We innovate at breakneck speed to attract new customers and stay ahead of the competition. Simultaneously improving service quality and enabling rapid, continuous change seems impossible on the surface.

At Netflix, Operations Engineering is a centralized organization whose charter is to accomplish just that by applying high-leverage software engineering practices like continuous delivery. real-time analytics, and automation to solve operational problems. It's well established that many traditional IT Operations teams struggle to bridge the gap with software engineering. Operations Engineering is no exception. And while DevOps as a construct seeks to address this gap, it doesn't go far enough. It does not explain how to bridge the gap or even why it's important to do so.

In this talk we’ll use Netflix Operations Engineering as a case study to address these questions. We'll explore common challenges faced by operational teams and strategies to overcome them.

Java 6 – needed to move forward on Java but struggled to drive adoption Perforce – many teams moving to Git – no story for supporting perforce in the cloud Jenkins – long queues & build times Ant – long build times, inefficient dependency management CentOS – slow delivery of new kernel and userland binaries Asgard served us well as a deployment & cloud management Mimir gave a great prototype and we learned a lot

Tech debt kept us from doing our jobs well

Does this sound familiar? Have any of you been on one side or the other of this situation?

To move forward we defined the concept of the paved road The paved road promises a well supported integrated developer experience. Java 7 – just to move forward – Java 8 already on the horizon Git – organically adopted by many teams Gradle – built time reduced due to efficient dependency management Ubuntu – more frequent, well vetted userland binarie & kernels Jenkins shards to fix long build times Started building our next generation cloud console & continuous delivery platform Spinnaker

We staffed up and went for it – big bang

Read to the audience:

He that can earn ten shillings a day by his labour, and goes abroad, or sits idle one half of that day, tho' he spends but sixpence during his diversion or idleness, ought not to reckon that the only expense; he has really spent or rather thrown away five shillings besides.

- Advice to a Young Tradesman

Please raise you hand if you know which puritanical workaholic wrote this? In addition to the obvious intent behind this there is a more profound message. Time spent working is related to the money you make but time is also in and of itself a form of currency. It’s the exchange or giving of time that drives the economics of an engineering organization

Netflix has a freedom & responsibility culture. You build it you run it perfectly aligns with our values around autonomy & ownership

This leads a high pressure situation created a shortage of time.

Read definition out loud Out of curiosity – who agrees with this definition? Who disagrees? Not only is there disagreement but the general construct isn’t really that helpful

It doesn’t address how to bridge the gap or why it matters to do so? What’s are the strategies for success?

It’s the practices, tools, culture Motivations the reason for doing DevOps is to achieve operational excellence

We do the undifferentiated heavy lifting for out customers. This means we take on the operationally oriented common engineering work across teams so that each team can focus on their core charter.

We do the undifferentiated heavy lifting for out customers. This means we take on the operationally oriented common engineering work across teams so that each team can focus on their core charter.

Going back to our Ben Franklin quote – time is a form of currency. In our engineering world time really is currency. We don’t pay each other to do work. We commit time to projects. In other words we have a time-based economy.

Audience – can anyone name one of the strategies?

Stop spamming us!

Audience – can anyone name one of the strategies?

A free chaos monkey for good ones

\

There are several approaches that you might take to solve for this problem. I’ll explore each one.

And once you’ve proven that you can deliver you have some money in the bank. You have earned a seat at the table. Now you’re ready to build strong partnerships.

• What are your biggest
operational pain points? • How can we help? • How well are we meeting your needs today? • What would you like to see from us in the future? Listen Shower, rinse, repeat Talk to your engineering customers