 Thank you very much. Thank you, thank you. Alternative images, Sig, let's talk about it. The goal of alternative images is, it's a great alternative image, is sent to a stream, by default it comes with a net boot image and this 10 gig DVD, and there's no in-between. Well, we want variations. So that's what the Sig was set up. We invite all groups to come. The hyperscale Sig is one of our main themes. And whenever we do these things, we have lots of goals. We're not gonna go all this. It's been one year since I've announced this at, it was, anyway, it's been a year since we announced it. This is a Sig that's gonna take a long time setting up. We had to get up the infrastructure, of course we had to set up the Sig. We had to investigate what kind of images are we doing. We looked at lives, install plus live, just plain installs, containers, immutable. Out of all those, we sort of tossed out containers because that's what Podman's for. People can make their own containers. So we investigated how to make them. The live CDs, Kiwi and Image Builder. And to be honest, the only one that ended up working right now is Kiwi. So let's go into doing some of that. This was meant to be a lightning talk, so maybe I'll slow down a little bit. Unless you guys are gonna have questions after. But this is getting to the good stuff, what we've actually started doing. We got Kiwi set up in the Sig infrastructure, the CBS, Centos build system. Neil has made some test images. Unfortunately, they are having problems booting, so they're not really what you want. But the infrastructure is almost completely set up. We should be able to push images up to the mirrors, just like RPMs are. Live CD and Image Builders are not happening. Live CD just because we don't have Pungie. I believe that's the reason. Anyway, it's not happening. Image Builder, that's a whole other story, Image Builder. We also promised we were gonna do documentation, the documentation has started, it's still in rough shape, but there is some documentation. One of the things that I've done, one we found out we couldn't do Image Builder is, I says, hey, here's how to make your own images using the API. I have since found out at this conference that, hey, there might already be a command line, so I don't have to, the documentation might get cleaner. And we're gonna tell you how to do Kiwi things using the Kiwi Image Builder, but that documentation hasn't happened yet. So where's our future line? Kiwi, we're close. We're always like one month away from the Kiwi images. That'll be a live image that you can install from. Very much like the KDE spinning Fedora or the workstation in Fedora. We are gonna do both KDE and GNOME, we're not gonna be, even though I'm the KDE, love KDE, we're not gonna be selfish and we're gonna do a GNOME one too. And if others wanna join once we get the documentation, hey, we can do, I really wanna do my ultimate desktop image that has KDE, GNOME, XFCE. All the fun stuff, but that's still many months down the road. Once we get images published, we're gonna have sort of some supported ones, the ones that go on the mirrors. We will have those refreshed at least quarterly so that we don't have old images just sitting around. And we, as people come to us and get things going, we'll figure out their consistent things. Documentation, I just said about one, but we're gonna have more how-tos. Wow, I'm not talking slow enough. I'm supposed to start just two minutes ago. Okay, we're gonna have more how-tos. We're gonna have better builder old images. Once I started working with the image builder, I sort of found that this is sort of cool. I hate the web interface. Well, it's not bad. But you can do so much more going through the, using the APIs and stuff. So we're gonna have more templates for the image builder. That's it. So I meant this to be a lightning talk. I didn't mean it to be 15 minutes. Do we have questions for this? Or I can talk really slow. Good, we have one. As the person who also does a lot of the images for the Rocky project, A, I'd love to talk about how we can collaborate and work on the different goals that we have and also the similar goals that we have because our kickstarts that we use to build our images are based on the CentOS ones. So there's the natural evolution there for the history of that. The other side of it is what do you think of the current landscape as you were talking about all of the different options for building images? There's a lot of tools that have been developed by Red Hat and others and are sort of in interesting states, I guess is the best way to put that. I'm thinking like Image Factory, which is what Rocky is currently using and based off of to build. You mentioned Kiwi. There's a bunch of other solutions as well. I guess what are your thoughts on the building landscape as it exists right now? I would love to have more than Kiwi. Not that Kiwi's bad. If we can get it into the thing, the one thing that's limiting us is the CBS, the CentOSig built infrastructure. We would really like our images to be built in that or possibly Fedora, but Fedora sort of doesn't want us. So that's why we're in this room. But if we can get it to work on the SIG infrastructure, we would love it. Yeah, because I believe Image Builder did come up. I put live CD and I believe Image Builder did come up. Oh, yeah, sorry, I'm taking this. Somebody told me every once in a while, don't see what just comes to your mind. But OpenSusie has some really good tools too. So yeah, if we can get it there, I would love to get it. So the automotive is also trying to do things. Theirs is gonna be a little different and we haven't quite figured out how would we get that in there too, which is probably why they haven't really been with us because we don't know how to build their images on this SIG infrastructure. Anyway, that's the thing. We'd love more than one way. SIG is the only one that currently is fitting. Any other questions? Brian, back there. I've got sort of a philosophical question for you, Troy. So when you have a large release engineering operation and you're building a bunch of images for people, you're kind of making decisions that you think are on behalf of what the users might want or something like that. What do you think would make the user folks more comfortable generating their own images or dealing with their own blueprints rather than having them pre-generated? That's sort of why I was documenting the image builder things. Oh, I don't have to repeat the question because you said it into the mic. One of the ways I think users would be more comfortable doing it is by doing their own configs. Maybe starting with a kickstart but doing their own configs. If we can make it easy for them, like I said, we as the Kiwi group, not Kiwi group, the people that are currently active in the SIG, we're gonna set up some initial kickstarts and stuff like that but we would love for other users to come and if it is something that we can auto-generate, we're gonna get scripts doing once we're things so that once, like I said, once a quarter, just automatically redo their image. We don't want somebody to just drop it in our lap. We'd like them to at least show up every once in a while and say, yeah, this is the right image but we'd love for the users to make their own kickstarts, make their own templates. So hopefully that makes them comfortable and if our instructions aren't very good, tell us that they're not very good and we'll work with them to make them more comfortable because I do realize that sometimes what goes on in my head doesn't answer some of these questions. So my documentation isn't always the best way. I definitely would love if someone says it's not good to work with me so that it is good. Any other questions? Thank you for the questions, by the way. And there's Neil in case you're wondering, he helps with the Kiwi stuff. So any Kiwi questions, go right to him. All right, thank you.