 I think they're getting close there, and there we go. All right, I'm going to share my screen and try and drive this meeting as I want to using this lovely agenda. And I'm just going to don't really have any upcoming events. And from my perspective, unless anyone on the call is hosting OKD related talks or events, if you are, let me know. You know, the next thing I have up on my radar is a November 17th at KubeCon. I'm going to be hosting an OpenShift Commons gathering there and probably trying to put together a panel of or a talk at some of some ilk around OKD and insert that into the agenda. So stay tuned for that. If anyone's doing meetups or anything like that, that's using OKD or talking about OKD under the hood in some aspect. Just let me know and I'll use my social channels to get the word out about that. I think we have, let me just double check. You're coming back here. Who's on the call right now? We have Christian, who I will unmute and unmute all Christian and Charles. So I'm wondering, I know Vadim couldn't come. Maybe Christian, if you could give us a little update on any issues or engineering bits that have gone over in the past two weeks have come up. I haven't synced with Vadim. And from my side, there's not a lot of news this time around. Okay. All right. This may be a short meeting, which is always a good thing. We're still waiting for a place to host the binaries for code ready containers. Yeah. So that did not happen. I take it in the background. Not yet. Okay. So. And it's not something that we could put on quay.io. I'm just wondering. Is it. They're pretty huge is what I recall. They are. Yeah, well, and they're not container images. They're, you know, they're downloadable executables. I'm just trying to think where else we could put it. And I think the conversation you and I had was where are the current ones being hosted? And I think the answer was it was behind a subscriber firewall. Is that correct? It is. And, and Praveen said that they have to go through a red hat group. To post new releases. We were hoping we could find a place and we may still be able to find a place in the Dora. Whatever the door is hosting their things. I'll. I'll find that email thread and raise it. Back. It may be that. Dusty or somebody from that team just hasn't had time to look at it yet. Neal, do you have any thoughts on this? Neal is who's my, one of our other fedora folks here on the call. Well, I would if I knew what we were talking about, because I just came in as Charles just finished saying a sentence. You want to explain the size problem. Yes. We've got working builds now for code ready containers for okay D. We need a place to put them that we can link to from okay D. So people can download them and right. They're about two gigabytes each because the holy cow. Yeah. The actual if you download the, you know, the supported CRC the binary actually includes the embedded virtual machine. Right. That is okay D or OCP in the case of right, right. Okay. So we just we need a place where we can put these that, you know, as we build new releases, we can put the new images up there. So there should be a place. So I think it should be possible. I would suggest filing a ticket with the fedora infrastructure team on the fedora infrastructure pager group. I'll just drop a link into that into the chat. And then it's a question of figuring out how we want that to distribute like there's we. So like I think putting it somewhere is the easy part figuring out how people can how it will be replicated so that it is accessible for everyone is the harder part. Technically, we can of course make it part of the mirror network. The problem is that there's nothing in the container ecosystem that supports a mirror network. You don't really have a good way of dealing with that. Well, these aren't containers. Yes, but the binary itself. Oh, well, the binary is already fully self contained. So it could just be mirrored as a blob. Yeah. No, no, no. Yeah. So we can probably put it on the mirror network along with the rest of the F cost stuff. It's a question of just working at the logistics of how we upload and how we sync and things like that. Most of that is tied into Bode and like obviously this is work that way. This will probably wind up being something similar to what we do with fedora media writer, which is I don't remember exactly how that's distributed. But there's some precedent for it. File a ticket there and let and we can work on figuring out how to get that rolled out. I don't expect there to be a problem other than like figuring out the logistics of how this is going to work. Yeah. Because we already do this for a couple of other things. Nothing quite so enormous as a two gigabyte, you know, go binary, but you know, but we've done it before. It's like a giant image. Yeah. That's all nice. That's wonderful. Thank you. Thank you for that. And you know, I figured there'd be somebody on this call who could figure this out for us. So thanks. And the sooner we can make that happen, the better. Now my machine has frozen up. So I'm going to stop sharing my screen for a second and go back. There you should see it again. All right. And I know that Charo and I have made no progress on cookbook and recipes. So we still, we still have that the all of the all of the videos that we did on the 17th are now up on the YouTube channel. And that's the content that we're going to use to do this for or at least kick it off. Yay. There was there was also a person who had an Ali Baba one. And they, there's been a couple of questions. I've seen them fly through on the Kubernetes slack on open ship Devon. Oh, they were interested in the Ali Baba one. It was I think it was the person that we who was going to do the Ali Baba one is now just getting to it. And I don't know that person is on this call. So they are speak up and let me know. Did we get any further with the Fedora containers folks? I know you were going to talk to his name is escaping me. Blamant. Blamant Christians. Did we figure out anything to do with them jointly? I haven't. I haven't talked to them in the past two weeks. Okay. Is when is do they have a sig meeting scheduled? I don't know if they do yet, but if they do, I don't know what it is. Again, that's I think this is more of we got to talk to Clemont and figure it out. Because because I this thing is literally just starting up. They probably don't have everything quite firmed up yet. So how about if I just, if somebody gives me Clemont's email. Yeah, I can do that. I will just invite him to the next one of our meetings. That works. And I think that'll be easier than trying to track him down and do something joint make it joint with us or something of that. Yep. Okay. So if you hand that off or even just forward him that email suggesting Neil, that would be great. Yeah, I'll just I'll drop the. I'll just drop the email address into here. There we go. I did in fact spell it correctly. All right. And Christian, I'll CC you and Neil both on that so everybody knows. Sure. All right. I don't know if anybody ever saw the the press release that went out on Sunday, but the world shifted and up for arm and Nvidia just bought arm. So, yeah, I don't even know what to say about that other than the world shifted. That's going to be an interesting new world, but I don't think this is the IOT stuff. If there's anyone on who has an update of the conversations going on from Fedora IOT and the store for Coro S folks. I don't think they have been talking yet so there wouldn't be anything to update. Yeah. So I expect I expect that if we're talking if we're talking if we're talking about what Nvidia said in their press release then we're going to start seeing people caring about open shift in arm based data centers rather than in little crappy devices out in the middle of nowhere. Yeah. So, I know we also have interest from IBM to build on the power architecture. They'll be joining us sometime. If they, yeah, if they find time for it. They've also been bugging, they've also been bugging some of us kind of randomly about supporting system Z, which is just going to be all kinds of fun because I don't think we have a way of testing that. That is in my home lab. You have a mainframe in your home lab. I'm impressed. So what one problem we have here is that our proud CI only runs on x86 and we need to pull our releases are payloads from that CI. We don't have any. Yeah, we can't build any other architectures right now, and we'll have to figure out a way how to either use a second and third build system for each architecture, or how to extend proud to actually have some worker nodes that run. Both of those seem equally unappealing. Right now we don't support clusters with a mixed infrastructure so as Pram runs on Kubernetes on OpenShift 4.x. Is that an OpenShift restriction or a Kubernetes one because like I've heard mixed opinions on that. It might be an OpenShift one, but I haven't heard of anybody running a mixed Kubernetes cluster either. Well, as OpenShift has a strong support commercially from Rattat, I don't think we'll allow that for the time being. How that would work with upstream Kubernetes, I'm not sure. I mean, I don't see a reason why it wouldn't work, but we'll definitely have to do something about that in the future. I think once there's more interest from the IBM side, we'll definitely use them to set that up for us, and for ARM-based things, we'll just have to see how we can proceed here best. We can probably finangle something from AWS with their Graviton stuff. I mean, I saw Tom Callaway posting numbers about how fast it took to build a full Chromium build on the Graviton systems in like, what is it, a little over an hour, which is 20 times faster than our build system in Fedora can do right now. So, I think I'm being conservative with saying 20 times. Pretty sure it takes like more than a day. So, like, there's a potential thingy there. I don't know what we can go from there. Mike, you have a thing to say? Yeah, I was just going to say for the people who are interested in kind of these hybrid cluster topologies and multi-architecture clusters, there have been some discussions coming out of the cluster API community about, like, how they can improve tooling to allow for more hype. You know, and obviously this started as a discussion about how to have a mixed cloud cluster, you know, like AWS, GCP or something. But people quickly ran to the point of, you know, wondering, you know, can I run mixed architectures across different things. So, I don't have any links like offhand, but if people are curious about that, I'd poke around some of the issues and I think this topic's come up before. Yeah, that'd be awesome. I don't think we have investigated this enough, but yeah, I think we should do that now. On the operator side, maybe just to give another quick status update on that. There's been a new bundle format that was introduced for the operator hub hasn't actually migrated to that. Once the operator hub does that, I will be able to kind of release the same operators that we built for OpenShift, also for the community for OKD. It's a little bit, we kind of have to wait a little bit for that here. Just maybe as a little teaser, we'll be releasing the Windows machine config operator to operate a hub very soon. It's already, the PR is already open, and we definitely want to aim at supporting OKD there as well. I'm currently helping out that team for a little bit. So working on that mostly right now. And yeah, there should be something soon for that. Christian, can you say something about if, do you know if the Windows machine config operator will also support vSphere sometime around 4.6? So I'm not sure if, I think that's a 4.7 target to support that. I'm not entirely sure, but so we will support AWS and Azure first, and then vSphere as a third option, probably not until 4.7. Yeah, it's also in the works. Okay. I think 4.7 is correct on that, Christian. That probably makes some sense considering how much effort it's been just to get Azure and AWS working. I imagine it isn't actually working yet, but yeah. Well, I mean, I was trying to be charitable, Christian. I'm working on that right now. So I just, yeah, probably my fault. I haven't gotten it to work yet, but Mike, I actually have a PR open for the cluster API provider. I'll hit you up with it. And I think I saw your name there, Christian. So yeah, hit me up again though for sure. Yeah, I think I have to change up a few things. I want to test it first, but yeah, I'll definitely ping you. And do you know if the machine config operator can also change the configuration of Windows nodes with machine config CRs? No, that's not something we plan on doing. So we do download the machine config from the machine config server, and then we only take the CNI and Qubelet config from that. So we, yeah, the only configuration you can kind of change there is the CNI plugin configuration and the Qubelet config. We don't support writing arbitrary files or anything like we do on Windows nodes. It's really much, much, yeah, much more limited in that regard. Okay, thank you. That might be something that will be extended, but not right now. Just to follow up on what Christian's saying, there are a couple PRs out right now that adjust the templates. I think this is on Azure that you can use to mint Windows machines from. So I know there is an ability to change the template that a Windows node gets minted from. So like that, it doesn't allow you to actually change the configuration at the MCO level, but there is a way you could do it through the templates. I think that's on Azure. Okay, thank you. So I'm asking a naive question here because I've just been reading about metal three. Does that help us get any further with arm, the bare metal provisioning or not. Maybe maybe is the maybe is the probably the correct answer here because as much as provisioning stuff is good to have. It doesn't matter when we don't have binaries. Right now, like the biggest blockers that we can't actually run anything we provision on arm. Because we don't have okay the binaries we don't have a pipeline for building and testing. We don't have anything actually for arm. I'm pretty sure metal three will get us to the point where like once we have binaries, it'll be fairly straightforward for us to go and say, here's the thing go do the thing. Now you have a you now have a node or a master or whatever. I feel like that will be fine. But we need to have something to put on there first. And I think, as Mike was mentioning earlier, I think we're going to have to get some more focus in the sooner rather than later on this idea of hybrid clusters across architectures because I don't know about you, but I am not all that enthusiastic about running an open OKD master node on on a Raspberry Pi. I feel like that's going to end very badly for all parties involved. So, so I think it's I think that's definitely something that we're going to have to, as part of doing like serious arm bring up or any alternate architecture bring up we're going to have to, we're going to have to think about that and figure out how to get there. So, and one more thing to add there I think with the, especially with arm hardware, if it's not a full on server thing, we probably won't be able to use the machine API for that for bringing up new nodes, because that needs an open management part, which for example Raspberry Pi doesn't have. You can fake all these things. You can take all those things on a Raspberry Pi like you could even make the Raspberry Pi pretend to be a UEFI capable device, like it's gotten to the point now that that basically as long as you're working with a Raspberry Pi or real computer. You're probably fine when it comes to when it comes to arm stuff, but if you're working with anything else you're just toast. So, which is actually quite unfortunate because this is mostly the fault of the arm ecosystem and I don't expect us to get any better, but hey, whatever. Yeah, having that move towards UEFI would be would be nice, having at least that on all the device. Anyways, I think we should focus on getting UPI user provision infrastructure here working first with ARM devices, for example, and then we can get the machine API operator for that later. But yeah, right now the the most important thing is that we don't have any binaries build any containers built for other architectures than x8664. One note, we don't even have mold cubed images for regular OKD yet. Yeah, we do need the ironic images for just standard x86 bare metal. I would just say to you, and this is kind of, I guess, a little bit, you know, from where I'm sitting the metal three stuff, you know, it's going to be landing in 4.6. But I think we'll probably see big growth for it in 4.7. They're doing a lot of work on kind of the internal infrastructure for how those resources are managed. So, you know, back to kind of Diane's point, I really wouldn't expect to see like something like, you know, ARM builds or whatever for metal three until at least after the 4.7 timeframe because I just I know that team's doing a lot of time on kind of infrastructure stuff at the moment. But that's fine. We just have a plan of attack if we're going to even if we're going to look at doing arm we just need to have a plan of how we're going to get there. And I think starting from binaries and images and then going to UPI is a good starting point. Because by this point we have enough UPI based documentation thanks to Charo that it should be relatively straightforward for someone to manually online a Raspberry Pi based note if they wanted to. Okay, thank you for answering all of my questions there. I think the reason I was asking was because the metal three crew are going to do an AMA for me on October 19. The two guys from Ericsson are coming. So, yeah, so if you are, if you want to come with your questions, that's I just thought that it might be a way to open up that conversation and just get it on their radar. And I'll post the link to that in into the into here as well. So I just, I know that it always feel the arm stuff always feels to me like this outlier because we got so much other stuff to do. But it's on the radar. The I just, then I just posted in the chat if you're going to meet with the metal three guys, and you could please remind them to have a look at that issue, which is the list by the mate with all the images were missing and they should. Yeah, yeah, in an optimal case they would they would add them at those images themselves. So the two guys that I that it's pep more and who from red hat but it's two guys from Ericsson I think who are maintainers of this or end users of it. And for Paris Jean, we had Rosa and mile Kimmerlin are these either the guys that you've been chatting with or asking for this that doesn't. It's not this isn't signed to anybody yet so anybody. Anybody even responded to that even. No, I think he tacked some some folks but. Dimitri. Yeah, it reminded them again like four days ago because there hasn't really been any activity on that. We should probably go ahead and open an issue on each of that repository. So they, yeah, they have it on the radar more. If you do that, and I will now. Yeah, I can do that. That would be great and I will, I will see if I remember. And I will also try and get Dimitri to come to the session as well. And here's Dan. Doug. Okay, I know that. That's usually pretty responsive anyways. Okay. Moving back to wherever we were. I remember that we had the idea that the community should be able to contribute more to OKD. After after the GA. And where I, I'm stumbling. Most often over is to build the images from the release payload on my own to try out things like an example is the OVN Kubernetes. Network stuff where I get lots of error messages from, I think, because CI things are still linked in that where I don't have access to. And I think it would be great to get more acceptance from the community if they can build everything on their own. I know that this is a big task, but it's the only chance to get more people involved without. Yeah. Leaving the stuff. Uncompileable behind. And getting frustrated. I think it would be maybe not the biggest task, but it would be worth the effort. In my opinion. What do you think about that? Am I completely wrong? No, that's definitely a goal. I'm interested in what projects you're unable to build yourself specifically, because most of the projects should be buildable with just the the top image in the repository. I think it was the OVN Kubernetes because there was one PR missing. So Windows containers work with OKD 4.5. I was struggling with that since a few weeks. And yeah, Vadim got me a few tips that I gave me a few tips that what I should patch, but it was above my skill level with the internals of OpenShift. And is this specifically for Windows or for any platform? No, it's OVN Kubernetes. There is some thread in Slack I can try to find it. Yeah, you can throw me the link to that. So what I'm just trying to capture this in a. You can follow up on it. Is there any issue logged at all? Or is this more along the lines of our documentation is insufficient? I think it something is weaved still to to Red Hat internal CI system. It's my opinion, but I can't I can't try to find the link and post it in Slack. Where we just cut that with service party. Okay. And it was expecting that this is a common situation, but if you if you are surprised Christians and maybe maybe it's an exception. This is repository. And what I also would love to see is maybe one video that explains how to build something and get it into the release payload. So we can do it step by step on our own. There is some documentation, but it seems like maybe it's a better idea to write down the workflow or make a video that exactly step by step what you have to do. That would be very nice. Yeah, because I'm going, if time permitting I'm going to attempt to build the the RDO images myself to try to get the bare metal scholar working. That'll be a release payload that that's a gap in in my knowledge to. If it's documented somewhere actually Christian, do you know. I'm not really, to be honest, in the OCD repository series some documentation from Vadim. Yeah, but it's a little incomplete. Yeah, so we compose that payload on the CI system and what I what I have done in the past is just replacing some of those images in there which you can use within OC command. But I haven't actually composed my very own payload from the from the start. So I'll have to look we do that in CI somewhere. And I'll, I'll I'd have to check where that is done and how exactly that is done but essentially the payload container only contains a manifest of all the other containers. Yeah, it just contains references to all the containers that I use by that payload. So actually just being able to replace a particular container image would probably get us started. Yeah, that's definitely a thing that is possible just with with the OC command and then our open is it openshift install. Yeah, you can definitely replace images kind of define your, yeah, an override for specific images for that's kind of the development flow. You use when you develop for one specific operator you would just want to test a devil build of a specific operator image you can kind of take the standard payload and then just replace that one image. So the image version, the operator version you want to deploy is then deployed. I'll be bugging you about that on Slack. Yeah, I'll try to dig up some some documentation about that. I'm sure there is some. I just wanted to add another comment here about building the individual components from the Docker files that are in those repos. We just had a, we just had an internal effort where we were trying to get these Docker files kind of all in the using the UBI eight images all building off rel 8 and whatnot and my impression from that is that not all of the projects have the same. I don't know consistency with how they're creating their Docker files. Our team in specific like we tried to make very careful to have Docker file dot rel as the builds that use, you know, rel a subscription base. And then we have a Docker file which is where we're trying to keep all the community based builds in place. So you could use just publicly downloadable images. But the problem I noticed is that not every project has done that and there seems to be an unevenness. So I think, Joseph, what you might have run into, I'm not sure if that's an open shift project you were building from. But it could be some of our Docker files are not up to community standards at this point, in my opinion, I think we probably need to do another round of making sure that our build CI for our product is building off of these rel images, and that we leave the community with a good set of artifacts to build from so that this is just a problem. It's not in every repo but it there's an unevenness to the consistency of these things I just as a warning of throw that out there. Yeah, okay. Yeah, at the same way, we build those images on the CI, the CI can actually replace that from directive within the Docker file. So if you try to build it locally, you might get a different base there and even one that might not be publicly accessible or even out there anywhere. So you may have to adapt that if you run it locally. Yeah, I mean this is something we're aware of internally read out and we're, you know, we're trying to make it better but I don't I don't know how quickly it'll happen. Unfortunately, but I mean, community help is always appreciated in that respect. So I pasted the select thread where I just had a problem with the repository and the error message. Just for your information. All right. All right, is there anything else that we should be covering off today? Any new issues. I'm wondering if anybody wants to take on because the one item that I don't have anyone we didn't do a deployment on GCP. Okay, D4. Anyone has access to those resources or time to do it. That would be lovely. Sally O'Malley. That's a good person. Yes. I know Sally. Well, yes, that's a good hint. Thanks. I will ask her. He's a little busy chairing dev comp us these days. So hopefully, and organizing that. What was the ask there Diane, you just, you want to see a GCP installation or. Yeah, I want to, as I captured for the August on August 17th, all of the other clouds, I would like to for completeness. I'd like to get Google Cloud and OKD deployment videoed for Google Cloud. I mean, I have access to GCP. I could, I could try to do it, but I would have to be asynchronous if I could just record it sometime and send it to you. I could probably do that. Cool. Let me, I'll start a thread with you and Sally and see which of you has the time to do it. And that would be great. So, and then we can edit down. We can fast forward through the cluster up part of it. Because that was on the day out. That was the thing that took the longest. I have a little bit of bad news. The t-shirts are not coming. And I'm trying to get I tried. This is me. I'm just not a t-shirts and stickers kind of gal. Now we're trying to get them into the red hat cool stuff store so that I could ship from there. I apologize for that. It turned out in order to ship them to everybody was going to cost $75 each t-shirt. So, I decided that we might want something better than a t-shirt for 75 bucks like a meal with a drink together sometime soon. Yeah. So, I will put a note out on the mailing list and as soon as we get get it in the cool stuff store, then then the drop shipping becomes less of a problem. And that's, you know, that was that was an interesting exercise in futility, but it and taught me that I should stay out of swag business. So, I know. There really isn't enough open shift swag in the cool stuff store. I've been shocked that I haven't been able to buy polos and hats and. Yeah, I'm not surprised at all. Yeah, work is hat. Most of the most of the community swag disappeared after red hat switched vendors two years ago. Yeah. And it's, it's coming back. I know Josh Burke is working on her and. And that's. Yeah, so you're happy Joseph that you're not the only one not getting the shirt seeing is how you design design the logo I figure I should figure out how to at least print one and get it to you. I just feel like the poor woman who is my assistant for for these sorts of things is, you know, tried mightily so Morgan Becker thumbs up to you for for trying to figure out how to make that happen. But I just just I couldn't couldn't figure out a way around the job shipment and the customs charges. And this is this is the thing when you do fly to an event with a box full of t-shirts. You don't have to pay customs and everybody else has to tuck it in their t-shirt in their suitcases and take them home. You don't have to deal with that. But yeah, anyways, we will get them get something okay D ish into the cool stuff store at red hat and that will enable me to and anyone else to. Ship them easily. So that's what that'll probably take another month of Sundays to get that figured out. So that's what the bad news I have for today other than that most things are going well. And there will be. Oh, I swad wise I was going to thank Dato. I got my fedora nest stuff with your beautiful stickers in it. And yeah, you're welcome. It's a Dato sticker on the back of this laptop and the little robot one was very keen with the kids. So, um, well done. And so that was great. If anyone it was our pleasure. Yeah, I was very embarrassed because here was they managed to get this whole little thing off. But when you start thinking about the cost of FedExing that little bag of stickers to everybody who attended nest. My cheap New Englander mind just said no. So, even when it's not my money. It said no. So anyways, um, we did it. I haven't received mine are you sending it to Germany as well. No, so I'm not the one handling the sending of the stuff. You'll need to, you'll need to bug Marie, I believe we're sending it everywhere we're having troubles. We're having trouble sending it internationally because well, everybody's having trouble shipping internationally. Yeah, it's swag in the virtual era has is is not an easy thing. Good thing I got all the swag that I ever needed over the past few years. So, that's that. So, next meeting hopefully we'll have Clement come and talk to us about what's going on in Fedora containers world. And I will not. I think I'm hearing a little bit of closure for today ending 20 minutes early, unless someone else has another talk. Going going gone. So, um, Charo, hopefully we can connect with the Fedora folks and get that image up there and update the landing page. And then once we get that, then we'll move on to the next task of cookbooks and recipes. Um, and figuring out what to do with all how to get the videos more prominent on the pages. Okay. D dot IO and in the world. And on the pipeline now. That's a good one and anyone who wants to write blog posts or anything else about okay D just let me know and I will endeavor to get them out in the social channels. And if you see anyone doing okay D in the wild. We're always looking for case studies. And as I mentioned, I'm going to do a gathering on November 17th at coupon day zero. And would like to have a panel or a talk around okay D there and get that done. So, if you are going to have in the next, I'd say. Let's see what's today. So the next 30 days, if you've got okay D running in production or POC someplace or know someone. Let me know. And keep putting your dogs in the videos because I am currently dogless and it's painful. All right. Is charo taking care about the dev community together. Yes, charo is like on the hook for everything now too. Joseph is asking. Oh. I said, charo was supposed to be my external person on like co cherry thing and then we hired him. So, yeah. So now we're going to have to like find another externally external body to who's willing to do that. It might be an onboarding process for a red heart red hat hire. So, just be careful. What does the co chair do shows up for meetings and answers questions. And, you know, so that's there, there is no, yeah, there's not really anything super official about the co chair role, but I like having myself as a community person. A couple of engineers from the red hat team and at least one external community representative as a co chair. Too bad old dominion transport was. But that lasted about 15 nanoseconds and then somehow he got himself. I wasn't part of that process. I didn't do it. I might, I might be willing to do that if, you know, charo and I could talk about like what this involves and what I need to what we need to do. And maybe I think, yeah, I'd love to be cloned. Not really these genes. Yeah, anyway, there's some recessive dreams here. What I'm really looking for is an end user that has a production deployment and I think data is coming coming up soon. Yep. We're working on our infrastructure is being revamped is the nice way I could do it. The, the, the more accurate way is it's being set on fire and and and then rebuilt from the ashes to support things like okay deep at scale. So our our production deployment strategy hopefully should be kicking in fairly soon now things have been sluggish because of well world events have not exactly made things easy. You're muted Diane. I'm not muted. I'm just making funny faces at the chat. Well, I actually have to say that I think Joseph Meyer, if you have. 2000 devs using okay D and production in the next few weeks that would be a wonderful use case to talk about. So let's let's let's see how that all rolls out. And and tell me again, how what the name of your company is Joseph. In shorts. You wrote in shorts. Okay, I knew I was going to say it wrong if I said it out loud. So that that might be another possibility to. So, let's talk about it on the email thread and yeah, BC it we love you BC it British Columbia Institute of Technology. Yes. Is that your alma mater. No, I'm UMass Amherst. Englander. So, yeah, but and I don't think that. I know the long story. So that would be good luck Joseph and and maybe what we can do Joseph is showcase you at the gathering in November. For that deployment and what it took, if you're if you're willing and your company is willing to let us do that. That would be great. Because I really want to figure out how to showcase some of the okay D work and Bruce. Yeah, ask your boss Joe Joseph. That would be great. And maybe the other co-chair like you can never have too many co-chairs is in my book is is the fedora liaison. Maybe that we can put Neil in that role on something. I love I love co-chairs. That means I can not show up once in a blue moon. I don't know if we want you to not show up because we like having you here. Yeah. All right. Well, I'm going to let everybody go back to their day jobs and there's a lot of stuff going on. So I'm going to try and. Get climb up to the meeting next time. So thank you guys. Take care and be safe. Hopefully you're not as smoky as it is here today in British Columbia. I know BC it downtown Vancouver. I bet you are getting smoked out too, but we're hoping that everybody in Washington and Oregon and California are safe today. Take care. See y'all. Thank you. Bye. Thanks everybody.