KubeEdge Community, 26 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: KubeEdge Community Meeting 20200826 (Pacific Time)

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

Hey everyone today is uh peaking time august 26th, uh uh u.s time august 25th. This is the cooper edge community meeting.

A

Today we are going to discuss.

A

Let me share the screen.

A

Today I have one item here: is discuss the 1.5 release, so uh please I saw a lot of people drawing the meeting.

A

Please enter your name here to show your account show your support to our community, because I see about certain people in the meeting right now. Please enter here here. Is the google doc link? Please add your name here.

A

Here is our meeting.

A

A

Here is our 1.5 tracking, so 1.5 release is scheduled on november november 15th, so the code freeze, we schedule normally is october 31st. So that's two weeks before we release the new release so be prepared. uh Now, let's go over the list.

A

The first one is the inherit from 1.4 is yeah about the cooper control, exec.

A

Is jail or darshan.

A

Here no they're- not here- let's leave this here because they are doing the implementing. Let's wait for it, wait for them. The next one is a support, k, okay yeah. That means get data from edge core db for troubleshooting.

A

A

A

So the status uh we just say we have a pr already submitted, however, uh is still having some issues. So it's not ready for merge, so it's almost done, but we need some minor.

A

Modification this pr is, this is ready.

A

Pr some improvement submit.

A

So we need to address some code review issues for this pr.

A

Also, I suggest you create an issue, so we can uh easily uh track that then uh this dbm package for coupe edge- I don't think dashawn- is here today.

A

So let's go over to the next one. uh This is for the edge node cross, submat communication, uh this one. I will take it so for this one. We have some proposals.

A

uh To integrate in y with cobatch and together this one, we have some pocs, but we are doing uh the proposal. So I'm to say uh this one: we are going to have a community review for our implementation.

A

The next one is a release progress. I don't think that shout here, I'm going to skip for the next meeting.

A

um Support this watch yeah. This one is also uh from 1.4 release, so anyone can give update on this one.

B

B

A

This is another underdesign is uh implementing uh ta.

A

So it's a second half of september we're going to have.

B

A

So we going to have some something ready for the second half of september.

A

Okay, this one is empty website upgrade. I let me see so kevin is not here today, so I'm leave that for for the future supported pipeline on the edge.

A

So that's from the sig iot uh shive. Do you notice the detail of this.

A

So we put owner for whom kevin or anybody.

C

A

The cabin or you take it, I don't know what the detail it is.

A

Leave that for here right, let's see that john here uh do you want to give some update on on a few issues? First, one support yex easy on the edge.

A

uh Hello, hello, yeah.

C

uh Now this is finished. uh It's on the review.

A

So it's still under review or any uh code review we need to address or is for, is waiting for more reviews.

C

The whole function is completed, but some details, someone had different different answers: okay, we'll leave it here.

A

So dbm package: do you have any update on this.

C

A

C

Want to post it after after sound release of the opposition, finished.

D

A

So hey, I see uh logang, so you are you. I are you proposing this data pipeline or somebody else in the sig iot propose this.

D

Pipeline on the edge.

E

D

A

D

I will ask other.

A

People for clarification, this.

D

A

Motorbike mapper go implementation chenway, so.

A

No, I don't see him here.

F

um This is proposal, I'm also interested, and so I I uh and I have a contact way uh offline. So maybe we can work together to do this.

A

Okay, should I put in a proposing or.

F

Proposing, okay or.

A

Design under design.

F

On the design, I think.

A

Okay, so um you don't.

F

Worry can't wait: uh she's a china unicorn.

A

Okay, okay, I think okay, anyway, okay, thank you uh edge, mesh, optimization.

A

Do you want to give some.

C

Update on this- uh let's say suppose in the past- and uh nobody knows what they review this: okay, so something I have completed, and the post process.

A

D

A

This one, I suggest uh I will contact kevin, so we going to have a formal review or some design changes, because um we were thinking. We need a better.

D

A

D

A

Optimization is not enough. We probably need some a better design to rewrite this or a a big change. Another simple optimization, so this one we can I'm thinking we just turned to a discussion or reviewing.

A

Options and uh support is not the clockwork as deployment.

A

I think that the rest are all from you.

C

Yeah, the is something about the key admin. Now we use the key administrator called as.

C

Systemd, we still need the needle ins install cloud core as a deployment. Then we can use the key bias relative disorders to control it.

A

Okay, so uh I see you have a waiting for review. You already have pr yeah, okay, I'm we're going to take a look at that one.

C

My second one is it's something like command exists. Result output cleared me, use a lot of linux command, but the the error, the error log is very poor, cannot help users to find the true error.

A

Okay, so let's schedule someone to review these two error check the last.

C

One is uh it's a big change since, uh in the past survey, do not check any arrow, so we will we we need to this because the science we want to check.

B

A

Okay, yeah this one, I'm going to review that. Thank you.

A

I think that so far is all about the 1.5 release. Anybody. uh So here you can get this one from our github readme. If you want and anything new you can edit this spreadsheet and we are going to discuss in the next meeting.

A

So, what's the other one is.

A

In my mind is a cai, so yesterday we got some a request from baidu uh china, unicorn and uh all talking about do we want to add some seek or do we want to form a sick ai to discuss, particularly for the ai on kuber edge, so uh this one we need uh if we're going to have a four more seek. We need some more governance, governance, dock and we are going to have some ghost setting.

A

You're going to have a discussion, so if anyone interest I'm going to create a new slack channel on this one and.

A

So if you are interested, unless let's discuss in the slack channel, then we can discuss more in the community meeting about this one and that's all I have today. So anyone have more topics you want to discuss or to show in this meeting.

C

A

Do you have anything here or I'm well, you're.

B

A

Do you have anything you want to.

B

A

We can wait for.

A

B

B

B

A

So my suggestion is, basically you want the partition. Clock call clock core right, so you have multiple clock core deploy, not not only the yeah because, as edge core is still a one per edge, one edge core per edge. So your purpose is partition cloud core. Basically, you have a multiple cloud course for each region or each cluster.

A

uh You have one cloud core that would understand correctly. Yes, so basically uh congress proposal is say: instead of a current h, a setup, we not only have one active one passive core. We have multiple cloud cores, so each cloud core we partici partition it to control a set of edge cores.

A

But my question is for each cloud core: do you use d1 h8 setup or you only have one active cloud core? Do you need a one passive two.

G

Standby still still actually so position girl still.

D

G

Have active passive right.

B

A

You have passive setup, so the problem is, uh are you you are going to still have one etcd right because.

B

A

Must patient cloud core on on the.

D

A

A

So, based on my experience.

A

I don't know, probably you will find.

G

The bottleneck is on.

A

The kubernetes.

D

Cluster, it depends how.

A

A

It depends how many uh edge node or worker nodes you are controlling, so the bottleneck, probably on the etcd side. So uh currently we have some improvement kubernetes, so we find out.

A

If you want to reach large scale, so you will see, etcd is the bottleneck, then the api server and the controller manager. So it may not on the cloud core because similar to controller manager, you can each controller, you can have multiple copies. I think we we do. Can we do.

B

I have multiple cloud course.

A

But so that's why I suggest. The next item is the performance test. We need to find out the bottleneck. I.

D

A

E

A

Doubt the uh the bottleneck we are, the first appear on the etcd. If you only have one etcd, you file, millions or even thousands of thousands of.

A

If you have millions or thousands of edge nodes, so I suggest we do some performance tests or some simulation to see, I highly doubt the etc.

A

Dcd, probably will be, will be the bottleneck ahead of a cloud core.

D

A

So my suggestion is, you can go for your design. However, at the same time, I.

D

H

We do some performance tests.

A

Probably you will find that different bottleneck. You know is that.

B

The bucket of water bucket.

A

You need to find the lowest the lowest one who leaked the water so.

E

D

E

A

Clock for multiple clockwork will.

B

B

A

I think you can go for the design, then we can bring up next week or the weeks after we can discuss.

B

A

Okay, you know that's a proposal directory. You.

D

D

A

Have proposed you can submit one cr, so we can take a look at this. Oh.

D

B

A

Okay, so the next one is from you or yes,.

B

You wanna discuss more.

A

While we're going to the next item.

B

uh I think we can go next set.

D

B

The next one is from.

A

B

B

B

A

Okay, so let me rephrase suggestions uh during the discussion on slack channel or wechat group for people. The developer feedback is the key enemy. Reset is not.

D

A

D

We are supposed to do.

A

So there's still some left over in the uh after you do the key enemy reset so.

B

When you do a restart key.

A

Enemy in it, you will man some unknown.

B

Or unpredictable unpredictable.

A

Predictable errors so to solve this problem going to propose this, we.

B

A

Do a really full reset, so he proposed this.

D

Is what he collect the data from.

A

The cloud and site so people please go here. Let me add an item here.

B

D

Okay, I'm sorry, I missed.

A

E

A

Me put a proposal, or you have this one right.

A

I think your pr is just pr, you don't have a code right. I suggest you create an.

D

Issue, so we can check that too. What do you think? Yes.

A

D

A

D

You've created issues, people can give.

E

A

So here is uh number.

E

D

E

We need a better key.

A

Enemy reset, so if you have any suggestions, please go to this pr, this pr. In sorry,.

D

A

Are in this pr to give you a feedback to see if he missed something.

B

Or you have more.

I

Suggestions to have a better key.

A

Enemy reset, so please come here.

D

D

A

D

A

Okay, thank you. You have more.

E

A

A

Suggestions so yeah. Thank you, okay, any more items. Anyone want to discuss.

A

uh I see in the chat window of soojin, you asked what's the pr code in the retail group or oh yes, it's the region. uh How? How do I share the qr code here or.

A

How much uh where are you from? Maybe we can find somebody to drag you into the group? I I don't have that new ohio deadline.

J

A

Let me uh see uh who can maybe you can go? uh Are you in the stack channel too or no I'm not saying.

A

Can you help him to get into the.

A

Group, uh could you introduce you a little bit of sujin? Are you from.

I

Okay, I'm from mili.

I

Dynamics, startup company and yeah, like.

J

A

Know so if you know him so we can, he.

I

Will I can, I can send him through soon it says, there's a private talk.

A

Yeah, that's a user group and the c discussion group I think shift- can help you to jump both of them. Okay, thank you.

A

Yeah yeah, welcome to the community. uh Anyone have more.

A

Questions uh shiver, if you, if there's no other issues, I'm going to end this early.

A

Okay, sure, okay, uh thank you. Everyone uh we discussed today's item uh next week will be uh europe front. Frankly, uh friendly time is uh in the afternoon, and also I I post the link up here. If you want, you can add your name here uh yeah. This is in the google doc yeah please. If you can, please share the name here so to show we have a lot of people join the meeting yeah. Thank you yeah. uh If you have anything you can either uh post in the slack channel, we are going to help.

A

You guys uh add it to this google doc we gonna discuss.

A

uh I think that's for today. Thank you. Everyone, I'm going to support, uh stop the recording unless somebody uh hear the last call.

A

If, if you have anything, uh there's the last chance you added to today's meeting, if not I'm going to end this meeting a little bit early.

A

Yeah. Thank you. Thank you. Everyone see you next week.

A

B