Red Hat OpenShift OKD Working Group, 5 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: OKD Working Group 2020 05 05 Full Meeting Recording

Description

OKD Working Group 2020 05 05 Full Meeting Recording

A

Hello, everybody welcome to the okd working group and we're gonna just get started here. If you haven't yet. Please add your name into the working group meeting notes. The link is in the chat and we'll get rockin and rollin here today we have a couple of things. Thank you all for participating in red hat summit. Last week. The summit content is online at the at the registration page I'll, throw that in chat to Christian and Vadim, give an awesome state of OK d4 talk.

A

We had a little bit of traffic in the okay de chat room. Wasn't it is wonderful as I thought, but I think they tried to reproduce the the booth experience and have one chat worm pretty much for every single booth. So it's not as effective as I think in person, but it was still a very interesting learning curve for everybody else. I don't know. Buddy I saw you in the chat room a few times.

A

Neal was in the chat room at one point, but you know the people have thoughts about how the Red Hat summit went.

B

It was pretty good. Actually, I I was pleasantly surprised at how well that worked out. Diane I I.

A

Thought it was pretty amazing from an open shift Commons perspective. At one point we had 3600 and some folks logged into one of the things one of the presentations that we did in the morning. I haven't got all the details on the total counts of everything, but it was pretty amazing to get that many eyeballs on some of the stuff. That's going on here, I.

B

Heard there was I heard there was a t-1000 total attendees or the Red Hat virtual summit, which was just mind-bogglingly huge yeah.

A

It was I think um the first day there were 8,000 people logged in for Monday, which was day zero for and which is when we host the open ship Commons of those. You know, I think a lot of them were people just looking to see make sure they were set up for the following days, but then, on the next day it was insane I. Think at one point, I saw 70,000. It may have gotten up to 80,000 people registered, so it was pretty crazy. I'm, just I still think for me what you know.

A

The content was amazing and getting to see all the talks that I don't normally get to see. It was pretty great, but I wasn't so thrilled with with the chat experience the interactivity, mostly because it was just hard to find people so I'm. Looking for any feedback on that.

B

Her dad was that was my low point as well like it was difficult to get in touch with people be reminded that people were notified, trying to talk to me things like that it that one was the low point, but, like other than that, I was impressed at how well this this went. I.

A

Was I mean if there was a lot of upfront work on getting stuff there, but I overall I was pretty impressed remains to be seen. I've got two more Commons gatherings coming up that are going to be virtual stand-alones, though using the same platform, so any feedback people have loved to hear that I'm still getting access to the dashboard behind the scenes to see what actually happened. So I'll keep you all posted when that happens. So today, I know Vadim and Christian are both here.

A

If you guys could give us a quick update on okd and where we're at right now.

C

Yeah sure so, hi everybody so I think we're getting really close to merging the MCO. Our branches four point: six development will open next Monday and I'll by then I'll have all the PRS needed lined up and they'll, be, hopefully they'll get reviewed quickly and merged very soon. After the opening of the branch of you master, the unfreezing of the master branch next week, it's quite a there's.

C

The dual support: PR I'm working on right now, first spec to inspect three dual support in MCO and that's quite large. So it may take a few days to get that reviewed, but yeah, eventually, it'll it'll be merged into MCO, and then we can sort of rid us rid ourselves of the F course branch pork in MCO for the Installer.

C

We may need to carry the D fork a little bit longer, but we've sort of come to the conclusion that we can actually release okay, DG a with the Installer still being worked, because it's yeah it's easier to just maintain one fork. Instead of two and yeah there shouldn't be too many large breaking changes in the install in that time frame anyway.

C

So that's good! It's still.

D

C

B

So does that, so that means that everything is gonna get merged in all they have cause branches get merged in, except for the Installer. Is that what you're saying yeah.

C

So we only have two F cross branches: it's only MCO and installer sort of forked or F course, and the MCO will we'll be able to support both operating systems from the master branch and the Installer eventually we'll be merged as well, but because OCP is still defaulting to spec.

C

Damn, that's actually not quite clear when that will switch over will happen. So until then we may have to carry the Installer fork, but we may even get it merged sooner and sort of have dual support of the Installer in one in one master branch and introduce a build flag or something. So we have to two different bill: no binary builds or all the installer but yeah for in for now, OCP still defaults to spec two, even though we will have dual support in the MCO already.

A

Also heard that even I didn't hear him actually I saw it in the chat we have a beta 5 coming out shortly. Is that I.

C

Think what him can can answer that I think it's in the works. Yes, buddy yeah.

E

Sure I tagged the latest nightly as better five and it's running up great tests now she's that too we have failed, I'm. Looking into the details of that and if it passes it would officially become the better five.

E

If the upgrade fails, we will scrap it and promote a nightly with the fix, so it's almost ready, but not officially, yet ready awesome. Another another fun thing we're working on is the ability to install a single node cluster.

E

Unlike CRC, it would be a proper full-blown OGD cluster, the operators enabled, but it would use a bootstrap node, of course, but you would be able to put all the parts into one single machine. Of course you won't be able to upgrade it, but other than that. It's it's a as good as many other Oh kitty cluster. That pull request is not yet merged, but I think it should should be, should be merged eventually,.

C

Cool I, so for there's a few other issues we've had in the past and they're also getting close to to getting resolved, and that is the missing OpenStack support. We have right now, so we're still waiting for the new ignition at 2.3 release. I think it is for spec 3.1 and that PR, to sort of finish that release is open right now and that's going to get merged this week. So the next Fedora core OS base image will we'll have that support and we will sort of re-enable OpenShift OpenStack the support with that as well.

C

But let's I think if a thing how many people have been waiting for so that should be in beta 6, which I will I don't know if we want to make another beta release next week or wait 2 weeks and get get all of that in with beta 6 but yeah very soon, as well.

E

um I, don't expect a lot of changes in for that for right now, since it has just been out of the door, so we can delay this particular visa to 2 weeks there. We won't miss much I, guess.

C

Yeah I agree, and should we should we do the next beta release after the beta 5 that's coming out today? Should we base that on top of 4.5, then already.

E

That's a good question: I guess! So, if we could, there would be great but I'm concerned about the stability.

C

Yeah yeah I agree. We should maybe wait for the 4.5 freeze, which is planned for the end of this month, and then the next beta after that made maybe beta 6 or beta 7 at that point, would then be based on 4.5, with the dual support MCO, where we sort of don't have the D forked MCO in there anymore.

F

Yeah I think that might be a better plan because for dot the 4.4 right now is is so stable as it is, and I say that with quotes around it, but it is pretty darn stable, I'd hate for us to take it backwards. If we introduced something funky with some instability in 4 or 5, well,.

E

14 4 bills are not going away; we would still have them as a night lease. It's just a matter of choosing which nightly to promote that's.

F

True anybody that was aware and wanted to could stay on the on the for for Knightley's I.

B

Mean honestly I'm not sure what we're trying to argue. What are we arguing against like? Are we arguing against doing more integration work into the four-four line to get get okd out, or are we saying we should move the goalposts again? Two, four five? No.

C

So I think the.

E

Road to DA should it be like better 59 and then eventually GA or we should have less often betters and then GA just choosing the frequency I don't have any any particular well.

C

E

C

Before we do GA, we should have at least one, if not two or three beta releases off of that release branch. Essentially, though, right now, the plan is to get all the all the dual support stuff into the new master, which will be four point six and from there we will do a back part into sort of F course 0.5, which will be released.

C

Four point: five, plus the dual support things and that will sort of be the last parked branch we will have to maintain on the MCO side from there on out any release, branches that are branched off 4.6 will be the same for OCP and okd, but we will go GA, probably with the F course, 4.5 branch, which will include a few bits from 0.6 master, but it'll, be much more easy to maintain just those just those few audio support bits in 4.5 and then well after after 4.6 it'll it'll just be one branch, yeah.

F

Okay, so so our GA would be on four or five with still a little bit of the F cause branch left in it. But then our our next alpha release for for looking to the next GA would be off of the now unified master. Exactly exactly so. Why are we making this distinction.

C

It's because we we don't have the capacity to back port everything, no.

B

C

B

No, that's not what I mean I'm. Sorry, I didn't quite say that right. Why are we like what I'm actually asking I guess is? Why do we care about the release tree trains? Why don't we just as soon as it's merged, we switch everything forward and then just be done with it.

C

So it's it's a stability thing. We may have things breaking other things, other components in master, because the other component might not be ready. I mean it'll, build in CI. But there's always you know it's not it's not a released thing. So there's no! No stability! Promise. We can give that's.

G

C

We we sort of want to build okd off of the release branches as well. Okay, that's.

B

Fine I, just I, just want to understand why we're talking about release branches stuff, because we haven't actually formally made a release of okay D. Still that that's.

D

B

Ireland, that's why I'm asking because all of this conversation of stable branches and whatnot is confusing to me, because we still don't have an okay T for release, though, from from my perspective, the way I see this is if we can get to having if we can get to having MCO merged, what stops us from just shipping MCO from the future, with everything else being a stable tree. That's.

C

Essentially, what the plan is, so we plan to release okay D at this point together with OCP, 4.5, okay, and so once OCP 4.5 goes GA. We, we can be sure, that's stable. So on top of that, we will just back part the very few things that are already in master at this point into F course. 4.5 and that'll be the GA relief, so yeah I'm expecting to release okay D together with OCP 4.5.

C

A

Is the timing yeah.

B

I was gonna: ask you.

A

Could dust all the other questions? I get the timing one so.

C

I know that the development freeze or 4.5 is at the end of this month at the end of May and it'll, be I, don't know a little bit after that, so probably in June or July I would expect.

B

So we're looking at two more months of not having an okay T release.

H

B

Ga right well, I mean well so here's the other thing like we still don't have something for okay d, io to say: hey you want to do this now go go! Do it, we still don't I, don't care if it's GA or beta or whatever, but we still have OC cluster up, because we don't have a CRC that words for okay D. We still list okay, t3 11 in the container, and we still list mini shift like at this point: I, don't care whether it's beta or GA.

B

We need to do something and- and that's what.

E

B

E

And we have a link on the down-low Paige says: try the Oconee for better and that I.

C

Do agree with Neal here, though, that having the OSI cluster up and all the old stuff on the front page is not a good look, and also we that's another thing. We don't have the CRC yet so that's what buddy mentioned earlier, the PR that allows or single host single node clusters and that will essentially unblock Oh CRC builds of okay D as well. Is that.

B

P are actually merged, or is it open somewhere, like I I, don't know which PR we're talking about all right.

C

That's open, that's on the MCO and we may yeah that'll, probably just get merged in the F cross branch, because that's sort of the four point: four branch Vadim. If you have a link to that otherwise I'll paste it in a minute.

A

E

Work for me so I think I'll creating you cards on the community. Okay,.

B

So so, for me, I'm just gonna, say two months from now having GA, okay, fine, whatever my more immediate concern is I want a beta that people can use in every mechanism that we support for OCP and that and we already we have all we don't have the CRC and I'm honestly I, don't care if it's a little janky we could I would like to like what can we do to help make this happen? Is what I want to ask? Yes, O'neil.

F

Via deems got a single node cluster deployment that you can run in AWS I've got a repeatable one. You can do either on bare metal or in libvirt. Okay,.

D

F

Finished writing up the the instructions. Okay, you do it, but even with the current beta, you can get a full full single node cluster up and running. There's a couple of things: they're a little wonky. You have to do during the install process, but but you can get one up and running and and it's barfing a few things until we get until that PR that vadim was referring to goes in, but it's it's perfectly functional and you can you can try everything out won't around on your you know eight or a twelve gigabit.

F

You know gigabyte ThinkPad. You need a fair amount of ram, but but it's doable. Okay.

A

So churro that you guys have you're hitting a lot of nails on the head today for me, because one of my asks was going to be help me help everybody else, get the okay di outside looking to some semblance of usability.

A

So it's not all 3.11 focused and I've put the link to the okay, the site here, and if anyone wants to work with me on on cleaning it up, I'm thrilled to have you help, though, but I wanted to get Charo to talk a little bit more about the work that he's doing with a single node cluster and working towards getting a CRC up, because that, for me, is the thing: that's gonna change this page.

A

If we have a code ready container, then we can replace this mini shift or just shift this mini shift container stuff over to the downloads page and emphasize you know the CRC on the and the single node cluster stuff. Here, that's my game plan. So I've been you know a bit overtaken by summit, but also been waiting for something to give people to replace the mini shift.

F

Yeah and I think I think if we can get some clean instructions written up for bare metal, libvirt AWS once you're there, it's a more repeatable pattern and I actually I when I first started this trying to get it ready. What was it last weekend.

D

F

I actually got the full single node cluster up in using the github code, ready, slash, SNC I had to hack the the script up, a little bit that that Praveen uses, but but that's how I got the first one up and running what failed at that point was actually building the the CRC bundles and, judging from the from the errors that I didn't dig into too far, I think that's because I was running on CentOS 7 6 and it was expecting some things that are available on rel, 8 I.

F

Think praveen was probably doing his builds on on a rel, 8 machine, or maybe a upstream Fedora, but the single no cluster. It came up and running. So what I did from there is realized that what it was doing was was not that far different from how I was building my bare metal upî clusters, sitting on libvirt using bbm C, so I hacked up the tutorial I had put together and used it to build. A single node cluster then realized that I wasn't thinking it all.

F

The way through and I didn't need a load balancer with the bootstrap I could actually use DNS temporarily, so so I've redone it again just using DNS a records to poor-man's load. You know balance between bootstrap and master, while they're coming up once the master is up and bootstrap is complete. You just remove those DNS records and destroy the bootstrap node if you're using libvirt.

F

Once you get it to that point, you can shut it down edit, your you know, verse, edit, your your host and add the RAM to that master that you were using for the bootstrap. So if you're, if you're doing this on a little box with 32 gig of ram, you can easily create a single node cluster that has 24 gig of ram and that's actually pretty usable.

A

So, though, the next steps- I guess, is my question here, so if you're gonna do some documentation of that, so that it's a really usable process for other people. Yes, in.

A

But the bundling of the CRC did a building of the CRC bundles failed. That's not the same thing as having an excuse me if I'm wrong a CRC, no.

F

It's not what it effectively would do is it would allow somebody to to create for themselves what you actually get with CRC, because really what CRC is and I may be speaking a little out of turn because I've only tinkered on the edges with it, but it's basically a pre-built virtual machine that is then bundled up so that you can pull it down and run the script that configures your local environment. So if your local environment is hyper-v or libvirt or I forget at the moment the one that's native to the Mac it it configures.

F

This bundle to run that virtual machine on that. So you get a locally running instance for anybody that wants to do some significant work with it. I'm not sure running it on a laptop, even a nicely. Beefy laptop is even anything something someone's going to want to do so running it on a little sidecar server is probably a better option, and that was the approach. I was taking.

B

Yeah, this problem is that this stuff, eventually has to, in some form or fashion work on people's laptops, which is I, think one of the things people of the MCO and all these other things to change for CRC have been working towards trying to shrink the the Minimum Viable openshift, so that people can do it on there. Yeah.

F

And that's some surgical work. We could. We could really start doing after the fact. Well, I think one of the at least personally what I've observed one of the one of the challenges that we have is that we have to go back into the open ship code itself and undo things that were written into it for a 3-node environment right and I. Think the polar requests that we've got open around the Etsy decorum is a good example right, the Etsy decorum guard because it was built for a data center.

F

It says if I don't have three I'm, not I'm, not healthy right, and that was coded into it. So we have to go back and make these things configurable to run in a non data center ready environment I mean.

B

The flip side of it is, you could do clever things like have three of them running in containers inside of there and have them quorum on one node, it's stupid and you shouldn't do it in production. But those are the kinds of things that that I did for making openshift 3x work in the single machine when I wanted it to pretend to be production. Ii yep.

F

Absolutely that's some of the stuff I think we'll have to work through to get it.

C

There and get the.

F

Size down prometheus is another example right. It runs to pods with like seven containers in each pod and that's probably overkill for a single node.

F

Its weight will be other things like that that well, if you want to test out monitoring okay, you know we're gonna have to surgically pare down the size of some of these operators and what they, what they expect to be there to call themselves healthy right.

A

So in my quest it gets better stuff or getting people started on this page, the okay d io site. Do we put in try out the beta the latest okay D, for beta release as a single node cluster, and we get started over here.

A

Is that even the right link, yeah.

F

That's the old, OSI I think we'd need, but we'd need to put together some Doc's around building a single node cluster yeah.

D

F

I would I'd love for someone to take what I've put together and polish it up. I'll make it a solid as as I can try and get some work done on that this. This next weekend, yeah.

A

So, at the very least, this this line here should hope to try the beta release- page yeah, okay. So that's that's wrong! I'm! Just trying to get what's wrong here, because this this stuff here that I'm pointing to the OC cluster up and get started is all 3:11 stuff brain there's.

F

A

Here so this at this one, oh.

A

Yeah the page is whacked. Let's just put it that way.

D

A

It's post summit: we can work, we can fix this, but I was hoping that we would fix this with either this single node cluster install process or CRC and then announced the reuse routing of this page or something and I and I am happy to take. You take a look here. I think everybody can see this if you have, if you see broken links, this is where this page lives. Let's throw that in the chat, if you haven't done so already.

F

One of the things I like about the single node cluster versus CRC two is that you could share the single node cluster without setting up a funky, H, a proxy routing or something yeah.

A

F

Think CRC, you can only get to it from whatever machine you're running it on yeah.

B

Because it hooks into DNS masks on your computer right right, you.

G

Can use a chain products to set up CRC nodes remotely and like on remote machines. We've done that on servers in our infrastructure.

C

G

It wants to open that CRC testing domain name though so it becomes really confusing right.

F

What I'm, using if you have access to DNS you can create records and then.

F

G

What I do at home, but yeah, that's not good! You can't do that inside of a large organization.

A

All right so I I'm trying to parse where we're at right now so getting the documentation for the single node cluster somewhere in the repo that it can be linked to whether it's on that first page.

G

Just want to, if possible, I just want to revisit something. Neil said a few minutes ago about you know deploying OpenShift to like containerized to a fully containerized installation earth. This is something that I'm like really curious about, and I've been looking at from the perspective of the cluster API work that we do, because there is a way to make cluster API look at a provider. That's like a container based provider and I'm curious. If there is like there's a lot of work.

G

That needs to be done here, but I'm actually curious to see if there's a way that we could make the openshift installer use this container based provider to get us to an end point of having like a single machine architecture with containers as the backing for what would normally be nodes in a kind of a cloud situation or.

B

Even thinking about this, more simply like things like the bootstrap node stuff, don't necessarily the bootstrap processes could be simplified in that manner as well.

F

Container yeah I mean it doesn't mean much or.

E

For OpenShift, um theoretically, that's possibility is that you kind of create a container from an ignition file. Oh.

B

You're asking for a challenge you can totally, you can totally create one the problem. The issue is, you need to omit it and that would be like you'd either have to use system the end spawn or somehow trick pod man to do enough to make system. Give you a boot sequence.

E

If you do boot sequence, that's definitely not a container.

B

Running a kernel it just does enough to boot up the in it and start the start ignition and then that's it, and then you throw it away at the end. I.

E

Mean if it works, I'm super fine with that.

B

Anything about whether it works or not right now, I'm just saying that that is a way to do it. If we wanted to do something.

A

All right any resolution there I.

C

G

C

Single node cluster is the topic that will follow us along a little bit more because there's a few different proposals for openshift upstream going on right now how to solve that, and we don't really know how that's going to end up and, of course, we'll have to follow whatever upstream decides eventually. So, even if we, whatever we do right now, it may change in the future, but I think it's yeah I think it's definitely good to to get that working on on the 4.4 code already.

A

If we could add it into the getting started section, is that the appropriate place to put it? You know how to run as a signal node in the getting starting page, yeah.

H

F

Would make sense.

A

Yeah, when I'm popping around too many places but yeah, if we could, even if you could just put basically Chara what you know so far in there as a section that would be helpful, and that would be something that I could link to from the okay to do page.

A

C

A

Would be everybody.

H

A

Help correct your grammar and fix things. Oh they'll.

F

Be plenty of that.

F

I've also created some helper scripts and files like for your DNS, and things like that. Do you want me to just link to where I'm keeping that in my github or do we want to do a pull request and create a section in okay, D for single node cluster I? Would.

A

Like it to be in okay B, if we could, but I would settle for it in your home directory for now,.

F

Their first just to get us started and then and then, if folks help with simplifications or fixing issues, then we can pull it over and just make it part of the okay D. That.

A

Would be a great thing in my humble opinion, so let's see if we can get that going in the next couple of weeks and and don't worry too much chair about your grammar or things and then, if we can have a list of any variations on themes that we have to do to make it work. I found other other platforms. It.

F

Was a former teacher- and she is very much onto my grammar- so Wendy will take a look at anything. She'll fix it all right when.

A

Everybody else will test it so.

F

I did actually have one more comment on one thing: I forgot to mention: building the single node cluster, using the the CRC things that Praveen has done. The the F caused instance that it spins up for both the bootstrap and the master node by default only have a gig of space allocated for sis root, which is grossly undersized too, to fit everything that goes in a single node cluster, so I actually had to modify the terraform config in the and then build a custom.

F

Installer I had modified the code for the terraform in the installer to create 34 or a 32 gigabyte disk, and then it successfully ran doing it. The the way that I'm doing it with the UPI install stuff I didn't have to do that, because I'm building the libvirt and telling it you know how big a disk it has I don't know. If anybody here has any insight into how, with the ipi method that CRC is using, it knows how big to make its history I.

E

Don't think it's possible, but we could ask the door across people to extend the size of their images. It would still um yeah. Basically I would rather solve this on the Fedora crow s, image, side, yeah.

F

Okay, okay I'll get with you off offline in on where we need where we would need to open an issue. It was an easy change, but but again it's hard coding the size, so I wouldn't want to necessarily plant that in the Installer.

A

All right, so we've beaten that dead horse I can see that next time we need to ask the phonic Kaiser to come to talk about GPUs on ok, d4, we're still Azure is still. It sounds like the outlier. We still don't have a fedora core OS image. Officially up there is that correct statement. I.

B

Think nobody has carrots so far, I've heard nobody has carried it forward to make it so that we could get an official image up there so like this is a thing that, as far as I know, is a red hat side problem.

A

Figure out, it's.

B

Not like we aren't making the images we just can't do anything with them.

A

Yeah once we uploading ourselves all right um and the beta is available, but there's still a blocker on opens time just going through the list here, and so that's still be still is truth and we haven't done anything around documenting how and okay d4 release is built yet, and that was one of the things that we wanted to do so, but I think getting.

F

Start on that I, don't I haven't done anything with it, since he created that he some initial things around hacking on okd. For that.

A

Was bidding uh-huh.

F

A

I will follow up so.

C

I think it's essentially that's, maybe two different things, so the main okay, D releases and all the CI builds are defined in the open ship to release repository.

C

This is where all these CI jobs in the open shift organization live and that's also where okay D builds come from and they then get promoted to beta releases at the moment from there, and then we could also have documentation about rebuilding everything on your own somehow, but maybe we should already link to the release repository because you can, you can just you know, check out the files there and all the jobs dig through that. It's not the yeah. It's not super easy to see what we're what lives where, but you can.

C

You know, definitely check it out and dig in there already. So the release repository is really where everything lives. I,.

A

Think it's um rather than asking people individually to dig in we're just as some sort of short documentation about what all the pieces and parts are, but personally I'd rather get this single node stuff. Then, in the next coming weeks, yeah.

F

So officially that was my priority too, because I wanted to have one running so I hadn't looked at that it's the contributing dot MD, that's in okd repo! That's the document. The Dean started working on.

A

If we could just keep in the loop over the next two weeks and make sure we get to a decent single node install and if people can take a look at okay di, oh and give me feedback on, you know, even if you wanna just print a picture of the page and put X's and O's or whatever it is and send it to me, I'll try and reshape the page as we go along and fix things up, and you can also make full requests against it too.

A

Is there anything else we should be covering I know, I was gonna, mention that kou Connie? You went virtual on us, so we're not gonna host an okay, D working group meeting physically at that place at that time, but we may do something in the background. I'll try and figure out what possibilities there are when I meet with the DNC F folks later this week, maybe they'll make a chatroom available there for us to blather on about wonderful, ok, D stuff, but I'm.

A

Not sure yes did any of us get ok, D related talks or Fedora core OS related talks accepted to coupon.

A

For this virtual one that we should be promoting you think of it, send me a link and I will turn that engine on.

A

Otherwise there.

E

Are several talks which are related to Oh kitty, but not directly? For instance, C groups to be to talk from joosep is what we're planning to have. You know lp3. Once we were base to kubernetes 119 um I'll, find a few more slightly related to Oh kitty as well.

A

An ok D guide to food con I have a new con. You virtual.

A

I think I've got a talk scheduled on Friday to talk about the coop convert rule stuff with the new stack. So if there's things that we want to promote or something I can sneak it in that conversation as well get the word out, is there anything else that we should be talking about today we got 10 more minutes, left I'm, not going to show anybody. My kovat haircut that I let an 18 year old kid cut, but I'm not going to be in video for a few days.

D

This weekend, slippers.

F

I could go back to my long-haired nineties days, I.

B

Already lived along here tonight these days so.

C

I'm good I'm slowly getting there. Actually barber shops reopened this week in Germany here, but I haven't gotten around to to going there when.

B

We need your long haired self to show up at least once I went.

A

Back to the eighties.

C

It's neatly hidden under under a rat hats right now, so.

A

No I got I, got a red hat to con that I've been wearing the past couple of days.

A

So the next meeting we have Christian. What do you have in the calendar.

C

So trippy in two weeks, just ah the next meeting should be in two weeks from now. I think we shifted the cadence because of at least that was my understanding because of the virtual summit by one week.

B

I thought that was just that was done as a one-time thing, because we okay.

C

So I'm fine with either we could do the next meeting next week or Eddie them. Whatever you say, I.

B

I'd really prefer not screwing up the cadence if we don't have to because because it's it's all it's hard enough getting all this scheduling, don't write it to begin with.

C

Yeah, that's fine! So let's do it next week same time to them, then, two weeks after that, again cool so by next week, just to answer Joseph's question about the procedure that leads to GA I've written up an enhancement proposal that I will put up on the ok, D enhancement in the enhancements repository in OpenShift very shortly, and that will sort of be the document. The living document, where everybody from the engineering and architecture, side and OpenShift will chime in to she sort of nail down the the ga definition of OpenShift.

C

Of course, will will we have our recommendations in there and yeah so that should be up yeah tomorrow. I just want to get some code ready. First, so I can just say you know not a lot of work. It's already done just merged this PR and we're there yeah, but I will post a link in the to that in the OpenShift dev channel and all the slack channels were usually communicating.

A

And I'll ask you about it again next week. So if you can throw me the link or add it in here on top oh yeah,.

C

A

Charlie, it's any way possible by next Tuesday. You have that right up added into the readme MD. That would be great, and then we could look at that and just focus on getting a single node installation in okay di Oh updated over the next week would be my priority list from everybody. So if you can make a pull request against the okay di Oh website, if you see anything wrong or have suggestions, just throw it in the issues or or okay di, oh I'll try and adjust and address them. It.

F

Looks like a cold and rainy weekend in Roanoke this weekend, so yeah.

F

D

C

Thank you all for joining in and I will see you, and we will see you in one week all.

G

C

Have a great rest of your day, guys yeah, you too, y'all too bye, bye,.

C