This episode explores the intersection of infrastructure automation and security through the lens of the Crowd Strike outage. We’ll discuss the tension between maintaining stable, reliable data center infrastructure and the need to embrace change and innovation.
Recent events like the CrowdStrike outage demonstrate the paradox that infrastructure teams face. We’ll dive into the importance of having multiple control planes and standardized processes that can adapt to rapid industry changes.
We start talking about walled gardens and the momentum and push that causes us to get into vendor active environments in this episode. This is going to be a multi-part discussion where we look at the drivers of AI in the future.
In this case, we used up a lot of time before this recording talking about Kubernetes and what’s next for Kubernetes and containers, as well as how that ecosystem has been shaping up. This conversation is about the wall gardens that could be broken down, and in some cases, have actually been built taller because of containerization and Kubernetes and infrastructure and how infrastructure works.
After that background before going into the discussion, we pick it up on how these ecosystems and walled gardens are self reinforcing as well as chinks in the armor that will allow us to go back to interoperable standards.
Martez Reed and I have an in depth conversation about the challenges of propagating technology inside of enterprises, this core challenge of selling silos and individual technologies. What Martez describes as beneficial tool sprawl versus building up systems and integrating things and end to end technology. This is what I’ve been calling infrastructure pipelining. We break down what’s going on in the street related to Open Source technology, Kubernetes, other aspects of what’s happening and how things fit together in an interesting and dynamic way.
TechOps series episode 3 covers how to automate against API’s. We discuss exactly the ways in which you can use API’s effectively, and ways you can run into trouble. We also discuss how we should be consuming API’s, both as a consumer but also in times when we have produced API’s. Many ideas discussed were pulled from learning how people consume our API’s and what we can do to help make them better and safer.
Enjoy this broader TechOps series where we are diving in deep in tips and techniques that improve your journey as an Automator.
We dive into data operations in today’s episode! We cover the idea that with all of the work we’re doing in AI and ML data analytics analysis, you actually have to steward your data.
We also cover processes controls, like what we have with DevOps in infrastructure, but with similar types of concepts (governance controls automation) around how your data is flowing in your system.
We dive into the chaos created by Broadcom’s acquisition of VMware. In this episode, we discuss what Broadcom is doing, why it’s a problem, how enterprises are reacting, and what alternatives are on the market.
We cover the whole mess in all its glory, and even provide some love for Broadcom.
After a brief hiatus, thecloud2030 group is back and deep in tech, talking about things that we think are going to come on the tech front, sans AI.
In this episode, we take some time to go through Kubernetes, hardware, software, bill of materials, and some governance. This includes a smattering of predictions to get your year started off with a bang.
From there, we are going to be moving into our tech-ops series. Find more details about that in today’s outro!
What is innovation? Today we continue this discussion, specifically drilling into the three horizons model for creating growth and value.
We spend a lot of time talking about how companies innovate using that model, what it means and what are examples of it? How does that spark take place? We bridge you further down the innovation learning process in this meeting.
Transcript: otter.ai/u/He9h2NVxazKMDN9a13…?utm_source=copy_url Image by Dall-E prompt “please create a close up picture of a flock of birds navigating between three different horizons. the birds are smart and know which why they need to go”
We dive deep into the technical subject of governance and policy enforcement, including the tools, techniques and processes that you need to be aware of to do a good job with policy and governance enforcement.
We cover how to get started, what to think about, what to be aware of, and chip away at your governance and policy challenges including developer development portals, infrastructure pipelines and DevSecOps.
Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, discusses the October 19th conversation about limiting large language models (LLMs) and AI. The discussion focused on creating legal limitations for artificial intelligence and technology, highlighting the potential impact of regulations such as Section 230, which governs internet service providers’ moderation of content. Hirschfeld suggests that changes to Section 230 could be a critical component in controlling emerging technologies, inviting listeners to explore the insightful conversation at the2030.cloud.
We dive into the dynamics of open source projects and monetization today, specifically starting around the TerraForm and open tofu split. That topic is one that we love to chew over and potentially over analyze, but today’s discussion is different.
We go into how ecosystems are built both in open and proprietary and cloud systems, and look at sort of a historical perspective on what makes a project successful from an ecosystem perspective. We also dive into why some projects work like that, and why some projects don’t.
Today’s episode gives a new take on some of the dynamics going on in the open source communities through the lens of what happened with Open Tofu and TerraForm.
