KubeVirt Community, 21 Jun 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: KubeVirt Community Meeting 2023-06-21

Description

Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/

A

Alrighty we're three minutes past the hour. um Let's start welcome everybody to the Qbert community meeting. It is the 21st of.

B

A

um We're rocking up to the halfway part of.

B

A

Everyone's had a lovely week, um let's get started. Do we have anyone today that is new or has maybe not new, but hasn't introduced themselves before um now's our chance to say, hey how's it going so please pipe up or use the raise hand, function of Zoom.

A

I'll, take that as a no, in which case uh we'll move on to the schedule. Check-In and I've got this here. um Stu.

C

Sure thing so I believe you were out last week. The feature freeze did happen. uh Our original plan was to have it on June 6th, uh due to uh interactions with a bug and kubernetes. We, as a group, chose to postpone that by a week and the feature freeze did happen on the 13th. We did cut um the branch at that time and so I think we're on track. If looking ahead at the schedule, we've got released, Ken at zero one and ga uh in the next uh weeks.

C

I, don't foresee any problems in meeting those as far as I know, there's not any uh major bugs that would disrupt that schedule. At this time,.

A

Perfect, thank you very much um and yeah I I'll soon need to be getting onto top of the um actually. So would we now be able to start going through release notes if, once we've had a feature, freeze, we've now got time to be able to just kind of sort through and um categorize and amend any of them. That.

C

I think that's a fair thing, because you're absolutely right at this point uh feature freeze literally means those words we're not adding new features. At this point.

A

So anything that.

C

Is counted as a feature we should be able to go back to and double check on, release notes all.

A

Righty, thank you well, in that case, I'll probably send something out to the mailing list. Saying hey. If everyone wants to help out with here, uh I probably need some help.

A

um Only thing that we have in the gym at this point is uh for me just saying that uh yeah we had difficult this bus uh over the weekend and it was really great to see so many people from the super Community.

A

Whereas I am aware it's the largest grouping of Cuba people in the one spot since the pandemic, um it was really nice to meet a whole bunch of new people and to see some people I've met in briefly the past kubecons, um and especially thanks to everyone who helped out and talked to people who are at the booth, um there's nothing else on the agenda or the open floor so we'll move on.

A

But um if anything does bring to mind, please throw it into one of those two places or wherever you want um I look through the pull requests. I could not see anything. What I saw was a lot of do not merge and little green lgtm and approves so. Thank you very much for everyone for staying on top of that.

A

There was one thing on the mailing list, which it does have some comments, but I did want to um yep highlight here just in case anyone had missed it. um Cubit Network, binding plugin, there's a link to the thread and in that is a Google doc. So please have a look at that um and if it's here and he wants to say anything about it,.

A

Good, in which case uh there was.

A

um I saw a lot of bugs opened by Lee uh wood, but they were all to do with instant type, so I presume he's raising them as a matter of process and he does actually need them called out because he and resembly Felix are will be working on them. um Felix. You look like you're here to say, but that's director, we don't need to you, don't need to pull out any of those bugs.

A

I think you're unmuted, but I can't hear you.

A

All right, um I'm going to presume that I understood correctly, in which case we've already got one bug um this one up here.

A

Run strategies manual and B and stop being a snapshot always fail the timeout.

A

So this sounds like it's an issue on the storage side, in which case is there anyone from I'm actually not entirely sure where this was because the Run strategy I think is compute, but it's talking about storage issue. So if anyone from either of those two sigs is able to weigh in on this.

B

If you wanna, uh this is M henriks. If you want to tag me, you can I'll try.

A

To look later perfect, thank you very much nice to hear your voice again.

A

That brings us to it the end of what we have here. No one's added anything in the agenda all the European floor. um Does anyone have anything that they would like to add.

B

I can edit something uh right now: I'm working on implementing uh Seaside driver based on camera, storage, demon and I'm fighting with the read write, many support, I'll just put a link here to mail lists.

B

All right here, I think that someone might be interesting to read about implementation, and if someone would have found ideas, please feel free to contact me.

A

Wonderful, a little bit context perfect. Thank you.

A

Does anyone else have anything else, since we're we've got plenty of time before us.

A

A

Oh actually, there was something I wanted to call that um I noticed that it's merged, but I did want to thank Daniel Hiller for sending out a PR about the um the flake finder and the proud documentation.

A

um I know that was uh something that came up at the project meeting in kubecon and what was it April, um and so thank you very much for jumping on that and everyone who approved and got it merged so without any further further Ado. Unless anyone has anything that they would like to end uh I'd like to add, we will end this meeting.

A

um So I'll do a little countdown three two one.

A

Thank you very much for being here. uh Thank you very much for weighing in on this stuff and hope. You have a lovely week and we'll see you next week.

B

A

Everybody bye-bye.