Track host
About the track
In theory, having a solid SRE program is required for successful cloud IT services. In practice, not all SRE programs are created equal, and in fact many attempts to establish an SRE program have failed or even backfired. What distinguishes a good SRE program from a bad one, and is there a framework for preventing catastrophe? This isn't an idle discipline. Many of the practices mentioned in the original SRE materials are now hotly contested, like MTTR, root cause analysis, and runbook automation.
SRE deserves a critical and optimistic review. For example, are qualitative methods better suited to evaluate the success of SRE over quantitative methods? As a practice, SRE may be the software industry's best hope of holding off governmental regulations around availability, uptime, and certification of software engineers. That hope can only be fulfilled if we have effective SRE practices
The day in the host's words
Sessions in this track
Wednesday 26 October. 5 sessions per track, chosen and introduced by the Track Host.
10:35 Bayview Session SRE The Endgame of SRE Amy Tobey Senior Principal Engineer and SRE practice Leader @Equinix The containers are deployed and the builds are green. Yaml flows through the system, linted, reviewed, tested, and shipped with ease and regularity. Our intrepid SRE finds themself at a crossroads. The infrastructure is great but teams still struggle to maintain error budgets. 11:50 Bayview Session SRE Did the Chaos Test Pass? Christina Yakomin Senior Site Reliability Engineering Specialist @Vanguard_Group People used to ask me all the time how to figure out if their chaos test has “passed,” and I’d always say “well, that’s a loaded question.” To confirm that a chaos test “passed,” we need to do verification of hypotheses - sometimes you’re trying to prove some system behavior occurred in response… 13:40 Seacliff ABC Session [Panel] SRE: Is it Working? Courtney Nash, Amy Tobey, Christina Yakomin, Sasha Rosenbaum How does SRE mature from a craft with a wide range of skills and levels of expertise to a mature discipline? 14:55 Bayview Session SRE Rethinking Reliability: What You Can (and Can't) Learn From Incidents Courtney Nash Co-founder @The VOID, Previously @Verica, @Holloway, @Fastly, @O’Reilly Media, @Microsoft, & @Amazon This talk presents research collected from the VOID—an open database of public incident reports. Containing over 2,000 reports for almost 700 organizations, the database allows for more structured review and research about software-related incident reporting. 16:10 Bayview Session SRE The Eternal Sunshine of the Toil-Less Prod Sasha Rosenbaum Director of the Cloud Services Black Belt Team @RedHat One of the most important decisions in building an SRE practice is what kind of work should be assigned to the SRE team, and in what percentages.QCon San Francisco 2022 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.