Istio Test and Release Working Group, 6 Nov 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Istio Test/Release Working Group Meeting 11/6/2018

Description

Meeting Notes
https://docs.google.com/document/d/18QgpvBH9N8Io5xU-0piysyOYif65U03m8GabpvHb4IQ/edit

A

So this is the the agenda for today's meeting.

A

So basically, the one point, one release one point: 104 wheedies and a quick update about ham charts. If you have anything else that you want to discuss, feel free to add to this agenda. Otherwise I feel like this will be a short meeting.

A

So the first, the first thing is the 11.1 Willy's pen, which we are it's already. In effect, we have created a work with each one, one branch and all the one one development should happen in the release branch, we're still targeting to cut the cutting they released by sometime this month, hopefully before Thanksgiving. So that gives us around two weeks before we can cut this release. The Coe is to stabilize release as soon as possible, and we still have a bunch of issues.

A

If you don't get it, though, we still have a bunch of one-one-one issues that we need to resolve.

A

We still have around like 17 p, 0, p, 0 items.

A

If you are looking for contributing, feel free to take a look at any of this. It is possible that we may not be able to get every single p 0 before well in this two weeks, and we may end up changing some of this. Do you want to.

A

Any question about one by one.

A

Okay and then, as for and the second topic, is 104.

A

As we actually have, some customers and users have found problems in 103, so we are targeting a 104 sometime this month as well. If you look at.

A

The one dot Oh issues we still, we have two to be zero issues. One of them is a performance regression. Mixer, unfortunately uses more CPU in 103, then 102. That is something we will address in 104 and.

A

B

Other issue is a caught failing.

A

B

A

A

Facing hypercube image released us the America yeah.

C

I put that on I, don't know what for background I come from pivotal I've been working on K native when we use SEO as a dependency, I'm kind of getting looped in to sort of figure out how to do compliance, and all that. So as part of that, you saw that one of the posts we hooks is using an old hypercube image. So I was just wondering one like I can make the P art updater for one one with that, be something like. What is the tolerance to accept that 4chan?

C

She, maybe even getting in 1.0, for this.

B

C

A priority, but it's just more of me, like just asking the question great.

A

So 104 is going to be impacted in past release. We only warn critical bug fixes so for the other non-critical behavioral change that probably should be done in 101. Instead, okay.

A

Unless this is super critical.

C

I, don't know what you define as critical like I, think.

A

C

Is just a foot pain problem.

A

C

Think the other thing too is the other image is really old, so you can maybe throw in like some it's a security thing. It's, but it's a posted Lee hook right. So just a one-off, a render job so yeah I'm fine to punt this 21.1 and I can make like a PR I think it's already even there. So, okay yeah! So the Sun. It's a non-issue.

D

C

It's a postally hook to clean up the secrets and then the subsequent one one release has changed it to use an SEO image that has coo cuddle only and is much slimmer.

D

C

No, not at all so yeah.

A

Questionable, whatever.

A

So it's not the topics about harm charts, Soham charts are now build a novel of daily releases and monthly releases, a strong for daily for daily releases.

A

They can be found in this stable location, so you can I think you can install them directly from from this URL and this URL, the the the fire was that this knowledge gets updated every day and for that reason, I actually have removed no static chart from this year, I only because they were built from some from some heavy convict, maybe a couple weeks ago, and they get our update very easily. We have a more reliable way to get it to charts.

B

D

As a user, when they install the charts they're not going to need to.

D

A

A

C

I've been asking a few questions, but ultimately I saw that we have license collectors for the ghost source and I noticed that we're not, including in the Ecco container, is the proper copyright and licenses for the Envoy and its dependencies at least that like I, don't see it so one question I have is: is anyone actively working on to include that the?

C

If not, then that's like something that I know like pivotal is interested in, and is that then something that you would want me to contribute back like, for example, like a tool that potentially does some Basile queries and then scans the necessary repos free licenses.

A

Sure I am actually not aware of any more anybody working on this one.

D

And that's how we generate the aggregated license file. We might have missed armboy, because the source code of the Envoy is not necessarily in here or maybe just because it wasn't written. So it would be great to actually have this contribute to the community.

C

I see yeah I saw Stephen changes, so let's say the SEO CNI repository and it uses the underlying license. Gem scanner I was just wondering if anyone was looking into this for the Envoy source yeah. So.

A

I think the existing aggregated license was created from Martin some time ago, using yet another like licensed, collector or aggregator I believe Stephen has something else and it produces slightly different result. I don't know if we have adopted it, but both of them, yet both of them get licenses from the underlying go sauce go of me, so I'm boy is probably excluded and if you can contribute I think that would be great, but.

B

It will be great if.

A

You, if you can in touch it with both Stephen and Martin, okay, do.

C

You mind adding their names to the doc I think I've reached out to Steven Steve.

D

A

C

D

So I guess it would be nice to have this as a SEO approach, rip its your repository project somewhere or utility, because it will be useful to come and collecting items for common projects with a misdeal, because the wheel, yeah I know so we could have multiple projects within the it's, your org that needs such a tool.

A

David, what what is your github handle.

C

D P ro ta, so, okay, I, don't know what I'll be able to contribute I'm only on this for a few more days in terms of sorting out compliance, um so we'll see we're gonna see if there's a way to automate it in the time frame that I'm around for this I know like fairly spaz. Ol has a query option that can at least give you all the dependencies for a bill target. So maybe that is a potential start.

C

So I guess to clarify. Martin originally wrote the code that the go tool first and in the go source and I.

A

Think he got majority far away from cube noddy's, okay,.

C

Yeah once I'll go it's much simpler.

E

It is Austral mind. Oh yes, Piero.

D

So any back to the whole charts question, so these are just three releases, but eventually they would goes to would they go to somewhere the static chat, location somewhere? Yes,.

A

A

A

A

Great suppose, we'll go to something like one point, one point: zero slash chance as well. I see.

D

Okay, instead of P.

A

Releases release and releases the actual LTS of monthly release, but.

D

Then the extra release does people still have to point to the Google storage I'm trying to think out. You know what are the repo ads command? They need to do with helm for the official release.

D

Url is a little bit undesirable because it has so much content in here, because we have pre release and all the release contents in here to.

D

Typically, have a stable folder and it has all the stable charts and then they have well.

A

D

A

They just need to replace this with the actual version.

A

So this the the part that that changes, yeah.

D

But there's also a search function that people could search a particular repository and see what are the chats in there. So do you want them to you, have a different URL for every single release. I guess that's my question. Oh, would you I think from a user perspective rather and one single URL down with the copper, multiple releases down the road because I think that's how it works for some of the other chats so.

A

How do you put multiple versions in the same in the same directory? Well,.

D

So what they have is they have a top directory, and then they have a stable folder that hosts the staple chats and then they have like developmental folder that has unstable charts, and then we think that top folder there's a search function. You can search for charts in the repository and then I think you just need to add the top repository folder. That's a typical experience. People deal with helmets instead of every single version of charts. You know that you, you don't have to drill into every single detail.

D

The posture I'm just trying to you know, have us the kaabah common repository structure as the community. How much mass was I.

A

That can be done, I think for now. I just try to mimic whatever we had on East Ohio before, but if there is a standard way to set up this directory structure and put all the charts in the same location that can be done as well. Yeah.

D

Let me send you an example: if I can find a one, so you have, you know, I knew you know what I'm talking about some of the common wise people set up.

A

So yeah, if you send me some information, I can follow.

D

A

And David: do you want me to create an issue for this or let.

C

Me let me reach out to Stephen and another person. First I, don't know my I'll see what I can do. It depends on the time. Okay, so.

C

If I, let's say make lots of progress quickly, I'll make an issue then I. Imagine that something to contribute, but essentially gonna time box. This and ultimately, in the worst cases, I might just list out the dependencies to scan manually and end that off to like a compliance thing here. So if I can automate some of that collection and I'll contribute, it's not, then.

C

A

Well, I mean it's probably a good idea to create an issue anyway. If, for some reason we we left out, I'm Laurie is something we should address as well.

C

Yeah, let's give him credit.

A

Yeah, so let me create an issue anyway and then either you or somebody else can together.

C

Yes sounds good.

A

All right Tiago do you have anything to add no.

E

No nothing from my side. Okay,.

A

E

A

Yeah no problem anybody else, any other things that you want to talk about. Oh.

C

Quick question: where do you see that Zen hub tab don't need to be like a member, and you see, oh in order to see the POS and all that stuff? Oh, you.

A

Actually need to be store, sent off. Oh, it's just a Chrome extension.

A

Okay, so I think that should be it. Oh.

B

I I was late at the meeting. Did you discuss one point one already? Yes,.

A

So we are working toward one point one, and is the plan is to cut the one point, one Billy's in around two weeks before Thanksgiving, so there are around thirteen P zero issues at this point and we should close ammo as much as possible for the photos that cannot be closed. They probably will be pushed out to one point. Two: okay,.

B

Is it another LTS release? Yes like want.

A

101.1 will be and LTS release. Oh nice.

B

So we have two branches or 1.1: we will duplicate the duplicate 1.0, so.

A

We already have to release one one branch and all the one one development will happen in one, the one, the wheel, each one, one branch and the branch was cut from master two weeks ago. I think.

B

A

So they are it. Is it already diverse from with each one? Oh no.

B

I mean, what's one point on: is release it. We, we are still going to provide patches for 1.0.

A

So at this point we know that we will be creating 104 and the it around the same time frame as 11.1 after 1.1 is created, whether we will be creating batteries on one point, one all depends on whether we find another critical path in 1.0. Okay,.

B

Make sense thanks yeah no problem.

A

Any other question.

A

All right, if not that's all for today, thank you. Everyone see you guys next time, oh.

C

Thanks bye, thank.

A