94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

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	Keguang He	China Mobile
Byung-Woo Jun	Ericsson	N.K. Shankaranarayanan	Individual
Dan Timoney	AT&T	Paweł Pawlak	Incognito
Dan Xu	Huawei	Seshu Kumar Mudiganti	Windriver
Dong Wang	China Telecom

	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	Sandra Jackson (Deactivated)	Board Update
	TCC / ONAP Liaison Updates	Paweł Pawlak	Discussion SECCOM: Announcement for ONAP releases prior to London: All ONAP releases prior to London are broken because AAF certificate is expired. Users should select London+. ONAP has a default policy for supporting n - 1 ONAP releases. Is this policy good enough for the AAF certificate issues of ONAP releases prior to London? Action Point: TSC/DOC/ARCCOM/OOM should publish this on the ONAP wiki, release note, etc.
	Task Force Updates


Operations (40 minutes)	TSC Activities and Deadlines	Paweł Pawlak	Update the ONAP main wiki welcome page needs to update the ONAP main wiki welcome page to reflect the New Delhi release.
	Release Status	Byung-Woo Jun	Update project status: PTLs started updating project status, key updates and benefits. Thanks! Project Status in New Delhi Release note: on June 29, 2023, #AGREED the "O" release will be Oslo rather then Odessa
	RelEng/Infrastructure
	PTL Updates	Andreas Geißler	SDNC cannot be updated for Biermann Dan Timoney : need confirmation from SDNC Andreas Geißler : coordinates with the SDNC team Update of CI/CD for open source SMO Louis Li from the O-RAN SC SMO shared their deployment upgrade Andreas Geissler created feedback from the OOM perspective (Feedback for OOM), and sent his feedback to Louis Li. collecting feedback
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Paweł Pawlak Amy Zwarico Byung-Woo Jun Byung-Woo Jun	SECCOM: Github vulnerability issue; Amy Zwarico opened an LFIT ticket (https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26421), and Jessica Gonzalez provided LF's password practices for Git. Thanks Jessica!! resolved. See the report from Amy Zwarico , 2024-01-30 Security Subcommittee Meeting Notes ARCCOM: @Fiachra Corcoran (PTL) initiated the DMaaP Message Router deprecation in New Delhi, by following the unmaintained project transition step #1, Project State: Unmaintained For the steps #2,#3, and #4, ARCCOM and OOM have found impacted projects and are analyzing impacts. The PTLs should analyze the project impacts for New Delhi. At this time, ARCCOM approved the request with a condition (impact analysis), ONAPARC-802 - Getting issue details... STATUS . SECCOM, please review it and respond back to us. plans to work with SECCOM and OOM for security enhancements for New Delhi Study item: AI/ML-based security
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping		ONE Summit : the session agenda for ONE Summit 2024 has been published, https://events.linuxfoundation.org/one-summit-north-america/program/schedule/ . APRIL 29 - MAY 1, 2024 \| IN-PERSON LFN DTF May 2-3 following ONE Summit

Zoom Chat Log

00:12:09 Byung-Woo Jun (Ericsson): https://lf-onap.atlassian.net/wiki/display/Meetings/TSC+2024-02-01
00:27:35 Andreas Geissler (DT): https://lf-onap.atlassian.net/wiki/display/DW/Feedback+for+OOM
00:48:48 Toine SIEBELINK (EST): https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26426

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.

1
00:11:26.770 --> 00:11:28.120
Paweł Pawlak: Hello! Good morning.

2
00:11:29.620 --> 00:11:34.650
Byung-Woo Jun (Ericsson): Hi, Pablo! Hi, Mul! Hey. Mr. Luis?

3
00:11:34.730 --> 00:11:47.029
LJ Illuzzi: Hey, folks? Yeah, this is yes. Hi, yeah, quick. Update. Sandra had an emergency. So I was asked if I could cover the meeting for today. So here I am.

4
00:11:47.340 --> 00:11:53.329
Byung-Woo Jun (Ericsson): Okay, I see. I see. Okay, thank you for joining us. Oh, absolutely, of course.

5
00:11:55.060 --> 00:12:00.599
LJ Illuzzi: If if somebody can send me a link to the meeting minute the agenda, that would be great.

6
00:12:01.610 --> 00:12:09.659
Byung-Woo Jun (Ericsson): Okay, I can send you to. Okay, yeah, you could drop it in the chat if you'd like. Yeah, I'm doing now. So perfect. Thank you.

7
00:12:09.790 --> 00:12:17.969
Byung-Woo Jun (Ericsson): I just did. This is the was Sandra made. And I updated for some topic. And so anyway, so

8
00:12:17.990 --> 00:12:19.379
LJ Illuzzi: okay, great

9
00:12:22.040 --> 00:12:31.179
Byung-Woo Jun (Ericsson): sorry we can't.

10
00:12:31.360 --> 00:12:33.300
Byung-Woo Jun (Ericsson): Umhm. Okay, no problem.

11
00:12:41.530 --> 00:12:58.169
LJ Illuzzi: The one item I'm seeing from Sandra, the Lfn Cross organization updates. Absolutely. Yeah.

12
00:14:24.120 --> 00:14:28.309
Byung-Woo Jun (Ericsson): Can you? Can you share? Can you share the meeting? Note?

13
00:14:28.490 --> 00:14:32.290
LJ Illuzzi: I can. Yes, I can. Yeah. Give me 1 s.

14
00:15:03.000 --> 00:15:06.560
LJ Illuzzi: do you? Do you typically start with the anti-trust policy

15
00:15:07.720 --> 00:15:11.749
Byung-Woo Jun (Ericsson): user to them? Yeah, okay, like that. Yeah.

16
00:15:11.990 --> 00:15:25.289
LJ Illuzzi: So Hi, everybody. I am filling in for Sandra for this week. she, she has some kind of an emergency. I don't have any details. but I was asked about 10 min ago if I could.

17
00:15:25.520 --> 00:15:39.100
LJ Illuzzi: cover this meeting. And I'm happy to do that. So let's start, and I'll I'm sorry my name is LJ. Luzzy, I am with the Linux Foundation networking, and I am a technical community architect. Some I know

18
00:15:39.390 --> 00:15:41.050
LJ Illuzzi: lot of you folks on the call

19
00:15:42.030 --> 00:15:53.829
LJ Illuzzi: we start. Community meetings are reviewing the Linux Foundation anti-trust policy. The policy is important where multiple companies, including potential industry competitors, are participating in meetings.

20
00:15:54.060 --> 00:16:04.670
LJ Illuzzi: Please review the policy, and if you have questions, contact your company legal counsel. members of the Lf. May also contact Andrea up to Grove, affirm Jerry Smir up to Grove, Llp.

21
00:16:04.900 --> 00:16:09.560
LJ Illuzzi: Which provides legal counsel to the Lf. Alright.

22
00:16:10.210 --> 00:16:13.079
LJ Illuzzi: So here's the agenda.

23
00:16:13.410 --> 00:16:14.920
LJ Illuzzi: And

24
00:16:14.960 --> 00:16:31.020
LJ Illuzzi: again I'm pretty pretty fresh here, so I'm not gonna be able to do the Lfn Cross organizational updates that was on the agenda for Sandra. So I'm gonna hand it off to you. Folks. Go on mute and just let me know how I could help.

25
00:16:31.300 --> 00:16:32.360
Byung-Woo Jun (Ericsson): Okay.

26
00:16:32.590 --> 00:16:55.769
Byung-Woo Jun (Ericsson): next topic. Tcc, on a reason update. I put Pabo your name because II reason I'm saying is, last week, we inform Tsc members about this. But you, you know, have suggestion. So any okay, pabu, you can.

27
00:16:56.490 --> 00:17:00.269
Paweł Pawlak: This is our regular policy that we support

28
00:17:00.440 --> 00:17:03.119
Paweł Pawlak: n, minus one release. Right?

29
00:17:03.620 --> 00:17:13.109
Paweł Pawlak: So even if we have a situation that there is a problem, if A. F certificates for some older releases.

30
00:17:13.440 --> 00:17:15.470
Paweł Pawlak: We cannot.

31
00:17:15.589 --> 00:17:19.970
Paweł Pawlak: We we are unable to support multiple releases back.

32
00:17:20.200 --> 00:17:23.870
Paweł Pawlak: So as stated here. So

33
00:17:24.089 --> 00:17:35.930
Paweł Pawlak: all honor releases prior to London are broken because of this issue with Af. And and the our consumers are are encouraged.

34
00:17:36.220 --> 00:17:39.859
Paweł Pawlak: Persuade, persuaded, or you know.

35
00:17:40.100 --> 00:17:45.350
Paweł Pawlak: or even forced to move towards London plus right. This is this is the message.

36
00:17:45.540 --> 00:17:53.660
Paweł Pawlak: And this is our policy for multiple releases back. So this is really not nothing new for for the onup community.

37
00:17:54.790 --> 00:18:04.610
Byung-Woo Jun (Ericsson): So that means power, though. We don't have to do any special app because we have a default policy for supporting N minus one on it releases

38
00:18:04.690 --> 00:18:34.420
Byung-Woo Jun (Ericsson): so documentation architecture. Come, II changed the Wiki page, I indicating this, but we don't have the special announcement because we we do our business as usual, because currently we have we working on the New Daily. But once you're London is N minus checkpoint action point, we don't have to do anything right.

39
00:18:35.560 --> 00:18:38.399
The only thing that we could do is maybe to draft

40
00:18:38.690 --> 00:18:43.119
Paweł Pawlak: some some dedicated email message

41
00:18:43.220 --> 00:18:54.209
Paweł Pawlak: to our consumers. the ones that are not participating in the TSC. Just to inform them that. Okay, we have this situation. So if they are not running

42
00:18:54.390 --> 00:18:56.510
Paweł Pawlak: London plus.

43
00:18:56.590 --> 00:19:02.940
Byung-Woo Jun (Ericsson): then may they may experience some difficulties with this af certificate expiration, right?

44
00:19:03.870 --> 00:19:11.189
Paweł Pawlak: Maybe just just. You know, the best would be to to have everyone participating actively. But there are some

45
00:19:11.330 --> 00:19:23.579
Paweł Pawlak: consumers that are not that much actively participating and and just to to let them know that this is something that that we observe, and in the remedies to to upgrade simply.

46
00:19:23.850 --> 00:19:26.579
Byung-Woo Jun (Ericsson): we'll send it to owner discussion

47
00:19:26.610 --> 00:19:28.530
Byung-Woo Jun (Ericsson): or some other other channel.

48
00:19:29.210 --> 00:19:33.879
Byung-Woo Jun (Ericsson): Which email are the address or groups we want to send.

49
00:19:33.970 --> 00:19:42.150
Paweł Pawlak: To be honest, I don't know. Maybe I could check if the the consumers that we have in mind.

50
00:19:42.520 --> 00:19:45.829
Paweł Pawlak: I'm thinking about the spark New Zealand right

51
00:19:46.160 --> 00:19:56.119
Byung-Woo Jun (Ericsson): communication. They already know about this, but the email will be better communication, maybe.

52
00:19:56.710 --> 00:19:58.170
Paweł Pawlak: and

53
00:19:58.250 --> 00:20:01.720
Paweł Pawlak: I don't know about Canada. What is the status on their side

54
00:20:01.810 --> 00:20:04.179
Paweł Pawlak: because there is no I

55
00:20:04.210 --> 00:20:14.570
Byung-Woo Jun (Ericsson): kind of successor. Well, China, mobile, China telecom, they know very well because they contribute. They. So we have team members

56
00:20:14.790 --> 00:20:17.810
Paweł Pawlak: working with us at the T sea level. So

57
00:20:17.820 --> 00:20:25.050
Paweł Pawlak: I'm sure this is nothing nothing new for them. I'm only thinking about the ones that that we we know that

58
00:20:25.110 --> 00:20:30.339
Paweł Pawlak: are using on up consuming it right? And they joined our our

59
00:20:30.650 --> 00:20:40.210
Paweł Pawlak: Tc last year to to present their feedback. So we know that they are using it. And and I think it's good to to simply let them know. Right?

60
00:20:40.500 --> 00:20:42.029
Byung-Woo Jun (Ericsson): Okay, okay.

61
00:20:42.510 --> 00:20:53.679
Byung-Woo Jun (Ericsson): Okay, we can discuss offline, you know, who's the okay? Okay next, Louise, can I share my screen? The just? If you don't mind.

62
00:20:55.310 --> 00:21:01.119
Byung-Woo Jun (Ericsson): you can stop sharing. I can share my thank you. Thank you.

63
00:21:02.610 --> 00:21:04.870
Byung-Woo Jun (Ericsson): Let me know if you see my screen.

64
00:21:05.070 --> 00:21:14.060
Byung-Woo Jun (Ericsson): Okay, this one kind of acting release manager on behalf of the Pride, for now.

65
00:21:14.480 --> 00:21:26.760
Byung-Woo Jun (Ericsson): So the update last week we asked to update the project status. And I noticed the Pto. They started updating project status key updates and benefit. Thank you so much.

66
00:21:26.980 --> 00:21:30.900
Byung-Woo Jun (Ericsson): Here, if we click this. And this is the

67
00:21:31.400 --> 00:21:47.700
Byung-Woo Jun (Ericsson): many of the you know, active, you know, active Pto, and they updated their project chart version and stats state, and then, active or not, I'm going to add some additional check, and they already there. Thank you. And also

68
00:21:47.950 --> 00:21:50.029
Byung-Woo Jun (Ericsson): they start the feeling of the

69
00:21:50.170 --> 00:21:59.800
Byung-Woo Jun (Ericsson): the key updates and benefit. Okay, so you will come if you don't have any changes. And they just put the note changes like Fiakra, dmf.

70
00:21:59.830 --> 00:22:01.759
Byung-Woo Jun (Ericsson): so we're, gonna you know.

71
00:22:01.990 --> 00:22:17.359
Byung-Woo Jun (Ericsson): talk to Peter next Monday meeting, and they can do so if they have no changes, they just send up with no changes. But they, we need to know this information to forming the to form the release content matter later on. Okay.

72
00:22:17.400 --> 00:22:20.019
Byung-Woo Jun (Ericsson): okay, that's the one. So

73
00:22:20.070 --> 00:22:47.350
Byung-Woo Jun (Ericsson): the other one II was. I wasn't the meeting. And then someone asked about the What's the name of the old release after a new daily I think the we agreed to name it. Oslo. Is that correct? Yeah. Oslo will be the, you know. I just put a note here because to refresh our memory. But we stole Oslo. So okay.

74
00:22:48.630 --> 00:22:59.940
Byung-Woo Jun (Ericsson): Andrews, I put some edge a pt, update. I put this one, and then you can lead us, Danny's here. With Andrews Andrews, you can.

75
00:23:00.210 --> 00:23:06.539
Byung-Woo Jun (Ericsson): Yeah. So that that is unfortunately, not here. Okay.

76
00:23:06.600 --> 00:23:08.080
Andreas Geissler (DT): yeah. So

77
00:23:08.410 --> 00:23:21.939
Andreas Geissler (DT): yeah. So I mean, II noticed that or I have told that already, a couple of weeks ago, a month ago, even in the time when we had

78
00:23:22.180 --> 00:23:30.200
Andreas Geissler (DT): the Montreal release. That the Sdn C could not be updated because

79
00:23:30.260 --> 00:23:40.439
Andreas Geissler (DT): Sdn C in the stnc one interface was disabled or removed, which was to be one interface.

80
00:23:40.650 --> 00:23:42.940
Andreas Geissler (DT): This was used by.

81
00:23:43.050 --> 00:23:50.680
Andreas Geissler (DT): I think, all of the clients it's mostly it's so and or the most critical one is SO,

82
00:23:50.990 --> 00:24:01.460
Andreas Geissler (DT): and what I wanted to now coordinate together with our team, which would like to

83
00:24:01.880 --> 00:24:11.020
Andreas Geissler (DT): correct or to to now implement the changes needed for the new or the the the changed interface.

84
00:24:11.100 --> 00:24:16.750
Andreas Geissler (DT): We wanted to arrange some some meeting together with the Sdn. C. Team.

85
00:24:16.850 --> 00:24:27.019
Andreas Geissler (DT): but I cannot get hold on on Dan or someone from the call centric team who is doing usually the implementation

86
00:24:27.110 --> 00:24:38.479
Andreas Geissler (DT): not not the code. No, not sorry. Not quote centric. the team High Street debt, High High Street technology, I think, was doing it.

87
00:24:38.670 --> 00:24:48.650
Andreas Geissler (DT): So I sent mail. II check tried to get him via slack, but at the moment no reaction. So he's also not here today.

88
00:24:49.210 --> 00:25:03.680
Andreas Geissler (DT): So we start. We will start to investigate what to do. But I think there. So our we suspect that there will be also some changes still needed in Sdn. C. As we have seen it.

89
00:25:03.800 --> 00:25:20.570
Andreas Geissler (DT): But anyway, we want to co coordinate that now. And to get a newer release of Sdn see into the own up deployments. So otherwise we are stuck with the one basically from

90
00:25:20.650 --> 00:25:34.620
Andreas Geissler (DT): the London release. Yeah. So the official or, yeah. So the London release is also the Montreal release and but we could not up, as it could not be updated. As I said, yeah.

91
00:25:34.710 --> 00:25:54.559
Byung-Woo Jun (Ericsson): So we wait for Dan. And then if someone can contact, then so I'm gonna send separate email to Dan and then CC engine. And then we need to resolve this one. We need a new interfaces. I'm gonna read this way for now. So Action Point and you are already doing it. So

92
00:25:54.590 --> 00:25:59.749
Byung-Woo Jun (Ericsson): I'm going to put coordinate you already doing is send the email on twent, and just waiting for

93
00:26:00.140 --> 00:26:06.279
Byung-Woo Jun (Ericsson): confirmation from Sdn. C. Danielsi kimoni. So we'll see. Okay, thank you. Okay.

94
00:26:09.090 --> 00:26:14.680
Byung-Woo Jun (Ericsson): Next one. Can you debrief a little bit about this. See? Icd.

95
00:26:19.240 --> 00:26:21.079
Byung-Woo Jun (Ericsson): Angeles, I cannot hear you.

96
00:26:21.310 --> 00:26:38.529
Andreas Geissler (DT): Yeah. Sorry. Yeah. I had. Or we have reviewed, or I'd read review the suggestions and the findings from Luis Lee. And and I created

97
00:26:38.560 --> 00:26:50.820
Andreas Geissler (DT): page actually to collect all the to collect the feedback. And I just before this meeting. I sent him back a mail

98
00:26:50.870 --> 00:27:01.520
Andreas Geissler (DT): with our findings and our let's say, feedback. So let's say there there is not. So

99
00:27:01.690 --> 00:27:09.580
Andreas Geissler (DT): there is a couple of interesting parts which he has found, but which are partly already solved in the new release.

100
00:27:09.990 --> 00:27:15.080
Andreas Geissler (DT): And yeah. So basically,

101
00:27:15.140 --> 00:27:26.610
Andreas Geissler (DT): as I said, we gave feedback, and sent him. Now the link to our page which we have created just can put it into this, into the

102
00:27:26.990 --> 00:27:32.860
Andreas Geissler (DT): chat, the link so that you can add that. Then to the

103
00:27:34.130 --> 00:27:39.839
Byung-Woo Jun (Ericsson): okay, okay, if you put the chat. Okay.

104
00:27:41.630 --> 00:27:48.380
Byung-Woo Jun (Ericsson): okay, that's good. Let me put this here. Okay, thank you. So here.

105
00:27:50.520 --> 00:27:55.300
N.K. Shankaranarayanan: Just a comment. Thanks, thanks, Andreas, for for creating the page. I think

106
00:27:55.500 --> 00:27:59.320
N.K. Shankaranarayanan: it's good to have this sort of documented

107
00:27:59.630 --> 00:28:06.259
N.K. Shankaranarayanan: and and and like you said you, most of the comments are probably not new to you. But

108
00:28:06.750 --> 00:28:19.550
Andreas Geissler (DT): but it's it's important feedback that someone's yeah. Yeah. I totally agree. It's always valuable, valuable feedback, and it's good to get that information.

109
00:28:19.600 --> 00:28:27.510
Andreas Geissler (DT): I mean what already what we had also. Now, we got also now, feedback in in the Om meeting

110
00:28:27.590 --> 00:28:53.830
Andreas Geissler (DT): from Tata which we are hopefully trying to also include into the deployment and into the changes and even Tata, most likely or hopefully, will also contribute their changes and their improvements of the code. So so we had this, and last week. A presentation

111
00:28:54.020 --> 00:29:01.900
Andreas Geissler (DT): from the group. And they will then hopefully, then also try to improve our code and our

112
00:29:02.070 --> 00:29:10.590
Byung-Woo Jun (Ericsson): yeah deployment. Yeah, I think that they can use from Tata, I think. Most likely. They gonna start officially contribute to also.

113
00:29:10.770 --> 00:29:19.109
Byung-Woo Jun (Ericsson): But we are still talking. If they can do anything for new Delhi. But they anyway, they're gonna share their what they have done

114
00:29:19.240 --> 00:29:30.600
Byung-Woo Jun (Ericsson): with Andrew. So we know some. And you know, input. So once they they already share the day the architecture and enhancement slide for security and the logging blah blah blah!

115
00:29:30.640 --> 00:29:46.169
Byung-Woo Jun (Ericsson): So that's good thing. And then I think that they are still working their enhancement internally. Then, once they internally sorted out, then they can, you know, contribute to own it to me, I guess the most likely so

116
00:29:46.580 --> 00:29:51.060
Byung-Woo Jun (Ericsson): possible. That's my thing. Is that my understanding correct, Angie?

117
00:29:53.410 --> 00:30:03.140
Andreas Geissler (DT): Yes. So that's the plan. But if we have already some enhancements which would be useful beforehand. We are maybe try to

118
00:30:03.190 --> 00:30:09.179
Andreas Geissler (DT): include that even if they are not contributing it actively, but they want to share some

119
00:30:09.250 --> 00:30:15.859
Andreas Geissler (DT): some improvements they have done, and maybe then I can incorporate that, even if they are not actively

120
00:30:16.210 --> 00:30:19.149
contributing it with their.

121
00:30:19.210 --> 00:30:23.940
Andreas Geissler (DT): But let's see, so Oslo, is there perspective where they can

122
00:30:24.210 --> 00:30:39.390
Byung-Woo Jun (Ericsson): by themselves, then, have some resources available for us? Yeah. So once they share that, you know they are already sharing with you that you can schedule your phone or enhancement. I think that's a good thing. Okay, good.

123
00:30:39.690 --> 00:30:40.670
Byung-Woo Jun (Ericsson): Thank you.

124
00:30:40.940 --> 00:30:42.960
Byung-Woo Jun (Ericsson): Anything else. There's no main.

125
00:30:43.170 --> 00:30:48.939
N.K. Shankaranarayanan: Who's the main int of contact for this? And Tata, who's keeps track of awareness.

126
00:30:50.480 --> 00:30:52.060
Byung-Woo Jun (Ericsson): which which content

127
00:30:52.170 --> 00:31:03.760
Byung-Woo Jun (Ericsson): for for Tata, a person, Matthias, he's the main guy something like that. Yeah.

128
00:31:04.160 --> 00:31:15.480
Byung-Woo Jun (Ericsson): you can check in the Oom meeting. He's the one present.

129
00:31:15.680 --> 00:31:21.519
Byung-Woo Jun (Ericsson): So we're gonna move on to next one. Andrew, if you don't have any additional comments. Is that okay?

130
00:31:22.880 --> 00:31:23.570
Andreas Geissler (DT): Yep.

131
00:31:23.770 --> 00:31:36.840
Byung-Woo Jun (Ericsson): okay. So stop company. Update. Second, the I think any open an Lfit ticket for Github vulnerability issues. I think, Jessica.

132
00:31:37.010 --> 00:31:47.439
Byung-Woo Jun (Ericsson): she responded. I think she has some. Probably. Jessica. Could you elaborate?

133
00:31:47.480 --> 00:32:08.739
Jessica Wagantall: Yeah, it's mostly potential security attack when related to via Github credentials. But we brought this in in the release engineering team. And this should not affect us. Since

134
00:32:08.920 --> 00:32:28.740
Jessica Wagantall: credentials for organization, ownership are given just internally and anything related to job triggers or Github actions are handled via a different credential that doesn't have organization rights. It just has repo ripple permissions.

135
00:32:28.810 --> 00:32:45.330
Jessica Wagantall: internally, the credentials are still rotated every time. We get to know about any data leak or whenever something else changes in the organization. So I think we should be going on this.

136
00:32:45.600 --> 00:32:52.149
Byung-Woo Jun (Ericsson): Hmm, okay, thank you. You know, II put as a result. Thank you. Jessica. Okay, thank you very much.

137
00:32:53.040 --> 00:32:55.080
Byung-Woo Jun (Ericsson): Next item,

138
00:32:55.120 --> 00:33:13.799
Byung-Woo Jun (Ericsson): Akom. Yakra, he's Pto of the Dmap, and we discuss this matter with him, and also in oem with Andrew. So he initiate the Dmap message router that this you know, he initiate the application in New Delhi

139
00:33:13.910 --> 00:33:19.439
Byung-Woo Jun (Ericsson): by following the unmaintained project. Tradition step one. I'm gonna show you in a minute.

140
00:33:19.700 --> 00:33:29.850
Byung-Woo Jun (Ericsson): And the step 2 and 3 and 4, our come oem have found impact project and some dependencies. So analyzing the impact. So

141
00:33:30.330 --> 00:33:47.070
Byung-Woo Jun (Ericsson): so Pto should analyze their project impact for new daily how to remove the decouple or Dmf Mr. From their project if they can. So, based on this condition outcome conditionally approved.

142
00:33:47.450 --> 00:34:00.919
Byung-Woo Jun (Ericsson): So this is the kind of impact you know, depends on impact. This is the kind of owner of the pricing mechanism. We we review that. And then this is additional

143
00:34:01.650 --> 00:34:07.910
Byung-Woo Jun (Ericsson): item we need to discuss. Excuse me, excuse me. So I just put the conditional approval.

144
00:34:08.179 --> 00:34:16.559
Approved this, based on the impact on Pto, so at next Monday we're going to discuss about this Ptos.

145
00:34:16.719 --> 00:34:24.630
Byung-Woo Jun (Ericsson): if they can do or not. So then, based on the they can do. If they can do, remove the dependency from

146
00:34:24.690 --> 00:34:33.429
Byung-Woo Jun (Ericsson): New Delhi, then we can safely duplicate the amounts. That's the current plan. If you look at this.

147
00:34:34.810 --> 00:34:56.600
Byung-Woo Jun (Ericsson): we are following this on, maintained the project the retirement and tradition. So as a first step the Pto Fiacra. He initiate this pro application process and the informed outcome. And then I send the separate email to second, and the second should be moved. The audit, you know, the review.

148
00:34:56.739 --> 00:35:11.979
Byung-Woo Jun (Ericsson): the impacts, security perspective. And then after that outcome, we're review photo and 2, 3, 4. We're hand over outcome. And then we're gonna report back to Tsc. And TS. The, you know, the

149
00:35:12.030 --> 00:35:18.209
Byung-Woo Jun (Ericsson): make some recommendation. So we did follow this process for

150
00:35:18.270 --> 00:35:29.500
Byung-Woo Jun (Ericsson): one for Cps and the other. you know the one of the components. So we know how to do it. So basically, okay, so that's what we are going to do so here.

151
00:35:30.330 --> 00:35:31.219
but the

152
00:35:31.500 --> 00:35:43.989
Byung-Woo Jun (Ericsson): already initiated so, Andre, you talk, we talk about this. And then if if they can remove the dependency of email, Mr. I think we are

153
00:35:44.060 --> 00:35:51.139
Byung-Woo Jun (Ericsson): good, but we have to still have information from Ptos. Andrew. Do you have any other? Some more details? Yeah.

154
00:35:51.440 --> 00:35:55.280
Andreas Geissler (DT): some comment. Yes. So

155
00:35:55.580 --> 00:36:01.289
Andreas Geissler (DT): I know. So I have the overview about at least from the

156
00:36:01.840 --> 00:36:06.590
Andreas Geissler (DT): I have the the screenshot basically

157
00:36:06.680 --> 00:36:07.830
Andreas Geissler (DT): for

158
00:36:08.090 --> 00:36:15.840
Andreas Geissler (DT): of the existing let's say message router users

159
00:36:16.490 --> 00:36:18.910
in the feedback

160
00:36:19.770 --> 00:36:25.159
Andreas Geissler (DT): which which was sent beforehand, but just create a new one.

161
00:36:25.340 --> 00:36:27.989
Byung-Woo Jun (Ericsson): and I know we had

162
00:36:28.060 --> 00:36:35.149
Andreas Geissler (DT): so in. And so I know that the the the policy component is already working on that.

163
00:36:35.380 --> 00:36:42.749
Andreas Geissler (DT): I know that we from Dt will work on that on the so side

164
00:36:42.830 --> 00:36:47.509
and most likely also on the A and the AI side

165
00:36:47.560 --> 00:36:59.449
Andreas Geissler (DT): and on on some of the DC components to get rid of that. But there, there are still some components which are pending like the Stc

166
00:36:59.540 --> 00:37:06.600
Andreas Geissler (DT): And a couple of DC components. But I, as I said, I put this just update the

167
00:37:06.710 --> 00:37:10.400
Andreas Geissler (DT): the screenshot from

168
00:37:10.550 --> 00:37:16.999
Andreas Geissler (DT): Kia Ali actually to show that what? Who is impacted on that? So in the feedback.

169
00:37:17.040 --> 00:37:18.730
Byung-Woo Jun (Ericsson): how about the Holmes?

170
00:37:19.430 --> 00:37:22.680
Andreas Geissler (DT): Holmes is as well. So homes and Nba

171
00:37:22.820 --> 00:37:25.439
Andreas Geissler (DT): they also, and be affected. Yes.

172
00:37:26.480 --> 00:37:32.089
Byung-Woo Jun (Ericsson): So this one the Stc. We don't have Pto. we have 2.

173
00:37:32.120 --> 00:37:51.000
Andreas Geissler (DT): And actually, though, if it's great, you doing a 9% years. So anyway, I know that I know that Stc had done something. But there's still, one small thing I have think has to to be done. But I'm not 100% sure, because I know that they have done some

174
00:37:51.000 --> 00:38:07.309
Andreas Geissler (DT): some implementations or some changes. But but nevertheless, everything we have to check that. Yeah, okay, great. This is the impacted project. I think the Andrew is still working on it. And then II saw those policy team they

175
00:38:07.460 --> 00:38:26.650
Byung-Woo Jun (Ericsson): and creating cheetah ticket. That's great. That's great. So once all the impacted project under the relationship and dependency sort it out. We can process next steps. That's the plan. But Theakra initiate the

176
00:38:26.770 --> 00:38:30.200
Byung-Woo Jun (Ericsson): application process. Okay for information.

177
00:38:30.250 --> 00:38:34.950
Byung-Woo Jun (Ericsson): So I'm gonna Pablo, I'm gonna talk this at the next Tuesday

178
00:38:35.150 --> 00:38:44.639
Paweł Pawlak: the second. And then if you have any concern from security perspective. We can, you know, address to is that right?

179
00:38:44.830 --> 00:38:55.650
Byung-Woo Jun (Ericsson): And then also, the you know outcome. We plan to work with the second and an OM. For security enhancement for a new daily. And then I think Andrew has some plan.

180
00:38:55.750 --> 00:39:04.360
Byung-Woo Jun (Ericsson): and then also we are studying about AI. A IMA. Very security. So still a very beginning stage. But since the

181
00:39:04.790 --> 00:39:25.810
Byung-Woo Jun (Ericsson): in new daily China, mobile China telecom, they, and also how way they put a lot of intent based AI based the the transformation and also configuration optimization for orchestration. So we as part of the trend we are starting the aim. Everybody security, too.

182
00:39:25.810 --> 00:39:41.240
Byung-Woo Jun (Ericsson): Okay, and the Medusa. And then Pablo and the Emmy and Maggie and Tony there we are working. We know this issue. So okay, so and we're gonna I'm gonna work with the second for this, too. Okay.

183
00:39:41.620 --> 00:39:48.910
Byung-Woo Jun (Ericsson): okay, so should I back to you. Probably. Can you address about the upcoming event and housekeeping?

184
00:39:50.560 --> 00:39:53.330
Paweł Pawlak: Yeah, sure. So

185
00:39:53.430 --> 00:39:58.170
Paweł Pawlak: in fact. one more item, they I haven't added here. But

186
00:39:58.260 --> 00:40:05.060
Paweł Pawlak: we need to update the welcome wiki. Because it still reflects London release.

187
00:40:05.470 --> 00:40:09.030
Paweł Pawlak: I don't know if it's like that that that

188
00:40:10.040 --> 00:40:14.820
Paweł Pawlak: this is that this was done by Lf. Pen team. Or

189
00:40:15.840 --> 00:40:19.740
Paweł Pawlak: how was how was it organized? Maybe it was release manager, or maybe

190
00:40:19.750 --> 00:40:23.590
Paweł Pawlak: maybe not. I didn't know who was doing it, but usually it was changing.

191
00:40:23.970 --> 00:40:27.470
Paweł Pawlak: So as we F. Montreal

192
00:40:28.050 --> 00:40:32.450
Paweł Pawlak: in the air, right? So maybe it's good to to to

193
00:40:33.160 --> 00:40:36.679
Paweł Pawlak: made some adjustments in the in the welcome Wiki, right?

194
00:40:37.050 --> 00:40:56.799
Byung-Woo Jun (Ericsson): II put in this Tsc activity, is there? Okay? Or you want? I don't know if you've seen the communication. But Kenny's moving

195
00:40:56.850 --> 00:41:00.609
Paweł Pawlak: to Lf responsibilities, right?

196
00:41:00.850 --> 00:41:08.740
Paweł Pawlak: So will be supported by another colleague. I hope maybe next week we we would have

197
00:41:09.030 --> 00:41:20.580
Paweł Pawlak: this person joining us right. Hmm! We had a very long er good good experience with with Kenny from the from the very beginning of this project.

198
00:41:20.960 --> 00:41:22.870
Paweł Pawlak: So

199
00:41:23.160 --> 00:41:27.589
Paweł Pawlak: we'll be missing, Kenny a lot, probably. But

200
00:41:28.200 --> 00:41:35.690
Paweł Pawlak: okay, there are new challenges for Kenny. So we need to shark any with other projects. And and yeah.

201
00:41:36.630 --> 00:41:42.480
Paweł Pawlak: there is an item for the

202
00:41:43.520 --> 00:41:52.839
Paweł Pawlak: or the housekeeping, and yes, right? So it will be followed by the some additional on that meeting.

203
00:41:53.160 --> 00:42:02.859
Paweł Pawlak: So I don't know, guys. If you plan, please check for the for the agenda for the only summit, but it will be the Dtf. For the my

204
00:42:02.870 --> 00:42:04.230
Paweł Pawlak: second and third.

205
00:42:04.700 --> 00:42:06.279
Paweł Pawlak: so probably

206
00:42:06.350 --> 00:42:10.739
Paweł Pawlak: good time to think about the topics that you could cover.

207
00:42:10.950 --> 00:42:26.609
Paweł Pawlak: and and then to propose those topics. I'm not sure if he have already some deadline for submission. It's a bit too early. But but we started at the second some discussion on on the topics you'd like to to cover. We have already some small list.

208
00:42:26.720 --> 00:42:30.670
Paweł Pawlak: So maybe looking at the Ptl. Side looking at the

209
00:42:30.730 --> 00:42:35.209
Paweł Pawlak: some some other subcommittees, or, you know.

210
00:42:35.600 --> 00:42:40.230
Paweł Pawlak: teams in general. think about the topics you would like to to cover.

211
00:42:40.400 --> 00:42:43.480
Paweł Pawlak: And yeah, there is still some time to

212
00:42:43.660 --> 00:42:49.539
Byung-Woo Jun (Ericsson): to consider it. Great good comment. Pablo, for information yesterday, Sandra

213
00:42:49.820 --> 00:43:02.050
Byung-Woo Jun (Ericsson): and Donwong and the myself. We talked about this one, and then, Sandra, I think, she said, she will follow up. What's the deadline for the topic suggestion.

214
00:43:02.050 --> 00:43:21.750
Byung-Woo Jun (Ericsson): And also we need to have a program what? The manager, I think team, will he volunteer last one? But, he said, there will be last one. So we need to find some other person to handle to. You know, the programming manager. So okay, we can discuss for the next time.

215
00:43:22.480 --> 00:43:27.800
Paweł Pawlak: By the way, because this meeting on on Wednesday appears to in my calendar

216
00:43:27.960 --> 00:43:37.650
Paweł Pawlak: probably 1 h too late. Right? That's why II when I drink yesterday. In fact, I think it was really after the meeting.

217
00:43:37.980 --> 00:43:53.390
Byung-Woo Jun (Ericsson): Right? Yeah.

218
00:43:54.250 --> 00:44:00.260
Byung-Woo Jun (Ericsson): alright. You run through. We run through the old items for the agenda.

219
00:44:01.810 --> 00:44:05.410
Byung-Woo Jun (Ericsson): Are there any additional topics you would like to cover today?

220
00:44:07.210 --> 00:44:12.089
Byung-Woo Jun (Ericsson): Anybody I talked, though II had but

221
00:44:12.190 --> 00:44:20.099
Byung-Woo Jun (Ericsson): anybody from Tsc. Member you have any. So we have any volunteers for Pts. Monday meeting to to be

222
00:44:20.540 --> 00:44:25.390
Paweł Pawlak: delete delete this meeting we already had twan we already had.

223
00:44:27.520 --> 00:44:38.170
Byung-Woo Jun (Ericsson): so I mean the I asked. I sent the email to Peter, but I haven't heard any. Any. The you know volunteer. That means, maybe I'm gonna

224
00:44:38.860 --> 00:44:46.990
Byung-Woo Jun (Ericsson): do it for topic for a Ptr topic so Andrea's I mentioned about the dependency. Okay, the

225
00:44:47.130 --> 00:44:53.830
Byung-Woo Jun (Ericsson): that's why I can. I can create it. The the the meeting agenda for next week and about the

226
00:44:53.930 --> 00:45:09.979
Byung-Woo Jun (Ericsson): Dmap Mr. Dependencies, that's we. Gonna we can put topic for discussing at the Pta. And then Andrews, you know, need to be there another Pto and then hope then, join the Ptr, so I'm gonna put Sdn C topic

227
00:45:10.320 --> 00:45:12.800
Byung-Woo Jun (Ericsson): and the the

228
00:45:13.160 --> 00:45:24.549
Byung-Woo Jun (Ericsson): team a message. It out issue 2 issues into Pto. so I hope that there's a volunteer from Pts. But otherwise. as last week and I can, I can act in

229
00:45:25.120 --> 00:45:29.560
well, then, all power you want to do. It's up to you

230
00:45:31.810 --> 00:45:34.860
Byung-Woo Jun (Ericsson): and to do what? Exactly pittier meeting.

231
00:45:34.950 --> 00:45:36.400
Byung-Woo Jun (Ericsson): hosting, hosting.

232
00:45:36.980 --> 00:45:51.800
Paweł Pawlak: Well, okay, I can volunteer for the next Monday to to host. Right?

233
00:45:52.020 --> 00:46:07.100
Byung-Woo Jun (Ericsson): III don't mind. I'm doing it. But in case you cannot, then no, but we should switch guys. I don't want to put anything on your shoulders should be like passing, switching

234
00:46:07.300 --> 00:46:13.240
Paweł Pawlak: responsibility as long as we have. You know, we don't have

235
00:46:13.260 --> 00:46:20.640
Byung-Woo Jun (Ericsson): success or full successor of of David sounds good to me. Okay, okay. Alright, that's it.

236
00:46:22.180 --> 00:46:26.169
Paweł Pawlak: Any ideas for the next 2 week agenda guys, any proposals

237
00:46:28.640 --> 00:46:30.310
Byung-Woo Jun (Ericsson): don't know yet.

238
00:46:30.570 --> 00:46:35.059
Byung-Woo Jun (Ericsson): Talk to next Wednesday again, Pablo, with you.

239
00:46:36.120 --> 00:46:44.569
Byung-Woo Jun (Ericsson): Are there any specific tickets that are open to Lfit

240
00:46:44.880 --> 00:46:48.500
Paweł Pawlak: that we should review, or their pending? Or, you know.

241
00:46:49.660 --> 00:46:51.479
Paweł Pawlak: is there anything that we should

242
00:46:51.860 --> 00:46:55.690
Toine SIEBELINK (EST): maybe. Pablo, yeah, thanks. How are you?

243
00:46:56.370 --> 00:46:57.430
Toine SIEBELINK (EST): It's on here.

244
00:46:57.960 --> 00:46:59.000
Byung-Woo Jun (Ericsson): Okay.

245
00:46:59.090 --> 00:47:09.930
Toine SIEBELINK (EST): I was talking to Matt. We had an issue the last 2 days with the bills we needed some new dependency in the Github actions

246
00:47:10.010 --> 00:47:20.160
Toine SIEBELINK (EST): now that has been resolved. But I asked Matt either as part of the same tickets, or maybe as a part of a new ticket. And maybe this is something we can discuss in more detail on Monday

247
00:47:20.250 --> 00:47:25.950
Toine SIEBELINK (EST): or next Thursday meeting. I don't think the Github actions job should block

248
00:47:26.280 --> 00:47:31.590
Toine SIEBELINK (EST): the the delivery. So at the moment, if the Github action fails

249
00:47:31.960 --> 00:47:43.410
Toine SIEBELINK (EST): we cannot merge the code in in garret. We have. So we have verified jobs. We still have to all the verified jobs we have in the garret.

250
00:47:43.730 --> 00:47:56.879
Toine SIEBELINK (EST): and when they pass that that's basically that should be the criteria they pass. Then then the patch should be allowed to merge. But get up actions. It's just kind of a an extra check if the the same verification would pass and get up actions as well.

251
00:47:57.100 --> 00:48:04.980
Toine SIEBELINK (EST): But since we've introduced it, there has been about 4 or 5 different issues that weren't directly related to the normal bills.

252
00:48:05.350 --> 00:48:12.209
Toine SIEBELINK (EST): But they did block us from emerging. So I've asked, can we do something about the git of action blocking

253
00:48:12.230 --> 00:48:23.960
Toine SIEBELINK (EST): the the normal bills. Can we have a way to overrule it, or can we make sure it's not not a condition anymore, anyway, that's the ticket I would like to discuss, or something I want to follow up on next week.

254
00:48:24.210 --> 00:48:25.830
Byung-Woo Jun (Ericsson): Do you have a ticket number?

255
00:48:26.220 --> 00:48:36.009
Toine SIEBELINK (EST): Yes, it's kind of related could be one. You can. You can send me offline because I'm gonna write the agenda for Pto. So 3 topics. So

256
00:48:36.150 --> 00:48:41.179
Byung-Woo Jun (Ericsson): you know Andrew's copy, and then also the DM Dmap, mo.

257
00:48:41.370 --> 00:48:54.620
Byung-Woo Jun (Ericsson): and then your your topic. Okay, if you give me one more minute or not seconds, it's in this chat. Now. So you should.

258
00:48:55.410 --> 00:49:02.989
Byung-Woo Jun (Ericsson): okay, copy link. Okay, okay, I do that. And then run the the pt, here next Monday. Okay.

259
00:49:03.480 --> 00:49:04.400
Paweł Pawlak: yeah.

260
00:49:05.250 --> 00:49:08.489
Byung-Woo Jun (Ericsson): Okay, yeah. That's it for me. Okay.

261
00:49:08.980 --> 00:49:10.749
Toine SIEBELINK (EST): hey? Thanks. Everybody. Have a good day.

262
00:49:10.800 --> 00:49:14.660
LJ Illuzzi: I'm just back next week.

263
00:49:14.810 --> 00:49:19.829
Paweł Pawlak: Thank you. Thank you. Bye.

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

Browser not supported