Category Archives: All

Why Jenkins in DevOps?

What kind of orchestration systems does the industry use for infrastructure, automation and controlling day to day operations?

In today’s episode, we talk about infrastructure pipelines at the tooling level, and specifically the use of Jenkins and other CI pipelining tools for ops and orchestration. We dig into why and how you would do this, and what pieces are missing from the system. That conversation leads us into larger day to day challenges.

If you are doing infrastructure ops and DevOps automation, you will get a lot out of this session.

Transcript: otter.ai/u/dbTdHdYTIt5bU1G8SFghKSijhU0
Image: www.pexels.com/photo/barista-wit…d-tattoo-6205639/

Rob’s Hot Take:

In the May 19th Cloud 2030 Podcast episode, Rob Hirschfeld delves into the intersection of payment systems, PCI V4, NFTs, blockchain, virtual reality, and the metaverse. The discussion highlights the often overlooked XRP or ripple specification, enabling banks to transfer funds outside the SWIFT system, introducing alternative ways for banks to exchange fiat currency with significant impacts on credit, microtransactions, and blockchain conversions. The episode emphasizes the importance of understanding seemingly esoteric elements that can shape the future landscape and influence how it evolves. Explore the full conversation for insights into this intriguing combination of PCI, V4, Kryptos, and the Metaverse.

PCIv4, NFT, Metaverse, and CRypto! Oh My!

What is the intersection between augmented and virtual reality?

In today’s episode, we discuss changes in payment systems, Metaverse, NFTs and micro payments. All of which have to do with PCI and how we handle process payments.

We had a fascinating conversation about how all of these technologies intersect, and how one can drive another.

Transcript: otter.ai/u/Jbj52Opa37Vwmci1myBC7LsSXtY
Image: www.pexels.com/photo/selective-f…-figurine-362685/

Cloud2030PCIPaymentsMetaverseCryptoNFTAR/VRMicropaymentsRipple

Rob’s Hot Take:

In the May 17th DevOps Lunch and Learn, Rob Hirschfeld discusses the use of Jenkins and other CI/CD pipeline tools in day two operations, emphasizing the missing discussions around operational requirements, tooling, and integrations in common day two patterns. The conversation reveals the tendency in operations to avoid discussing or sharing common practices, even when widely used, due to embarrassment or perception of it being the wrong approach. The episode explores how acknowledging and addressing these patterns is crucial for building effective day two operations, offering valuable insights for those interested in DevOps, infrastructure, and automation. Join the ongoing discussions at the2030.cloud to delve deeper into these critical topics.

Content Moderation – Safe Social Media?

What type of speech can we control, allow and amplify? Today’s episode was about content moderation in social media. The issues here are nuanced, but absolutely critical for our functioning society to get right.

We discuss various interlocking issues, including what type of feedback loops we are creating and what the historical precedents for building safe systems are.

Transcript: otter.ai/u/197TTpOUZd8p2Y6RzDGltLq13i4
Image: www.pexels.com/photo/man-wearing…elephone-1587014/

Rob’s Hot Take:

In the May 12th Cloud 2030 discussion on social media and content moderation, Rob Hirschfeld highlights the need to make these systems safe for users and societies. The analogy of social media being like cars without seatbelts prompts questions about incorporating protective measures into these platforms. The discussion delves into the challenges of serving the users versus the current purposes of social media and emphasizes the importance of governance in shaping the future of these systems. Join the ongoing conversations at the2030.cloud and explore the insightful May 12th episode for a deeper understanding of content moderation in social media.

Governance As Code (pt 1 – identity)

Our discussion about governance as code today is one of a series that we’re going to be starting. In today’s episode, we started out discussing what is Governance as Code. Then we dug into identity and how important it is to know who is doing what in a governance process.

Special Guest: Kapil Thangavelu twitter.com/kapilvt

Along the way, we touch on topics such as Infrastructure as Code, trust, logging, and audit – all essential components for governance.

If this is your first time hearing about Governance as Code, you will learn a lot here. Even if you already know the topic, the back half of today’s podcast poses some fantastic conversations and questions.

Transcript: otter.ai/u/X5xXz3Gw0ot23jFsccZr_k9w-D4
Image: www.pexels.com/photo/gray-airpla…ol-panel-3402846/

Rob’s Hot Take:

In the May 9th Cloud 2030 discussion on “Governance as Code,” Rob Hirschfeld emphasizes the significance of building automation as code for creating resilient infrastructure. The conversation focuses on the challenge of tracking identity in automated systems to understand who initiated specific changes. Recognizing the importance of untangling transitions and identifying contributors becomes a foundational component of governance as code efforts. Join the insightful discussions at the2030.cloud and explore the in-depth May 9th episode of DevOps Lunch and Learn with Cloud 2030.

Green Data Centers

What’s going on with green data centers, why does it matter, and how do we think about it in a wider context? In this short conversation, we discuss green data centers and creating carbon neutral infrastructure.

This isn’t just about servers using electrons – the actual conversation about making our infrastructure carbon neutral includes thinking about all of the components that go into our infrastructure.

We also have an upcoming series of conversations on green data centers and carbon neutral infrastructure.

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

WTF My MFA is MIA

How do authorization systems need to be built and made resilient for distributed infrastructure? We discuss how having a single centralized authorization system is incredibly fragile compared to distributed edge infrastructure.

Everything we build has some element of distributed component tree and resiliency in it, and we need to make sure that the authorization systems are included in that analysis.

We explored how you can make MFA more resilient and how you can improve the security of authentication by building additional layers of trust based on behaviors.

Transcript: otter.ai/u/KTg3WSqSKuswLIypoBwD4HyMzcA
Image: www.pexels.com/photo/hand-holdin…sh-drive-5474298/

Rob’s Hot Take:

In the April 28th Cloud 2030 Podcast, Rob Hirschfeld delves into the challenges of implementing two-factor authentication (2FA) in distributed infrastructures with centralized authentication. The critical problem revolves around creating resilient systems that don’t solely rely on external factors for authentication, considering the potential impact on every service and component in the infrastructure. The discussion emphasizes the importance of behavioral analysis in authentication, scrutinizing user behavior to ensure trustworthiness, especially in scenarios where full authentication is not available. The full conversation explores these aspects in depth, providing valuable insights for building resilient infrastructure. Join future discussions at the2030.cloud.

OSS, Promotions, and Lava Lamps

How can promotion boards be hostile or hurtful to open source technology? We talk about the dynamics of corporate support in open source technology, and if being rewarded for internal work at companies translates into challenges for open source technology.

This discussion starts to peel apart what makes open source technology sustainable, and what it works for. We bring up an analogy of a lava lamp where things heat up and then cool down as part of a natural cycle, which can be a normal cycle for all software, and that led us back to how promotion boards work.

We covered a lot of ground through the dynamics of corporate software governance and open source and interweaving those together.

Transcript: otter.ai/u/nZS6rtcam88JUuqMctOiEyWq5G4
Image: www.pexels.com/photo/food-cold-d…nk-glass-5677999/

Rob’s Hot Take:

In the Cloud 2030 podcast on April 19th, Rob Hirschfeld discusses the challenges of sustaining open source projects and the dynamics of job review boards. The conversation highlights the common evolution of software projects, where initial excitement and rapid development give way to stabilization, increasing complexity, and less excitement. The key takeaway is the need to recognize and reward individuals contributing to the maintenance and extension of existing projects, emphasizing the importance of such work for communities, companies, and society. Join the discussion at the2030.cloud for diverse opinions and insights.

APIs With Composable State

What makes API’s complex? In this episode, we talk about how we compose APIs into higher level systems, and how we think about the design elements that go into building durable, reusable API’s.

This is a classic topic for us, and in this discussion we looked beyond the API itself and started talking about the state of the system and how you manage that state.

Transcript: otter.ai/u/Oae5e_ay0d_l48TmWk3PO3lpIDU
Image: www.pexels.com/photo/a-nacho-chi…ng-sauce-5848731/

Rob’s Hot Take:

In the Cloud 2030 podcast on April 21st, Rob Hirschfeld delves into the complexity of APIs, emphasizing the layered and nested nature of API systems. The discussion unveils the challenges of managing distributed state within APIs, where each layer needs to be aware of and interact with the state of adjacent or underlying APIs. The key insight is that without a well-understood distributed state model at the architectural level, building resilient APIs becomes inherently complex. Join the conversation at the2030.cloud for a comprehensive exploration of API design challenges and solutions.

Musk, Twitter and Web3 Social Media

Will Elon Musk take over Twitter? What are the tech and societal motivations for creating distributed social media?

In today’s episode, we discuss the future of social media and if we can create distributed social media and distributed user interactions. We also question how these systems could be monetized and controlled, and who would benefit from those changes.

This is a fascinating discussion about how we will build human interaction in the future.

Transcript: otter.ai/u/J2B4oRO5WTohJI1KqqNobfyZsdE
Images: www.pexels.com/photo/a-group-of-…num-foil-7105799/

Rob’s Hot Take:

In the April 14th episode of the Cloud 2030 Podcast, Rob Hirschfeld explores the potential implications of Elon Musk taking over Twitter and delves into the broader questions about the future of distributed systems, regulation, monetization, and centralized control. The discussion contemplates the evolving landscape of social media, distributed ledger technology, and infrastructure. While no definitive answers are provided, the conversation highlights the ongoing shift toward decentralized systems and the impact it may have on the market in the coming decade. Join the discussion at the2030.cloud for a deeper exploration of these complex and significant topics.

Can Kubernetes Prevent Vendor Lock In?

How does Kubernetes create lock in versus how could Kubernetes be used to prevent lock in?

Lock in is not always a bad thing. When you avoid committing to a single vendor, you may have to work to the lowest common denominator or deal with heterogeneity in your infrastructure. Heterogeneity is pretty normal, and you might have to do this work regardless, but when you commit to a vendor you get to focus on using the vendor’s strengths.

In this episode, you’ll pick up some great tips on how to reduce your lock in when using Kubernetes.

Transcript: otter.ai/u/vIo1p15bb6VmcrWjwgOLbM25nq4
Image: www.pexels.com/photo/silhouette-…door-knob-792032/

Rob’s Hot Take:

In the April 12th episode of the Cloud 2030 Podcast, Rob Hirschfeld delves into the nuanced discussion of whether Kubernetes prevents or exacerbates vendor lock-in. The key takeaway is that lock-in is not inherently negative, and there’s a need to balance risks and consider the inertia associated with established systems and practices. The podcast encourages listeners to think intentionally about using Kubernetes as an abstraction layer and to recognize the value and challenges of inertia in platform development efforts. For further insights and discussions on DevOps and future strategies, visit the2030.cloud and join the conversation.