Tag Archives: Infrastructure as Code

Orchestration Balancing Events And Flows

When working with orchestration in automated systems, how do you find the right balance between things that are event driven and things that are workflow driven, or more linear?

We go through some of the history of where we went from linear orchestration (Ansible) to timed orchestration (Chef or Puppet). We also discussed SaltStack, which had an event driven system into it, but didn’t gain the traction that we might have expected as we look at the amount of orchestration systems that are now coming to light.

In this conversation, we address the balance between when you orchestrate and when you want to do workflow and linear transactions, and how to find that sweet spot.

One of the things that we’ve determined is, there aren’t a lot of tools that hit that sweet spot. And I think if you listen carefully, you’ll see why.

Transcript: otter.ai/u/ynb8KndfUhKsTvQG6965ktepv-Y
Image: www.pexels.com/photo/a-choir-sin…a-flower-7569413/

Rob’s Hot Take:

In the August 16th orchestration discussion on Cloud 2030, Rob Hirschfeld emphasizes the importance of striking a balance between orchestrated systems and event-driven operations. He highlights the challenge of comprehending the consequences of operations in complex systems and emphasizes the need for a blend of orchestration and event-driven approaches while ensuring that automation workflows remain understandable to users. Hirschfeld encourages listeners to explore the full episode at the2030.cloud, where the discussion delves into various tools, techniques, and considerations for building effective systems.

Everything As Code !

What makes Everything as Code and Infrastructure as Code interesting? In today’s episode, we discuss what makes something code-like and the idea of Everything as Code, based on Patrick Dubois’ article “In depth research and trends analyzed from 50+ different concepts as code.”

Reference: www.jedi.be/blog/2022/02/23/tre…0-as-code-concepts/

Some of our conclusions were practical, like if a concept is a process that is reproducible and auditable, that’s what makes it code-like. And some other possible conclusions were that it’s just marketing because it makes everything programmable. The reality is somewhere in the middle.

Transcript: otter.ai/u/E1TezO2XutwJyS-vCNetslwWO4A
Image: www.pexels.com/photo/man-in-grey…icky-note-879109/

Rob’s Hot Take:

In the Cloud 2030 Podcast episode on March 29th, Rob Hirschfeld provides insights on the “everything as code” discussion. While acknowledging the term’s playful exaggeration, Hirschfeld emphasizes the underlying desire for reproducibility, auditability, and code-like experiences in various aspects of operational and infrastructure activities. Despite the term’s potential for marketing hype, the aspiration to apply code principles to different facets of infrastructure management remains significant, influencing how we build and manage systems. To delve into this engaging discussion, check out the full episode on March 29th, available on the2030.cloud.

Improving Automation Safety

Making automation safe is essential to making it usable at scale. How do we make automation safe? We found a lot of great insights drawing from space craft design, aircraft, aircraft design and other systems where safety is super important.

Automation is a force multiplier. If we don’t factor in safety when we build it,then we could create a lot of harm in systems from wasteful spending to actual injury. These designs have very real implications.

Transcript: otter.ai/u/p9w4aKOqm3rpHhbDtRTaLgN3GIA
Image: www.pexels.com/photo/toddler-usi…-on-road-1642055/

Rob’s Hot Take:

In the Cloud 2030 Podcast on March 15th, Rob Hirschfeld underscores the critical importance of automation safety in system design. Emphasizing the need for thorough testing, he discusses how safety, especially in complex systems like airplanes and spacecraft, requires continuous testing and monitoring. The conversation delves into the significance of not just completing tasks but also exercising and testing systems in various scenarios to ensure their safety. To explore these insights further, listen to the full episode on March 15th at the2030.cloud and participate in the ongoing discussions.

Terraform Usage Patterns (Gitops, IaC, Templates)

Cloud provisioning is very difficult when you go beyond simple provisioning and start thinking about how to to stitch together infrastructure in a repeatable way!

Specifically, today’s episode is a deep dive into Terraform usage patterns.

We get very hands on as we talk about how you manage state files and how you connect things together with Terraform.

We will spend a significant amount of time discussing in the fall because building infrastructure in a scalable automatable way, is a critical topic for the group.

This is an ongoing topic for us – stay tuned for more episodes!

Transcript: otter.ai/u/A-NgZOfa1xeIPA1uQOh8_bSStck
Photo by Artem Beliaikin from Pexels [ID 1079033]