About to go onstage in the Gold Room at the Palace Hotel to tell the world how Stackdriver and GCP make implementing SRE practices easier so you can have high reliability! #GoogleNext18
Woo, we did it! And I made it to my next session on time afterwards too!
Summary: we discussed four key areas: (1) why operability matters and how DevOps+SRE improve reliability, (2) why/how to set up SLOs & an error budget focused on measuring your customers' needs, (3) reducing TTD/R w/ tooling, and (4) transparent SLIs for debugging #GoogleNext18
Key tech: Stackdriver SLO for instrumenting, measuring, and alerting on error budgets. Stackdriver Monitoring features including Metrics Explorer by locality tags, metadata joins, and Query Notation for advanced joins. Exemplars for traces and metrics in one view. #GoogleNext18
All of these inspired by the best practices of 15+ years of SRE at Google. We want to make it easier for everyone to scale their systems without overloading their ops teams. #GoogleNext18
and we want to improve collaboration with our customers by reducing silos not just within companies but between customers and their cloud providers. Thus, transparent SLIs from us to you, and, soon, transparent SLIs from you to us if you want a single pane of glass. #GoogleNext18
Here are the slides for the talk on implementing SRE with help from Stackdriver tooling!
I'll link the YouTube video as soon as it's available as well. [btw this thread is one of the few times on Twitter that I *do* speak for my employer] drive.google.com/file/d/1iOMaYI…#GoogleNext18
As much as SRE is about doing more with tooling, it's also about culture change! Remember to check out cloud.withgoogle.com/next18/sf/sess… tomorrow about the cultural changes needed to make SRE work! #GoogleNext18
Session video is up for how to improve reliability by implementing SRE measurement and debugging techniques with Stackdriver!
Kudos to the video team for producing it on such a short turnaround! #GoogleNEXT18
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Final talk I'll be getting to at #VelocityConf before I dash to Toronto: @IanColdwater on improving container security on k8s.
@IanColdwater She focuses on hardening her employer's cloud container infrastructure, including doing work on k8s.
She also was an ethical hacker before she went into DevOps and DevSecOps. #VelocityConf
She travels around doing competitive hacking with CTFs. It's important to think like an attacker rather than assuming good intents and nice user personas that use our features in the way the devs intended things to be used. #VelocityConf
My colleague @sethvargo on microservice security at #VelocityConf: traditionally we've thought of traditional security as all-or-nothing -- that you put the biggest possible padlock on your perimeter, and you have a secure zone and untrusted zone.
@sethvargo We know that monoliths don't actually work, so we're moving towards microservices. But how does this change your security model?
You might have a loadbalancer that has software-defined rules. And you have a variety of compartmentalized networks. #VelocityConf
You might also be communicating with managed services such as Cloud SQL that are outside of your security perimeter.
You no longer have one resource, firewall, loadbalancer, and security team. You have many. Including "Chris." #VelocityConf
The problems we're solving: (1) why are monoliths harder to migrate? (2) Should you? (3) How do I start? (4) Best practices #VelocityConf
.@krisnova is a Gaypher (gay gopher), is a k8s maintainer, and is involved in two k8s SIGs (cluster lifecycle & aws, but she likes all the clouds. depending upon the day). And she did SRE before becoming a Dev Advocate! #VelocityConf
"just collect data and figure out later how you'll use it" doesn't work any more. #VelocityConf
We used to be optimistic before we ruined everything.
Mozilla also used to not collect data, and only had data on number of downloads, but its market share went down because they weren't measuring user satisfaction and actual usage. #VelocityConf