 Thank you, James. Did you hear what he said there right at the end? Over four million cores, and ironic. That's pretty incredible. I think that it's awesome when we have the opportunity within our community to see all of these different perspectives. Amy, who's helped build ecosystems around open source. James, who is one of the largest consumers of open source, running some of the largest infrastructure. And next up, we're going to get from some of the developers who are building it. And so James talked to four million plus cores. That's obviously something that's going to be a fairly stable code base that you're going to rely on for that. But ironic is also one of the projects that's getting pushed into new areas like HPC and machine learning and supporting containers. And so up next, we're going to see how you can take bare metal and take it into some of those really cool new environments. So help me welcome Chris Hodge and Julia Krieger. All right, demo time. So like I was saying, you're going to show us one of the cool use cases that's kind of cutting edge. This is stuff that's very new, very much still being developed, but that involves ironic as one of the underlying components. Yeah, this demo is going to show how ironic is being used in a new way to manage hardware, like the machines we have in front of us right here, using Kubernetes. And what we're doing is we're going to create a new custom resource inside of Kubernetes called bare metal host, which is going to be backed by ironic. And so we're just going to start with a fresh, brand new Kubernetes installation, nothing there. And as you're watching, at the top of the screen, you're going to see the status of our system. So you can follow along with that. To the left of the screen, you're going to see the manifests that we use to define what our bare metal resources look like. And then to the right, you're going to see the commands we run to bring the whole system to life. All right, let's get it started. So yeah, let's start out. We're just going to watch all the resources in the system. And so we're using kubectl to watch our bare metal hosts and OpenStack bare metal node list to watch ironic's view of the system. And so we start that up. So one of the things you're going to notice is that there's actually nothing happening right now. We're seeing errors up at the top there. And that's because we have literally installed nothing except for Kubernetes. And so we're going to start off by running a local installation of Ironic. And we bring up the Ironic service. And we're going to see that Ironic is connected. And then we can. Some of the errors went away. Yep, some of the errors went away. But we still don't have this resource type bare metal hosts. And so we're going to use this new project called Metal Cubed to create these bare metal hosts and make Kubernetes aware that we can manage these resources. And so as we run this, we're going to see that we go from we don't know about this resource to we have no resources found. And that's because these servers, you're a little mini data center here, they actually are not registered. They don't have anything installed on. They're just bare machines. Right, these servers haven't been enrolled yet. And so we have to tell Kubernetes and Ironic about this. And the way we do this is with a manifest. It's a YAML file that we have on the left here where we define our three nodes which have a state. Are they online? We give them a name. And we also talk about how the hardware interfaces that we have to turn them on and off and provision them. And so we have three of these nodes defined in this file. And we use cube control and apply this file, which we call hostsEnrolled.YAML. And when we run that, our nodes are created. The credentials to communicate with them are created. And almost immediately, we see this reflected in the resources in the system. So Kubernetes says that we know about these resources. They're ready to be provisioned. And Ironic says, yep, we know about this, and they're ready to be managed. So now, we can update our hosts file, our host manifest to add a little bit more information to the system. And so for node one and node two, we're going to bring them online, and we're also going to define different images that we want to provision them with. So on node one, we're going to install a basic Linux image. And on node three, we're going to install a Kubernetes image. So we go back to our command window. We apply it to our new hosts up manifest. And we launch it. And again, all of the resources change. They change from state ready to provisioning. And Ironic begins the deployment process. Now, if you ever worked with bare metal before, you know that it can take a little bit of time to clean the systems, boot them, get everything set up. And so while we do that, I think that Jonathan might have an exciting announcement for us. Sure. So one of the things that we have seen growing as a use case within OpenStack overall is bare metal. It's gone from single digits to mid double digits in terms of production usage within our user survey over the last couple of years. And we see it driving some of the newest use cases from our user base. So what we are doing this week is we are launching a new program around Ironic to bring together the vendors who are creating products that integrate it, as well as the users like James and others who are basing their fundamental data center components around it. And as we started to put this together, we had a really strong response. We have over 30 companies that have already joined up to participate. So that's a lot of momentum in this. And I think that what these companies want to do is they want to get together and find a path forward to share how they're doing it, their use cases, and also to help direct the future of development around Ironic and bare metal overall. So if you want to get involved in that, you can go to openstack.org slash bare metal to see more information and start working with this new part of our community that's forming up. We also have PTL of Ironic here today. And Julia has spent years and years working on Ironic and bare metal overall. And I'm going to hand it over to her to talk a little bit about why she thinks bare metal is very important. Thank you. So if we look at the history of computing, we started out programming our computers with the design of the electrical mechanical circuitry in the, I won't even call a box, racks. As time went on, we developed new ways of programming them. We developed operating systems to make things generic, to make it even easier to program them. We even started virtualizing them, virtualizing entire systems. The point really is, though, that every concept in the history of computing is an abstraction of a concept that supports it. We put forth a tremendous amount of energy into making computing easier. We're trying to take away the difficulties of how we orchestrate all our systems, how we construct and manage our networks, how we deploy the operating systems, and how we manage the servers. But one fundamental thing at the bottom of this is that the underlying hardware still has to be provisioned, and it still has to be maintained. And if you think about computers and cars, they're very similar. Cars need to be built just like computers. They need the tires rotated. Unfortunately, not computers. But you need a little change in your car. And you also occasionally need things inspected. Make sure that they're in proper working order. And cars sharing the same interfaces and everyone being able to drive them the same way doesn't take away that we have to manage this underlying technology beneath it. And that brings such a key point home that the success of the technology at the top of the stack really relies upon the solid foundations that we lay at the bottom of the stack. Which brings us to Ironic. Ironic is an open stack project that helps solve the problem of managing provision bare metal systems. It started as a driver for NOVA as a way to make bare metal machines look like virtual machines. You get a fully managed, multi-tenant, bare metal cloud with the same APIs that you used to deploy a virtual machine. Yeah, and over the years, Ironic has matured into more than just a simple computer driver, which is why it's one of my favorite open stack projects. It's a powerful standalone service for managing and provisioning bare metal. And it has this rich feature set that includes support for a wide number of industry power management and provisioning standards and drivers. It allows for hardware inspection and discovery. It has mechanisms for firmware updates. And it also has a framework for lifecycle management. One of the best things about it is it has a small installation footprint, which makes it a useful driver and a useful integration layer for other management tools, like the one we're seeing. We're demonstrating today with Metal Cubed. Coming back to abstractions, one theme that we probably all know is that as you add more abstractions, you start to lose performance. It's the interpreted versus compiled languages, virtual machines versus bare metal kind of differences. Yet the rise of cutting-edge technologies on top of these abstractions is creating a demand for highly performant and flexible tooling. In our demo, we're showing you how Ironic can help deliver performance in this new reality. So let's see how that did it work, Chris? Yeah, so if we go back to the demo, we can see that both of the nodes that we have have moved from a manageable state to an active state. Ironic says they're active and powered on. And Kubernetes says that they're provisioned and ready to go. So in the time that we started the demo just a few minutes ago, we went from Kubernetes installation all the way to managing our own mini data center. And so you installed Ironic. You brought these machines up, enrolled them, and you did all of that through Kubernetes APIs as well. Yes, exactly. That's cool. I mean, that is such an awesome example of, I think, what we were talking about earlier, of collaborating across boundaries, of bringing projects and communities together to bring that power that people are looking for. So thank you for showing us that today. If people want to learn more about it this week, what should they be doing? Today, we have several sessions that people might find interesting. And if you want to see this live demo with Chris, he'll be in the Open Infrastructure Lounge. In the Open Infrastructure Lounge, you can find it on the schedule. And I'm happy to provide demos of this or of Ironic with Nova. Excellent. Awesome. Thank you. Well, thank you for showing us that today. And I'm glad that the demo god smiled on us. So I talked some about my personal experiences. And we heard from Amy. We heard from James. We heard from Julia and Chris. And I think that we talked about what we've learned and what we've seen and the opportunities that are ahead of us. And some of my most important experiences have happened in this community. And many of those things that I've learned and that I think all of us have learned, we've learned from you. And we've learned from participating with all of you as we have built OpenStack and all of these open source tools over the last few years. Learning and solving problems together is what we do. And collaboration without boundaries is how we do it. And I want that to be a theme for all of us as we get ready to spend our week together working to try to solve problems, to try to create new innovation, and to try to drive the state of the art forward enabling 5G and machine learning and AI and all of these incredible new use cases. We have an awesome opportunity to make sure that as we go out into the future, more and more of it is built on open source and open infrastructure. So let's go do that this week. Have a great week, everyone, and thank you for being here.