Antrea Community, 4 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Antrea Community Meeting 01/04/2021

Description

Antrea Community Meeting, January 4th 2021

A

To start, as you heard from the very friendly zoomboys, we have now started the recording.

A

So thanks for thanks for attending uh for today, we don't have a well-defined agenda, meaning that there is a no pre-scheduled topic to discuss for today. So it's going to be a more open, open agenda, meaning that feel free to propose the topic you like to discuss- and uh you know, will build the agenda during the meeting.

A

So if you have any topic, you would like to bring up. Please come forward.

A

Perhaps shall we provide a brief update on the release status.

B

uh Which, which really is the last.

A

One or the next one I mean if you want, if you want to ever, do a postmortem of the uh last release. That would be. That would be great. Otherwise I was more. I was more thinking discussing the status of the release we are working on at the moment.

B

uh So uh sure, but I have to wait, I have to take a look. uh I don't even know what what the planned release date is out of of the top of my hand. So all right, so I have it as february 10th uh 2021 for the 0.13 release.

B

um I'm not aware of any like a major feature that we have scheduled for that release, but maybe I'm missing something. I know that we have been working on the notepad local feature, which is going to facilitate integration with external load balancers.

B

I know that we're planning to support like endpoint slices in the entry proxy implementation and I believe, we're planning to actually one major change for 0 13- is that we're planning to support running entry and a cumulative cluster without using q proxy at all, so entry proxy will be able to implement a node port.

B

I believe those are the major things for 0.13.

A

Perfect yep yeah cool, so um thanks for the update and after we had the meeting, I think was uh on december, the eighth, uh the meeting where the team from intel presented their uh their plan around the cnf uh integration. Has there been any follow-up since then.

B

I don't think so: they're still supposed to come in and do a demo of what they've implemented, but I guess with the break and everything things have been postponed a bit. I'm hoping we can do that at the at the next community meeting, but I don't see them in the in the zoom meeting right now. Yeah.

A

Indeed, okay, so we'll keep waiting uh for the next community meeting perfect and- and I I don't- really have many updates on my side. um You know that the entry operator for kubernetes that uh roy has been mostly working on has been published. uh I would say, I think, a few days before before the christmas break and uh it is in a different repository. It's not part of the main entry repository and uh that thing, even if it's open source. It's, however, not part of uh it's part of a different uh github.org.

A

It's part of the vmware github org, not the vmware dash uh hyphen tons of uh github org. um At the moment, uh let's say that that thing is uh mostly tailored for uh deploying entry and openshift, but uh there is a plan that probably ray will present at the next community meeting for running the operator with any kubernetes distribution.

A

So it is something that anyway, you can easily try out the way. I prepared a very good documentation for uh getting up and running and we should be ready, I believe, very soon, also with the automation for pushing the container image for the operator to the anterior docker up and also for releasing for releasing the operator image itself anyway. So that's about the operator and anything else to bring up for today, any bug you would like to discuss any anything. That's annoying you documentation, improvements.

C

So talk about there that was certainly I can either feel other potential items might be.

A

C

Yeah, probably we uh we are still working on basically abstract and young, and the other folks are still working on some land policy enhancements. I think we'll have a group of new features to be in their distinction level. Sitting. Sorry, like the group, crd or namespace level label.

C

And maybe we can have service group stats project, probably not all these features, but we will delegate some new features for that policy and then uh I think we plan to do ipv6 choose flow too, um and on windows supported there'll, be some enhancements too, for them to support continuity.

C

I think that was important for us to support some kubernetes distributions, like tkg.

C

And you, you know, uh google guys uh working together with us to be writing on tr for windows. 4G. uh We made some progress before the holidays. um I I believe google gets able to run and trade our gku with windows already, um but they want to support low-income mode. um I think we had a the pr for for that.

C

So maybe we can um punish that appear on the officially support loading camera for windows and gk. You can leverage that um yeah some other items remember.

A

Thanks a lot for the for the updates engine.

A

Is there any comment on this?

A

Any uh any follow-up.

A

Perfect so well, uh this was.

C

A problem sorry.

A

Yeah we can. Finally, we can finally figure out what exactly we are supposed to to support with ibm.

A

That's right, and uh I don't think that uh ipam enhancements are a reasonable target for 013 unless it turns out that what we need to do is simply have an equivalent support of. uh I mean doing what the host local plugin does, but without running the the node ibm controller.

A

If that's just just that that we need to do it's, it's going to be relatively easy and we can implement it in 013, but the feeling is that we might need a slightly more complex solution and therefore I don't believe that this is going to be something that we can target with 013 but, as you said, we'll soon figure out exactly what we need to do.

B

Perfect so and.

A

B

Genjen uh regarding windows supports, since you mentioned the container d support on windows. uh I believe the two other things that came up were no encap mode on windows and hyper, and support for windows without the hyper-v dependency, all those things like also in the 0.13 timeline or all those items going to take more time. I guess the ipv1 is going to take a long time, but I think you guys are the prototype for no encap mode on on windows.

C

Yeah, I think the reasons here. Maybe you can provide more details. I think you have a workaround pr. I call the walk around, but maybe it can be the final searching too for the long command and because you can get more information on container detail.

C

D

So for the new income support. Currently we have work around because there are some issues in obs. So for the final for the final solution, we need the fix from the upstream of s to fix uh one ct triangle issue.

D

So before that uh we will just, uh we must need the workaround for the uh for the knowing cam mode.

C

um But even with the workaround I at least I don't see any big issues right. Do you agree with me.

D

Yes, I think there there won't be a some big issue.

C

So we do pretty well can be one temporary solution uh that can be merged all right.

D

I think we need some more tests for it, yeah, because there are some change for the flow and the interface config, we'll have to have a double.

C

D

Yeah, that's the uh no income support.

C

And for container direction, we also target for 0.6 seating right.

D

uh Yeah I'm trying for for this release, but in this release we will only also support the workaround for it, because um currently we have no proper way to work with the continuity.

D

So we we must need a workaround.

D

B

And for uh hyper-v uh running on windows without hyper-v, is there any like plan to do that.

C

C

E

For the upstream hyper-v disablement, I think we have to depend on the upstream over s to do some change to to support the disabled, hybrid disablement. We have already talked with windows, os developer, jin jun, who is in welfare, and he has already agreed to to currently. I have not the accurate timeline to to really have this uh change in upstream overs, but hopefully it will be ready by middle this year.

D

D

C

uh I think we talk about another one. First results: we talk about the possibility to uh release 0.1 watching. Do you want the top voice.

C

I'm not sure everyone know about it, so.

C

You think we we still did multiplying on that one. I thought we have a. We have a plan to uh uh release the adult. One from this is 0.6. 13 can be 0.1 right.

E

I think maybe it's 13 or 14.. I think yeah.

B

I think we should something we didn't discuss for 0.13, but especially if we want to do 0.1 soon is, I think we should uh introduce the new um api.

B

uh The api names that we've discussed previously uh transitioned from vmware 10 zoo to entry.io um personally I'd rather do that for 0 13 and then make 0 14 be 1.0. I think, having like a release of buffer since this is a big change, would be nice.

C

Then, if we believe we want to do 0.1 in the rate of 14, I mean the release after 0.6 13. According to you, we we must do the api change in 0.6.

B

Yeah yeah, that's something we didn't bring up earlier, but yeah. I think we should uh try to do the api change as soon as possible.

C

uh Chen, do you see any issue for that? Oh you think we can do that in 0013.

F

Note yet I think just maybe we need to replicate some code, especially in some in the registry module the logistic package. um But I don't think there is a hard problem for the change.

E

C

uh Actually, I don't know we have discussed this year.one plan before or not in committee meeting. If not probably, we should first ask anyone. I have any concerns or other.

A

A

Okay, is there any more question on this.

F

A

Okay and uh anderland, the I noticed your message on the chat is this something that uh we should uh discuss in the community meeting or is just.

B

uh No, no! It's just like. uh We just discussed two items right: the api renaming uh to use entry, dot io as a domain name and our intent to release entry or 1.0 early this year. I think we should open github issues for that, so we we can continue the discussion online and and on slack as well.

A

Yes makes sense, uh then that makes sense. It's a good proposal.

A

Okay, so um I think that uh we discussed quite a good number of topics for today. Is there anything else that uh might make sense to bring up for today? um I will wait 20 seconds for any other topic to come.

A

Up all right, since we have a few minutes to spare, I will uh I will bring up a community meeting topic. As you know, from the slack channel we have been discussing the idea of discussing the idea of having an antria office hours meeting to be held in the pacific time afternoon.

A

Bi-Weekly just like the andrea community meeting, the idea will probably to have it in each other week. We will have either the community meeting or the office hours meeting. In my opinion, this meeting should not be a.

A

Let's say second version of the andrea community meeting, meaning that the entria office hours meeting should have a deliberately open agenda allowing community allowing community members.

A

Even new new, buys new new starters newcomers to ask questions about andrea, both as developers and as users and and it should also be a forum for discussing open issues for discussing uh uh if you prefer uh implementation choices.

A

You know a more let's say a more interactive meeting, rather than the community meeting, where the pattern is normally that we have a predefined agenda of presentations and there will be a presenter and then there will be questions about the presentation.

A

So um in my understanding there is not an official process in the let's say in the kubernetes ecosystem to start an office hours meeting. So all we have to do is uh set up. The zoom call add uh you know I'll, add something about it to our readme in the github repo, and then that should be it. So uh is there any feedback on this idea? Do you think it's a good idea? Do you think we should do it differently or do you like? Do you just like the idea of having an additional meeting?

A

I know I know, probably you. You already have too many meetings in your daily agenda, but uh you know the andrea community meeting is set at a time which is uh not really comfortable for for many people, especially those based in the u.s and and probably we need the forum apart from slack for discussing day-to-day project matters.

A

What is your feeling on this idea?.

B

uh Well, I like the idea, but if it's, uh the idea is to have something that's different from a community meeting and uh really like something like office hours. So does that just mean that we need to make sure that those office hours are going to be staffed every time by like two or three people which are who are familiar with entry, and then we're ready to take questions about uh the project, how to use it? How to uh contribute to it and.

B

New ideas before breaking them to the community meeting, that's.

A

Right, that's right! So that's that's the the typical style of these office hours meeting where, typically, you have, as you said, two or three subject, subject matter experts on the call that are ready to address all the sort of questions that might come. You know either it could be architectural. It could be questions about the implementation. It could be questions about documentation, so it would be better to have as much as many as many experts as possible on the on the call.

A

That's why that's why it's it's a different style from the community meeting and uh if we don't think this is the right approach, uh we will and I have been proposing an office hour, comm an office hours meeting, because that's typically what most projects in the kubernetes ecosystem have. They have a community meeting and an office hours meeting.

A

But if we don't believe this is the right format, then we will reconsider whether adding a second community meeting in let's say a u.s friendly time zone and therefore the community meeting will move from bi-weekly to weekly or weather. Reconsider the idea of having an alternating bi-weekly meeting so, for instance, will be one one instance. It could be at four a.m.

A

Gmt and the other instance could be at.

A

9 00 pm gmt day, which could be, should be 1 p.m, pacific time. So this is the choice that we really need to make, whether we want to have a different format or whether we want to have the same format the different time. I'm aware, probably you don't have the answer already right now or if you have feedback, please share it. If you don't have feedback right now, it's completely understandable and please share it on.

A

G

I definitely like the idea of the uh office hours um and I think that either that or having a weekly community meeting uh with a u.s friendly time zone and uh this time zone uh working that the moving uh every meeting having it be a uh rotating time is just more confusing. I think, and people may miss the meeting um with a rotating uh time, though, so I think that either two community meetings or the um preferably the office hours, I think, would work the best.

A

From my site, uh thanks for the feedback, scott, it's indeed the the choice that we made when we moved the community meeting to the current timing, uh we held the survey and uh and the the option of of using this single time slot was preferred over the option of having a rotating time meeting. Personally, I agree with you. If we we go forward to a rotating uh rotatings uh to a rotating meeting, I will be probably the first to miss some meetings. uh It's it's kind of common anyway.

A

So uh please, uh let us know um your feed your feedback on slack as uh we would like to get started, uh probably with this office hour meeting starting next week, if possible or in in two weeks time at most, so that we can uh also you know, address this since we've been discussing about this for about a month now, all right. So that's all I had to say about the community meeting. Is there any other topic that we like to discuss?

A

Otherwise we can close this meeting earlier for this instance and give everyone back 30 minutes of the days all the evenings for our friends in palo, alto and california,.

A

All right, it seems that, uh therefore, this is all that's all for today, I'm going to stop the recording now and I would like to wish everyone again, a great start, a great 2021 and uh thanks again for joining this meeting, and I will talk to you. We will talk again in two weeks time, thanks and everyone.