TSC 2024-01-25
BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f
Passcode: 209247
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/ | |
|---|---|---|---|
| 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 UpdatesMAC, SPC, TAC, EUAG, LFN Board | @Andreas Geißler @N.K. Shankaranarayanan @Byung-Woo Jun | ONAP and O-RAN SC collaboration:
| |
TCC / ONAP Liaison Updates | @Amy Zwarico @Byung-Woo Jun |
| |
Task Force Updates | |||
Operations (40 minutes) | TSC Activities and Deadlines | ||
Release Status | @Byung-Woo Jun |
| |
RelEng/Infrastructure | |||
PTL Updates | @Byung-Woo Jun |
| |
Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements | @Byung-Woo Jun @Andreas Geißler @Amy Zwarico |
| |
Events & Meetings (5 minutes) | Upcoming Events & Housekeeping |
|
Zoom Chat Log
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:01:41.720 --> 00:01:43.560
Byung-Woo Jun: Hello, Dong Wong! How are you?
2
00:01:44.360 --> 00:01:49.360
Byung-Woo Jun: Hi, Biel? I'm good. How are you? Good! Can you hear? Can you see my screen?
3
00:01:49.510 --> 00:01:51.360
Dong Wang (China Telecom): Yes, yes, I can see it.
4
00:01:51.370 --> 00:01:53.560
Byung-Woo Jun: Okay, let's wait.
5
00:01:53.830 --> 00:01:56.359
Dong Wang (China Telecom): Okay, yeah, that's the weight of your second.
6
00:01:56.480 --> 00:01:59.930
Byung-Woo Jun: Yeah, okay, thank you. And I'm mute.
7
00:02:14.610 --> 00:02:15.970
Byung-Woo Jun: Hi andres.
8
00:02:21.290 --> 00:02:24.689
Andreas Geissler: Hi, I hope you can see my screen, too.
9
00:02:24.870 --> 00:02:27.549
Andreas Geissler: Yes, I can. That's good.
10
00:02:29.850 --> 00:02:39.499
Byung-Woo Jun: I think the Kenny and Sandra in training was submitting today. So they're gonna start joining from next week. So
11
00:02:51.780 --> 00:02:53.060
Byung-Woo Jun: nice. Wait.
12
00:02:55.460 --> 00:02:57.340
Byung-Woo Jun: Hi, Shankar, I liam.
13
00:03:08.660 --> 00:03:14.069
Byung-Woo Jun: hey? Let's wait one more minute, and then we're gonna start. Maybe some more people.
14
00:03:19.340 --> 00:03:20.770
Byung-Woo Jun: Hi, Thomas.
15
00:03:27.750 --> 00:03:30.440
Byung-Woo Jun: I we can
16
00:03:30.560 --> 00:03:32.770
Byung-Woo Jun: stop Sandra
17
00:03:32.950 --> 00:03:43.120
Byung-Woo Jun: and Kenny. They are in some meetings or training, so they told us they cannot attend this meeting so.
18
00:03:43.410 --> 00:03:49.900
Byung-Woo Jun: and Donwong, Kaguan and Mars said, we are going to host meeting today. So
19
00:03:50.030 --> 00:04:04.640
Byung-Woo Jun: as a start, I so this is january 20 fifth Tsc. Year, 2,024. I'm going to start our meeting, and then don't want and Kegwan please the.
20
00:04:04.980 --> 00:04:08.100
Byung-Woo Jun: you know, jump in any time you want to,
21
00:04:09.350 --> 00:04:11.690
Byung-Woo Jun: update. So
22
00:04:12.480 --> 00:04:33.230
Byung-Woo Jun: Andrews. So this agenda is 11 cross organization update. We are talking about briefly about own sc collaboration. I see Nk. Shanku I mentioned. But there is some follow up and between Orange and OMT. And Andress can. Briefly,
23
00:04:33.240 --> 00:04:36.580
Byung-Woo Jun: you know. Talk about this and
24
00:04:36.790 --> 00:04:44.000
Byung-Woo Jun: Tsc. I'm not sure any going to join today? At the second we want to
25
00:04:44.350 --> 00:04:47.060
Byung-Woo Jun: make announcements for onap
26
00:04:47.200 --> 00:04:51.339
Byung-Woo Jun: releases prior to London and saying all on it.
27
00:04:51.450 --> 00:04:54.549
releases prior to London are broken
28
00:04:54.560 --> 00:04:57.179
Byung-Woo Jun: because aaf certificate is
29
00:04:57.530 --> 00:05:10.219
Byung-Woo Jun: expired. So you just should select London, plus. That's the kind of the current announcement we want to propose. So we need to some agreement from Tsc member today.
30
00:05:10.510 --> 00:05:18.250
Byung-Woo Jun: Then we are going to change documentation and other Wikis release notes based on that
31
00:05:18.310 --> 00:05:29.709
Byung-Woo Jun: and release status I'm going to share briefly about the project status in new daily releases. And I sent email to Ptl for the key updates benefit
32
00:05:30.040 --> 00:05:42.540
Byung-Woo Jun: and the Pt update. I'm gonna share a brief debrief to what happened this Monday. Not much. And and also we're gonna report our com and oem and the
33
00:05:42.630 --> 00:05:44.530
Byung-Woo Jun: second dates.
34
00:05:44.610 --> 00:05:47.910
Byung-Woo Jun: And then there's some updated.
35
00:05:47.960 --> 00:05:51.120
Byung-Woo Jun: and the event coming
36
00:05:51.480 --> 00:05:57.059
Byung-Woo Jun: on on any summit is scheduled and the session topic agenda
37
00:05:57.180 --> 00:05:58.980
Byung-Woo Jun: has been published.
38
00:05:59.290 --> 00:06:16.810
Byung-Woo Jun: and also Kenny confirmed elephant Dtf. Will follow when he summit. I think it will be same time like last year, and May second and third. So that's the basic agenda. If you have any any additional agenda, just let me know, and let's start from the beginning.
39
00:06:18.130 --> 00:06:31.520
Byung-Woo Jun: So there's some collaboration as Nk. Shankar mentioned last week. and James Lee, and then Luis from Orn, Sc. Team contact OM. And others.
40
00:06:31.580 --> 00:06:37.189
Byung-Woo Jun: and they share their their presentation slide deck. How they gonna wants to use the
41
00:06:37.700 --> 00:06:45.000
Byung-Woo Jun: on it. And Andres, do you have any update for this? You want to and talk about briefly about this?
42
00:06:45.380 --> 00:06:53.749
Andreas Geissler: Yeah, I don't know that the the presentation, and wanted actually, and this week to go
43
00:06:53.840 --> 00:06:59.439
Andreas Geissler: through the slides to give some comments or some feedback to
44
00:06:59.450 --> 00:07:25.429
Andreas Geissler: the let's say, conclusions and the changes which would propose and and we're done so we. Unfortunately, as some colleagues from Tata wanted to present their enhancements, or they change changes and questions, and even want to. Let's say, contribute to OM. We postpone this discussion, maybe to next week.
45
00:07:25.520 --> 00:07:51.170
Andreas Geissler: But in the meantime we will. I will definitely go through the slides and make some notes so that we have. let's say some let's say, Pre, that I have some some pre notes here. What would be done? Or what is the plan? For example, here? Yeah. So there is a plan to deprecate the the message.
46
00:07:51.170 --> 00:08:01.620
Andreas Geissler: So that's something what? Of course we can. We can stay. And all of these these other
47
00:08:01.880 --> 00:08:10.830
Andreas Geissler: thoughts. Yeah. yeah. So I will definitely give that a feedback or collect this feedback, and then we can go next week
48
00:08:10.890 --> 00:08:24.589
Andreas Geissler: in the Om meeting through my notes, and then, maybe, if others would have some other notes from our team, that would do, we conclude that and and give that back to Louise
49
00:08:24.820 --> 00:08:31.000
Andreas Geissler: or James Lee so, and that, that will be done. Yup. And
50
00:08:31.180 --> 00:08:41.510
Byung-Woo Jun: to make some kind of conclusion out of that. Sure, thank you, Andreas, I think you know, maybe next week we can work something from all an Sc team.
51
00:08:41.679 --> 00:08:51.509
N.K. Shankaranarayanan: And as Andress mentioned about Tata communication. Yeah, yeah, just just a comment to Andreas and yourself.
52
00:08:51.750 --> 00:09:01.279
N.K. Shankaranarayanan: when you look, look at the presentation and look at the questions from Louise. Just keep in mind. If if
53
00:09:01.570 --> 00:09:04.660
N.K. Shankaranarayanan: if you think that is a good
54
00:09:04.990 --> 00:09:16.199
N.K. Shankaranarayanan: sort of reference implementation or default method of using own app and OS components for for the Smo.
55
00:09:16.540 --> 00:09:20.610
N.K. Shankaranarayanan: because that's the discussion is going in that direction. And
56
00:09:20.880 --> 00:09:24.620
N.K. Shankaranarayanan: and I would be interested in. If if you think, for example.
57
00:09:24.710 --> 00:09:36.869
N.K. Shankaranarayanan: you might have one conclusion, saying, This is the right thing to do, let him do it, and we'll make that the standard implementation for other people to follow. or he might come to a conclusion, saying, what he's doing is right. But
58
00:09:37.120 --> 00:09:57.670
N.K. Shankaranarayanan: there are other ways of doing it. And so there are multiple options. And so it it'll it will be good to know which way you are thinking that that's the plan. We you know, when we have a meeting with the at the Oem team we test. We gonna discuss about that. We're gonna review the their presentation side.
59
00:09:57.730 --> 00:10:09.300
Byung-Woo Jun: And good thing I found from the slide deck his state. I think that they are moving on to latest on it, frozen because we they had experience with the aaf
60
00:10:09.360 --> 00:10:25.129
Byung-Woo Jun: aaf under certificate. So they, we convince them to to move on to London, plus. So I think the one of the slides that they are doing it. And also, yeah. Also, I think they interest me. Select us. You know
61
00:10:25.300 --> 00:10:38.650
Byung-Woo Jun: the select own app functions, not every owner platform that's a good thing, and conforming to streamlining. And not only the Orient team. We're gonna talk about more tata communication.
62
00:10:38.650 --> 00:10:59.699
Byung-Woo Jun: They are interested in taking some of the owner function. That's a good thing. So Andro's team already supporting the individual project in selection based on the owners streamlining. So I think there's good synergy between owner and the orange and the Tata communication. So anyway, we're not talking about. So, okay, that's the thing.
63
00:10:59.990 --> 00:11:03.559
Byung-Woo Jun: Andrews, do you have any additional comments? Well, we're gonna move on.
64
00:11:04.080 --> 00:11:06.120
Andreas Geissler: No, you can move on. That's fine.
65
00:11:06.560 --> 00:11:11.020
Byung-Woo Jun: Thank you. Desk. Update any question. Stop us.
66
00:11:11.340 --> 00:11:15.560
Byung-Woo Jun: And Amy is not here today. So second
67
00:11:15.950 --> 00:11:20.829
Byung-Woo Jun: we are. We have some discussion this week, and so we know
68
00:11:20.890 --> 00:11:39.290
Byung-Woo Jun: aaf certificate ex expired. And then so we need to tell our customers, and then some participant companies. We need to tell them, all owner releases prior to London are broken because of the af certificate issues.
69
00:11:39.470 --> 00:11:50.450
Byung-Woo Jun: So they should select. You know, London plus. So is that okay, to send this announcement to public. So
70
00:11:51.170 --> 00:11:59.070
Byung-Woo Jun: you know, I like to get some content from Tsc, any objection. Yeah, I'm not sure we're gonna do both, because not enough. But
71
00:11:59.250 --> 00:12:04.590
Byung-Woo Jun: do you have any objection telling the customer we're going to go this path
72
00:12:06.310 --> 00:12:11.910
Andreas Geissler: if you have any objection just wanted me on that. I fully agree with that to do that.
73
00:12:12.170 --> 00:12:13.670
Byung-Woo Jun: Yeah, so great
74
00:12:13.720 --> 00:12:38.149
Byung-Woo Jun: and so this is action point. And then tsc documentation. Thomas, I'm not sure what which document section you need to put that in. And then I'm going to change outcome and also walking with Pablo and Dongwong and Kegwan. We're gonna push some Tsc, Wiki and some release notes. We're gonna announce that. So when
75
00:12:38.150 --> 00:12:56.380
Byung-Woo Jun: they customer look at the own app, and they try to download the own app function. They should know they should select the London plus. Okay, this is kinda done. We're gonna do this. And we're gonna talk separately about how you gonna publish this on it, Wiki? And then
76
00:12:57.530 --> 00:13:03.509
Byung-Woo Jun: Rtd, Thomas, okay, so, Thomas, do you have any suggestion here?
77
00:13:05.140 --> 00:13:15.810
Thomas Kulik: Yeah, just thinking about it. But definitely, put it in the we should put it in the release note in the the composite release note of Umhm
78
00:13:16.260 --> 00:13:21.300
Thomas Kulik: of the the latest release. Yeah.
79
00:13:21.490 --> 00:13:23.260
Byung-Woo Jun: yeah, that's the.
80
00:13:25.860 --> 00:13:36.630
Byung-Woo Jun: And then I look at the David Mcbride previous release note. And then I'm gonna squeeze him. And then I'm gonna talk to you before we publish it. Okay.
81
00:13:36.730 --> 00:13:37.590
Byung-Woo Jun: okay.
82
00:13:38.130 --> 00:13:44.659
Byung-Woo Jun: okay, 2 down. And I'm gonna share this project. Status.
83
00:13:44.900 --> 00:13:58.339
Byung-Woo Jun: okay, this is what we created. I actually, I created copying the David Mcbride. And then we are trying to update the update this page related information. So anything I,
84
00:13:58.600 --> 00:14:11.660
Byung-Woo Jun: and you know, change the orange, you know. So service design. Sdc, we don't have active Pta any longer. Vfc. And the unhong, she confirmed. She's not Pta any longer.
85
00:14:11.680 --> 00:14:41.259
Byung-Woo Jun: So we're not sure. And then so, Thomas, we have a project lead for some of the components, even though they don't have a ptl, but they have a stay, active commuters. So the project is the active. So, okay, we, we have a separate column for New Delhi, and this project is active, even though, we don't have. Ptl, so this is the additional column we're gonna indicate. So this is responsible for the Ptl.
86
00:14:41.330 --> 00:14:48.309
Byung-Woo Jun: And then they have to update the Harlem Chart version, and they want to use for New Delhi.
87
00:14:48.730 --> 00:15:06.409
Byung-Woo Jun: And the good thing is Andrew's Om days is he supports flexibility on the Halem chat versioning. So, Pto, if you don't have any major changes, you don't have to change the major version so. But let Andrews knows about this.
88
00:15:06.410 --> 00:15:23.160
Byung-Woo Jun: Because she need to manage it to umbrella. Helen chat so that as as long as this of some communication between Andrews and the Pto. It should be fine. And then yes, it will be flexible, Andrews, you said, is that my understanding. Is that correct?
89
00:15:25.440 --> 00:15:27.759
Andreas Geissler: Yes, that's right, that's right.
90
00:15:28.030 --> 00:15:49.739
Byung-Woo Jun: So whatever you see. And whatever I get anyway, I know when there's a patch that I will anyway take into consideration for the updates. That's fine. I put the voluntary active. Ui. We know how this really active anyway, and project status new daily. This is the same thing and the key update.
91
00:15:49.780 --> 00:16:01.519
Byung-Woo Jun: So I can't take a few the ptos to update their feature putting key update benefits. So you know, Pto, please the
92
00:16:01.860 --> 00:16:20.800
Byung-Woo Jun: or the Tsc Inquis, Pto to put the information. I think. I ui! They were gonna put the the key benefit, you know, and then update 2 updates one from China mobile, one from China telecom. So this is kind of a changes. Okay?
93
00:16:21.020 --> 00:16:24.840
Byung-Woo Jun: So that's the one I'm back to here.
94
00:16:26.040 --> 00:16:44.990
Byung-Woo Jun: So Etl and the this week, just the we share the information about the how oem helm chart versioning, as you know, supported in the new daily. So we just share this new the plan and handling with the ptl.
95
00:16:45.270 --> 00:17:00.539
Byung-Woo Jun: so that's the good thing. So anyway, if you want to see more detail, you can go to this pages. But that's the basic updates. okay this week. So I think it's a good thing we have a burgeoning flexibility. So okay?
96
00:17:00.940 --> 00:17:04.790
Byung-Woo Jun: And then, yeah, go ahead. Yeah, I have a question
97
00:17:04.940 --> 00:17:09.670
N.K. Shankaranarayanan: we used to. We used to track the use case work
98
00:17:10.109 --> 00:17:12.009
N.K. Shankaranarayanan: book. And before
99
00:17:12.119 --> 00:17:16.349
N.K. Shankaranarayanan: now it's become more autonomous. But there is still
100
00:17:16.670 --> 00:17:21.339
N.K. Shankaranarayanan: activity going on. For example, the Sun use case. We are continuing.
10100:17:21.560 --> 00:17:34.810N.K. Shankaranarayanan: It's all Oran focused. Or in this case Oran and Cps focused. And there is. And and II don't. I know the work that is happening, and some of it is overseas. Some of it is on app.