 Hello. All right, can you guys hear me OK? All right, timer has started. So thank you all for coming to my talk. It's open stack in 0 to 45 seconds, engineering at the speed of light, brought to you by OpenMetal. So just a little bit about who OpenMetal is, we're a relatively new company. We spun off from InMotion Hosting, who's been in the traditional kind of web hosting business for more than 20 years. We are a silver member and infrastructure donor for the OpenInfo Foundation, as you saw. We were also nominated for a Super User Award. Very nice that folks do to recognize us for the work we're doing. We do have a booth here. If you'd like to come talk after the presentation, we're in booth B9 over by the far door on that side of the floor above us. So as I'm sure many of you are familiar with, getting your open stack cloud together, it's not easy. It's not something that you can just do on a snap in a lot of cases unless you already know really well what you're doing, especially if you're trying to do a side project or some testing, you have to get hardware. You have to get your company to give you the approval to get the resources to get your cloud set up. You have to configure that hardware. You have to set up all your software. You know, you're going to use stuff for storage. You can use something else for storage. You've got to set up OpenStack itself. You have to get OpenStack out. And then you get to do your work. So I don't know what your experience with OpenStack is, but I know for me, it's easily hours, weeks to get OpenStack set up before I can just do whatever it is I need to do. And it's hard to justify that kind of expense when you just need to run some tests for a week or a day or a couple of days. That's the kind of experience I want to talk about. And I want to tell our story about how we've wrestled with this issue and how we've gotten past it. Because there's a lot of important work you have to do. So you get a new OpenStack release coming out. You need to test it to make sure it's not going to ruin your public cloud or your private cloud. Well, do you have hardware laying around to do that? Do you have that budget for that? Do you have the budget for the time? Can you go to your boss and say, yeah, just give me $100,000 so I can buy a lab in our data center that we're just going to run for a week for testing and throw it away afterwards? I hope your boss always says yes, but I know for many people that's not a case or a world that we live in. For us, though, we've been working on this solution for a year and a half to try to make OpenStack as simple and easy to deploy as possible. And we really are aiming to get it down to a single click. We believe that if we can make OpenStack as easy to use as a public cloud, it'll really just unlock what you can do with OpenStack and the value you can get out of OpenStack. And then you can get everything together and get going and do your job and get on your way in true cloud fashion. Because if you may, I don't know if you've poked around the Open Infrastructure Foundation's website, but some of their core values talk about for the cloud. It's about being able to provision resources without having to ask for permission or having to do a big, complex thing. That's what they describe being the cloud or the true cloud experience as being. So I'm going to show you what we've been working on. We're just going to go through real quick our deployment process. It didn't take any time at all. So we've got these different hardware types. We started out with a hyper-converged cloud deployment, each hardware node. Runs SEP for storage. It runs a compute hypervisor. It runs control plane services. So we're going to start with this one here in the middle. The main differences are hardware specs, but that's not as important for the purpose of this demonstration. Really, I want to show you guys how we've gotten to that one click experience for deploying Open Stack. Go ahead and give it a name. We'll give it a public SSH key. So this cloud, it is going to spin up three boxes. They're entirely dedicated to this cloud. They have their own control plane. You have bare metal access. That's why we've got to put this SSH key in. We do have a trial system, so you don't have to put in a credit card if you're approved for that. And there we go. So what I've started doing is deploying a cloud. And in about 45 to 60 seconds, we'll have a ready to go fully set up Open Stack cloud that the user can log into Horizon just right away. So we'll let that go. Let that do its thing. Actually, it's done. So that's it. We have a full Open Stack cloud in a single click. And it's just right there. Three boxes ready to go. And if you're done with the cloud, you can just delete it as simple as this if I can type things correctly. And it'll go back. All the hardware will get cycled back. We do have Horizon. Here's the Horizon login for that cloud. So this is the kind of experience that we wanted to offer and bring forward to Open Stack for users to be able to get to Open Stack. And I just want to tell you a little bit about some of the things that we've been able to do when you can do this. When Open Stack is really as easy as just one click. So I know for our engineers, it's been wonderful. I mean, when we have somebody come in and says, hey, I want to use Open Stack for this thing, we can get started right away. We can turn it around that same day and give them a cloud and put it in their hands and start testing, start benchmarking, start profiling. There's no, we'll get to you in six months. We got to order hardware. We got to get the whole thing set up. Our engineers love being able to test out new services in Open Stack and do configuration changes and test out things in a safe environment. So let's say you want to deploy a new service, like Open Stack Manila for file sharing. And you want to make sure it works and you understand it before you roll to your public cloud or your existing deployment. That's something that you can do when you can turn Open Stack on in just a second and get it going. We've also tested new releases of Open Stack so that we can know it's going to be perfect before we roll it out to our customers. Just these are the kinds of things that we're connecting our engineers and that we want to share with the community with all of you and your engineers so that you can use Open Stack and do the things that you would love to do in an ideal world, but can't because of budgetary or hardware or other kinds of constraints. One other advantage for this platform and this kind of approach to Open Stack is that you can have multiple clouds. So there's no more putting all of your eggs in one basket. I know one of the big features of the cloud is that it's supposed to help you make your infrastructure into cattle, not pets, it's supposed to make it reusable, but I think the cloud's a little funny because if you have one big cloud that's running all of your assets, that's your pet. It's not cattle anymore. You're just consolidating all of that risk into a single big unit and when you can deploy multiple clouds, it's easy to start breaking up your workloads. You can have multiple customers on their own individual clouds or multiple business units on their own clouds and you can really quickly meet your customer's needs, meet your team's needs without having to be bound by, oh no, we don't want to break production or break the big public cloud or big deployment that we have because we're scared of it. So if you'd like to try this out, you can check out our website. We do have a free trial. You can spin up a cloud just like I did and try it out for 72 hours. It automatically goes back into our pool when that time elapses. You can also come talk to us at Exhibitor Booth B9, like I said. If you want to talk to me, this is me. I work for O-Metal. That's my email address, my LinkedIn, my Twitter. Happy to always connect to people and talk about OpenStack or other things, not OpenStack. Also like philosophy. And I have a second degree black belt in Taekwondo, so I have other things that I'm into. But if you guys have questions, I'd be happy to take questions. This is the end of the presentation time, so yes. So right now we are hosted. We'd like to do on-premise. We just haven't gotten there yet. Our software solution is designed to be portable. This is just a question of getting those development resources lined up. We use OpenStack Bifrost to manage the hardware. So theoretically we should be able to use whatever hardware that Bifrost supports. And then otherwise we use other open source tooling to deploy onto the bare metal systems. Yes. So Starling X, I understand, is more focused on edge computing and giving you that full or like edge computing experience. I'm not familiar enough with their product to say the exact same things, or like what the exact lineups are. I know one thing that differentiates us from other competitors in this space is that we give each cloud a full dedicated control plane. So it is fully isolated from every other cloud in the system that's deployed. So I have six minutes left. Do you have any other questions? Yes, sir. So how would you like an additional project for this kind of deployment purpose? Thank you. You said if you were to test Manila or whatever else project, how can you get in each part within this four to five seconds employment? So this interface here is for our higher level management system. This is our open metal central. And through the system, you could deploy multiple clouds and each cloud just shows up with its own management area. So the same way I just deployed that cloud, I showed you, you could do five, 10, 15 clouds, however many clouds you want, and organize them through this interface. That's how I would spin up for doing testing or research. I mean, that's how we as a team do it every day. To a date, we've deployed almost 800 clouds through our system over the last 18 months. Almost all of those have been just testing, development, research, throwaway kind of clouds. Oh, I'm sorry, I did misunderstand. Yeah, so you have full control of the boxes. So you can log in and add Magnum or, I've done this myself for some of our end customers I've added, so we have a core configuration that includes the core open stack services of Magnum and Octavia, but I've added Manila, I've added open stack Zoom, I've added open stack Courier afterwards. You can customize the deployment however you want after it's been set up and deployed, because you have full access. And we use Kala Ansible for our deployment system, so all you have to do is just change your Kala Ansible configuration and rerun the deployment, and it'll work. And there you go, you'll have your cloud set up. You're welcome. Any other questions about the presentation? I'm happy to take questions on other random things as well. We've got three minutes left. All right, well, thank you all for listening to the talk. I hope you've come away with something interesting. We're really excited about this platform that we've built and we really would like to share it with the community. Because, you know, we're the same kind of people as you are, we have the same kinds of challenges and it's been a big help having this kind of flexibility and this flexible infrastructure and we wanna enable others to enjoy the same experience and flexibility that we've enjoyed building this platform. So my name is Jayden. I'm Senior Product Manager, but I do a bunch of other things too. It's complicated, but I'm over at the booth today and through the rest of the summit. So thank you all.