 Hi, this is from Al Fahir, within the Pocket Designs series. We're about a week out from the Design Summit, and I've got Jim here with me. Jim, can you tell us a little bit about yourself? Hi, so my name is Jim Roland Hagen. I work for Rackspace as a software developer, and I'm the project technical lead for Ironic for the Metacos cycle. So Jim, according to the user survey, Ironic has been gaining a lot of adoption. Can you expand on what Ironic is? Yeah, so we're really excited about the adoption we've seen. Ironic, as a whole, is just about provisioning bare metal servers. It started out as kind of a project to do that in a cloud-like fashion, treating servers as a cattle instead of pets. And we've been just pushing forward on that goal. There's some other projects we've seen to help more of the operator experience around that, and one of them is ByFrost. It's essentially a set of Ansible playbooks to quickly deploy Ironic in a standalone fashion without the rest of OpenStack, and from there, be able to spin up bare metal servers from an inventory. So folks have been using that to kind of spin up bare metal servers ad hoc. You know, if they're setting up like a small clock, just spin those up and then they can go on and provision them from there. And I think that's a really valuable use case. Some of the more pet-like use cases can use that. We've also seen a lot of work on Inspector, which is a project to get things into Ironic. So you bring your racks into the data center, hook them up, and just start them up. Inspector takes care of the rest. It goes out, it routes a RAM disk there. It figures out everything about those servers. And I think this ecosystem tools we're building here is going to be really valuable for operators. Very cool. And I know Ironic also used December or independent users. How's that going from the cheats at all? So far, so good. So it took us a while in Liberty to get our first release out, and within a month and a half we had two more releases, the second of which had something like 30 or 40 bug fixes in just a few weeks. So I'm really excited about getting features and bug fixes out to our users faster. And I hope to do those even more frequently in the future. So during the design summit in Tokyo, what were some of the hot topics that I wanted to discuss and more of the decisions? So a lot of our things came down to just general stability. There's a few different things we're working on that front, mostly around testing, some of the NOVA interactions and that sort of thing. And as far as users or operators are concerned, what were some of the needs that you identified to solve their problems in the summit? Right, so the NOVA thing is a big thing. Right now there's not much HA or room for failure in that integration, and we are going to fix that. So given that focus, what would you say are the top three priorities for either new features or enhancement state system ones? That's a big one. Another one is just general better testing. And then a lot of our users have been asking for good rate support and networking support with Neutron. And so being able to do some of that is what we want to accomplish this cycle. Great. And then generally the private work group has been using the concept of themes such as scalability and so you can see manageability, modularity, and dropability and help you to understand direction where projects are headed. So could you elaborate on possibly where some of the key needs for your project in Netaka? Sure. So as I've implied, resiliency is a huge one for us. Making that story good, making things well tested, just generally releasing good software there. And then scalability is a big one too. The NOVA changes I mentioned will help us scale out to tens or even hundreds of thousands of servers. Just to elaborate on the testing thing, we're starting an effort to have third party testing for all of our drivers. So that's going to be huge for us, just ensuring that those all work as expected for our users. And beyond that, we would love some help. If you can write code or review code, please come join us. Great. Thank you. We look forward to amazing things in Netaka. Thanks for your time, Jeff. Thank you very much.