11 flippin' great talks on DevOps for $100.

April 3, 2013

Gene Kim i

Why We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations

Gene Kim will present his findings from an ongoing study of how high-performing IT organizations simultaneously deliver stellar service levels and deliver fast flow of new features into the production environment. To successfully deliver against what on the surface appear to be conflicting objectives, (i.e. preserving service levels while introducing significant amounts of change into production), requires creating a highly-coordinated collection of teams where Development, QA, IT Operations, as well as Product Management and Information Security genuinely work together to solve business objectives.

Gene will describe what successful transformations look like, and how those transformations were achieved from a software development and service operations perspective. He will draw upon fourteen years of research of high-performing IT organizations, as well as work he's done since 2008 to help some of the largest Internet companies increase feature flow and production stability through applications of DevOps principles.

James Turnbull i

Hell Has Frozen Over: DevOps & Security

A lot of Dev and Ops people look at their security teams with disdain: "Those guys are arseholes. All they ever do is sit in meetings and tell us no." They know there's no way Security will ever embrace DevOps. In turn many security folks see the emergence of DevOps as the inmates being put in charge of the asylum. It'll all end in chaos and disaster.

So who's right? Can DevOps and security co-exist? Can they be friends? We will take a deeper look at:

  • What DevOps means for Security
  • How DevOps can be sold to Security
  • How DevOps changes the risk landscape for the better
  • How those Security folks might know some things that could make DevOps better

You'll see how DevOps and Security can have a long and prosperous friendship that makes more awesome.

Will Farrington i

Boxen: How to Manage an Army of Laptops and Live to Talk About It

At GitHub, we've been growing pretty quickly and that sort of growth presents a lot of challenges. We were feeling the pain of trying to teach everyone (developers and designers alike) how to get GitHub and all our other projects running on their laptops. The process was failure-prone, complex, and time-consuming. So, last summer, we created the first iteration of The Setup — GitHub's method of managing laptops without getting all authoritarian about it. We quickly realized that other organizations needed and wanted this environment, so we started back with the basics and re-architected The Setup into Boxen. The same tool, the same method, but written for modularity and general consumption.

We’ve since released Boxen (as of January 2013) and other organizations are using it to great success. This talk explores our design choices with Boxen, how we use Boxen internally, our recommended design patterns for managing Boxen-driven automation, and some new goodies coming down the pipeline for Boxen.

Taylor Weibley i

Zero Down Time Operations: How to Get Atleast 3 9's of Uptime

No one wins an award for having the most popular status site. I'll show you the top practical techniques we (37signals) use for keeping our sites available at all times, even during scheduled maintenance! From hardware choices, to network topology, to high availability services, it all matters. I'll introduce tools like intermission and mysql_role_swap and show you how we've used custom alerts and dashboards built on top of statsd + nagios to intercept problems before they impact users.

Joshua Timberman i

You Should Be On Call, too

One of the reasons for the DevOps movement is that all developers should carry pagers and be on call, right?

Well, not quite. However, there is a common area of conflict between operations and development teams about site outages related to application-related issues that developers know how to debug and fix much faster than operations typically does.

In this talk, I'll discuss some companies that have successfully implemented developers on call" policies and what that means. I'll also discuss the business value, why it matters, and how it helps create a collaborative culture of sharing.

Jesse Newland i

ChatOps at GitHub

Ops at GitHub has a unique challenge - keeping up with the rabid pace of features and products that the GitHub team develops. In this talk, we'll focus on tools and techniques we use to rapidly and confidently ship infrastructure changes using Campfire and Hubot as our primary interface, and the benefits we've seen from this approach.

Lindsay Holmwood i

Escalating complexity: DevOps learnings from Air France 447

On June 1, 2009 Air France 447 crashed into the Atlantic ocean killing all 228 passengers and crew. The 15 minutes leading up to the impact were a terrifying demonstration of the how thick the fog of war is in complex systems.

Mainstream reports of the incident put the blame on the pilots - a common motif in incident reports that conveniently ignore a simple fact: people were just actors within a complex system, doing their best based on the information at hand.

While the systems you build and operate likely don't control the fate of people's lives, they share many of the same complexity characteristics. Dev and Ops can learn an abundance from how the feedback loops between these aviation systems are designed and how these systems are operated.

In this talk Lindsay will cover what happened on the flight, why the mainstream explanation doesn't add up, how design assumptions can impact people's ability to respond to rapidly developing situations, and how to improve your operational effectiveness when dealing with rapidly developing failure scenarios.

Drew Blas i

Migrating a live site across the country without downtime

Chargify.com's customers rely on us to process payments for them 24 hours a day. We do not have any planned maintenance windows: we're simply expected to be up all the time. We recently migrated from a private datacenter to EC2, moving all our operations and data across the country with zero downtime. All thanks to a combination of highly-automated configuration with Chef and specialized DB tools like Tungsten.

You'll learn about our pain points in planning the switchover, like:

  • Synchronizing data
  • Cross DC communication & VPNs
  • Redirecting traffic
  • Redundancy
  • Migrating Redis/Resque
  • Automation

And most importantly, how we addressed every one! I'll demonstrate how we rebuilt our entire infrastructure platform from the ground up: New system images with all new cookbooks that were deployed into our existing operation without any interruption. Finally, I'll discuss testing our stack and how we replicate it among various environments and plan for future expansion.

Jason Roelofs i

Keep Ops Happy, Designing for Production

Building applications in Ruby is fast and fun. Features fly, progress is quick and everyone's happy, until you have to deploy. While services like Heroku make deployment easier than it ever has been before, there's only so much they can do for you, and no-one is happy when customers can't use your application!

This talk will go over steps developers can take to protect against common production errors as well as more advanced techniques to keep your application running smoothly over the long term.

Seth Vargo i

TDDing tmux

You want to test your cookbooks? Cool. Where do you start? In this talk, I'll walk you through step-by-step the process for executing test-driven development on a cookbook. From real-time feedback with guard and terminal-notifier, to chefspec, fauxhai, and foodcritic, quickly learn how to apply both basic and advanced tests in your infrastructure.

Allen Rohner i

The Many Ways to Deploy Continuously

So...Continuous Deployment. You hear that you should be practicing continuous deployment, but nobody every pointed out that there are many different ways to do it!

This talk compares and contrasts different kinds of continuous deployment strategies. Implementation, requirements, tradeoffs will be covered. Case-studies, examining different strategies practiced at companies such as Facebook, GitHub, IMVU, Heroku and CircleCI.