 Welcome everybody. Thank you for joining us. Thanks for attending NEST as well. It's a great turnout, so glad to see a lot of growth in the community over the past year. I'm Jack. I'm a program manager in Microsoft's Linux Systems Group, and I'm joined here by the lovely Dusty Mabe, and we're going to talk to you about Fedora on the world's computer and how we're onboarding Fedora onto Microsoft Azure. So, like I mentioned, I'm Jack. Some of you might know me, some of you might not. I've been a Fedora person for a long time, longer than I'd like to admit. Since the project started, basically, I used to run marketing. I created ambassadors and FodCon, which eventually turned into this, which is awesome. So, yay, FodCon. I'm an AMA Linux contributor as well, and I help make Linux awesome on Azure as part of our Linux Systems Group, and we are hiring, so if you're interested in doing cool things, please let me know. So, we already picked a name, so we'll skip this. Garfunkel it is. So, Microsoft Azure is the world's computer. We have points of presence in 140 countries, 200 data centers, which is mind-boggling, 175,000 miles of fiber. I can't get fiber to my home, and we were talking about this in the sponsor social before, so I'm a little sad about that. But the one surprising thing that you may not know is that actually 60% of cores and 60% of the images in our marketplace on Azure are Linux. So, Linux actually makes up a really large part of Azure, which I think most people hear Microsoft and automatically assume Windows, but that's actually not the case. And I have a really cool link down there at the bottom to an interactive demo of the Azure infrastructure worldwide. It's like this 3D globe, and it shows you all the POPs and all the data centers and stuff, so if anyone wants to check that out, I was impressed by it, so that's really cool. So, the bad thing about Azure, Fedora was missing until today. If anyone has been following along, we've been trying to bring Fedora into Azure for quite some time. The primary impediments are, so the way to get a distro into Azure until now was through Azure Marketplace. And there are really some issues there because that's really focused on commercial offerings and having your own tax ID and stuff like that, business requirements around SLA, supportability, some legal concerns, and some of those kind of really didn't fit with how Fedora operates. So, there was lots of discussion back and forth and just trying to make this happen for a very long time. On the technical front, there are also issues like making sure stuff like WA Linux agent is included in there, and that's like our provisioning agent, which does a lot more than just that, but basically that's the gist of it, similar to Cloud in it. So, there were lots of challenges, but we made it happen. So, now, how did we do this? With something we like to call Azure Community Galleries. So, Azure Community Galleries are a new feature of Azure, I should say, which is in public preview right now, and what it lets you do is it lets content publishers that have non-commercial, non-proprietary content to just basically set up their own galleries and share their images with everyone in Azure. So, like I said, you can share those out to all Azure users. You don't need to worry about things like multi-tenancy and permissions and stuff like that. So, it's truly like a purely public gallery. Images are also, the Community Galleries are 100% free. The only cost associated with that is obviously image storage fees, which are not too bad considering what the size of the images are, but we need to make sure that people are aware of that too. Other than that, it's a very standard image creation process. There's nothing you do differently or special for the Community Galleries. And also, one of the biggest and most important parts are that projects provide their own legal agreement. So, really any open-source publisher that wants to get their software out to the larger Azure audience can basically release it onto Community Galleries and put up their terms essentially. And so, you retain the same license as whatever your upstream license is. There's no funny business there. And then also, all Community Gallery images are community supported. So, it's not something that Microsoft necessarily has any outside agreement with. Now, if there was an entity that wanted to provide support, that's totally okay. It's just, you know, the implication in anything in Community Galleries is that if you're looking for support, you're going to work through the community in order to get that support. So, Fedora and Fedora Core OS. So, Fedora Core OS images are already actually built. They've actually had those for quite a long time for Azure. So, stay tuned for the Dusty Mabe Show coming up where you'll learn more all about that. And Fedora proper images are on the way. You can follow along on Pagger. We have kick starts ready to go basically. And then just because I know the question is going to come up, right? What about WSL2? We have hurdles. We'll get there. You know, this is a first step. It's actually a big step. And so, hopefully we can eventually get to a place where we can have Fedora on WSL as well. So, I will turn it off to, turn it over to Dusty and the Dusty Mabe Show, take it away. Yeah, I was going to say the Dusty Mabe Show makes it sound way more exciting than what it probably is. The Dusty Mabe, no show. Next slide. So, who is the Dusty Mabe? There's actually more than one of me, but don't try to find the other one. Long story short, I have a wife and two kids and two dogs who were our kids before we had kids. We live in North Carolina. And I enjoy learning and experimenting with new technologies. I really like, I guess, the whole software industry. It moves fast. It's exciting. Originally, I was focused a little more on hardware, which doesn't move as fast. But now I'm an engineer at Red Hat. I work on Fedora CoreOS and Red Hat CoreOS, which is the foundation of OpenShift. I was previously involved in a project called Atomic Host, and that kind of led into Fedora CoreOS. I was also involved in the Fedora Cloud Working Group for a long time, still kind of am, but David Duncan is kind of running the show there now, and I just tried to help him when I can. Next slide. So, specifically, Fedora CoreOS and Fedora CoreOS, as you mentioned, we've had Azure images since our very first release of Fedora CoreOS. This bullet point right here is actually a link, if you had access to the slides, to our very first release with the Azure image in it. That was from Fedora 31 in December of 2019. So we've had an image for a long time, probably didn't have docs off the bat, and definitely didn't have CI. Starting at the end of March this year. So we finally worked it out with Azure. They started a open source credits program, and we got some credits from them with an account for Fedora. And so now we're actually running CI against the Azure images that we create, but there wasn't really a way for us to share them with other people until now. Next slide. Yeah, so our user experience was kind of lacking. So for Azure, for all of the different cloud images that we create, which we have a lot of, there's this download page, right? This is a screenshot from our download page where you can go and actually download the file. So for Azure, it's a compressed VHD file. And as a user, you go there and grab it first, and then you can use it. And I'll go through that a little bit more on the next slide. So here's actually, if you go to the next slide, here's our pictures of our documentation. So these are screenshots. So first you actually have to download the Azure image. So it's just a file, download it. Then you have to upload it, upload the file, and create the image before you get to this next slide, which is actually launching the VM instance. This is where you want to be from step one, right? You want to basically be as close to success as possible. And for example, comparing to some of our other cloud providers, if you go to the next slide, you'll see we have a separate tab, which is cloud launchable, right? So like these are cloud providers where you can actually go directly to the cloud provider and launch Fedora CoroS as quick as you possibly could, right? So you can click on these links on this page and go directly to the cloud provider, assuming you're signed in and launch an instance, or you could use the CLI tools and use the references. So like the AMI or the image family name and launch those directly. That's the experience we want to give people, but we haven't been able to do that for sure. If you go to the next slide, it's actually, I'm reusing Jack's slide from earlier, but with your community galleries, now we as an organization can share images publicly. We are an organization, Fedora, who has non-commercial, non-proprietary content that we want to share. We don't really want to sign a bunch of contracts and stuff like that. We just want people to be able to use it and to basically reuse our existing license that everybody who's using Fedora uses. So now we have the way that we can do that, and so we're pursuing that. If you go to the next slide. So for me, as I approach different cloud providers, because we work with a lot of ones, I like to kind of have a mental model of how the different cloud providers work and map them to one another, because that allows me more sanity over time. So specifically for images here, for AWS, you kind of create an image market public and you just share that image reference with everybody. I think they have some more constructs that they've come out with recently, but I'm not as familiar with them. With GCP, the way we do it for Fedora Core OS was we have an image family that we created, and then we create images, and then we add them to the image family as we do releases for Fedora Core OS. With Azure, they have a very similar setup to GCP except there's this outer layer thing called a community gallery. So first you create a community gallery, then you create an image definition similar to an image family, and then you create images and add them as image versions to the image definition. So at least for what we have with Fedora Core OS for GCP and what we will have for Azure, you'll be able to follow essentially a reference that gets updated over time as we do new releases every two weeks. So as long as you're following that reference, you'll always be up to date when you're launching new instances. Next slide. So what's next for us with Fedora Core OS? So we're hoping to have this finalized for Fedora 37. There's a few things we still need to do. One is we need to automate essentially the addition of images to image galleries similar to how we're adding images to image families in GCP. We need to update our Fedora Core OS going SDK, which is called Mantle, to essentially make the correct API calls as part of our release process. The other piece we wanted to kind of wait on and deliver at the same time is 64-bit ARM images are currently in preview in Azure, and we support AR64 with Fedora Core OS. So we wanted to essentially release them at the same time. That's still in tech preview, but I think it's exiting soon, so hopefully by Fedora 37, it'll all come together. Next slide. So, okay, demo. So earlier we got the suggestion for Garfunkel as the name for that we should use. So I'm going to try to share my screen. And so I actually scripted this process so that it could kind of run in the background as we were given the talk. So if I scroll up here, I can see I ran the date command first, and then I ran my script with Garfunkel as an argument. So it started just afternoon in my local time zone here, which is when this talk started, and we essentially have a gallery name of Garfunkel, et cetera, et cetera. And then basically I ran a few commands using the Azure CLI that created the community gallery, enabled public sharing, created an image definition, and then finally, if I go all the way down here, an image version within that image definition. So the image that I used in this image version had previously been created by me. It takes a little bit more time to upload things and create that image, but those are two steps that I also could have automated in this process with a local file upload and then as your image create command or something like that, I forget exactly the syntax. But I'm going to toss it back to Jack. He has a separate account from me. I don't have access to Jack's account, and he's going to see if now he can use the image that I just created. All right, so this is the Azure portal. So we're going to go and create a resource, and we're going to tell it that we want to create a virtual machine. So resources get deployed into a resource group, so I'm just going to type Garfunkel there, and we're going to call it Test. I believe you shared that in East US. Dusty, correct? Yes. It happens to be where I'm located. Yes, so one thing that you need to keep in mind is that images need to be replicated into the regions you want them to be available, so if you don't share it out in a certain region, it won't be there. For AWS, I think we replicate everywhere, so we'll probably try to do the same. So this is where you see all the images here, and then we have here on the left community images, which is where the community galleries live, and so I'm going to search for Garfunkel... Yeah. Garfunkel Gen2. So that is the image that I'm going to create on a small VM so I don't get in trouble, and we're going to generate a new key. Let's just let this run real quick. And by the way, now would be a good time for any QA. If anyone has any questions and stuff, you can post it there in the QA tab on Hoppin. Yep. I see one at least at the bottom. Is there a link to the Fedora Community Gallery image? Searching on Google does not seem to yield anything, so we don't have it done just yet. We basically are in the process of kind of getting to the point where we automate everything. I could publish one today, but it wouldn't be automated, and there's not a lot of value in that, in my opinion. So yeah, we're going to work on automating it, and also I believe the AR-64 armament since stuff is coming soon, so we'll just deliver it all at the same time. Yeah, we were actually testing that earlier today, so I mean it should theoretically work fine, but the ARM GA is coming really, really soon, once that's ready, we should have that available as well. So why is Jack wearing an Ubuntu jacket? It's not an Ubuntu jacket. Why would you think there are no logos? I don't discriminate, man. There is like a shadow of a logo on your right hand side. So it used to be like a Kevin Durant basketball thing. I'm not going to lie. I thought the same thing when I saw it up close. You should have told me that before, Dusty. I'm actually only wearing this because it's boiling here, and the air conditioning is on, and so if I'm not wearing this, I'd probably be shivering over in the corner. So by the way, this is taking a little bit of time. That's probably because this is the first time anyone is deploying this particular image, so it's probably getting copied to like several places in some Azure data centers somewhere, in Virginia most likely. We have one other question. There are buttons for easily starting Fedora in AWS. Could we add similar shortcuts for Azure? I see. Yeah. So the link that Pavel gave was for Fedora cloud base, and so yeah, there was a link earlier in the presentation that was a tagger issue for against the cloud sig for creating an Azure image. So that would need to happen first, and then I imagine we would want to update the website to be equivalent, like AWS image, click here, GCP image, click here, Azure, click here, et cetera. So anyone that we're updating in the cloud directly, we'd like people to use that otherwise we're doing that work for nothing. Yeah, and that is the plan to have it on there. So once those images are done, which should be pretty soon, we will update the site. Let me see if there are any other questions. I actually am interested in clicking through in the presentation for that infrastructure map that you were talking about. Oh, I believe it's just infrastructuremap.microsoft.com. I can go back and check and post it. But okay, yes, it's created. So we should have an IP in a second. So I've already, this is an SSH client, and yes, I'm using Windows. Don't blame me. I work for Microsoft. That's the host. That's username. I already put in the key, and so if all goes well, and I don't know where it went, we should be able to SSH into our very own Fedora Core OS instance launched on Microsoft Azure. What's the uptime on it? That's actually, up two minutes. That's the good time. So I guess let's get back into the run through the rest of the deck. Did we skip a slide? No, we didn't. Okay, so cool. So how can you get involved? That's what this is all about. Please do get involved. Fedora Cloudsig, which we butchered the spelling on. Fedora Cloud on Libera. They're bi-weekly meetings every other Thursday, I think, Wednesday. I've lost track of time at this point. But yeah, the calendar's up on the site. And for Fedora Core OS working group, issues, forums, docs, the mailing list, of course, Fedora Core OS on Libera and on Matrix. And the weekly meetings are on Wednesday there. So please, we do need your efforts. Yeah, David Duffy's saying Thursday. So yes, Thursday, sorry. Yes, please do get involved. We can use everyone's help. There's definitely a lot to do. And we're glad to be able to bring Fedora to the world's computer, Microsoft Azure. And we hope that if you are interested in helping out and or deploying Fedora on Azure, please message me. I will try to see if I can get you some credits to try that out. It's really, this day has been a long time in the making. So thank you to everyone involved. Thanks. Thanks, everybody.