Pushing O11y Uphill: The Single PAIN of Glass
Tracing Adventures From PR to Production
There's No Place Like Production - Shift Conf
Intro to Threat Modeling in the Cloud - Open Source Summit NA
Avoiding Alert Fatigue and Burnout - WTFisSRE
Cognitive Apprenticeship in Action with Alert Triage Hour of Power - SRECon23 Americas
Taming Feral DevOps - DevOpsDaysLA
DevOpsDaysLA talk about the aftermath of burnout and getting your DevOps transformation back on track.
30 Interviews Later...
Lightning talk reflecting on the his and lows of a summer of 30 SRE interviews
Best Vends: The How and Why to Befriend Your Vendors
If you are on the “buy” side of build versus buy this talk is for you! By buying a vendor’s product you are inviting them to be a part of your team and your platform - why not make the most out of your investment? From participating in betas to simply reading vendor emails I will give you a dazzling array of activities you can do today to start on the path of becoming best vends.
Microservices Means Macrocommunication
The tl;dr is “how microservices can better facilitate communication between team members and from team to team”.
Adopting microservices means a shift in architecture of our system and in communication. Letting your upstream and downstream dependencies know of major changes is not just a courtesy but required in order to keep things moving.
Communicating early and often takes shape in strategies like:
- informative deprecation warnings
- temporarily providing backwards compatibility
I’ll take the approach of “do this not that” and look at realistic examples such as:
- during active development a team picks up your work and suddenly becomes a dependency - how do you gracefully communicate constant changes?
- Or its endpoint deprecation day and you still have active consumers - how to provide the tools they need to migrate to the new stuff.
- Or the nuts and bolts of why and how keeping documentation up to date will add to your daily productivity.
Disposable Infrastructure: You Only Build Me Up To Tear Me Down
I’ll start with my definition of disposable infrastructure,
Automating the process of provisioning, configuring, deploying, and tearing down cloud infrastructure and services.
Essentially 1 script to go from 0 to live application and from live application back to 0 again.
Then talk through and show the code for each major step the program is running through:
- Reading in the configuration file describing the desired infrastructure and set up (1 service per instance)
- Generating a plan and invoking Terraform to provision EC2 instances, security groups, load balancers, and a database
- Generating a playbook and running Ansible to configure each instance according to what service is running on it
- Packaging the deployed environment