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

Passcode: 209247

2024 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 Software Systems
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	Muddasar Ahmed	TAC Update. https://wiki.lfnetworking.org/display/LN/2024-04-17+TAC+Minutes TSC 2024-04-25
	TCC / ONAP Liaison Updates
	Task Force Updates


Operations (40 minutes)	TSC Activities and Deadlines		LFN Booth: Features 3 main kiosks, each focused on: AI, Cloud Native Telco, and Cloud Native Automarton (Nephio). https://docs.google.com/spreadsheets/d/1JOiPasxwbcPr810TUn93bJE4OwKzU21cIWJxrBTBORY/edit?usp=sharing
	Release Status	Byung-Woo Jun	Is the Oslo schedule OK? Release Planning: Oslo TSC Voting for the Oslo schedule on May 9th.
	RelEng/Infrastructure
	PTL Updates		Recommended packages upgrades are available on the restricted Wiki. Jiras are created per project. New Delhi Package Updates Need to check NG Portal status CLM jobs. Any update? Jessica Gonzalez , ongoing. Fiete Ostkamp to provide an update about implementation progress. Update from Fiete Ostkamp : maven based jobs use the lf-infra-sonatype-clm Jenkins builder that triggers the com.sonatype.clm:clm-maven-plugin for gradle there currently is no such builder available in global-jjb Sonatype officially does not provide an equivalent plugin, but there is the Sonatype Scan Gradle Plugin that could provide similar functionality Ticket opened by Fiete: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26527 ongoing; Jessica and Fiete are discussing this.
	OOM Update	Andreas Geißler	OOM Update Most patches are in. One issue with SDNC, to be consulted with Dan. Dan Timoney needs to get involved ASAP.
	Logging Implementation Proposal	ematpil Logging_improvements_25_04.pptx	Logging Standard format is not applied by all the components, Jakarta Best Practice Proposal for Standardized Logging Fields - v2 STDOUT/STDERR is not applied by all the components. Root access issues of fluentBit
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements		ARCCOM: prepared for LFN DTF presentation.
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping	Byung-Woo Jun	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 ONAP programming committee member: Byung-Woo Jun deadline for topic submission is April 12th. The committee members will discuss the LFN DTF schedule based on the finalized topics next Monday need to add presentation topics, https://wiki.lfnetworking.org/display/LN/2024-05+LFN+Developer+Event+Sessions Byung-Woo Jun , LFN DTF presentation sessions have been scheduled at the DTF programming committee this Monday. FYI only, https://teamup.com/ksofwkj4xse7ggyioa ONAP meetings canceled next week for ONE Summit and D&TF (PTL, TSC SECCOM & ARCCOM)

Zoom Chat Log

00:11:26 Muddasar Ahmed: Visionary Statement: "We aspire to lead by example, fostering a culture of unwavering dedication to software quality and security. Through meticulous testing, continuous improvement, and proactive risk management, we aim to deliver capabilities that exceed user expectations and reinforces trust in Opensource Software."
00:11:33 Byung-Woo Jun: TSC 2024-04-25
00:11:38 Muddasar Ahmed: Our commitment to software quality and security is unwavering. We envision a culture where every member of our organization embraces these principles as essential elements of our work. To achieve this vision, we pledge to implement rigorous testing processes at every stage of development, leveraging automation and advanced tools to ensure thorough analysis of our code. Furthermore, we will prioritize continuous improvement, actively seeking feedback from users, stakeholders, and other LF communities to drive iterative enhancements. By proactively identifying and addressing potential vulnerabilities, we will fortify our software against emerging threats. Our goal is not just to meet industry standards but to set new benchmarks for excellence. Through our dedication to quality and security, we will inspire confidence in our users and demonstrate our unwavering commitment to their success.
00:20:38 Tony Hansen: Logging has been an issue since the very beginning
00:25:16 Muddasar Ahmed: Reacted to "Logging has been an ..." with thumbs up
00:43:36 Byung-Woo Jun: Tony, I sent you email for the SDNC DMaap MR dependencies.

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.

WEBVTT

1
00:00:57.920 --> 00:00:59.030
Sandra Jackson: And morning.

2
00:01:03.010 --> 00:01:04.220
Byung-Woo Jun: Hi! Good morning, Sandra!

3
00:01:36.100 --> 00:01:37.280
Byung-Woo Jun: I'm Odessa.

4
00:01:38.830 --> 00:01:39.800
Muddasar Ahmed: Morning.

5
00:01:40.170 --> 00:01:40.720
Byung-Woo Jun: 8.

6
00:01:42.510 --> 00:01:43.730
Byung-Woo Jun: We have a year

7
00:01:43.850 --> 00:01:45.560
Byung-Woo Jun: session. Yeah.

8
00:01:48.900 --> 00:01:49.600
Muddasar Ahmed: Yeah.

9
00:01:49.760 --> 00:01:51.640
Muddasar Ahmed: working from home today.

10
00:01:52.590 --> 00:01:53.000
Byung-Woo Jun: Came.

11
00:01:53.000 --> 00:01:54.949
Muddasar Ahmed: Dog is not cooperating.

12
00:02:39.440 --> 00:02:41.750
Byung-Woo Jun: I can't go on! You can't go.

13
00:02:45.150 --> 00:02:46.280
Keguang He: Hi! Duane!

14
00:02:46.570 --> 00:02:48.030
Keguang He: Good night. Everyone.

15
00:02:50.860 --> 00:02:51.710
Byung-Woo Jun: You don't.

16
00:03:05.110 --> 00:03:07.449
Sandra Jackson: Alright! Give it another minute or so. Here.

17
00:03:07.530 --> 00:03:09.059
Sandra Jackson: that's folks come in.

18
00:03:34.160 --> 00:03:35.650
Paweł Pawlak: Hello! Good morning!

19
00:03:36.550 --> 00:03:37.459
Byung-Woo Jun: Hey! How are you?

20
00:03:38.060 --> 00:03:39.300
Paweł Pawlak: Yeah, good. And you.

21
00:03:39.610 --> 00:03:40.779
Byung-Woo Jun: Good, good.

22
00:03:48.090 --> 00:03:50.900
Paweł Pawlak: Oh, we have a special guest, our Mateos, right.

23
00:03:51.760 --> 00:03:54.140
Byung-Woo Jun: That is in modest side to post.

24
00:03:54.140 --> 00:03:54.570
Mateusz Pilat (TCL): And 3.

25
00:03:54.570 --> 00:03:55.040
Byung-Woo Jun: He says.

26
00:03:55.040 --> 00:03:56.089
Mateusz Pilat (TCL): So so hi.

27
00:03:56.650 --> 00:03:57.460
Paweł Pawlak: Yes.

28
00:03:59.090 --> 00:03:59.660
Byung-Woo Jun: Bye.

29
00:04:05.560 --> 00:04:13.486
Sandra Jackson: Okay, I'll go ahead and get started with our regular announcements that are showing up that when you come into the meeting, hold on for a second.

30
00:04:13.770 --> 00:04:14.603
Paweł Pawlak: Please Sandra,

31
00:04:15.080 --> 00:04:24.059
Sandra Jackson: When you come into the meeting, the meeting is being recorded that includes chats and private chats. If you're dialed in on a telephone and need to

32
00:04:24.410 --> 00:04:28.060
Sandra Jackson: speak. You need to press Star 6 to unmute yourself.

33
00:04:28.840 --> 00:04:43.079
Sandra Jackson: And then just a reminder of the anti trust policy that we operate all of our conduct law meetings on if you have any questions about it, you can reach out to your company's legal counsel, or if you are a member of the Links Foundation.

34
00:04:43.160 --> 00:04:48.210
Sandra Jackson: You can reach out to Andrew up to grove of the firm guest up to Grove LLP.

35
00:04:50.750 --> 00:04:51.920
Sandra Jackson: Alrighty

36
00:04:55.540 --> 00:04:58.099
Sandra Jackson: Oh, good! We have a tech update today.

37
00:05:01.310 --> 00:05:06.627
Sandra Jackson: the a booth. I'll talk briefly about the booth that will be at the one summit

38
00:05:08.340 --> 00:05:12.239
Sandra Jackson: release status, our regular Ptl updates

39
00:05:12.330 --> 00:05:22.811
Sandra Jackson: and subcommittee updates, and then some housekeeping, so we can go ahead and jump into it. If if are there any questions or comments about the

40
00:05:23.460 --> 00:05:24.670
Sandra Jackson: today's agenda.

41
00:05:27.250 --> 00:05:28.010
Sandra Jackson: Okay?

42
00:05:28.110 --> 00:05:33.459
Sandra Jackson: So then I will hand the floor over to motorcyc.

43
00:05:40.330 --> 00:05:41.550
Sandra Jackson: Thank you so much.

44
00:05:43.110 --> 00:05:44.770
Muddasar Ahmed: I had to find my

45
00:05:44.780 --> 00:05:46.140
Muddasar Ahmed: unmute button.

46
00:05:46.580 --> 00:05:48.529
Sandra Jackson: No worries. Do you need to share anything?

47
00:05:48.980 --> 00:05:53.129
Muddasar Ahmed: Not really, but I can give you a quick rundown. What's the latest right now?

48
00:05:53.360 --> 00:05:53.860
Sandra Jackson: Okay.

49
00:05:53.860 --> 00:05:55.720
Muddasar Ahmed: And the last tack meeting

50
00:05:55.950 --> 00:06:02.790
Muddasar Ahmed: we, as usual, discussed, discussed, upcoming Dntf and one summit.

51
00:06:03.240 --> 00:06:05.179
Muddasar Ahmed: But there were 2 votes.

52
00:06:05.830 --> 00:06:07.150
Muddasar Ahmed: One was around

53
00:06:07.860 --> 00:06:11.700
Muddasar Ahmed: leaf incubation. There was a road to

54
00:06:11.740 --> 00:06:13.059
Muddasar Ahmed: bring leaf

55
00:06:13.510 --> 00:06:15.270
Muddasar Ahmed: at the incubation level

56
00:06:15.310 --> 00:06:16.489
Muddasar Ahmed: as a project.

57
00:06:16.520 --> 00:06:18.430
Muddasar Ahmed: and what was approved

58
00:06:19.636 --> 00:06:31.920
Muddasar Ahmed: they had presented couple of time in the tech meetings, and I think, lot of time. It is a gradual process, but in this case they have proven that they have

59
00:06:32.120 --> 00:06:35.369
Muddasar Ahmed: at all the requirements for incubation level of the project.

60
00:06:36.420 --> 00:06:39.930
Muddasar Ahmed: There was also a

61
00:06:40.510 --> 00:06:42.880
Muddasar Ahmed: approval of documentation

62
00:06:43.705 --> 00:06:46.530
Muddasar Ahmed: tech has produced documentation on

63
00:06:47.950 --> 00:06:49.270
Muddasar Ahmed: new project

64
00:06:49.340 --> 00:06:51.490
Muddasar Ahmed: induction and

65
00:06:52.276 --> 00:06:53.589
Muddasar Ahmed: project promotion.

66
00:06:53.740 --> 00:07:04.060
Muddasar Ahmed: So there are some goals set up. Those documentation has been revised last time. I guess it was 2021 when some of those processes were created

67
00:07:04.520 --> 00:07:05.280
Muddasar Ahmed: deck.

68
00:07:05.380 --> 00:07:11.170
Muddasar Ahmed: and the member companies felt that documentation should be reviewed. So we did review.

69
00:07:11.763 --> 00:07:13.630
Muddasar Ahmed: Made some changes to it.

70
00:07:13.910 --> 00:07:15.720
Muddasar Ahmed: clarify a lot of stuff.

71
00:07:16.250 --> 00:07:18.500
Muddasar Ahmed: and then boarded to update those.

72
00:07:19.350 --> 00:07:20.850
Muddasar Ahmed: That was

73
00:07:21.090 --> 00:07:24.479
Muddasar Ahmed: couple of things that have been going on around

74
00:07:25.767 --> 00:07:28.010
Muddasar Ahmed: tax role. And

75
00:07:28.968 --> 00:07:31.960
Muddasar Ahmed: elephant projects quality and security.

76
00:07:32.140 --> 00:07:33.722
Muddasar Ahmed: So I presented

77
00:07:34.900 --> 00:07:39.849
Muddasar Ahmed: a topic area that we're considering to

78
00:07:39.990 --> 00:07:41.200
Muddasar Ahmed: write up

79
00:07:41.440 --> 00:07:47.730
Muddasar Ahmed: elephant security and quality goals, some sort of visionary statement

80
00:07:48.290 --> 00:07:50.129
Muddasar Ahmed: that we can use

81
00:07:50.640 --> 00:07:57.110
Muddasar Ahmed: when we design our deliverables in individual projects.

82
00:07:57.200 --> 00:08:06.030
Muddasar Ahmed: So I will give you some of those texts in the chat. Sounds like you can put it in your Dsc. Meeting, I think, is

83
00:08:06.160 --> 00:08:09.390
Muddasar Ahmed: this requires ground up support.

84
00:08:09.640 --> 00:08:11.459
Muddasar Ahmed: We are producing softwares.

85
00:08:12.480 --> 00:08:17.689
Muddasar Ahmed: software or capability that either vendors or

86
00:08:18.070 --> 00:08:23.760
Muddasar Ahmed: organizations going to incorporate, to offer their services to their end customer

87
00:08:23.920 --> 00:08:25.880
Muddasar Ahmed: and will literally become

88
00:08:26.280 --> 00:08:29.510
Muddasar Ahmed: a link and a service value chain.

89
00:08:30.010 --> 00:08:33.859
Muddasar Ahmed: And if we don't uphold certain minimum

90
00:08:33.890 --> 00:08:35.730
Muddasar Ahmed: quality and security

91
00:08:36.030 --> 00:08:37.700
Muddasar Ahmed: levels.

92
00:08:38.409 --> 00:08:41.760
Muddasar Ahmed: we are actually then contributing towards

93
00:08:41.809 --> 00:08:44.820
Muddasar Ahmed: breaking that link and service value chain.

94
00:08:44.960 --> 00:08:50.100
Muddasar Ahmed: So, taking our responsibility as developer of those capabilities.

95
00:08:50.190 --> 00:08:51.410
Muddasar Ahmed: I think it's

96
00:08:51.610 --> 00:08:58.370
Muddasar Ahmed: up to us to self, manage and set our goals and and the bar for ourselves.

97
00:08:59.036 --> 00:09:04.540
Muddasar Ahmed: Don't think it's a top down approach that will work in open source community. So

98
00:09:04.700 --> 00:09:07.200
Muddasar Ahmed: putting something together for ourselves.

99
00:09:07.220 --> 00:09:16.920
Muddasar Ahmed: Hey, this is is, this is a a goal that we are marching toward doesn't have to be specific. But we need to change the culture where

100
00:09:17.120 --> 00:09:20.061
Muddasar Ahmed: we always set quality goals.

101
00:09:20.700 --> 00:09:23.360
Muddasar Ahmed: good example is that you may have

102
00:09:23.500 --> 00:09:25.947
Muddasar Ahmed: technical debt or outstanding

103
00:09:26.780 --> 00:09:28.890
Muddasar Ahmed: work that you haven't tackled.

104
00:09:29.280 --> 00:09:32.710
Muddasar Ahmed: So there are 2 ways you can look at open source software.

105
00:09:32.770 --> 00:09:34.427
Muddasar Ahmed: One is to

106
00:09:35.590 --> 00:09:37.790
Muddasar Ahmed: put something out and walk away.

107
00:09:37.810 --> 00:09:45.269
Muddasar Ahmed: But some of the work becomes permanent fixture, the Cuban daddies, and a whole bunch of other projects. In one example.

108
00:09:45.500 --> 00:09:46.200
Muddasar Ahmed: that

109
00:09:46.630 --> 00:09:55.170
Muddasar Ahmed: we take it as de facto. This is the way to do business, and we hope, in our own app to some of our capabilities in the future will

110
00:09:55.670 --> 00:09:58.819
Muddasar Ahmed: still be used as a multi domain orchestrator.

111
00:09:58.900 --> 00:10:07.289
Muddasar Ahmed: So if that's the case right? We need to think permanency. And that means we need to take care of some stuff that's broken or half cooked

112
00:10:07.450 --> 00:10:15.660
Muddasar Ahmed: and tech technical debt. Retirement is one of those. What if you have some dependencies there outdated.

113
00:10:15.690 --> 00:10:20.509
Muddasar Ahmed: or you have a big security hole, you know. You know it's been reported.

114
00:10:20.760 --> 00:10:23.289
Muddasar Ahmed: but you haven't found the time.

115
00:10:23.440 --> 00:10:25.760
Muddasar Ahmed: All of these are project level

116
00:10:26.100 --> 00:10:31.939
Muddasar Ahmed: activities that don't think they need to go in the goals. But I'll give you an example, it's a very high level.

117
00:10:32.050 --> 00:10:36.649
Muddasar Ahmed: and I look forward to getting some feedback from Tsc members, so

118
00:10:36.700 --> 00:10:39.240
Muddasar Ahmed: we can suggest something back to the

119
00:10:40.080 --> 00:10:41.890
Muddasar Ahmed: tat elephant tag

120
00:10:42.300 --> 00:10:44.360
Muddasar Ahmed: and see what

121
00:10:44.400 --> 00:10:48.520
Muddasar Ahmed: what we can come up with, that we can share with other projects as well

122
00:10:50.890 --> 00:10:54.049
Muddasar Ahmed: any thoughts or question. Let me put that stuff in the chat

123
00:10:54.180 --> 00:10:55.610
Muddasar Ahmed: center for you.

124
00:10:59.860 --> 00:11:01.850
Paweł Pawlak: Thank you, Madazar, for this update.

125
00:11:02.990 --> 00:11:05.339
Muddasar Ahmed: I'm not able to.

126
00:11:05.620 --> 00:11:11.239
Muddasar Ahmed: Sandra. If you can give me the page URL, I'll just put it in the notes.

127
00:11:23.350 --> 00:11:25.459
Paweł Pawlak: Sandra, we cannot hear you if you speak.

128
00:11:27.350 --> 00:11:29.689
Muddasar Ahmed: Or I can slice and dice.

129
00:11:30.330 --> 00:11:35.450
Byung-Woo Jun: I I mean, I can send the link to Modessa. This is the meeting notes.

130
00:11:36.150 --> 00:11:38.220
Paweł Pawlak: Yeah, it's it's in the notes.

131
00:11:38.590 --> 00:11:39.510
Sandra Jackson: Isn't jet.

132
00:11:39.650 --> 00:11:41.670
Sandra Jackson: You mentioned the chat? Yeah. Hmm.

133
00:11:42.710 --> 00:11:44.349
Sandra Jackson: okay. Got it. I will

134
00:11:46.520 --> 00:11:47.719
Sandra Jackson: drop it in.

135
00:11:47.730 --> 00:11:48.725
Sandra Jackson: Okay,

136
00:11:50.590 --> 00:11:52.139
Sandra Jackson: hold on for a second.

137
00:11:52.140 --> 00:11:55.784
Paweł Pawlak: Sandra question as we have. Matt was joining us

138
00:11:56.320 --> 00:12:00.259
Paweł Pawlak: just in order to save his time, can we? Could we switch to

139
00:12:00.820 --> 00:12:04.869
Paweł Pawlak: to the point. He wanted to to race to Tsc.

140
00:12:06.065 --> 00:12:07.130
Paweł Pawlak: okay.

141
00:12:07.130 --> 00:12:08.909
Sandra Jackson: Do you need to share anything for that.

142
00:12:10.760 --> 00:12:13.339
Mateusz Pilat (TCL): Yeah, I have a few slides regarding this.

143
00:12:13.340 --> 00:12:14.756
Sandra Jackson: Okay. Let me stop.

144
00:12:15.110 --> 00:12:15.780
Mateusz Pilat (TCL): Over.

145
00:12:15.780 --> 00:12:19.230
Sandra Jackson: Hold on for a second. Let me just add this in, and then I'll stop sharing.

146
00:12:20.230 --> 00:12:22.449
Sandra Jackson: Okay, all for you.

147
00:12:22.790 --> 00:12:24.630
Mateusz Pilat (TCL): Alright let me

148
00:12:26.680 --> 00:12:28.820
Mateusz Pilat (TCL): figuring out how to stand that. Okay.

149
00:12:35.930 --> 00:12:39.859
Mateusz Pilat (TCL): Alright. Tell me, tell me, please, if you can see my screen.

150
00:12:42.530 --> 00:12:42.920
Paweł Pawlak: No.

151
00:12:42.920 --> 00:12:44.720
Byung-Woo Jun: Not yet not yet.

152
00:12:45.680 --> 00:12:46.560
Mateusz Pilat (TCL): Okay. Oh.

153
00:12:46.560 --> 00:12:46.969
Paweł Pawlak: Yeah. Will. Come.

154
00:12:46.970 --> 00:12:48.370
Byung-Woo Jun: I mean. Come, you come in. Yeah.

155
00:12:48.370 --> 00:12:54.269
Mateusz Pilat (TCL): Alright! Alright! Alright so what's this all about? So?

156
00:12:54.320 --> 00:12:57.000
Mateusz Pilat (TCL): And anyway, the story is quite try to be brief.

157
00:12:57.150 --> 00:13:11.349
Mateusz Pilat (TCL): I I got the task to improve observability from in in our platform. That. That's the problem. And one of the things to be to improve is logging right. So to make looks more like user friendly and more usable.

158
00:13:11.730 --> 00:13:20.649
Mateusz Pilat (TCL): So I started to look at the components that we use from on app gathering information about the logs and trying to figure it out. What's the best way to present it?

159
00:13:20.860 --> 00:13:21.730
Mateusz Pilat (TCL): Eyes?

160
00:13:22.689 --> 00:13:41.870
Mateusz Pilat (TCL): So that these are where my go. So fo first to get all that important data we can, then to have them passed, which is very important to me to present it nicely to the users and then to is, you know, to to make it manageable as possible, as easy as possible for the platform. And I did something like

161
00:13:42.890 --> 00:13:45.879
Mateusz Pilat (TCL): and I did an analysis of the

162
00:13:47.255 --> 00:13:52.660
Mateusz Pilat (TCL): existing logging. Let's say, situation in on app. I I did.

163
00:13:52.810 --> 00:13:57.541
Mateusz Pilat (TCL): I'm gonna show you now with you now in the next slide. So I went through the that's actually

164
00:13:58.050 --> 00:13:59.250
Mateusz Pilat (TCL): London.

165
00:13:59.390 --> 00:14:02.159
Mateusz Pilat (TCL): but that hasn't changed much in Montreal.

166
00:14:02.190 --> 00:14:04.049
Mateusz Pilat (TCL): So I went through all the pods

167
00:14:05.010 --> 00:14:09.610
Mateusz Pilat (TCL): all the outputs of the logs that there is, and that I I got pretty much like you can see

168
00:14:09.950 --> 00:14:14.960
Mateusz Pilat (TCL): quite a bunch of information which component looks, what what way?

169
00:14:16.480 --> 00:14:27.954
Mateusz Pilat (TCL): And I found I stumbled on couple of of issues when trying to like organize it, because first, the first, the original talk was just to get the logs, but they are not not much usable if you just just like strings of lines.

170
00:14:28.330 --> 00:14:33.080
Mateusz Pilat (TCL): So I try try to make it more usable, right? For for the user.

171
00:14:33.939 --> 00:14:34.709
Mateusz Pilat (TCL): So

172
00:14:36.260 --> 00:14:41.186
Mateusz Pilat (TCL): my first problem was a different format, as you can see, and I'm pretty sure most of you are aware of it.

173
00:14:41.480 --> 00:14:45.619
Mateusz Pilat (TCL): So we have enough components that there's no consistency in the way how they look.

174
00:14:46.440 --> 00:14:50.262
Mateusz Pilat (TCL): Try to tackle this problem. I actually kind of did it

175
00:14:51.350 --> 00:15:01.689
Mateusz Pilat (TCL): did it like analysis? What are the the parts? And I've managed to construct? And fluent d fluent beach, a configuration that parses, each container actually.

176
00:15:02.187 --> 00:15:20.262
Mateusz Pilat (TCL): differently, because that's that was the key takeout is that in on up each container, so not even each port, but each container, each each, each subco. We have a components in on that they have sub components and subcopinas usually consist of ports and pots. We have containers, and those containers, even within the same

177
00:15:21.102 --> 00:15:34.060
Mateusz Pilat (TCL): component, are logging in a different way. Different formats. So I've managed to create a bunch of configuration files and flu, and be that that allows me to parse it nicely to understand the logs as they come.

178
00:15:36.060 --> 00:15:38.985
Mateusz Pilat (TCL): But I realized that it's

179
00:15:39.610 --> 00:15:42.859
Mateusz Pilat (TCL): it's gonna be hard to maintain. It's gonna be like hard to

180
00:15:43.988 --> 00:15:47.271
Mateusz Pilat (TCL): handle regular expressions as much, you know.

181
00:15:48.170 --> 00:15:53.890
Mateusz Pilat (TCL): in in. Let's let's say you have a 60 pots from onup. So I would have to have a 60 configurations like this. I'm showing you

182
00:15:54.220 --> 00:15:59.518
Mateusz Pilat (TCL): 60 sections of configuration that would be able to for me to understand the logs right?

183
00:16:00.175 --> 00:16:05.340
Mateusz Pilat (TCL): So that was my first problem. That was my first solution. Then then I noticed that there is a second problem

184
00:16:05.894 --> 00:16:16.885
Mateusz Pilat (TCL): that. Not all the logs are printed into the Std out. So they these, there are parts of the components, parts of the logs that this is example from the I think this is

185
00:16:17.860 --> 00:16:30.300
Mateusz Pilat (TCL): This is from the bubble AI bubble, but partially that the take out is that there are some. We have a root logo that looks to Std out. However, there are like some metrics that are not logged there.

186
00:16:30.380 --> 00:16:35.121
Mateusz Pilat (TCL): and that's just an example. So we could. I think I saw more of more of the

187
00:16:35.964 --> 00:16:38.139
Mateusz Pilat (TCL): loga. Is that only

188
00:16:38.310 --> 00:16:50.709
Mateusz Pilat (TCL): log to file system, for example, on the port. So we miss those information. We cannot easily get them using just the Kubernetes standard logging approach. Right? So this is the problem, and I don't have a fix for it.

189
00:16:51.006 --> 00:17:03.813
Mateusz Pilat (TCL): This might be minor, because I don't think we. We may not want to have a metrics inside of the logs. We might not be much interested, but although I can argue that there might be a case that you would like to see. Also have a dashboard for metrics.

190
00:17:05.121 --> 00:17:08.280
Mateusz Pilat (TCL): Alright! So there are 2

191
00:17:08.810 --> 00:17:17.377
Mateusz Pilat (TCL): initiatives in the community I know about. So I know that there's a security team was a security Committee was promoting

192
00:17:17.890 --> 00:17:40.908
Mateusz Pilat (TCL): the global logging like as an even requirement. But that hasn't happened. So I don't know if the promotion was actually a global requirement for the components. But it's not. That doesn't happen, at least for the components that we use, and we use the most popular ones. And I know there was a nice article about next generation architecture, and then also in this. In this article there were some propositions.

193
00:17:41.707 --> 00:17:42.960
Mateusz Pilat (TCL): What to do.

194
00:17:44.200 --> 00:17:44.950
Mateusz Pilat (TCL): Okay.

195
00:17:46.870 --> 00:17:50.509
Mateusz Pilat (TCL): there are some propositions how to organize logging.

196
00:17:51.460 --> 00:17:53.220
Mateusz Pilat (TCL): Yeah, where was sorry?

197
00:17:53.450 --> 00:17:58.919
Mateusz Pilat (TCL): Yeah, that that this architectures that that's I agree that that looks okay.

198
00:18:00.000 --> 00:18:09.500
Mateusz Pilat (TCL): But it's still like a proposition. And I don't know what's the final solution for on app. If there's gonna be a logging mechanism provided with on app, which I don't really like as a solution.

199
00:18:09.810 --> 00:18:11.030
Mateusz Pilat (TCL): Are we

200
00:18:11.570 --> 00:18:20.229
Mateusz Pilat (TCL): like each each each implementator of of own app should provide own mechanism for gathering logs, because I can imagine that somebody will use azure

201
00:18:20.460 --> 00:18:28.315
Mateusz Pilat (TCL): on Prem. Somebody else will use somebody use azure somebody else was will use on prem, and and somebody else will use, for example.

202
00:18:29.482 --> 00:18:39.469
Mateusz Pilat (TCL): some dinetrays or data dog to gather logs. So all of them might be actually different at at at the end. So so that's that's one thing. But my goal is that

203
00:18:39.560 --> 00:18:42.040
Mateusz Pilat (TCL): whatever approach you use this

204
00:18:42.490 --> 00:18:51.369
Mateusz Pilat (TCL): common approach for logs would be an issue in every approach you would like to use right? Because, there's logs parsing and showing logs in the proper way.

205
00:18:52.177 --> 00:19:00.040
Mateusz Pilat (TCL): It's gonna be in everywhere. If you if you use a building cloud logging aggregation so, or like azure azure logs.

206
00:19:00.110 --> 00:19:01.853
Mateusz Pilat (TCL): or if you use

207
00:19:02.670 --> 00:19:07.620
Mateusz Pilat (TCL): even Kibana, the issue will be still the same. So

208
00:19:08.590 --> 00:19:16.043
Mateusz Pilat (TCL): I talked with Andreas on the our meeting, and he's okay with it. And actually, he's he's. I think that's my understanding that he's fine

209
00:19:16.490 --> 00:19:20.890
Mateusz Pilat (TCL): that we would like to in the as a Tcl in the

210
00:19:21.210 --> 00:19:29.905
Mateusz Pilat (TCL): components that we use. So at least those 4, but maybe more. We would like to actually implement something some some common understanding on logging.

211
00:19:30.320 --> 00:19:31.770
Mateusz Pilat (TCL): So the this

212
00:19:31.780 --> 00:19:36.479
Mateusz Pilat (TCL): there was proposed, like format, was proposed also somewhere else. So we can stick to this format

213
00:19:36.490 --> 00:19:38.769
Mateusz Pilat (TCL): and provide the single

214
00:19:40.690 --> 00:19:41.990
Mateusz Pilat (TCL): logs format.

215
00:19:42.480 --> 00:20:00.643
Mateusz Pilat (TCL): because then, if if ever component logs the same way, or at least has my majority of the fields the same, then it's it's way easier to parse it and to get the logs whatever solution you you use at the end. So we would like to fix those components that we use

216
00:20:02.114 --> 00:20:11.859
Mateusz Pilat (TCL): which is basically what I wrote here. So first of all, not all components even allow you to alter configuration after the installation. So there is component S, so

217
00:20:11.910 --> 00:20:14.810
Mateusz Pilat (TCL): that it has no option to

218
00:20:14.900 --> 00:20:16.049
Mateusz Pilat (TCL): to alter the

219
00:20:16.709 --> 00:20:36.209
Mateusz Pilat (TCL): logging format after deployment. You have to do it with some nasty tricks like mount new config maps which is like not not straightforward right for other components for AI, Sdc. They expose configuration. They don't allow you to change it during the installation, like before you actually deploy on up. They don't allow you to change the format.

220
00:20:36.790 --> 00:20:50.259
Mateusz Pilat (TCL): but you can alter it later. So let's say you, you have a way out. You can. You can make a patch small patch on the config map, and then then you have but the components like Sso. They don't expose it, and none of the as a component. So that's first thing I would like to fix

221
00:20:50.767 --> 00:21:06.640
Mateusz Pilat (TCL): so align so logging format with the other components. Second, is to force them all to log in the same way, like cps is doing, which which is in theory, Cps is actually following the guidelines in Json format.

222
00:21:07.355 --> 00:21:10.370
Mateusz Pilat (TCL): Then double check. If we don't lose any information.

223
00:21:10.680 --> 00:21:12.770
Mateusz Pilat (TCL): and that I have a like fourth

224
00:21:13.280 --> 00:21:14.830
Mateusz Pilat (TCL): item. But I'm not

225
00:21:14.840 --> 00:21:25.840
Mateusz Pilat (TCL): sure how to implement it yet. But I would like to have an a mechanism, common mechanism in on up components to switch between log levels, so which components would be logging in info level. But

226
00:21:25.850 --> 00:21:33.844
Mateusz Pilat (TCL): to make a mechanism that would allow to switch components to login debug for for some reason, if I need to debug something right? So this is proposition

227
00:21:35.680 --> 00:21:40.799
Mateusz Pilat (TCL): W. For the changes. We'd like to actually do.

228
00:21:40.920 --> 00:21:49.689
Mateusz Pilat (TCL): And and finally, I would like to have like. This is example from my key banner when I have logs already passed, so you can see I can have a I have some logs for for a component.

229
00:21:50.150 --> 00:21:55.043
Mateusz Pilat (TCL): and I have a request service name. I have plenty of information here.

230
00:21:56.350 --> 00:22:05.159
Mateusz Pilat (TCL): that I can use for sorting, you know, for doing statistics I can. I can, for example, see which which components is

231
00:22:05.760 --> 00:22:18.630
Mateusz Pilat (TCL): is returning me certain number, for example. It's gonna work certain numbers of of warnings or or messages, but but I can do it, thanks to proper parsing and proper handling logs.

232
00:22:18.790 --> 00:22:31.448
Mateusz Pilat (TCL): Right? So you can see here I created a dial that that's very, very simple dashboard. But I can see that that these components that, for example, the the ones that generates the more information I can dive in. I can.

233
00:22:31.820 --> 00:22:35.367
Mateusz Pilat (TCL): So I can, you know, see which one is, for example.

234
00:22:35.810 --> 00:22:39.838
Mateusz Pilat (TCL): throwing warnings for me. Right? I can go with sort of

235
00:22:40.590 --> 00:22:49.041
Mateusz Pilat (TCL): they have a keyword. And I can search the levels. And I can, for example, focus. So I can do it like, I can see, I have a access other debug. Okay? So I

236
00:22:49.859 --> 00:23:05.760
Mateusz Pilat (TCL): I can do those statistics and like generic for every component useful, but for to have them they only need to talk in the same language. Let's say so. That's something I I would like to fix, and I think it's way easier to fix it in the community to have a one standard

237
00:23:06.070 --> 00:23:14.349
Mateusz Pilat (TCL): than for me to construct a very, very long parser configuration, that is, it's also not efficient for the processing.

238
00:23:15.810 --> 00:23:22.049
Paweł Pawlak: Definitely good initiative, Matthews, just to give you an overview. There are some projects that we are.

239
00:23:23.010 --> 00:23:25.020
Paweł Pawlak: We don't have

240
00:23:25.810 --> 00:23:27.370
Paweł Pawlak: contributions anymore.

241
00:23:27.630 --> 00:23:30.009
Paweł Pawlak: right? Like a and I

242
00:23:32.170 --> 00:23:40.500
Paweł Pawlak: and and simply, we have no resources to do so right to do any modifications if you would be able to modify it right?

243
00:23:41.060 --> 00:23:50.040
Paweł Pawlak: And then I think you you you could have support from one of community, because this is increasing usability of on up

244
00:23:50.864 --> 00:23:56.380
Paweł Pawlak: from operational point of view. So this is a very valuable activity. Right?

245
00:23:57.720 --> 00:23:59.049
Paweł Pawlak: So, Hyung, can you come in.

246
00:23:59.050 --> 00:24:19.931
Byung-Woo Jun: Yeah, yeah, yeah, this is good. I think that we review the owner next generation security and log architecture which already, you know, shared, and I think that yes, you already saw that. And then, though during that that introduction, Bob Hyman, and from second, and we introduced the second introduced to

247
00:24:21.010 --> 00:24:43.260
Byung-Woo Jun: the Standard Security log format. That's what the Matthias mentioned. So I think. Cps team. They did. Poc. They put it in. I think the desk a very useful it. The example how we can do so they can. So I know they're not. We have only the few the owner component. And we call core.

248
00:24:43.310 --> 00:24:49.770
Byung-Woo Jun: And then those things still have. Pto, I think we need to discuss at the Ptr meeting about this new

249
00:24:49.780 --> 00:24:52.529
Byung-Woo Jun: format following the Cps path.

250
00:24:52.720 --> 00:25:12.760
Byung-Woo Jun: there's still creating the format, the the second the the provide as a global requirement or suggestion. So I think we should discuss, if we can. Provide one single format unified comment, you will be much easier in the front bit as a collector.

251
00:25:12.760 --> 00:25:28.209
Byung-Woo Jun: and we we did some Poc Ericsson, and then there at that time we had Sam issue, and then we have to handle a different format different passing, and then we have to normalize it before we send to elastic search. That's a good thing.

252
00:25:28.210 --> 00:25:28.585
Mateusz Pilat (TCL): Yes.

253
00:25:28.960 --> 00:25:39.489
Byung-Woo Jun: And then the second point is to standard our standard error. I thought that there was agreed by Pta all the Ptl. Before, and then we are informed

254
00:25:39.770 --> 00:25:47.750
Byung-Woo Jun: it's done. But actually, Mathias reported, you know, at Om, this weekend it was not done. So that's why

255
00:25:47.850 --> 00:25:57.159
Byung-Woo Jun: we need to discuss about standard. I'll send the error direction. It's not the require big the effort based on the Cps case.

256
00:25:57.220 --> 00:26:00.750
Byung-Woo Jun: And then we need to to achieve this. Otherwise

257
00:26:01.420 --> 00:26:13.690
Byung-Woo Jun: the collection through the new architecture has some issues. So there's good point. Matthias brought up this. And then we need to discuss further, and a Tsc. And Pto

258
00:26:13.700 --> 00:26:31.879
Byung-Woo Jun: for couple, you know a few things right? Cause tender or stand error. We have to finish. We are, we are informed, yeah, yeah, done. But actually, it's not done. This not good. And second on is the format standalice format following it. And then Jase format and the cps provide great example.

259
00:26:31.940 --> 00:26:49.770
Byung-Woo Jun: And that's the kind of a I think that we are. We did in the you know we did, up to certain point, and we dropped and and without resources. So so we need to discuss further. And if Matthias and Tata communication has some resource to contribute some in Oslo.

260
00:26:49.770 --> 00:27:06.089
Byung-Woo Jun: it'll be great. I think that's a good topic for Oslo. So I put the also logging enhancement as a also target the focus area. So I think that we need to talk the Tata communication. Tsc, and Pto.

261
00:27:06.110 --> 00:27:07.360
Byung-Woo Jun: that's my input.

262
00:27:11.047 --> 00:27:17.002
Mateusz Pilat (TCL): Thank you. So I, I think we all understand agree because that that's the needs I think the only like

263
00:27:17.650 --> 00:27:25.269
Mateusz Pilat (TCL): the only person who might be against it would be that somebody already implemented logging, formatting, and now we're gonna destroy it.

264
00:27:25.620 --> 00:27:26.890
Mateusz Pilat (TCL): But there's nobody.

265
00:27:26.890 --> 00:27:35.169
Byung-Woo Jun: Yeah, I think the the bob introduced many time to Pto or Tsc, many, you know, I think no big objection.

266
00:27:35.260 --> 00:27:43.630
Byung-Woo Jun: And so that become global requirements. So we, you know, we have to discuss again a Ptf, but that global requirement was agreed.

267
00:27:43.660 --> 00:27:51.699
Byung-Woo Jun: So we'll see. But how much the you know Pto the and talk about. But I think the I mean

268
00:27:51.750 --> 00:27:58.290
Byung-Woo Jun: based on Cps case. They're just, you know, creating some, you know, some configuration file. And then

269
00:27:58.420 --> 00:28:10.844
Byung-Woo Jun: but the the format, you know. So, Jason format. So anyway, we need to discuss further. But I think that there was discussed before and proposed, and then there was agreed, agreed, yeah, right?

270
00:28:11.210 --> 00:28:12.040
Paweł Pawlak: Yeah, yeah.

271
00:28:12.240 --> 00:28:18.679
Mateusz Pilat (TCL): Okay. So like, it would be okay just to, because that's not a huge change to change those those patterns, at least

272
00:28:18.810 --> 00:28:20.880
Mateusz Pilat (TCL): like if if we change them

273
00:28:20.990 --> 00:28:24.749
Mateusz Pilat (TCL): without thinking much, but just change the patterns from the

274
00:28:24.770 --> 00:28:28.849
Mateusz Pilat (TCL): unify them. So they will be logging the same. But just in Json format.

275
00:28:28.870 --> 00:28:35.340
Mateusz Pilat (TCL): Yeah, that's not a huge change like this doesn't require a lot of effort. The other stuff, like looking at the logs and analyzing

276
00:28:35.680 --> 00:28:40.000
Mateusz Pilat (TCL): if we need them or not, that that's requires effort, but changing pattern. Not really.

277
00:28:40.394 --> 00:28:45.420
Mateusz Pilat (TCL): So that that's and that would get us like 70% of the improvement. I would say, logging.

278
00:28:45.420 --> 00:28:51.495
Byung-Woo Jun: It's nice. So if you can, you know, do something for us, then it would be great. That's possible. Good topic.

279
00:28:51.760 --> 00:28:58.910
Mateusz Pilat (TCL): I can open. I can open just the message. Request changes, and then see how it goes and engage. Okay.

280
00:28:58.910 --> 00:28:59.899
Byung-Woo Jun: Okay. But don't you think.

281
00:28:59.900 --> 00:29:03.040
Paweł Pawlak: In minded for some projects that are, let's say, unmandined.

282
00:29:03.520 --> 00:29:05.889
Paweł Pawlak: You probably won't get any

283
00:29:06.831 --> 00:29:10.358
Paweł Pawlak: response right? Because there are no contributors there. So

284
00:29:11.170 --> 00:29:16.619
Paweł Pawlak: but okay, let's let's do do it this way. Next week Ptl's call is cancelled so we can.

285
00:29:16.620 --> 00:29:17.054
Byung-Woo Jun: Yes.

286
00:29:17.490 --> 00:29:20.590
Paweł Pawlak: For the the following week on the sixth of

287
00:29:20.700 --> 00:29:21.560
Paweł Pawlak: May.

288
00:29:22.390 --> 00:29:26.420
Paweł Pawlak: and to share with the with the Ptls

289
00:29:27.071 --> 00:29:29.980
Paweł Pawlak: the this this proposal.

290
00:29:30.490 --> 00:29:39.399
Paweł Pawlak: and and simply, as it is already a requirement, I think global requirement that that was already shared with the community a while ago.

291
00:29:39.490 --> 00:29:46.059
Paweł Pawlak: We we are just, you know, following the the requirement that was already agreed. Right? So

292
00:29:46.390 --> 00:29:54.540
Paweł Pawlak: is just to mention it in the release notes. So to inform Thomas Clique, who is responsible for the for the documentation

293
00:29:54.650 --> 00:29:57.420
Paweł Pawlak: after you complete your work. Right?

294
00:29:58.750 --> 00:29:59.650
Paweł Pawlak: Okay.

295
00:29:59.790 --> 00:30:00.630
Paweł Pawlak: yeah.

296
00:30:01.720 --> 00:30:06.171
Paweł Pawlak: Yeah. But but yeah, any questions, guys, any questions from the Tsc team or

297
00:30:06.490 --> 00:30:22.359
Byung-Woo Jun: 1 1 one comment. I think, Matthias. I think that you're gonna talk about the front with Route Texas. We had the same problem. So we had discussion at the second and even Maggie from Nsa. The team. And then they provide some

298
00:30:22.380 --> 00:30:24.790
Byung-Woo Jun: suggestion, and we walked in is

299
00:30:24.880 --> 00:30:29.200
Byung-Woo Jun: before I exon dropped the ball, and then we approve it. It's gonna work.

300
00:30:29.350 --> 00:30:48.730
Byung-Woo Jun: But you have a your own solution. So maybe you can discuss further about the how we gonna support the non accessible front or some restricted yeah. So we we can discuss. But you have us from your own thoughts. And then maybe as a second next time we can discuss about your suggestion.

301
00:30:48.730 --> 00:31:04.385
Byung-Woo Jun: And Maggie gonna be there so we can discuss about that. So we have a certain solution. But I'm not sure there's still a great solution yet. But there's a no perfect solution here. So if you have, you know, sort. And we can discuss at the second Pabo. Maybe we can discuss.

302
00:31:04.670 --> 00:31:10.759
Paweł Pawlak: This would be on the seventh of May. But I will show you in in the Polish time zone.

303
00:31:11.190 --> 00:31:12.139
Mateusz Pilat (TCL): Yes, I am.

304
00:31:12.430 --> 00:31:16.730
Paweł Pawlak: Okay. So 2 pm. On on Tuesday, seventh of May.

305
00:31:17.631 --> 00:31:20.340
Paweł Pawlak: Yeah, I could send you invitation

306
00:31:20.620 --> 00:31:22.779
Paweł Pawlak: if you share with me your email and.

307
00:31:24.503 --> 00:31:28.990
Mateusz Pilat (TCL): Sure. Okay, alright I'll write it in the in the chat.

308
00:31:30.430 --> 00:31:31.190
Paweł Pawlak: Okay.

309
00:31:31.190 --> 00:31:40.260
Byung-Woo Jun: That's good, the topic. So anyway. So we're gonna discuss more. And the also about general unlogging architecture and this implementation, and then, including the

310
00:31:40.400 --> 00:31:43.529
Byung-Woo Jun: good access. Okay, thank you. Thank you. Matthews.

311
00:31:43.730 --> 00:31:45.660
Paweł Pawlak: Yeah, sounds good. Thank you. Natash.

312
00:31:45.660 --> 00:31:46.490
Mateusz Pilat (TCL): Thank you.

313
00:31:47.020 --> 00:31:51.759
Muddasar Ahmed: Matt. Just can you please add your slides to the meeting notes? Thank you.

314
00:31:52.590 --> 00:31:53.130
Mateusz Pilat (TCL): Okay.

315
00:31:53.670 --> 00:31:55.536
Paweł Pawlak: Oh, yeah. Yeah, very valuable.

316
00:31:58.680 --> 00:31:59.699
Sandra Jackson: Alright. Thank you.

317
00:32:02.520 --> 00:32:10.519
Sandra Jackson: Okay, we'll move on. Okay, this this one here is quick. So anyway, the one summit is coming up

318
00:32:11.181 --> 00:32:24.838
Sandra Jackson: next week, and so we do have the Lfn. Booth. There is going to feature 3 main kios cloud native AI, and cloud me. I think that's supposed to say automation

319
00:32:25.624 --> 00:32:36.265
Sandra Jackson: at the end it was a copy and paste. So sorry I didn't catch that. But the link there. If anyone is attending and want to man the kiosk, it's a good opportunity to

320
00:32:37.150 --> 00:32:43.809
Sandra Jackson: to tell what's happening in in share what's happening in in your community. You don't need to be

321
00:32:44.470 --> 00:33:02.820
Sandra Jackson: yeah expert or anything. Just kind of know some information about Lf networking. But the link is there with the available time slots that they still need folks to fill. So if you're interested and you will be get one summit, please click on a link and fill in a slot to fill.

322
00:33:04.130 --> 00:33:06.859
Sandra Jackson: That's all I have for that. Any questions.

323
00:33:10.450 --> 00:33:11.210
Sandra Jackson: Okay?

324
00:33:11.710 --> 00:33:14.991
Sandra Jackson: Then we will move on to release

325
00:33:15.570 --> 00:33:16.630
Sandra Jackson: status.

326
00:33:17.150 --> 00:33:19.009
Sandra Jackson: And do you need to share Dion.

327
00:33:19.010 --> 00:33:40.099
Byung-Woo Jun: No, I think that we I share this before I just for now that we have. You know, schedule Kickoff, May 9, and Rc. November 20 first, and then sign up December 12, after 11 dtf, I like to have a Tsd meeting, and then we wants to have some kind of voting to approve this also. Schedule

328
00:33:40.100 --> 00:33:58.889
Byung-Woo Jun: on May ninth. That's my plan. So the please take a look at the that link, and then, if you have con some consideration suggestion or the date. And please let me know and let us know. Then we can change it. But we're gonna share this current schedule

329
00:33:58.980 --> 00:34:13.899
Byung-Woo Jun: at the 11 dtf, as a not yet approved that version. But October May ninth. We can have some kind of a voting agreement on the also schedule. It's not that we're not following the waterfall anymore.

330
00:34:14.427 --> 00:34:29.819
Byung-Woo Jun: Tta can start anytime. They want. We are doing agile base this way. So we have flexible when to start and when to you know. Rc, but for now this is kind of a a marketing version of the oslo, yeah, that's it.

331
00:34:32.420 --> 00:34:34.250
Sandra Jackson: Okay, any questions or comments.

332
00:34:36.760 --> 00:34:40.793
Sandra Jackson: Alright. So again, just reemphasizing, please,

333
00:34:41.440 --> 00:34:45.854
Sandra Jackson: take a minute to review it and be prepared to vote for it on

334
00:34:46.280 --> 00:34:48.510
Sandra Jackson: to catch your vote on May ninth.

335
00:34:48.929 --> 00:34:50.989
Sandra Jackson: Thank you. They are

336
00:34:51.670 --> 00:34:56.559
Sandra Jackson: okay. Moving down. What is happening. My page is moving. Okay.

337
00:34:57.577 --> 00:34:59.660
Sandra Jackson: actually, I think we did that.

338
00:34:59.740 --> 00:35:02.180
Sandra Jackson: Was there anything else in Ptl update

339
00:35:02.270 --> 00:35:03.570
Sandra Jackson: other than

340
00:35:05.710 --> 00:35:07.480
Sandra Jackson: I think we're good there. Okay?

341
00:35:08.180 --> 00:35:11.550
Sandra Jackson: So then, can we move on to Oom Update.

342
00:35:12.948 --> 00:35:15.400
Byung-Woo Jun: Andress is not here today. So

343
00:35:16.257 --> 00:35:21.620
Byung-Woo Jun: anyway, the report that the OM. Cause the Dan is not here either, Danoney.

344
00:35:21.650 --> 00:35:29.989
Byung-Woo Jun: because the one issue is the we are still waiting for Dan's input, for Sdnc for vehemen

345
00:35:31.220 --> 00:35:38.830
Byung-Woo Jun: the crystal. Remember the Andreas he changed or removeding the beer man, and they're going to Rfc.

346
00:35:39.060 --> 00:35:56.099
Byung-Woo Jun: But the Sdnc. One unit they still are referring that the beer man, so without changing it, the whole whole own app, you know, cannot go that path. That's why it's very urgent someone contact, then, Timoni. And what's the

347
00:35:56.100 --> 00:36:09.080
Byung-Woo Jun: situation? So he he deported the most purchasing only issue with Sdnc. So then has to respond. So we need to get his get involved as soon as possible. So

348
00:36:11.440 --> 00:36:14.140
Byung-Woo Jun: I don't know who who who can contact them.

349
00:36:15.630 --> 00:36:19.610
Byung-Woo Jun: So anyway, Sdnc need to change their modified to.

350
00:36:20.199 --> 00:36:29.060
Byung-Woo Jun: you know. Talk to Andrew guys guys so as soon as possible to fix it. Otherwise we have issue because of this Dnc.

351
00:36:29.350 --> 00:36:29.780
Paweł Pawlak: Done, the.

352
00:36:29.780 --> 00:36:30.360
Byung-Woo Jun: Yes, to.

353
00:36:30.360 --> 00:36:33.389
Paweł Pawlak: Tony, Tony, could we ask for your help here

354
00:36:33.650 --> 00:36:36.809
Paweł Pawlak: as you are in 1 one organization we've we've done.

355
00:36:41.620 --> 00:36:43.150
Paweł Pawlak: It was unlimited

356
00:36:43.700 --> 00:36:46.216
Paweł Pawlak: question to Tony Tony Hansen.

357
00:36:47.194 --> 00:36:48.619
Tony Hansen: Contact me offline.

358
00:36:51.190 --> 00:36:51.590
Paweł Pawlak: Okay.

359
00:36:52.100 --> 00:36:54.190
Byung-Woo Jun: Okay, so anyway, just.

360
00:36:54.190 --> 00:36:55.400
Paweł Pawlak: So beyond. Could you please.

361
00:36:55.400 --> 00:36:58.510
Byung-Woo Jun: I can send email to you. Okay, so yeah.

362
00:36:58.750 --> 00:37:07.019
Byung-Woo Jun: just ask him to talk to Andress. He knows the issue. And then Sdnc boom in some issue. So anyway, so okay, so

363
00:37:07.650 --> 00:37:11.800
Byung-Woo Jun: let him contact Andreas for more details. You know, I think he knows that.

364
00:37:12.270 --> 00:37:13.810
Byung-Woo Jun: Okay, I'll send you Tony.

365
00:37:16.040 --> 00:37:16.800
Tony Hansen: Okay.

366
00:37:18.590 --> 00:37:22.949
Sandra Jackson: Actually, I'm going to back up because I mixed up my sections here, hold on for a second.

367
00:37:25.330 --> 00:37:27.519
Sandra Jackson: Going back to the Ptl updates.

368
00:37:28.370 --> 00:37:32.868
Sandra Jackson: I was thinking that this is what he updated on. And he updated down here. Okay,

369
00:37:34.880 --> 00:37:37.420
Sandra Jackson: is Jessica on. Do you have a

370
00:37:38.130 --> 00:37:44.210
Sandra Jackson: I just saw her name. Do we have any updates on this, or is this still ongoing the Ng portal.

371
00:37:46.011 --> 00:37:56.838
Jessica Wagantall: Yeah. We we met last week before the oss, and we did some progress I need to reach out back to fed and

372
00:37:57.640 --> 00:38:04.640
Jessica Wagantall: and organize another meeting. I I think I think we did good progress. So we still ongoing.

373
00:38:05.150 --> 00:38:06.200
Sandra Jackson: Okay. Okay.

374
00:38:06.610 --> 00:38:07.170
Sandra Jackson: Alright. Yeah.

375
00:38:07.170 --> 00:38:13.140
Paweł Pawlak: And this is what we've heard on on on Monday. Call. Thank you, Jess, for for your help, and the team.

376
00:38:13.450 --> 00:38:16.759
Paweł Pawlak: So yes, please, please keep on moving on this so we could

377
00:38:16.820 --> 00:38:18.110
Paweł Pawlak: finalize it

378
00:38:18.491 --> 00:38:20.418
Paweł Pawlak: very soon. Right? Hmm, thank you.

379
00:38:22.140 --> 00:38:25.330
Sandra Jackson: Okay? And did I miss anything else in this section? I think I got it now.

380
00:38:25.610 --> 00:38:26.370
Sandra Jackson: Okay.

381
00:38:26.830 --> 00:38:27.510
Sandra Jackson: just.

382
00:38:27.510 --> 00:38:29.969
Paweł Pawlak: Just a com comment, if if may I?

383
00:38:30.415 --> 00:38:37.380
Paweł Pawlak: So yeah, it is. It is really crucial to to have those scans completed, and

384
00:38:37.540 --> 00:38:44.289
Paweł Pawlak: once you have the information about the vulnerabilities, and you know the the packages upgrades recommended. So

385
00:38:44.560 --> 00:38:49.239
Paweł Pawlak: please, for the Pts. Right, please don't hesitate to do the action.

386
00:38:49.330 --> 00:38:59.080
Paweł Pawlak: And I think we have already the the Cps project that's completed it. So congratulations for doing those efforts and looking forward for others to

387
00:38:59.250 --> 00:39:02.119
Paweł Pawlak: to follow the same path. Thank you.

388
00:39:03.750 --> 00:39:04.720
Sandra Jackson: Thank you, Pablo.

389
00:39:05.490 --> 00:39:06.350
Sandra Jackson: Okay.

390
00:39:07.357 --> 00:39:09.089
Sandra Jackson: now, I think I can move forward.

391
00:39:11.540 --> 00:39:18.669
Sandra Jackson: Going down to. We did that one. Okay, at our com, our com. Am I seeing it right, Ourcom?

392
00:39:19.433 --> 00:39:20.480
Sandra Jackson: Subcommittee updates

393
00:39:20.750 --> 00:39:21.780
Sandra Jackson: anything.

394
00:39:24.540 --> 00:39:32.699
Byung-Woo Jun: No, just. We are preparing for Lf. And Dtmf. Presentation from outcome as part of their own initiatives. So that's so. That's simple.

395
00:39:34.490 --> 00:39:38.880
Sandra Jackson: Okay, so are we through the agenda already to stop check. I think we are

396
00:39:39.990 --> 00:39:44.829
Sandra Jackson: okay. So then, I'll move down to housekeeping

397
00:39:46.590 --> 00:39:48.440
Sandra Jackson: and upcoming events.

398
00:39:49.940 --> 00:39:50.530
Sandra Jackson: some, but.

399
00:39:50.952 --> 00:39:52.640
Paweł Pawlak: Sorry for interrupting you

400
00:39:52.930 --> 00:39:56.889
Paweł Pawlak: guys, Le, next week, as we have those events. So all the other.

401
00:39:56.940 --> 00:40:04.260
Paweł Pawlak: let's say regular events of of on app like subcommittee meetings, or probably

402
00:40:04.310 --> 00:40:13.650
Paweł Pawlak: Pts. Call and project meetings would be cancelled right? So so everyone could could participate in the Gtf. And would not lose any.

403
00:40:13.690 --> 00:40:15.459
Paweł Pawlak: And I think, so.

404
00:40:15.830 --> 00:40:23.740
Paweł Pawlak: yeah, let's keep all the project and all the meetings, all the other meetings. Tsc. As well for the next week will be cancelled right? Because of those events.

405
00:40:23.900 --> 00:40:25.129
Paweł Pawlak: Just a comment

406
00:40:25.170 --> 00:40:27.380
Paweł Pawlak: to make make it clear. Okay.

407
00:40:29.220 --> 00:40:31.420
Sandra Jackson: Yup, I thank you, Pablo.

408
00:40:33.650 --> 00:40:36.700
Sandra Jackson: okay. So one summit is coming up next week.

409
00:40:37.800 --> 00:40:38.740
Sandra Jackson: And

410
00:40:38.890 --> 00:40:48.450
Sandra Jackson: after the one summit the tell-in is on is the Dntf, so just like Pablo said. Everything as far as own app Psc. Ptl. Meetings

411
00:40:48.961 --> 00:40:55.960
Sandra Jackson: will be canceled so that you can participate. We hope to see folks there participating.

412
00:40:58.070 --> 00:41:01.730
Sandra Jackson: I think that's it. Bayon. Did you have any additional.

413
00:41:02.820 --> 00:41:08.829
Byung-Woo Jun: No, no, that's that's my schedule already shared. And then we adjusted. And then, okay, so that's it.

414
00:41:09.750 --> 00:41:10.180
Sandra Jackson: Right

415
00:41:10.870 --> 00:41:14.319
Sandra Jackson: well, if there are no other comments or questions.

416
00:41:14.650 --> 00:41:16.889
Muddasar Ahmed: I have one Sandra.

417
00:41:18.720 --> 00:41:20.130
Muddasar Ahmed: Just wanted to

418
00:41:20.490 --> 00:41:24.820
Muddasar Ahmed: inform members here who may be interested in AI.

419
00:41:24.890 --> 00:41:28.130
Muddasar Ahmed: I think there was a line item up there. We didn't get to talk.

420
00:41:28.180 --> 00:41:29.790
Muddasar Ahmed: But the task force

421
00:41:31.020 --> 00:41:37.290
Muddasar Ahmed: we're thinking the task force was created. With the Board's desire to look into

422
00:41:37.430 --> 00:41:40.680
Muddasar Ahmed: FY. 24 goals and beyond.

423
00:41:40.980 --> 00:41:47.270
Muddasar Ahmed: And one of the items was, how can we leverage AI in elephant projects?

424
00:41:47.370 --> 00:41:51.519
Muddasar Ahmed: So there's a paper that was co-authored by many members.

425
00:41:52.256 --> 00:41:54.240
Muddasar Ahmed: The paper may be.

426
00:41:54.530 --> 00:42:02.119
Muddasar Ahmed: I think they are planning to share it. On one summit there'll be a booth. They will at least have some artifacts

427
00:42:02.460 --> 00:42:05.069
Muddasar Ahmed: for participant to take

428
00:42:05.490 --> 00:42:08.680
Muddasar Ahmed: one other thing they also try and do is

429
00:42:08.830 --> 00:42:14.990
Muddasar Ahmed: have an AI discussion. So tech members, other participants are welcome.

430
00:42:15.260 --> 00:42:18.344
Muddasar Ahmed: I think Kate Wong and some of his

431
00:42:18.740 --> 00:42:22.771
Muddasar Ahmed: collaborators from his companies been already working on it.

432
00:42:23.570 --> 00:42:28.490
Muddasar Ahmed: If they are going to participate, please join. Otherwise there will be a link

433
00:42:28.960 --> 00:42:37.419
Muddasar Ahmed: for remote participation in that AI discussion. Few things we wanna get feedback on. AI topic is

434
00:42:37.680 --> 00:42:45.220
Muddasar Ahmed: the task force. Job was not to be permanent. So I think at some point we need to

435
00:42:45.510 --> 00:42:53.994
Muddasar Ahmed: morph into what's next. And the next part could be, that lot of projects may be already doing some AI related work.

436
00:42:54.540 --> 00:43:04.070
Muddasar Ahmed: How do we combine these efforts? So we have a portfolio level visibility to what Lfn is doing for AI.

437
00:43:05.010 --> 00:43:14.920
Muddasar Ahmed: At the same time, let those projects do their work. Build the capabilities air. Related capabilities in their software offerings.

438
00:43:15.250 --> 00:43:18.879
Muddasar Ahmed: So please look out for a session at Dtf.

439
00:43:18.950 --> 00:43:22.089
Muddasar Ahmed: For AI. I think it should be on the schedule.

440
00:43:22.793 --> 00:43:26.559
Muddasar Ahmed: If you can join in person, join remotely and provide your feedback.

441
00:43:26.660 --> 00:43:27.819
Muddasar Ahmed: Thank you.

442
00:43:29.700 --> 00:43:30.279
Sandra Jackson: Thank you.

443
00:43:32.080 --> 00:43:34.000
Sandra Jackson: Any other questions or comments.

444
00:43:37.580 --> 00:43:43.139
Sandra Jackson: Okay, well, there, if if there's hold on, let me just check this chat really quickly.

445
00:43:43.220 --> 00:43:44.449
Sandra Jackson: Okay, thank you. Bye.

446
00:43:44.450 --> 00:43:51.689
Byung-Woo Jun: Just for Tony Tony, email, yeah, just for rest and see the email, mo, dependencies. So yeah.

447
00:43:53.350 --> 00:43:53.850
Sandra Jackson: Wonderful

448
00:43:55.167 --> 00:44:02.180
Sandra Jackson: so if there's nothing else, then we will see you next week in one summit.

449
00:44:02.710 --> 00:44:04.800
Sandra Jackson: or the d and tf, or both

450
00:44:05.763 --> 00:44:09.729
Sandra Jackson: and then the following week will pick up. So everyone have a good week.

451
00:44:11.130 --> 00:44:11.870
Byung-Woo Jun: Thank you.

452
00:44:12.010 --> 00:44:13.500
Paweł Pawlak: Thank you. Bye, bye.

453
00:44:13.580 --> 00:44:15.730
Paweł Pawlak: I have a good meetings in San Jose.

454
00:44:16.380 --> 00:44:16.805
Byung-Woo Jun: Kit.

455
00:44:17.500 --> 00:44:19.183
N.K. Shankaranarayanan: Okay. Bye. Bye, thank you.

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

OOM Update

Logging Implementation Proposal

Subcommittee Updates

Upcoming Events & Housekeeping

Zoom Chat Log

Browser not supported