TL;DR: infrastructure operations is hard and we need to do a lot more to make these systems widely accessible, easy to sustain and lower risk. We’re discussing these topics on twitter…please join in. Themes include “do we really have consensus and will to act” and “already a solved problem” and “this hurts OpenStack in the end.”
I am always looking for ways to explain (and solve!) the challenges that we face in IT operations and open infrastructure. I’ve been writing a lot about my concern that data center automation is not keeping pace and causing technical debt. That concern led to my recent SRE blogging for RackN.
It’s essential to solve these problems in an open way so that we can work together as a community of operators.
It feels like developers are quick to rally around open platforms and tools while operators tend to be tightly coupled to vendor solutions because operational work is tightly coupled to infrastructure. From that perspective, I’m been very involved in OpenStack and Kubernetes open source infrastructure platforms because I believe the create communities where we can work together.
This week, I posted connected items on VMblog and RackN that layout a position where we bring together these communities.
- How is OpenStack so dead AND yet so very alive to SREs?
- OpenStack’s Big Pivot: our suggestion to drop everything and focus on being a Kubernetes VM management workload
Of course, I do have a vested interest here. Our open underlay automation platform, Digital Rebar, was designed to address a missing layer of physical and hybrid automation under both of these projects. We want to help accelerate these technologies by helping deliver shared best practices via software. The stack is additive – let’s build it together.
I’m very interested in hearing from you about these ideas here or in the context of the individual posts. Thanks!
Pingback: KubeWeekly #89 – KubeWeekly