661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2023 TSC Recordings	2023 TSC Decisions	Anti-Trust Policy

We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Attended	Proxy (w/ @name)	Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Andreas Geißler	DT	Magnus Buhrgard (Unlicensed)	Ericsson
Cédric Ollivier	Orange	N.K. Shankaranarayanan	Individual
Chaker Al-Hakim	Individual	Paweł Pawlak	Individual
Dan Xu	Huawei	Ram Krishna Verma	Bell Canada
Dong Wang	China Telecom	Seshu Kumar Mudiganti	Windriver
Gervais-Martial Ngueko	AT&T	Timo Perala	Nokia
Keguang He	China Mobile

	Agenda Items	Presented By	Presos/Notes/Links/
Strategy (45 minutes)	ONAP takeaways		We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements.
	LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board	Magnus Buhrgard (Unlicensed)	I need a proxy, representing ONAP, for the next SPC meeting June 12, since I'll be on AL Paweł Pawlak will proxy Kenny Paul add Paweł Pawlak to meeting invite schedule for June D&TF: https://teamup.com/ksgw6qzqcmg9zbzsfq?date=2023-06-06&view=md3
	TCC / ONAP Liaison Updates
	Task Force Updates	Tony Hansen Toine Siebelink	getting-to-gold.pdf Run PoC and receive feedback Tickets have been created - need 2 more committers to get their 2FA


Operations (40 minutes)	TSC Activities and Deadlines
	Release Status	David McBride	London Release - RC milestone decision Schedule RC is scheduled for today Milestone Status Status for RC: NOGO Montreal Schedule #AGREED the TSC approves the following scheduling changes London RC rescheduled for June 15 London Sign Off rescheduled for June 29 Montreal M1 rescheduled for July 13 Discussion as to why there is no real outcry that the Montreal schedule will be slipping. Consumers note that they tend to make use of components as they are provided rather than necessarily waiting for the complete bundled release.
	RelEng/Infrastructure
	PTL Updates
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Paweł Pawlak Amy Zwarico	2023-06-01-BestPracticesForIntraOnapCommUsingServiceMeshAuthnAuthz_v3.pptx
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping		D&TF is June 6-8, please register: https://cvent.me/NKWY5M Schedule https://teamup.com/ksgw6qzqcmg9zbzsfq?date=2023-06-06&view=md3 Remember to cancel your meetings NO TSC on June 8

Zoom Chat Log

07:00:46 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:00:54 From Martial Ngueko(AT&T) to Everyone:
#info, Gervais-Martial Ngueko, AT&T
07:00:59 From Paweł Pawlak to Everyone:
#info Pawel Pawlak, Individual
07:01:01 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
07:01:06 From Keguang He(China Mobile) to Everyone:
#info Keguang He, China Mobile
07:01:15 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
07:01:53 From cah to Everyone:
#info Chaker Al-Hakim, IC
07:02:01 From Magnus Buhrgard, ONAP to Everyone:
#info Magnus Buhrgard, Ericsson
07:02:10 From Cédric Ollivier to Everyone:
#info Cédric Ollivier, Orange
07:03:32 From N Shankar to Everyone:
#info N. K. Shankar, Individual
07:05:09 From Dan Xu to Everyone:
#info Dan Xu, huawei
07:08:06 From Ram Krishna Verma to Everyone:
#info Ram Krishna Verma, Bell Canada
07:08:16 From Ram Krishna Verma to Everyone:
Apologies for joining late today
07:08:52 From Kenny PAUL (LFN) to Everyone:
D&TF is June 6-8, please register: https://cvent.me/NKWY5M
07:37:43 From Kenny PAUL (LFN) to Everyone:
#VOTE: Does the TSC approve the following scheduling changes? London RC rescheduled for June 15 London Sign Off rescheduled for June 29 Montreal M1 rescheduled for July 13 Please reply with +1, 0, -1
07:37:52 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:37:54 From Magnus Buhrgard, ONAP to Everyone:
#vote +1
07:38:01 From Paweł Pawlak to Everyone:
#vote +1
07:38:02 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:38:04 From Ram Krishna Verma to Everyone:
#vote +1
07:38:08 From Timo Perala (Nokia) to Everyone:
#vote +1
07:38:09 From Martial Ngueko(AT&T) to Everyone:
#vote +1
07:38:10 From Dan Xu to Everyone:
#vote +1
07:38:13 From Keguang He(China Mobile) to Everyone:
#vote +1
07:38:16 From N Shankar to Everyone:
#vote +1
07:38:22 From Cédric Ollivier to Everyone:
#vote +1
07:38:37 From Kenny PAUL (LFN) to Everyone:
#endvote
07:38:47 From Chaker Al-Hakim, IC to Everyone:
#vote +1
07:39:45 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the following scheduling changes London RC rescheduled for June 15 London Sign Off rescheduled for June 29 Montreal M1 rescheduled for July 13
07:48:38 From Kenny PAUL (LFN) to Everyone:
please register: https://cvent.me/NKWY5M

Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative! Information as to why .
They are included here as a time stamp cross-reference for the recording only! The notes above this line and the actual recordings are authoritative.

07:03:10 Transcript is on.
07:03:15 Recordings on
07:03:26 Go ahead and get started here by.
07:03:32 Mentioning our antitrust policy, this policy is important.
07:03:36 Whenever we've got. Folks from multiple companies participating in these meetings, please review it if you have any questions, please contact your company's legal counsel.
07:03:47 The LF may also contact Andrept Grove at the firm Gesman Uptgrove LP, which provides legal counts to the LS.
07:03:51 Policies in effect whether there is a member of staff on the call or not.
07:04:02 Okay, thank you. As always, these meetings are recorded. Please keep yourself muted unless you're speaking.
07:04:11 Send a text to me. I will have to cut and paste it into the meeting minutes. At the end.
07:04:21 And. Let's get rolling.
07:04:29 I don't. I think. Oh, the reason I'm filling in here is because Sandra is out for a few days.
07:04:39 Anyways, I don't think that we have any Any carriers providing feedback today.
07:04:55 No, I think we are. We are done with this part.
07:05:02 Okay, so this is something that can be taken just off of the Off of the template.
07:05:05 Yes, yes, I think it's. I think it could be removed.
07:05:12 Oh, that's ugly.
07:05:12 However, you could have a We could have a kind of follow up, right? And so. You know, discussion on the short and meet their actions but also long term
07:05:29 That's a follow-up of those to pick a race, right?
07:05:35 Yeah, okay, so I will leave it on the template then.
07:05:40 Magnus is looking for a proxy for The SPC meeting on the twelfth of June.
07:05:51 Yes, I'm, the owner of representative in that meeting. Then there are. Also direct representatives from members and so on, but it's their own app.
07:06:04 Hats that you have to put on.
07:06:12 So the SBC meeting. For folks. That, need to know in terms to fill in.
07:06:20 Happens at 1,600 UTC.
07:06:26 On the twelfth.
07:06:30 Is there somebody that can, act as proxy during that meeting? If so, I will make sure that you get the invite.
07:06:44 Okay.
07:06:39 Well if there are no volunteers I can I can My business. Hey, welcome.
07:06:43 Thanks, Pablo. I think you will benefit from it yourself. You can. Listen to what's up there.
07:06:54 Okay. Sure.
07:06:54 And please let us know. Thanks.
07:07:02 Okay.
07:07:15 Well.
07:07:19 Let's try that.
07:07:39 Okay. I see also there is a. Note here about the schedule for the DNTS.
07:07:55 Was this for the a specific, for the day? So Magna she wanted to call attention to the specific
07:08:04 Session, you know.
07:08:03 No, no that That was not on me. I didn't I didn't put that in.
07:08:08 Oh, okay.
07:08:09 Someone.
07:08:19 I think yesterday when we were we are reviewing with Sandra so we discussed that it will be good to put this schedule so on our community and also would have visibility on the different sessions for honor but not only for on up so I think this was the intention from Sandra to put it.
07:08:32 How's it? Cost organization, yes.
07:08:37 Hmm.
07:08:43 Okay, then we'll go ahead and shift there. I'm going to drop the registration link into the chat.
07:08:47 Yes, please.
07:08:49 If you have not registered, please do so. This really it's important to us.
07:08:56 It helps us out. For planning and follow ups and all of that good kind of stuff.
07:09:05 So looking at this at the schedule. The opening plenary, we've got.
07:09:16 Cross functional.
07:09:19 Things going on on. The first day. One of the, one of the big ones that I'd like to call attention to is
07:09:34 Talking about net field and own app getting into the 5G super blueprint. I think that's going to be a pretty important session.
07:09:46 And then at the. End of, Monday. Discussion about Getting, CPS.
07:09:57 Their gold security badge so somebody wanna say a couple of words about that.
07:10:04 Little bit of advertising.
07:10:08 I think that's the rest of me, okay, I've also, Yeah, we, yeah, we just were happy to share this information with, IT, which is a team seeing, just showing, what we don't, what we had to do to get the technical standard.
07:10:23 But if you haven't got by the way yet, we're very close. You might make it before that presentation.
07:10:27 We might not, very close thanks to the help Tony and other people. So yeah, that could be the same for the projects if they wanna see how, how we got there.
07:10:39 Excellent.
07:10:38 And maybe, we should we should say that we put that there on the Tuesday. Because of personal reasons for one of the presenters.
07:10:49 Yep. Cause it was already planned on the other day was it?
07:10:53 So, Yeah, yeah, it is. Is, is this, It was originally sort of the, yeah, on the Wednesday.
07:11:04 But it's quite okay to put there. It, in case somebody wonders why we. Spread it over 3 days.
07:11:15 Yeah, I I think the importance of attending this session is It is pretty high. It's super exciting that we are so close to achieving a gold badge within.
07:11:28 For one of our projects.
07:11:33 And.
07:11:32 Yeah, you. Yeah, please. Kenny, so yeah, you're right. I don't think that's the, I mean, it, that was not the reason why you put it on Tuesday, but I think it is sort of it fits well into this cross.
07:11:49 Domain because it gives it's it's interesting for also other people outside of ownup.
07:12:01 Yeah, absolutely. Absolutely. I agree with that. 100%.
07:12:03 Looking.
07:12:03 We, we could take any that's, you know, golden batch was like a golden, in the past, right?
07:12:09 But. We are really really close to it. So. Yeah, it's good to share.
07:12:16 The project perspective but also Tony from Second will be sharing his perspective and his journey on you know, working with LFIT, and, with the projects.
07:12:29 You know, increasing the score. So this is a joint effort on on both project side and and, who is dealing with the, from the early beginning of an app, right?
07:12:49 Absolutely. Absolutely. We've got.
07:12:57 Number of other sessions teed up. Throughout.
07:13:05 The rest of the days. Got a good mix and match of things that are going on.
07:13:14 Set up an ask me anything panel for LFX. I know that there's been some Questions about LFX security there have been some questions about insights and things like that so
07:13:29 Our good friend Henry Kuwait will be there, for folks that attended the event in Portugal.
07:13:36 Might remember Henry. Super great guy. I love him. He's really fun to be to be around any He's a good listener and I and a good helper.
07:13:48 So. Help you on that. He'll be bringing, one of the developers with him.
07:13:53 And. Possibly, one of the, product managers. Provided that we can get some timing.
07:14:07 So that's, oh, I just ran over my dog with my chair.
07:14:11 That is not good. I'm sorry.
07:14:14 Now you're part of the recording.
07:14:23 Anyway, so there's that session.
07:14:29 We've got updates. Magnus has a session continuing our. Streamlining efforts, within own app and then.
07:14:40 Some other stuff. That we've got going on.
07:14:49 Anyone wanna pitch their session? If not, we will move on. But please register.
07:15:00 Okay.
07:15:04 Remember to cancel, any meetings. That you may have on the calendar during the event. Falls during the event and we won't have a TSC on June eighth because that's next week because that is in the middle of the event.
07:15:32 Okay.
07:15:38 Tony and Twine.
07:15:54 Or a preview? Yeah.
07:15:49 Yes, I think this is mainly. You could, yeah, no, I, yeah, sorry, the, the, the, the, there, I think this was about, the tickets for, it was required, we need to get 2 factor authentication, our logins for, L and
07:16:07 F, man. I was a little bit confused about it because already had to factor for GitHub itself, but we needed to separate, to factor authentication for.
07:16:14 For L which I now got myself and all the committers need to have that so the tickets have been created and 2 of the 4 have been completed.
07:16:24 So we need 2 more committers and then I think it needs to be go back to Tony. To get everything approved before we get calls, but that's basically what's spending now.
07:16:34 Okay, okay, good news. Thank you for this update. So we're simply wondering. About the follow up so I'm glad that we are moving forward and Yeah, we are so close.
07:16:58 I'll make sure check check with us to commit this this afternoon.
07:17:00 Alright, thank you.
07:17:10 Come on.
07:17:16 Okay.
07:17:27 So I guess we will then shift to Mr. David Mcbride. Would you like me to share here or would you like to share?
07:17:33 I'll go ahead and share Kenny.
07:17:35 Okay.
07:17:39 Hmm.
07:17:52 Alright, well, I've only been gone about 10 or 12 days, but.
07:17:54 Feels like a lot longer. Than that. It's always a little odd coming back from.
07:18:01 Vacation and getting your head back in the game. Any who. So, we have reached our, RC, milestone date, for the, London release.
07:18:17 And a lot has been accomplished. So you can see for the projects, we have.
07:18:29 Well, it shows about 50%, but. If you discount the projects that, our headless then it's actually quite a bit more than that so a lot of progress has been made.
07:18:46 Particularly, this week. I was also, I was particularly impressed with the requirement owners.
07:18:54 This pie chart looked a little bit gram. At start of the week, but, the requirement owners rallied and, got most of their tasks.
07:19:07 Done. Nevertheless, there's still, significant amount of work. To be done here.
07:19:18 And in particular, I chatted with the Dan Tim and he's out on vacation.
07:19:28 This week. Isn't it outrageous when people take vacations? And so we, particularly need, his, input on, RC and the completion of his tasks.
07:19:41 He told me he thought that he could probably finish that up. Early next week. Anyway, I think that there's enough.
07:19:52 Here, left to be done that we can't move far forward with the RC. Normally I would suggest pushing the milestone out a week, but of course we have DNTF next week.
07:20:08 So that's not an option. So what I'm, suggesting is that we basically push everything out.
07:20:17 By 2 weeks Now, as I mentioned, before I left on my vacation, that.
07:20:27 If we did this, it would have knock on. Effects with the the Montreal schedule and so you can see that I've also recommended that we push out, M one.
07:20:44 We, 2 or 3 releases back. We, tried. Overlapping release schedules.
07:20:53 And it was it was a minor disaster. So, I, told myself since then, if we ever ran into that situation again that I would, avoid that.
07:21:03 So. Suggesting that we also push out M one. By 2 weeks to avoid that overlap.
07:21:11 Now, what this brings up is that makes, So that would push M one out to, July thirteenth and you can see that that is uncomfortably close.
07:21:28 To M 2 on the twentieth. I'd like to. For now avoid the dealing with M 2 and just kind of see where we're at.
07:21:41 Once we get out into, mid July. And then decide what we, want to do with them too.
07:21:49 We might move it. We might maybe collapse. M one attempt to there's A few things we could do there, but I want to see where we're at.
07:22:00 Once we get out into mid July, before we make a, decision about, M 2.
07:22:07 So. So that is my recommendation. Basically these 3 bullet items.
07:22:14 London RC pushed out 2 weeks to June fifteenth, London sign off. Pushed out 2 weeks to June 20 ninth.
07:22:21 And Montreal M one pushed out 2 weeks to July. 13. Does that make sense?
07:22:30 Any questions, concerns?
07:22:34 How are it affects the delivery date for the.
07:22:42 Right now I'm not, projecting any changes. I'm only suggesting right now that we shift M one.
07:22:50 So I'm, I'm not suggesting for the time being anyway that we, change any of the other milestone dates.
07:23:02 Huh. Okay.
07:23:03 Just an observation here. I mean in a company if you shifted out the the milestone. This late 2 weeks.
07:23:13 You would have everyone. Really upset and You would have sort of an outcry. I think this is a proof point that's not that many are actually waiting for the The London release.
07:23:31 As I've shown before, that's, I mean, we consume own up in another way now.
07:23:36 Say I'd love to hear someone. Sort of post me on this or contradict me on this but I I think this is something that we have to think about.
07:23:48 That's. There is so little angry people. When we're sort of pushing out this milestones time after time.
07:24:02 And I challenge. Sort of the Montreal. Time plan. To just sort of continue.
07:24:12 To push along. With this platform release. So I think we need to have a. A discussion or a at some point.
07:24:25 Sort of this discussion about what's the shape of Montreal.
07:24:31 And of course, I will bring that up in my. In my presentation next week.
07:24:38 But I think you're a bit, a bit head in the sand here. And I, I, I would like to have other people's opinion on this.
07:25:00 Well, I guess the only thing I would say is that, it's true. We, shift the dates around a bit, but 2 releases per year.
07:25:03 So that, is very consistent even though the specific dates, or times of the year.
07:25:12 That those releases happen shift around a little bit. The fact that we do consistent, that we do deliver.
07:25:19 2 releases per year has been very consistent.
07:25:23 Yeah, I agree with you and this is not any criticism towards you. I mean, you do. Best you can on this, but I still think that.
07:25:33 I mean As I said, the. The fact that people are not sort of. Very upset and making a lot of noise.
07:25:45 Is something that we have to. To think about.
07:26:07 Yeah, thanks, Magnus. And I don't look at it as, criticism of me personally.
07:26:07 I realize that, I think are necessary.
07:26:11 I think it also depends how the consumers are using. Own up if they are really using. Let's say it on the released versions or if like we are partly doing it already.
07:26:28 Taking the, let's say changed versions already into account. Yeah. So That means for certain components.
07:26:39 Yeah, so it whenever we have of course, let's say We are as we are doing, let's say.
07:26:46 Constantly updates in the systems in onup and we are testing them in gating. We usually be happy to.
07:26:57 To also have in between updates of certain components in our okay we are not in the in a production system.
07:27:06 That of course it's something different still but I think it is of course we are not so much bound on this.
07:27:14 These kind of releases yeah although of course It is. Yeah, of course a release, does make sense, of course, from, functionality and from, use case to step perspective which own up is presenting but if you just take certain components and you are sure, okay, this, this
07:27:37 component has in between my request to change already in or even we are doing the upstreaming for that.
07:27:45 And then of course we will take we take that even in between and I'm not waiting for the complete final final release state for that.
07:27:57 So maybe this is also maybe a difference. To the releases before it.
07:28:05 Yeah, thanks. Thanks for that, Andreas. I, we also tend to use the continuous design and delivery.
07:28:14 And, And then the last, the sign off. It's has a significance.
07:28:22 But it's not that's that's super important
07:28:32 Exactly.
07:28:33 And for other consumers, do you? For you see any impact on your plans?
07:28:43 No, I don't think so. Same as what entry us and, Magnus said, right.
07:28:48 So. We don't wait for a sign off to happen. Maybe we, start consuming things even before.
07:28:57 Okay.
07:29:00 Was if we see now especially especially now at this phase, where, where we have issues with, where, where we have issues with, with, SDC.
07:29:10 The SDNC delivery, and we then have to change of course because this is the consequence of the problems we see at the moment with the SDNC delivery that we need also to change.
07:29:24 Now code. Of other components, of course, this is a bit critical. So I'm happy, of course, that we shift the milestone now here for London, but we if we want to take then for example the new ODL version into into our environment will have to wait till we have 20 for example the
07:29:47 changes done in SO for example now. Because there are interface changes now which are coming with a new SDNC release and which was not shown beforehand.
07:29:58 And this is of course caused by the problem that. The late coming of the of the STNC patch.
07:30:08 Yeah, so that's of course and a problem we now facing here.
07:30:10 Sure, sure.
07:30:16 Okay, another comments guys
07:30:31 Just a comment that I, I'm glad, Magnus you. Phase the point it's very valid and it We should think about.
07:30:38 This, and because you asked the question, I was thinking the best. Seems to answer that people are using it.
07:30:46 So I'm happy Andreas and RAM actually. . And what do you say makes sense So then that, so I'm assuming then, the users of the code are already sort of.
07:31:01 Keeping track of the progress of the parts they want and then in some sense not looking at the the milestone date in some sense.
07:31:10 Yeah. But the mansions are still useful to guide the work at least. The initial ones, then one and 2 at least, you get a sense of what is being planned.
07:31:21 And after that, I think it's. Continuous. Yeah.
07:31:29 Thank you, Shankar.
07:31:36 And I would say maybe if since that's what's happening. Maybe it's useful. I don't think we need to track it, but maybe it's useful to identify early on.
07:31:45 As to who are the consumers and who cares about the work. So because then who is leading that? Okay, that project will know who the users are.
07:31:54 I'm giving you already know.
07:32:02 Yeah, I hope that there is a also direct contact from the various projects to their. Sort of, stakeholders or their consumers.
07:32:13 And, I know that's the case and I think I will also bring that up. That's sort of how we can.
07:32:23 Enhance that, communication. I, saw. That. that there is in CD foundation i think it's called ccd that they have ambassadors that they have sort of a a chart of people's email addresses, phone numbers and so on for people
07:32:50 in different expert areas. And, if you put it up like that. And I'll go in more into that.
07:32:59 Next week. Then you can get the direct contact between consumer and producer if you will. And shortcutting some of this And hopefully make.
07:33:13 Code available, sort of faster. And, and also with, more shaped towards the, the needs of stakeholders.
07:33:26 And I mean, you, you could argue that, that's the, this information is already there.
07:33:33 We've published the PTLs and then we know, but could be even better if you if you come into the sort of, or wiki or, our website.
07:33:47 You should be able to sort of get this sort of ambassadors. Page and you can look for your the specific functionality or the yeah features you're looking for and and maybe that will also make it sort of simpler than trying to browse through the documentation or and so on all you can get the link you can
07:34:11 get a direct link to the documentation through that ambassador. So I'll pick up some of those sort of, ideas, that inspired by other.
07:34:25 Other open source communities next week.
07:34:30 Thanks.
07:34:39 Alright, any other comments?
07:34:47 Okay, and. I just wanna confirm, for now you want me to proceed with, distributing and release management tasks for Montreal or are we wanting to pause on that?
07:35:08 I think until we decide not to do it, we should keep it. And maybe we have a discussion next week on it.
07:35:20 We've heard some, Info from Shankar for example that this is good to keep it.
07:35:26 To have a good understanding on the where we are with the progress for the for the So yeah, let's have a discussion.
07:35:36 And in this side on the next steps, right?
07:35:44 Yeah, we will not have a TC meeting next week, but. And I think it makes sense to collect sort of use cases and requirements for.
07:35:56 For the next release. But, I, doubt that.
07:36:04 That we should sort of go ahead in the similar way. But let's discuss that. On a later meeting.
07:36:20 I think we should end up after the session next week with some recommendation to TSC, right? I hope all theC members could participate.
07:36:18 Yeah, right, right. Yeah, I mean, inviting to
07:36:20 But then recommendation. Voting. Like the week after voting and having.
07:36:27 Sure. Yeah, I invite people to sort of take part in the discussion. I will have some ideas and some.
07:36:41 Yeah.
07:36:37 Sort of, inputs here. But I hope people can join that session and speak their mind. Okay, thanks.
07:36:47 Yeah, let's keep it as a brainstorming session. Magnus you will have some proposals you will have some ideas then we have the discussion.
07:36:54 Right. Right.
07:36:53 We end up with with the recommendation. Based on the discussion. Thank you.
07:37:10 Okay, terrific. So for now I will continue to, distribute the release management tasks.
07:37:16 As I always do, until, you know, given different direction. Okay, thank you.
07:37:26 So, Pavel, do you think we're, ready to go ahead with, the vote on my recommendation.
07:37:38 Yeah, I think we have the discussion. So. We can have a votes here.
07:37:41 Okay. Okay, Kenny, do you wanna drop the? Vote text into the chat.
07:39:04 Did you tally the vote? Kenny did it pass.
07:39:10 And it did.
07:39:13 Mute again. Yes, it is approved.
07:39:21 Okay, all right, terrific. Thank you. And that's it for me. Thank you.
07:39:36 Second.
07:39:50 Okay, then. Continuing on.
07:40:08 Next thing we have is,
07:40:12 Discussion on best practices.
07:40:16 Yes, yes, so. We had the discussion at the last second. On the impact on and the implementation of service mesh.
07:40:28 So, mmm. We've prepared, let me prepare the slides, based on the discussion we had and this is like intro for the TSC we would like to have a Some.
07:40:44 You know, in for sharing and the next PTL and then. And unfortunately second will not be organized on Tuesday because of the DTF.
07:40:54 But, for the next TSC, so the week after. And we would like to ask for a mmm.
07:41:04 TSC for voting and, you know. Making things done for the service mesh and if you go to the next slide which is We need the proposal. Jack, you are with us.
07:41:18 Maybe you would like to share some more insights. As for the intro. And just this next steps I think we need to modify it as it was discussed so And the 8.
07:41:29 The next week part will not happen for the for the TCA approval, but the week after probably because because simply we need to have a TSC meeting and it will not be next week.
07:41:47 Hey, would you like to? And briefly introduce the problematic as we have it here.
07:41:53 So,
07:41:58 Historically, we've had a need to. Have some degree of authentication and authorization when One component inside own app is making some sort of an API request to another component inside our app.
07:42:13 And typically, what we did, was to use, the HTTP basic authentication.
07:42:21 And essentially each component had its own. Mechanism for.
07:42:29 Setting up. Authentication and authorization with service mesh. That all gets offloaded.
07:42:39 The components, authenticate to each other mutually with TLS. And then there's a notion of authorization policies in service mesh that.
07:42:51 Control. What component gets to talk to what other component. And What we'd like to do is to be able to use that mechanism consistently across.
07:43:04 Oh, and in particular for components that that used to require the basic authentication simply to be able to turn that off.
07:43:14 So we don't need it anymore so we're not maintaining. Credentials in various ways through the different OM charts.
07:43:29 And that's really the. That's really the crux of it to essentially to take advantage of what Service Mesh offers and get rid of the.
07:43:41 The now obsolete ways of doing things.
07:43:54 So, the and team and they finished, service, mention, presentation during London. So that's by as Jack said, we don and also some of the basic authentication are used by project they contain the Kurdia Tax password which is not good.
07:44:01 And so since we already placed S mesh and on it, so why not concentrate to a service match.
07:44:10 All the way and then also the removed to clear text password and other you know it's non-standard.
07:44:20 That's this one. And so Andress, they finished the good work and then Jack and O the MT and finish their great work.
07:44:26 So we just wanna use it.
07:44:37 Yeah. And we plan to have, I'm glad, Girish, from Infost is with us today.
07:44:37 So we Maybe this could be interesting topic for reinforces to contribute. And to own up to support this initiative.
07:44:44 For the Montreal release so would you be, available for, some meeting?
07:44:53 In coming days. Having some discussion on what we would like to achieve and if it's would fit to your plans for contributions if it could be interesting topic for you.
07:45:05 Yeah, sure, sure, Pabel. I think we can plan it out probably after the DTF.
07:45:12 Okay.
07:45:11 Did you affect me, currently and understand to actually we had 2 sessions planned in DTF and we just kind of closing on those contents.
07:45:17 So maybe.
07:45:19 Okay, sure. Of course, no problem. Alright, so we plan something the week after, right?
07:45:26 The following week after the DTF, maybe beginning of the week after, right, the following week after the DTF, maybe the beginning of the week so we could have.
07:45:31 Some discussion and possibility to have your feedback. On this topic. So when we would be coming back to the TSC with the recommendation on the global global requirements.
07:45:44 And we would have maybe some resources that could, support this, this, This would be my intention.
07:45:55 Yeah before coming back to the TSC. With the asking for for the approval and, green light for having this global requirement in place.
07:46:06 Okay, so. I, I, I will, reach out. For the maybe.
07:46:17 Monday or Tuesday. The Not the next week, but the week after.
07:46:25 Okay, thank you.
07:46:23 Yeah, sure. Thank you.
07:46:32 Quick question to address. Do you see the scope of this, supports? It's just the OEM or Call this up into change code, project need to change code.
07:46:35 I did, depends if the components are, able at least to. To, remove the base off or other authentication will have to have this kind of Of course, they need to.
07:46:52 It's, so, I guess some, some components do that already and then we can change it just in that already and then we can change it just in OM that's clear.
07:47:05 But I don't know if all of the components are. Able to disable basically debatos, in there.
07:47:11 Implementation that has to be checked, I guess.
07:47:12 Okay. Okay, thanks. Maybe we can discuss it the PTO. Yeah, okay.
07:47:18 Thank you.
07:47:23 Okay, thank you guys. Nick 2, Kenny.
07:47:38 Ken you are on mute?
07:47:44 Just in case you are speaking.
07:47:48 Yep, okay, there we go.
07:47:52 I think that's it. We've already talked about the event.
07:47:59 That's what we've got on the agenda for today.
07:48:08 So if there is. Nothing else? With your permission, Oh, go ahead and Close the meeting.
07:48:16 Or we can just open the floor.
07:48:19 Okay, yeah. So guys, next week we have a TTF event, so please. Participate please contribute I think they will be several on up.
07:48:30 Related sessions. Let it be good place for, the discussions brainstorming. How you know ensuring that we are moving with one up in the right direction?
07:48:41 And also sharing with other communities and getting from other communities. Some latest updates because we are not in the vacuum right so Yes.
07:48:52 Thank you guys.
07:48:57 Thank you. Bye.
07:48:56 Thank you. See you then.
07:48:57 Thanks.
07:48:58 Okay everybody, thank you very much. Bye.
07:48:59 Bye.
07:49:01 Bye.
07:49:02 Bye bye.
07:48:59 Bye.

[data-colorid=p35c88dy3c]{color:#1d1c1d} html[data-color-mode=dark] [data-colorid=p35c88dy3c]{color:#e3e2e3}[data-colorid=g45igri9qu]{color:#333333} html[data-color-mode=dark] [data-colorid=g45igri9qu]{color:#cccccc}BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Agenda Items

ONAP takeaways

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

Task Force Updates

TSC Activities and Deadlines

Release Status

RelEng/Infrastructure

PTL Updates

Subcommittee Updates

Upcoming Events & Housekeeping

Zoom Chat Log

BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Browser not supported