Home
Contribute Contact Us Browse all meetings
Home Contribute Contact Us Browse all meetings
Antrea / Community / 19 Dec 2022
Antrea / Community / 19 Dec 2022
Previous Meeting Next Meeting
⏯
Add meeting Rate page Subscribe
youtube image
►
From YouTube: Antrea Community Meeting 12/19/2022

Description

Antrea Community Meeting, December 19th 2022

A

And good morning, good afternoon, good evening, thanks for joining this instance of the Andrea community meeting today is Tuesday December the 20th, uh and we don't have any Topic in the agenda for today, as uh Chan mentioned at the beginning of the meeting at the the discussion of user request, features will be held in the next community meeting, as several team members are unfortunately unable to join today, and also uh the discussion of ofnet announcements will likely be done in the next community meeting.

A

So for today we don't have much discuss unless everyone wants to bring up a topic as anything that they want to bring up for today.

A

So I'll wait a minute, maybe to wait for your topics and, if not we'll, go ahead, just with a check on the status of the entry at 1.10 release, which is supposed to be released. This season, this Friday.

A

Yes,.

B

Okay, I could give a quick update about the release process of.

A

Yeah, yes, yeah! Please please go ahead! Sean, okay,.

B

uh As you can see from the screen currently, there are uh eight uh PRS are left for this release and I. Think two of them are about Futures. One is about one important feature uh uh we want to include in this release. It's the seven level policy, so the number is four four one zero, and this is the most important patch to support the future, as in in it includes all the their path.

B

Change required for this future and I will review this PR a few lines and I think we are close to merge it and I think that the the end and then endpoint test and the new test has good enough coverage.

B

The only thing missing right now is the document about that feature which I am working on and and I will push a PR for that as soon as possible, and um the uh you may know that there are two other features uh with major features we want to include in this release. One is about uh stretch in your policy I, think of the code. Changes have been merged, except one documentation PR, which is the third one in the list.

B

Think about the status of this PR, uh because I I haven't seen. uh We reviewed this um Lola.

C

Or yeah I think this is a danger already left. Look to me a few.

C

It's not a big change. I think it should be okay to there's no risk of from my side.

B

Okay, great yeah and I'm addressing the final need right now.

B

Okay and uh the other major future in this release is about support bundle, collection, uh I, think we have uh merge all of the code changes and uh the same as stretch in our policy. The only left item needs the document for the future.

B

uh I see that PR has got an approval so as we should be able to merge it soon and uh the the last one I think it's about a continuity support, don't have support for Android engine Android engine on Windows I have reviewed and uploaded yesterday, but we are waiting for the CI to pass before we can merge it. So this there's no risky for this one and for the others, I believe they are all about a neon test coverage.

B

Improvement yeah and you may know that we we made a I, think a big Improvement on your test coverage in this release, as well as the last one.

B

So we have much quite a number of PRS thanks for the effort of of the teams and uh if anyone gets time, please spending more time on reviewing this new test. So we can get a higher average number at the end of the release. Yeah I think that's the one of the current status for my site. Thank you.

A

Perfect thanks thanks John thanks. A lot seems that uh looking good with two major new features, three major new features for this release and I, don't know if anyone has anything anything else to add concerning the ad entry as a 1.10 release.

A

Please, if you have anything else, any note about PRS that you are working on or reviewing, please go ahead now and then we'll move to the tier status.

A

Let's wait five more seconds.

A

And let's move to Tia so forth: here we don't have a lot of uh poor requests open, so our Milestone 0.4 Milestone is mostly done. We have two PR's open. One, unfortunately, will likely be a no. It's been reviewed, one is under review. We don't know honestly if this one about support bundle, collection will be merged in this release.

A

It seems that we have two approvals, so it seems that we speed up the review process, thankfully, in the last few days, and therefore we should be able to include this PR for support bundle collection using the tier manager.

A

There is a slightly difference with the ti that we have to collect, support bundles for multiple third-party components, including you know, clickhouse and Spark, and then the other PR that we have open is a service dependency graph feature for grafana, where basically, we display how much traffic goes from one part to the other or from pods to services, and this is in the last stages of review. We just had a little bit of a Slowdown for an issue with the testing and we should be able to merge it today or tomorrow.

A

So both pending PRS should be done by Thursday and we will do the our 0.4 release together with entry on Friday and that's pretty much everything that I have also for key, updated updates and which means that probably will reduce the topics for today's meeting. So I will say now: let's go into open discussion. If you have anything that you would like to bring up, please go ahead.

A

Waiting a few more seconds, giving you more chances to think about the topic topics that you like to discuss.

A

And uh it seems that's all for today, so you know that this is our last meeting for the year 2022. So I would like to use this chance to wish everyone happy ending for this uh this year and a great start to the new year and our next community meeting will be on. uh We likely need to be moved by one day.

A

The reason is that it's currently scheduled for generated the third Central European, Time and China time, but this Falls also on January the second U.S time and in U.S generally the second of this year will be a public holiday.

A

Therefore we might uh the meeting will likely be moved by 24 hours in order to allow to enable attendees from the United States to join uh in their working day, at least okay, so I think that's all for today, so again, uh happy ending for this New Year and I wish you a great start for the new year. So have a good one and talk to you next year.

B

Have a good one! Thank you. Bye cheers.