Video recording and production done by DevOpsDays.
In the course of their day-to-day work, our development team actively relies on our metrics platform to confidently ship code to production and debug problems. They measure and correlate behavior between services on live production workloads, use real-time data to reason and hypothesize about production problems, and add or modify metrics and instrumentation in production to prove out their assumptions. Our own success in utilizing the metrics stream from production to close our engineering feedback loop, has convinced us that this, practice, which we describe as Metrics Driven Development (MDD), is a requirement of building web-scale systems. It is a discipline that should be implemented by development teams alongside other development paradigms like Test-driven-development (TDD) and Behavior-Driven-Development (BDD).
Our talk will recount an episode where we employed MDD to diagnose an actual problem encountered in our production system running at scale. The audience will follow as the developer initially identified an anomaly in a production KPI metric, developed a hypothesis as to the cause of the anomaly, added instrumentation to the code in question and finally confirmed the original hypothesis through observation of real-time metrics. Along the way we’ll include references to specific tools and best practices that developers can adopt in their own MDD efforts. We’ll also demonstrate that MDD does not replace traditional debugging approaches like request logging or code profiling, but can often help narrow the focus of those efforts, which can be expensive or difficult to perform in web-scale systems.
This talk is a synthesis of cultural transformation, concrete engineering techniques, systems monitoring, scientific observation, and post-mortem. It will prove intellectually gratifying and valuable to anyone who is writing and shipping code to production systems, even if they are already following an MDD model. They’ll learn what requirements a metrics platform needs to support MDD, how to add lightweight instrumentation to code, and how to isolate problems by using metrics derived from that instrumentation. The audience will also see how MDD can be used in addition to traditional production debugging practices, and will come away with an understanding of how to ship better software through the use of MDD.
NOTE: Due to a recording issue, the first few minutes of Nikolas's talk got cut off :(
The increasing popularity of Devops the past few years signifies an organic transition in the IT industry. A remarkably similar transition has been slowly ongoing in multiple industries and fields, from academia to finance and even policy. We have begun to realize the paramount importance of effective interdisciplinary collaboration as the only solution for the immense complexity of the next generation of challenges. This requires a highly systemic approach that transcends the traditional organizational barriers. Progressive, innovative, and brilliant products require desiloisation, which creates conflict. The word conflict may include cultural or lingual connotations of violence and destruction, however once we harness its energy and steer it in a productive manner then we can maximize our collective efficiency. Devops is all about harnessing the power of conflict. This talk will focus on the significance of effective conflict resolution for Devops based on basic concepts of social psychology and systems thinking. It will begin by addressing the role of each individual member and transition into intra and inter group dynamics by introducing the audience to notions of cooperation and competition, the value of intellectual opposition, trust, and positive interdependence.
The last decade belonged to virtual machines, the next one belongs to containers.
Virtualization lead to an explosion in the number of machines in our infrastructure and we were all caught off guard. It turns out that those shell scripts did not scale after all. Lucky for us configuration management swooped in to save the day.
But a new challenge is on the horizon. We are moving away from node based infrastructures where hostnames are chosen with care. Gone are the days of pinning one service to a specific host and wearing a pager in case that host goes down. Containers enable a service to run on any host at any time. Our current set of tools are starting to show cracks because they were not designed for this level of application portability. It’s time to get ahead of the curve and take a look at new ways to deploy and manage applications at scale.
Introducing CoreOS...CoreOS is a new Linux distribution designed specifically for application containers and running them at scale. This talk will examine all the major components of CoreOS including etcd, fleet, docker, and systemd; and how these components work together to solve the problems of today and tomorrow.
Jennifer kicks off Day 2 of DevOpsDays Boston talking about how the attendees can support their women coworkers.
Leave the first comment:
Graphite and Statsd are indispensable components of the modern DevOps stack. Companies such as Etsy have demonstrated that instrumenting your business and being a data driven organization can improve the lives of your teams and be useful to help improve your products and your customers' experience.
Unfortunately running Graphite at scale is non-trivial. Acquia has matured over the years in its internal usage of Graphite and has learned many lessons along the way.
Come learn how we have scaled Graphite using Cassandra to store millions of data points all the while giving back to open source.