We continue our Governance as Code discussions in today’s episode.
We started by very broadly looking at Governance as Code generally, but quickly drilled down into Infrastructure as Code meets Governance as Code focused discussion. Understanding that intersection is critical to building something that is both automated and governable.
The topic explored how we audit controls for systems. We also need to make sure that when we build infrastructure, it’s following our policies. The challenge here is making sure that what we’ve automated is conforming to our governance.
We conceptualize data centers as core infrastructure components in today’s discussion about green infrastructure.
In our discussion about data centers as an industrial load that have peaks and valleys in demand, we dive into the grid as a connected system. We discuss how storage can disrupt the way power is generated and distributed, not only in the United States, but also around the world.
Distribution systems play a huge role in green infrastructure, just like networks. The way we assume that networks are available and robust, we have made the same assumption about power generation in the world to run these data centers.
These topics are all tied together, and you will see a lot of insights and similarities in how we solve and build green infrastructure.
What makes Open Source projects work? Today we discuss open source business models, motivations, what and how these projects work.
We moved from that into testing quality maintenance and ultimately SpaceX and Tesla. This conversation dives into how Elon Musk is transforming the industries that he’s in by looking at the delivery process.
How do you manage complexity? Something we talk about a lot in Cloud2030 is how challenging it is to understand complexity, measure it and cope with it.
Richard Cooke wrote a paper called “How Complex Systems Fail,” (how.complexsystems.fail) and in it he talks about complex systems having strong defense mechanisms against failure. That’s what we talked about today. How do we build defense mechanisms for complex systems, not by making them simpler, but by exercising them and testing them?
We discuss the importance of testing, validation, and layer of abstraction and testing the layers in this conversation. If you deal with complex systems, this discussion will be fascinating and actionable.
How is data center infrastructure adapted to edge distributed ledger technology workloads?
We think through if those demands (blockchain, proof-of-stake coins, etc) are changing the way we look at data center infrastructure, and the short answer is yes. We also explore the impacts of the type of workloads that we’re running and how we distribute them, rather than the type of equipment that we need to buy.
This conversation quickly becomes one about what we want to do with our infrastructure, not what the infrastructure is.
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.