Reliable License Models

We talk about software licensing in open source, and what it means to the broader market. In fact, we cover how it’s changing what the market actually is!

This is not not just open source licensing in general because at the end we didn’t care about the license. We are more concerned about utility, serviceability and operability of the products we use. We need to understand whether or not we can rely on them!

In short, the supply chain of the software was much more important than the licenses of the software

Transcript: otter.ai/u/kH-vbVxoymH9GGdNEi3jvF07c5s
Image: www.pexels.com/photo/gray-planes…om-window-127441/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the October 28th discussion about software licensing. He highlights the industry’s indifference towards software licensing as a critical battleground and questions the necessity of open source for good software, asserting that system support, maintenance, and trusted partners are more crucial. While acknowledging the importance of community goods like Kubernetes for creating abstraction layers, Hirschfeld emphasizes that the ultimate focus should be on the supply chain and invites listeners to explore the extended conversation at the2030.cloud.

Can DevOps Be More Collaborative / MSFT & Activision

We have a lot of questions about improving collaboration in organizations:
How do we deal with change in organizations
How can we get organizations to work together better?
How do we encourage collaboration around the automation spaces that we’re trying to build in DevOps.

In our discussion, a lot came back to something as simple as version control!

We also discuss how we handle coupling between systems. In order to collaborate, we have to couple systems. But if we couple them, we create complexity.

This podcast includes our warm up conversation about Microsoft acquiring Activision because that is ALSO about how you integrate to organizations and business plans! This was news of the day and I think you’ll be very interested in our take on it.

Transcript: otter.ai/u/itNrmoL9MgG980D8CZdo9XWd-xI
Image: www.pexels.com/photo/a-woman-pla…ith-kids-7176471/

Using Blockchain for Edge Computing

We started talking about blockchain and the edge, but that is not where it ended up at all! Our fascinating journey started with web3, and surprisingly, it’s potential for distributed infrastructure and distributed web.

That led us to edge: managing and trusting devices on the edge through distributed ledger (DLT). That led us to the distributed ledger landscape. The journey is important because some of these technologies will be essential for establishing trust in systems.

In this conversation, we walk through the progression of these very important topics.

See also: dltlandscape.org/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 podcast, provides a hot take on the January 20th discussion about Blockchain on the Edge. The conversation delves into trust, identity, and the need for reliable communication among systems, leading to a focus on distributed ledger technology (DLT) to address these challenges. Hirschfeld acknowledges the complexity of implementing DLT but invites listeners to explore the longer podcast for a comprehensive discussion on potential solutions and a roadmap for the future at the2030.cloud.

Exploring Edge Applications

This episode explores applications for the edge. We really try to dig in on what will work in the edge from an application perspective. We also explore what’s holding us back.

Every time we have a conversation about Edge, we help undangle the components of Edge. In this discussion, we get more concise about what type of infrastructure is needed to build real edge applications. We also define where edge applications are expected to work and where they don’t.

Transcript: otter.ai/u/7uwv5Z3aupwE5ZGBXBEUqw9zkbE
Photo: www.pexels.com/photo/red-and-bla…ot-statue-185725/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, offers insights from the December 2nd Edge Applications discussion. The conversation focuses on the challenges of building integrated edge applications composed of various components like platforms, compute, networking, and sensors. Hirschfeld highlights the need for collaborative data planes, digital twins, and an ecosystem that allows applications to utilize existing resources, emphasizing that these challenges in the edge space have yet to be fully addressed. He encourages listeners to explore the comprehensive discussion at the2030.cloud.

Is Edge HCI Necessary?

To explore HCI at the edge, we started with SUSE’s Harvester. It’s an HCI integration of Kubernetes, KubeVirt, and Longhorn (their storage system) plus some PXE booting magic they threw in there. From there we explored how Kubernetes can fit into Edge HCI.

That really morphed into Edge operations more generally. It’s not clear if hyperconverged infrastructure can or can’t fit. We covered items like AWS Outpost which is Amazon’s edge. We included items for the cloud to edge migration from an application development perspective.

There are a lot of fascinating ops and development topics throughout the conversation.

Transcript: otter.ai/u/Y2OH7SuJhPp4VRQSBAJk31-0_eI
Photo: www.pexels.com/photo/crop-person…ontainer-4498143/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, provides insights from the January 4th discussion on hyper-converged infrastructure (HCI) for the edge. The conversation explores the operational desire for clean and simple architectures with modular building blocks for easy implementation. However, it challenges the notion that platforms like Kubernetes can create a straightforward, self-building architectural solution for edge clusters, emphasizing the associated cost considerations. Hirschfeld suggests exploring the full episode at the2030.cloud for a comprehensive discussion on the complexities and potential solutions in the realm of hyper-converged infrastructure for the edge.

Resolving Software Dependency Chains

Dependency chains are complex and fragile when you’re depending on software, hardware cloud services that go away or change. In this conversation, we really examine the challenge of having dynamic vendor relationships and what we can do to fix and protect our environments.

It’s really hard to fix what can be vulnerable when it also changes your software supply chain at any moment! And that can impact any device in your infrastructure!! We work through that problem means in practical terms.

Transcript: otter.ai/u/mwpwVINGYfkQ5F5IERXgsM2oHsA
Photo: www.pexels.com/photo/focused-kid…d-puzzle-5063480/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the January 11th DevOps lunch and learn focused on managing dependencies in technology. The discussion reveals a critical realization that the interconnected and short lifecycle of technology components results in a near certainty of repercussions when patching or updating one part of the infrastructure. Hirschfeld highlights the serious security and continuity risks associated with unmaintained projects, emphasizing the need for improved visibility and management of software dependency graphs. He encourages listeners to explore the comprehensive conversation at the2030.cloud for insights into addressing these challenges.

A Pathway to Standardization

This episode was a fun and interesting ride from boring standards to locking APIs via NFTs!

We started talking about “civilization technology” where standards and regulations are applied to infrastructure. We are expecting this to happen in cloud (eventually) because it allows us to create ecosystems around the infrastructure. The historical patterns that we see in railroads, buildings and electricity will emerge in IT too.

Or maybe they won’t! We haven’t yet seen standards emerging in cloud or open source. And we had some really significant conversations around the interactions between these systems that would drive or resist standardization.

Transcript: otter.ai/u/-hhn6VEjtIQDl3UAHaCPUxCUaXo
Photo: www.pexels.com/photo/slatted-woo…en-trees-1423827/

A Pathway to Green Data Centers?

How do we make data centers green because, fundamentally, they are going to use electricity. But the sources of that electricity, how we respond to shortages of electricity and cost signals about that electricity are all critical to consider. These are the questions that lead us to how a green data center or green infrastructure gets created.

Our discussion also includes how infrastructure at the edge can play a role. Overall, there are A LOT of the factors that go into building and creating green infrastructure, including the motivations and signals that will hopefully change the market.

Transcript: otter.ai/u/9eirv3Rs292n7M1m8d1VaRPPRgA
Image: www.pexels.com/photo/clear-light…ray-rock-1108572/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, discusses the importance of green infrastructure in today’s episode. He emphasizes the need to understand the impacts of power availability on the cost and design of applications and infrastructure. Hirschfeld stresses that building for the future requires consideration of unreliable power, whether due to cost, availability, or shifting dynamics, and encourages listeners to explore the comprehensive discussion in the full podcast at the2030.cloud.

Evolution of Networking Systems

How do we evolve technology in the future?  We centered the answer on networking, but in a very general way.

The ability for a vendor to distribute technology and then connect things together and then build networks of that technology is a core component of how networking is evolving.   Ultimately, this is about building technology systems.

Sadly, that led us into a very dark place where we really thought through who’s going to own all of that infrastructure and their motivations.  How can we make sure that the people’s needs and the systems and the vendors’ needs are well aligned?

Transcript: https://otter.ai/u/H8ik1HcmSExVBRklYbSCsV4yu2k

Image: https://www.pexels.com/photo/shallow-focus-photography-of-keychains-1194036/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the November 2nd DevOps Lunch and Learn session, which explored the motivations and impacts of building highly networked systems. While acknowledging the significant societal benefits of interconnected technology, Hirschfeld emphasizes the importance of understanding and mitigating the potential risks, particularly regarding data control and accessibility. He advocates for building inclusive systems that prioritize adaptability and service to the greater good, inviting listeners to explore the comprehensive discussion on these critical topics at the2030.cloud.

What is Platform Engineering?

What is platform engineering? And why is it necessary and how to make it work compared to DevOps.

In this conversation, we really hit on the challenges of creating automation teams for building automation in scalable ways. Frustratingly, we never really came up with a particularly good answer to “what is a platform team” and why you should care. Strangely, your organization is probably building one.

Transcript otter.ai/u/zJeQbqXIyD8kZUxfKQdvQAfQGog
Image: www.pexels.com/photo/building-co…chnology-9617733/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the November 9th DevOps Lunch and Learn session focused on platform engineering. He highlights the challenge of executing platform engineering initiatives despite the straightforward concept of improving automation and tooling at an architectural level. Hirschfeld emphasizes the importance of defining success metrics, empowering teams to enforce standards, and adopting consistent, repeatable patterns and practices to advance the industry’s maturity. He encourages listeners to explore the insightful discussion at the2030.cloud for a deeper understanding of platform engineering’s significance.