 I'm going to go ahead and do a little bit of cheating. So my name is Jayden. I'm with Canonical, as you probably guessed from my amazingly orange shirt. And the time has started. So we're actually going to do this. Get serious. All right, so thank you guys for joining us. This is a lightning talk, so we're going to be cutting through things real quick. But if you have any questions, please feel free to find me. My name is Jayden. You can find my co-worker, Nicholas. He's a very, very smart fellow. Knows more than I do, I would say. So he's definitely a good person to ask. We also have people at our big orange booth over there. Can't miss it. So we're here if you have any questions. So we're going to talk about Microsoft, just to give you a quick rundown of what it is and who it's for and why we made this thing. Because you might be thinking, hey, Seth's good enough. Why do we need to shrink it down? What are we doing? So first, Microsoft is a new approach to delivering SNF. It's a SNAP. It also has a DQ-like cluster inside of it. And it still is a full Seth solution. So you can get all the great Seth APIs and features that you are used to with Seth. But it's just in a nice little package that's quick and easy to install. It's got some nice convenience interfaces that wrap some of the Seth functionality. So you don't have to spend a day trying to spin up a Seth cluster. You can just get it going. Get a Seth cluster up in five minutes or so and continue with the work you actually need to do that needs Seth but isn't spinning up a Seth cluster. And it really is meant to be run anywhere, especially on your laptop or the edge or someplace that is a lot smaller than a traditional Seth cluster. So the reason why we made this, though, is because I don't know about you, but have you ever needed to develop against Seth? But you didn't want to go through the trouble of setting up an entire Seth cluster. Or you didn't have one available because you would break production data or something like that. And so you either have to spend a day provisioning a Seth cluster that you're going to throw away or you just don't do the work. Well, Microsoft may be the solution for you because it gives you Seth. It gives you the tools you need to do your job to provide object storage, block storage, those kinds of things very quickly, very simply, very easy to get going. And it's also much more suitable for people who are less skilled and less familiar with Seth. It has a lot of thoughts about how to set up Seth and configure it so you can just get on with your day. And again, like I said, it's way more for smaller use cases, edge development, those kinds of things, embedded Seth applications, then that wouldn't be appropriate for a big Seth cluster with multiple hardware nodes and lots of OSDs and things like that. So as I said, it is a SNAP package. So you download the SNAP, gives you some commands to run that you use to bootstrap the Seth cluster to add the OSDs to manage Seth. If you use SNAPs before, it should be very, very familiar. All of the dependencies and things, of course, are packaged inside the SNAP. So you don't have to worry about messing up your host operating system or installing a bunch of extra packages. I like this because it means I can install it on my laptop without having to ruin my laptop in ReOS, as sometimes happens when you're installing dependencies and fun hidden software that projects require. And as I mentioned, we do use DequeLite for the clustering. If you're not familiar with DequeLite, it's a clustered SQLite implementation that we use heavily at Canonical for our cluster services to sync data between the different cluster members. It is quite nice. And this lets Microsoft maintain syncing the Seth state and making sure all the Seth pieces know what's going on and who to talk to and how everything is configured. And it really is meant for labs and environments that are not suitable for a three-node MySQL cluster or PostgreSQL cluster because that is a lot of overhead when you just need to do a development project. So like I mentioned, some use cases. We are targeting things like development, running it on your own laptop, we're running it in a lab, we're targeting edge uses, places where you only maybe have one hardware node, but you still want to have Seth APIs, Seth object storage, Seth block storage available. One use case that I really like, if you have had a chance to try out the new Sunbeam OpenStack deploy that we announced earlier this week, it uses Microsoft inside of it as an embedded application to provide block storage for OpenStack. So I like this because the end user, when they install Sunbeam, they don't have to worry about Seth. We can give them Seth in an embedded way. We can give it to them all configured out of the box thanks to Microsoft. And they can just go on with their day and enjoy the benefits of Seth block storage for OpenStack without having to become a Seth expert when really all they want to do is just run some VMs or learn about this cool new thing called OpenStack. New to them, not new to us, of course. But those are the main use cases that we're trying to target at this time, I would say. And we've got a quick demo showing you how it works. So let me switch over to that. This is an Askinima. If you're not familiar with it, it's a recording of just a command line session. So we're going to go through just some basic command showing you how to execute Microsoft and get Seth set up through Microsoft on a three node virtual machine cluster. So here we are installing the Microsoft Snap to start. We're going to install it on each one of those virtual machines. Have a little bit of trouble typing. How it happens when you're trying to record or do a demo. That's when you always make your mistakes. So here we are going to bootstrap the cluster very quick. It's already done. So the way you do Microsoft, you bootstrap your first node and then you generate tokens that you can use to add other cluster members. So we've generated two tokens to add the second and third Seth cluster member here in this demo, this type of the demo. And now on the VM1, we just ran the join command with that first token. So that tells Microsoft, hey, add this node in. This node that we previously bootstrapped. And then we joined the second virtual machine. And so now we're going to SSH into the first virtual machine, which is the first one we set. You can see here all three nodes are showing up in Microsoft. And here is your Seth status. It's showing three demons, one VM0, VM1, VM2. And now we're done inside of that first instance. So let's keep on looking and seeing what we've got going on. So here we're adding OSDs through Microsoft. Now you can see that we've got OSDs. And now we're just going to add RGW, just as simple as we added the OSDs. I wish I had more to explain, but I feel like it's pretty straightforward what's going on. And I really wouldn't be able to add much beyond enable RGW. So as you can see right now, we very quickly have set up an entire Seth cluster, bootstrapped it, added OSDs, added Rados gateway. All the pieces are right there. And now we're just going to run a quick, quick demo application to show you that this is actually working. It's not a trick. There's no smoke and mirrors. This is actual real Seth that will behave the same way that you are accustomed to, that you love, that you maybe don't love as much. It still is Seth under the hood just in this nice, compact, wrapped up package. So here we are adding just a bunch of demo data to S3 using S3-CMD, which is a command line tool for managing S3 objects. And I think that is the end. Yep. So two or so minutes. We set up a Seth cluster, added all the OSDs, got it all ready, showed you how it's working. Simple as that. I wish I had more that I could explain or tell you this is how it works, this is how it is, but it really is as simple as that process we just showed you. And sure, it's a little tiny bit sped up, but not really more than what you would think. And that's a URL for that demo if you wanted to see it again. Still there. Happy to pause a sec if you want to take a picture of that. I'm going to switch to the next slide since we're running a little bit low on time. And all of these slides in the talks will be on YouTube later. So don't worry if you miss this. And if you did miss it, just come let me know and I'll give you the URL. Happy to do that. So we do have a lot of exciting things on the roadmap. Microsoft is still relatively new. It's still very early days. So we're trying to add a lot more of the Seth features and expose them to the end user. You can see there we're going to encrypt the OSDs. We've got a lot of different things for scalability. Because even though we're targeting a small use case, we do want people to be able to have three or five nodes or a small number of nodes, like if you have an edge deployment with three or five hosts that needs block storage or object storage. And then we want to make it even more convenient and streamlined so you can get on with your day and do the work that you actually need to do. So if you'd like to try out Microsoft or learn more, we've got these QR codes. The one on the left takes you to the website for Microsoft. The one on the right takes you to the GitHub repository where the code actually lives if you want to check that out and see what that's about. I'll pause just a moment so you guys can take some pictures. And again, if you have any questions, just you can find me, you can find Nicholas, you can ask our coworkers, they'll let us know. Happy to pass along my contact information too if you want to reach out later. Yeah, because I know it's pretty exciting. I'm excited to see this come together because as much as I love Seth, I don't love having to set it up when I just need to do some work or some development. It's just not fun, not fun enough. And as I mentioned before, if you haven't had a chance to try it out, we are doing a game of sorts with Sunbeam. If you try out Sunbeam and you install it, you can get a code for a prize that you can redeem at our booth over there. We're still doing that today. We also have a demonstration and workshop today at 4, 4.15, something around that time that we're gonna have resources available for you to try out Sunbeam. If you don't have a computer or something like that here, and we'll have people on hand to talk about it. And I just mentioned that again, because Sunbeam is a really great use case where we're taking Microsoft, we're putting it in Sunbeam to provide Seth storage for OpenStack users. Thank you. We'll take some questions now. We've got just under four minutes. Yes. The question was, what is the minimum size of Microsoft? Can I run it on a single node? Yes, you can. You absolutely can. I mean, clearly, if the node fails, you're gonna lose data, so be careful. But, yeah, you can absolutely run it on a... Yes, in, yes. So actually, I mean, you can. The only thing you have to pay attention to are the crush rules that are... So the default crush rules are assuming three OSDs. And so you'd have to change those manually to change them appropriately for one node. We don't do that automatically yet. But that's also a planned feature to automate that and actually fix crush rules in that use case. Thanks. This is why I said he's the smart guy. Any other questions? Or what are the questions do people have? Yes. The question was, does Microsoft support snapshots and advanced Seth features? I mean, you have Seth. Like, you still do have Seth. And you can do all the things you can normally do with Seth. You just have to drop down and use the Seth command instead of Microsoft. That right now, the options that Microsoft exposes are just for the deployment. That's where we are. But we do expect down the road to add convenience commands for more advanced features so you don't have to be a master of Seth to enjoy those benefits. Any other questions? We have just under two minutes. Cool. Well, if anyone does have any more questions that you come up with later, I'll be here all day. Like I said, we have that Sunbeam Workshop too. If you wanna see real world use of Microsoft in action, come and try out Sunbeam, install it, see the Microsoft and how wonderful it is. Maybe win a prize. And spend some time with some awesome, orange-shirted people. Otherwise, thank you all for listening to the talk. Thank you all for coming to the conference and thank you for using OpenStack and Seth. I hope you guys have a good rest of your day and a safe travel home.