661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2022 TSC Recordings	2022 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)	Gov. Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Alla.Goldner	AMDOCS	Fernando Oliveira	Individual Contributor
Andreas Geißler	DT	Magnus Buhrgard (Unlicensed)	Ericsson
Bin Yang	WindRiver	N.K. Shankaranarayanan	STL
Former user (Deleted)	Bell Canada	Ranny Haiby	LF
cl664y@att.com - Proxy: Gervais-Martial Ngueko	AT&T	Seshu Kumar Mudiganti	Huawei
Dong Wang	China Telecom	Timo Perala	Nokia
Eric Debeau Sylvain Desbureaux (non voting)	Orange	Yuanhong Deng	China Mobile

Agenda Items	Presented By	Presos/Notes/Links/
Job Transition	Ranny Haiby	Notified the TSC of a status change a couple weeks ago Press release yesterday announcing that Ranny Haiby is now the CTO Networking, Edge/IoT and Access at the Linux Foundation Intend to continue on as a TSC member and other ONAP activities If anyone is concerned with that arrangement please reachout either publically on the TSC list or privately to Kenny Paul , cl664y@att.com or Ranny Haiby
Release Status	David McBride	Weekly Status Report Congratulations - Istanbul release is now officially available !! Jakarta release Last week, the TSC slipped the schedule one week to today (Mar 31) Schedule Milestone Status M3 at 99% (OOF) and M4 at 97%. Use Case Leads have completed their activities - Well done ! Open issue status and trend (non-release-management) #AGREED the TSC approves the Jakarta release M4 milestone with the following exceptions to be completed by sign-off: OPTFRA-1034, OOM-2941. RC scheduled for April 28 REQ-1155 - Getting issue details... STATUS Kevin Tang Need to fix EXTAPI-602 but repo (EXTAPI/NBI) is read-only David McBride and Kenny to discuss process for making bug fixes for EXTAPI/NBI (read only) and get back to Kevin Tang (also see PTL minutes PTL 2021-10-18 ) Kohn Release Proposed schedule #AGREED the TSC approves the proposed Kohn release schedule as presented in v1 of Release Planning: Kohn
RelEng/Infrastructure	Jessica Gonzalez	The old Intel/Wind River lab will be decommissioned TOMORROW! No VMs or data is being transferred. All lab uses are responsible for saving any data. New lab page: ONAP UNH-IOL Lab Previous notifications have been sent to the ptl, tsc, discuss, release and the requirements subcommittee lists. A 3^rd and final notification was sent out a few moments ago. https://lists.onap.org/g/onap-discuss/topic/90010990#23981 Tickets- Open showstoppers: IT-23794 blocking DCAE M4 Release Management ([DCAEGEN2-3112]) Tickets- Waiting on Community: Migration Status / Upcoming Changes
PTL Updates	Sylvain Desbureaux	OOM Gitlab Readout
TCC / ONAP Liaison Updates	Magnus Buhrgard (Unlicensed)	Liaison statement to 3GPP regarding IPR, for approval Reply to ONAP's questions received from 3GPP(ETSI) legal I propose to go through with the LS in order to get an official answer from 3GPP. #AGREED the TSC approves the release of the 3GPP liaison statement Version 1 as attached to these minutes, requesting from them on IPR questions 2. ONAP - TM Forum meeting on Intent based automation - 6th April 3. Presentation in TM Forum’s Multi-SDO Autonomous Networks meeting series (May time frame) I propose to re-use presentation(s) from DTF in January. Other suggestions are of course welcome.
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise		Next CNF Task Force meeting: now @1pm UTC Enterprise Task Force - vote in progress to confirm new schedule
TSC Activities and Deadlines	cl664y@att.com	The TSC approved the ONAP Project Level Badge proposal as documented in v12 of https://wiki.lfnetworking.org/x/b4YZB? SPC - Re: ONAP Strategic Planning Committee (SPC) Representative - Call for Nomination (Deadline April 6th, 2022) - Thank you Alla.Goldner , our former SPC representative 2022 ONAP Priorities / Action Plan - no update this week ONAP Community Awards: Istanbul Release -no update this week LFN Board follow-up actions - no update this week
Upcoming Events & Housekeeping	Kenny Paul	Open Networking & Edge Executive Forum (ONEEF) April 12 - 14, 2022 Virtual LFN Developer & Testing Forum EU June 13-16, 2022, Porto, Portugal In-Person Topic Proposals ONE Summit NA Save the Date! Nov. 15 & 16 2022 Seattle, WA, USA In Person LFN Developer & Testing Forum NA Save the Date! Nov. 17 & 18 2022 Seattle, WA, USA In Person

Zoom Chat Log

06:59:02 From Ranny Haiby to Everyone:
#info Ranny Haiby, The Linux Foundation
06:59:18 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
06:59:28 From Magnus Buhrgard to Everyone:
#info Magnus Buhrgard, Ericsson
07:00:03 From gervais-martial Ngueko(AT&T) to Everyone:
#info Gervais-Martial Ngueko for Catherine Lefevre, AT&T
07:01:02 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:01:07 From Bruno Sakoto to Everyone:
#info Bruno Sakoto, Bell Canada
07:01:17 From Yuanhong Deng (China Mobile) to Everyone:
#info Yuanhong Deng, China Mobile
07:01:22 From bin.yang@windriver.com to Everyone:
#info Bin Yang, Wind River
07:01:29 From N.K. Shankaranarayanan (STL) to Everyone:
#info, N.K.Shankar, STL
07:01:44 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
07:03:52 From Sylvain Desbureaux (Orange) to Everyone:
Hi, Eric is sick and I’ll proxy him but not for vote as he didn’t sent an email
07:07:06 From N.K. Shankaranarayanan (STL) to Everyone:
Congratulations Ranny! Wish you good luck in your new project.
07:07:42 From Timo Perala (Nokia) to Everyone:
All the best, Ranny! Looking forward to continue to collaborate with you.
07:07:59 From Magnus Buhrgard to Everyone:
Congratulations Ranny! Keep up the good work
07:08:25 From Ranny Haiby to Everyone:
Thanks everyone!
07:21:10 From David McBride to Everyone:
M4 exceptions: OPTFRA-1034, OOM-2941
07:21:55 From Kenny PAUL (LFN) to Everyone:
#vote does the TSC approve the Jakarta release M4 milestone with the following exceptions to be completed by sign-off: OPTFRA-1034, OOM-2941 +1, 0, -1
07:22:09 From Magnus Buhrgard to Everyone:
#vote +1
07:22:17 From Yuanhong Deng (China Mobile) to Everyone:
#vote +1
07:22:18 From Ranny Haiby to Everyone:
#vote +1
07:22:18 From gervais-martial Ngueko(AT&T) to Everyone:
#vote +1
07:22:20 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:22:21 From Timo Perala (Nokia) to Everyone:
#vote +1
07:22:24 From Bruno Sakoto to Everyone:
#vote +1
07:22:58 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:23:01 From Kenny PAUL (LFN) to Everyone:
#endvote
07:23:38 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the Jakarta release M4 milestone with the following exceptions to be completed by sign-off: OPTFRA-1034, OOM-2941.
07:28:55 From Kenny PAUL (LFN) to Everyone:
#vote Does the TSC approve the proposed Kohn release schedule as presented in v1 of https://lf-onap.atlassian.net/wiki/x/Dcj7? +1, 0, -1
07:29:05 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:29:09 From Magnus Buhrgard to Everyone:
#vote +1
07:29:11 From gervais-martial Ngueko(AT&T) to Everyone:
#vote +1
07:29:15 From Timo Perala (Nokia) to Everyone:
#vote +1
07:29:15 From Ranny Haiby to Everyone:
#vote +1
07:29:16 From Yuanhong Deng (China Mobile) to Everyone:
#vote +1
07:29:18 From Bruno Sakoto to Everyone:
#vote +1
07:29:19 From N.K. Shankaranarayanan (STL) to Everyone:
#vote +1
07:29:40 From Kenny PAUL (LFN) to Everyone:
#endvote
07:29:45 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:30:17 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the proposed Kohn release schedule as presented in v1 of https://lf-onap.atlassian.net/wiki/x/Dcj7.
07:33:08 From Kenny PAUL (LFN) to Everyone:
https://lists.onap.org/g/onap-discuss/topic/90010990#23981
07:33:37 From Kenny PAUL (LFN) to Everyone:
https://lf-onap.atlassian.net/wiki/x/m7r7 UNH Lab
08:20:49 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the release of the 3GPP liaison statement Version 1 as attached to this page, requesting guidance on IPR
08:24:29 From Kenny PAUL (LFN) to Everyone:
https://lists.onap.org/g/onap-tsc/message/8572

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

07:02:12 Oh, Guidoki, go ahead and get started with the normal administrative.
07:02:22 You y'all would have just gotten the little pop-up meeting is being recorded.
07:02:29 Notice. so I assume You've seen that everyone comes in muted.
07:02:33 Please keep yourself muted unless you're speaking if you are using a phone line.
07:02:37 You can use Star 6. If you send me a private chat message in the Zoom, it will become part of the public record, because I simply cut and paste these, as is into the meeting, minutes.
07:02:58 And this is our antitrust policy. Notice, You should all be familiar with it by now.
07:03:04 This policy is important where we have multiple companies, including potential industry competitors participating in these meetings.
07:03:12 Please review. if you have any questions please contact your company's legal counsel, Members of the Lf.
07:03:15 May also contact Gandhi Upgrove, the firm Gesmer Upgrove Lps, which provides legal counsel to Lf.
07:03:22 The You can also find this policy linked from the Lf.
07:03:26 And all of the project websites, and it is important to note that this policy is in force, whether or not to any member of the Lf.
07:03:36 Is actually in attendance at the meetings. Okay, stop that start.
07:03:52 Start start that. Okay. Sylvan got it. Thank you.
07:04:26 That works for me. Okay, have a quick message from Randy about a job.
07:04:34 Transition. we'll cover the release stuff cover infrastructure We'll get the oem readout on the git lab pilot couple liaison statements to review and then the associated stuff.
07:04:54 We always do anything else anyone would like to see added to the agenda today. Ok. Doke, I will stop sharing.
07:05:09 I know, Randy, you're not gonna share anything but I will turn it over to you.
07:05:14 Yeah, Thanks, Kenny, hopefully, it will be quick just an update.
07:05:20 So, about 2 weeks ago I notified the Tsc. as A.
07:05:25 Required about my job affiliation change I would put them that I'm, no longer employed by Samson.
07:05:30 Research America, but at the same time I would like to continue on my own up related activity.
07:05:36 2 and and roles and commitments today.
07:05:42 I can share with you that some more information about my new job.
07:05:45 So in case you missed the news i've joined the Linux Foundation to serve as the Cto.
07:05:51 For Lf networking edge and access. Once again I like to stress that my intention is to continue all my own up related job and elephant related.
07:06:04 Grows and positions from now on. So basically no change from my side.
07:06:13 5. My intention is to see the success of owner; but if somebody feels that with my new affiliation, it might be inappropriate for me to have any roles or positions please feel free to either publicly or privately, with
07:06:31 me, or if you don't feel comfortable reach out to Kenny or Catherine, and express your concern again. bottom line.
07:06:41 My intention is to continue doing or attempts to do good for this community and continue my roles, and even take morals related to own up in the future.
07:06:51 But we get if somebody since this differently please speak up and in any form you see hit that's all for my side.
07:07:00 Thank you. Thank you, granny. I can say that we are extremely happy to have you as as a member of the Lf.
07:07:28 Ray and I actually got together for lunch yesterday.
07:07:32 It was, hey? good to see each other and and just express. my gratitude for all the work it's been done, and and how happy I am that he's now part of the team.
07:07:50 So thank you so much. Thank you for the opportunity and the rest of the community for giving me the opportunity.
07:08:04 Okay onto Excuse me under release status. Thanks, Kenny.
07:08:12 I think I need privileges to share I didn't come in as came in as some imposter.
07:08:22 David. Yeah, I think maybe i'm Maybe if I just log in there you go.
07:08:32 Okay, all right. Yeah. I think I think I was not logged in when I signed in.
07:08:36 So Okay, Thank you. All right. So I sent out the weekly status report yesterday, so you can see details.
07:08:56 There. Some of that will also be reviewing in today's meeting. but there are some additional details. So invite you to check that out.
07:09:05 If you haven't already. Okay, and then, katherine added a note here, in case you didn't see it the weekly status quo.
07:09:16 We did close out all the remaining issues, and so unless Pavel once to dump a truckload of new issues onto the release.
07:09:31 I think we're done I'm Sorry I did take the opportunity to take a shot at Paabo.
07:09:40 All right, Jakarta. release so just to remind everyone where we're at last week the Tsc.
07:09:50 Decided to slip the schedule for m 4 by one week.
07:09:56 That was due to the fact that we still had a lot to do on m 4, and i'll also. the approval for M.
07:10:10 3 had required that M. 3 tasks be completed by M.
07:10:13 4, and there were still a number of those that were still outstanding.
07:10:16 And so we agreed to slip the schedule for M.
07:10:21 For one week all of the other milestones stayed the same.
07:10:26 So let's just take a quick look at Schedule see where we're at so can see M.
07:10:32 Flora here moved to today. March 30 first release, candidate and sign up are still as they were.
07:10:43 So Rc. coming up at the end of April.
07:10:51 Okay, so as far as the the milestone status.
07:10:58 As I mentioned, a lot of progress made since last Thursday.
07:11:07 So I appreciate everyone's hard work and moving the ball forward.
07:11:15 So, as we currently sit, we are at 125 out of a 126, that's you know 99% plus or the M.
07:11:32 4 project release management tasks 100% on the requirement owners for M.
07:11:39 4, and then as far as our catch up on M. 3.
07:11:46 We have one remaining issue. So between M. 3 and M.
07:11:52 4 2 issues that were behind. Okay, so what to do so I think that we've made sufficient progress that it that it makes sense to go ahead and approve M.
07:12:13 4 with these 2 exceptions. and just ask that those be completed by the Rc.
07:12:25 Milestone. Does that make sense? Does anyone have any other ideas, or hi?
07:12:42 This is Kevin Tan from networking slicing.
07:12:46 Yes, Kevin. Yeah. Hi. So I have a question. We actually have a bug fix to the Mbi ripple.
07:12:53 I need to be checked into an ib nbi report, but the report is up carved, and it's read-only.
07:13:01 So don't know where we need the car line to have to proceed with this issue, and we needed that fix.
07:13:13 You know we have already a talk to Erica but is not on the Quarterly, so he suggested to bring it over to here to have a kind of discuss which which project is a so it's a nbi notable
07:13:32 interface. I think this project and where a network slicing yours, case,
07:13:40 It was kenny. I don't I don't recall that project was that archived unmaintained nbi isn't a project.
07:13:53 It's part of external api but okay this is Archive.
07:14:01 Yeah, So we had a actually. In fact, I think it was the with the network slicing use case.
07:14:10 We had kind of a similar issue come up. I think, at the end of last year, right, Kenny, and I think we had to reopen a repo in order to accommodate a bug fix That was required.
07:14:28 And I think that was also for the the the network slicing use case.
07:14:32 Do you recall that one I I recall so yeah some some manner of of backflips needed to be executed?
07:14:44 I don't remember exactly what it was though yeah yeah sure There's a Ptl meeting on October eighteenth, 2,021 discuss this issue as it discussed like bug.
07:14:57 Fix, so that's the same market, that we actually needed to to do, and at that time it will like it will be open and to be reviewed by active commuter So that's that's a decision from that meeting I
07:15:13 think. Okay, and what's the what's the issue kevin Yeah, the issue right?
07:15:21 So there's a yeah so the chilla is ext Api dash 6 or 2 that's the July ticket issue, and it's so the multiple instance of slide, if it will fail or with the same service Well, for the same service,
07:15:42 the only one instance can be created. So if you creator more deported to fail.
07:15:48 So that's the problem Yeah, sorry what was the number it's so.
07:16:20 Okay. So i'm going to be meeting with with Kenny and Catherine later today.
07:16:28 Talk about an Mondays ptl meeting and we'll have a discussion about this, and then get back to you about how to proceed.
07:16:40 Yeah, catherine's out sick. Okay, all right Okay, Well, anyway, Kenny and I will, we'll talk about it and get back to you with the process.
07:16:57 All right, Kevin. Okay, Okay, thank you thank you so much. So i'm look back at the minutes that kevin brought up from the eighteenth of October.
07:17:10 That time. It said that the repo is unlocked still, but and there are active.
07:17:13 Committers. So yeah, we can we can look at i'm not sure what the status of the repo is at the moment, but off the top of my head.
07:17:28 Yeah, our developers could not submit. or push this fix to the reports.
07:17:34 It's kind of locked, I think okay in which repo is it again?
07:17:46 External Api the bit but wet weather specifically is it called it's external api and it's It's the Nbi repo, so it's literally called Nbi hang on a second let me go
07:17:59 to Garrett and take a look usually it's I think X: Yeah, it's it's I. Nbi: Yeah, it is Mbi.
07:18:26 So just like like that. It is, in fact, set to read.
07:18:38 Only external Api slash. and behind the system.
07:18:46 Okay, all right. We'll look into it discuss it and get back to you, Kevin.
07:18:53 Okay, Thank you. Okay, all right. So, Kenny. So the the recommendation is that we approve M.
07:19:15 4, with the 2 release management task exceptions. So, Kenny, do.
07:19:21 We need. should we vote on that? Yes, we should, and the exceptions are one is right.
07:19:38 1155. No, no, no, that that's a separate issue the exceptions are opt for 1, 0, 3 4 is one.
07:19:56 Are you with me, Kenny? I yeah, I was looking in the minutes and and and yeah, that that Rq.
07:20:07 That's a separate issue. Did you pick up one or 3, 4, Just please cut and paste it into the chat that that one.
07:21:15 Thank you, sir. and actually, since We're looking at this one sylvan, do you know the status of the the preliminary documentation for O.
07:21:32 M. I just as a as a agenda maintenance.
07:21:41 Please, plus a fewer dam. new information about streams and when that season match request. So when scheme will be merged, I will be a bit more documentation when unfortunately, I didn't have time to to do more than that okay, vote is in the chat
07:22:04 window. Give it another few seconds. Okay, gonna close it out. and that carries just squeaked in.
07:23:14 Okay, Okay, thank you. I mentioned this earlier. but Geez.
07:23:28 I think I well, that's not right sorry rc scheduled for stroll.
07:23:36 28. confirm that. Or see. April 20 eighth.
07:23:42 Yeah. So our C is coming up on April 20 eighth.
07:23:48 About a month from now. we have one week for one week short, just because we we so pushed out the M.
07:24:01 4 milestone. but we'll see how we can do Then also I wanted to quickly bring up wreck 1, 1, 5, 5.
07:24:25 Sorry. Actually, I meant should have said 1 0 7 1.
07:24:32 So I was looking Actually, what I was doing is I was looking at the the integration test status, and at this point all of the test plans should be done.
07:24:55 And all of the requirement owners have updated this.
07:25:06 Except that I noticed this one Rq. 1155.
07:25:08 It was still set to not started and so I sent out some email didn't get a response.
07:25:16 And then I was looking at the the epic, the requirement, it itself.
07:25:22 Cps enhancements for Chicago release, and I found this note down at the bottom about the requirement being deferred to defer to tell cone.
07:25:41 But the the change to the scope was to reduce scope when it should.
07:25:47 If it's being moved to cone that means it's being de scoped from the jakarta release.
07:25:52 So I I added, I know. Oh, I see. actually Tony got back to me.
07:26:09 Okay, I guess i'll it looks like like tony is working this. so i'll i'll follow up with with Tony about this, just to see if we can get this strain down all right, Then cone release so
07:26:26 i've presented. This schedule a couple of times in this meeting. it's been linked in the weekly status report 2 or 3 times.
07:26:38 It's also been presented to the the ptl meeting twice, I think, and I haven't received any feedback on it are no issues with the schedule, so i'd like to go ahead and proceed with with a
07:27:02 vote to get the the tsc's approval for the schedule.
07:27:08 So this would have us kicking off on April the seventh.
07:27:14 Our initial milestone. May the 20 sixth approval of global requirements, and with a signed off in on November tenth.
07:27:30 So, Tony, do you want to go ahead, or Tony Kenny?
07:27:34 Do you want to go ahead and and launch the vote what's the version of that document?
07:27:42 Let's see where's it page information I guess just look at the history.
07:28:09 It's the point one yeah and come on cut and paste.
07:28:29 Play with me Here, throw me a bone plank and we go votes in process, maybe a couple more seconds.
07:29:45 Okay, 1, 2, 3, 4, 5, 6, 7, 8. That also carries dong.
07:29:49 Wang got it. Thank you. So that is also approved.
07:30:03 Okay, and Kenny, I think that's it for me unless there are any questions.
07:31:00 Thank you. That And the previous one updated on the decision table. Tsc.
07:31:16 Meeting there linked that the other one Okay. captured.
07:31:54 Okay, moving on the to infrastructure stuff. The old intel lab managed by Wind River will be decommissioned tomorrow.
07:32:09 The This is a hard date, non-negotiable.
07:32:14 Once the lab goes down, it does not come back up any data that was.
07:32:18 There is lost and non-recoverable. No vms or any data is being transferred to the new lab, and all lab users are responsible for saving any data and requesting that new accounts are made in
07:32:36 the new lab with the donated intel hardware that is at the University of New Hampshire.
07:32:45 Previous notifications have been sent to the Ptl list.
07:32:46 The Tsc. list, the discuss list, the release list, and the requirement subcommittee list, the.
07:32:54 And a few minutes ago a final reminder was also sent out to those lists.
07:32:58 The link is here pointed at the discuss list i'll drop that in if you have any questions. the lab page is here.
07:33:17 It's got the instructions on How to how to get your account.
07:33:25 What needs to be done will also cut and paste that link into the chat.
07:33:45 So that is it? Are there any questions if you know of your coworkers that use the lab it wouldn't hurt to reach out to them and say, Hey, just wanted to check and make sure that you've created your new
07:34:12 account in the intel lab and copied or backed up any information that you might want to save.
07:34:20 So that we don't have folks saying Oh, the labs down?
07:34:27 Can somebody please look at it for me, because we you know kind of know that's gonna happen.
07:34:32 But once they realize the lab is down it's too late. So again, any questions on this Ok.
07:34:49 Dooke tickets and show stoppers we've got a ticket here.
07:35:03 23794 garrett merge looks like the last update.
07:35:24 Here was 3 days ago. vj I don't know if you're on the call.
07:35:34 Yes, you are, Hi, Kenny. Yes, actually, the last update is from miniature.
07:35:42 Could send that up i'm so I went to the bottom good grief.
07:35:54 I'm sorry I was yeah sorry. Okay, right here.
07:36:02 This which I saw the update and it. So I think the one thing I want to clarify is I mean the particular request in question.
07:36:10 We were able to progress on it. but I seems like there was some misunderstanding out of the way that the enforcement is implemented from Lf. Side right?
07:36:18 So right now, when a new info audio model is being pushed, the validation if the validation fails, I agree that should be blocked.
07:36:27 Ptls or commitors should not be allowed to override.
07:36:31 But in this specific case I mean there were other jobs which were also being triggered and preferring for different reasons which we know what it was.
07:36:38 Then we've been working on, that so the question was I mean when we tried to override the merge option was not still available and get it for us, so that's what prompted us to I mean part of need to
07:36:48 create a ticket here. So again it goes back to that or personal discussion, I mean, for the info audio on validation would be block regardless of what Job fails, or is it only for info or not verification? if it fails?
07:37:04 Then then the march should be blocked by the committers so it's more of a process question again.
07:37:16 It's right now it's not a blocker for us But yeah, it's just wanted to make sure we we have a clear understanding on how how this enforcement must be done for future changes.
07:37:43 So. So the the issue here is that the because the merge job failed, and it couldn't be overridden.
07:37:55 No, no, it's a very fair job. so the particular it put on you on something shared. if I invoke the 3 separates.
07:38:04 If you scroll down on the note from yeah so that's today.
07:38:06 So I explained here. So basically, there are 3 jobs which were getting triggered and 2 of the jobs where one was running the maven verify, which passed.
07:38:13 The other one was running csit, which failed because of a different, totally different reason.
07:38:16 Outside our project control. But but them keep job. Here is the info dot pm.
07:38:24 Or validation, which was successful, so we thought we should be able to override and proceed with merging the change.
07:38:29 But then, when Tony did the override and we still did not see the option to submit the change, and that seemed weird for us, and that's the reason we created this ticket, Okay, I mean we don't necessarily.
07:38:45 Have to resolve it, or have a i'll come here but can you?
07:38:49 I mean if I don't know if you were a lot of this ticket.
07:38:53 But yeah, if you can look through and suggest I mean what's the part forward, then should be okay right Now it's not a blocker.
07:38:58 So we were able to fix the failed job and rebase it and then go through the watch process.
07:39:05 But they shouldn't be blocked unless the info Rtml verified.
07:39:11 Job had failed in this case, that that that job was successful, so there was no reason to block the march from happening.
07:39:22 So mean in the garret we don't see any option to submit it.
07:39:24 So that was something, and you sure I mean we thought it was a bug in, get it.
07:39:30 But then, later, I think somebody clarified. This was a policy enforced by a love based on previous Dc. discussion.
07:39:37 But then that policy should have been specific to the info Adamel job, but not not for the any other job.
07:39:44 If it is involved, or after it's submission correct me if i'm wrong.
07:39:50 That job has been merged, or so the particular change in question has been merged, so we were able to fix the the other.
07:39:59 Job failure and then rebase and merge. But prior to that, from the project team side none of us had any option to submit it.
07:40:10 We were able to do, override the failed minus one and give a plus 2.
07:40:14 But then, typically, when you do a plus 2, you see a submit option to complete that much.
07:40:19 But in this case we were not seeing that option at all, and get it well for info or channel files there are.
07:40:30 We are strict on that one so if there is the verify doesn't work, then you're not allowed to march on that one right.
07:40:37 But, as I find out right, the very fee on the infrared Rtml was successful in this case, so that that should be the only job The Lf.
07:40:47 Rules should be checking against right not the and if there's any other jobs being together?
07:40:59 , yeah, I guess it's very neat you there any i'm say also I, priority looking issue, because I feel that if ever repo is not building the priority should be first come back and and ensure that any time what do you what do you job our
07:41:15 packing, so was the priority not on should let hold it.
07:41:22 Job should be true all the time. and the first thing to do, unless the yeah, the end for the animal, the 1,000,000 higher issue, or is really a will occur.
07:41:32 I was wondering about the priority in so, and maybe I just.
07:41:47 I just need to read through this. spend some time and and and just read through this.
07:41:54 We're up other other commits to the repo were blocked or not.
07:42:00 No that any other change for the repo we were able to progress it's just for the specific change.
07:42:08 It was blocked because there was some other, I mean, very, very job failed other than the for Dot.
07:42:13 Yeah, my verification itself that's seemed like an odd behavior I mean that's why I created this ticket.
07:42:25 So my understanding is that every yeah, every is now blocked and cannot.
07:42:32 And Tlb did the job are fixed right it's it's for every commit.
07:42:38 No, no, just just this particular moment. So other comments on the input or maybe again for you, mall doesn't go.
07:42:46 But any other change alone. Yeah, I mean, we can still override and merge if we need to.
07:42:52 That was not an issue only for the info art tamal.
07:42:54 It seems. I mean we realized part of this exercise that I mean we couldn't progress on merging that even if we were able to. if we were able to.
07:43:05 Even we were right the failed jobs minus one. This case, Yeah, I mean the bottom line.
07:43:16 I think the rule should have been. I mean the rule is correct to be enforced, but it should have been enforced only on the info Rtml verify status, not not on any other jobs.
07:43:27 Right. So the other jobs we had more and more validation.
07:43:29 Part of the repose that could be some failure, that transient areas we will.
07:43:33 I mean in this case both we were able to progress and address those issues.
07:43:37 This was a failed certificate issue on one of the other project component and and we were able to use a different image to get past that again.
07:43:47 Those are issues which we can work through a separate bug and fix it.
07:43:53 And info ttml is specific to getting the committed roles and assignment completed right, and that and since that validation had passed, I mean there was no reason to block that change for being merged as long as
07:44:06 that. But if my job is successful, Yeah, I agree with you in general.
07:44:14 But here I have to question so first i'm not I don't know if it's what you ask for is, do we want in guide?
07:44:23 I don't not guide them in sorry and would Would it be possible easily in 2 bikes and Jenkins Sorry, because again, i'm not an expert on a Jenkins to when you have only and further channel
07:44:38 that Jesus started then only as you inferior verify being started, and not just one.
07:44:45 So it would. Yeah, allow you to to be a lot faster because it's right, right?
07:44:49 Yeah, that was one of the I think recommendation came from this Right?
07:44:54 Yeah, we can tune up the jobs to make sure they are only involved when they are needed.
07:44:59 I mean up until this one. we'd run into this issue But that's something we can. Yeah, make sure the other jobs are not being triggered.
07:45:08 But yeah, i'm not saying that you should do that then so, and I was just I think if it was easy to do, because I understand that it may.
07:45:18 I know that, Om. Repo. We had this kind of issues, and but awesome for some deaths.
07:45:25 We are. He put one that away. It was too complicated to do nuts pretty good, so we we kept them.
07:45:34 But yeah, but I kind of agree with you i'm not sure this is doable with that with Jenkins, and there are so many configuration everywhere that's very up to you to know if it's possible or not to be
07:45:50 honest, but maybe that that's the main issue that it's each.
07:45:58 I agree with you. It should be exactly what you are saying but I'm. Not sure.
07:46:04 It's specific Okay, yeah, i'm not yeah I mean that's something.
07:46:07 If I left can clarify and conform right if if it is what it is, then yeah, I mean, we can make sure we go to effort to pim down the other jobs being invoked winning for audio, model, I mean it's tough for
07:46:23 some repose in this case. Yeah, because typically all the project very face starts. If there's any change on the root level and info dot, Tml is on the root level. So we need to exclude the invader tml
07:46:36 and and yeah, I mean feasible but yeah it's still something.
07:46:43 If if the ptls or committers are allowed to override in specific case, because we know the intricacies of each jobs and how they are related, I mean, we don't override.
07:46:53 Required. I mean I mean needed job to just to budget.
07:46:57 But at least in this case we know it was and related.
07:46:58 And we should be able to safely merge so yeah I mean again, I mean at this point, as I said I mean it's it's not a blocker but it's more of a process clarification question so getting an elephant if that's
07:47:13 something. can be looked at. an interview. see there's room to optimize the enforcement checker.
07:47:22 Then that'll be good. If not, then yeah If not I think there there are other work around. Some project teams can do, but that would be a of course not. not.
07:47:32 The preference. but for code. Okay, Okay, yeah, I I.
07:47:55 The main thing is is we don't have a blocker currently correct?
07:47:58 That's correct. Yeah, Okay, we've got what appears to be a bit of a corner case.
07:48:09 And not sure that even can do do what's requested in Jenkins.
07:48:20 I certainly don't have enough detailed background of this I did look at it a while ago, but I have not done the level of drill down.
07:48:30 That's clearly required to fully understand this so I guess I will look at that, and then consult with the with the folks on the rel inch team.
07:48:46 But one thing, Kevin. this ticket is merged so it's not blocking anything.
07:48:50 No, it's not yeah. I I did not this is a blocker here, but i'm not sure who brought the ticket in this discussion.
07:49:00 But yeah, it's currently it's not a blocker for us Okay, no.
07:49:15 Okay, well let's let's move on then Sylvan.
07:49:22 Do you need permission to share? Yes, please. Okay, one moment.
07:49:33 There you go, sir, so I have another pre-paired specific line I have.
07:49:44 I will share the site I have a used during if one
07:49:55 I have used during a left networks developer and testing forum.
07:50:00 I will just go fast on main points and and and not go to to deep into the details.
07:50:11 A. So just as a yeah, yeah, everything is really on Ohms side since October.
07:50:24 Unfortunately when we were already it was very close to to the release of Istanbul, so we prefer to defer, and as a release of Istanbul was also very close to Christmas time, we prefer to differ
07:50:41 also after Christmas and New Year. and unfortunately, as you know that that at this momenta times have been notified internally that I would start to walk on an app.
07:50:52 So I have preferred to to let the next pitch to take the decision to use a github or not.
07:51:01 But the the decision thing. 2 walking since this is already to work since October.
07:51:07 So we just go very fast, and Om and I get you and the job migration.
07:51:15 As I said, I will try not to take too much of your time, but but just to say, that's a Jenkins uses.
07:51:26 Vm: So all the dependencies are shared it's complicated to discard against different version of the semiconductor.
07:51:36 That is the way we would like to do. and most of the Jjbs that are proposed by my Linux foundation idea.
07:51:44 Obviously for Maven. So we Java code, and a little bit of doctrine, and not at all for what we did for for for Om, which is musty, Emma.
07:51:54 So we are kind of. We are always on the corner case.
07:51:58 And not really in the mainstream case, as, for example, this image for us,
07:52:07 Jenkins has more than issues and the needs so So the current guy choose of Omi is to to a further the the first I'm.
07:52:19 Taking a very, because we have to think of the I. Jenkins move to deeper and deeper.
07:52:22 Shi. So in great there is 2 that are there.
07:52:28 The stress. we check that to people the guy who was pushing a mass request as a valid cla signature, and i'll show that we have a issue.
07:52:39 Id and a sent by a stuff into the dipole.
07:52:46 You can put anything you want after the issue, Id as long as it is respect.
07:52:51 And what is a Gidd in in a in a ownup?
07:52:55 And and the same day as Long as it's a as to what should be Bsn by it's also a source, an off-site. G.
07:53:06 Jenkins Sweezer performed the which is a basic but it's a to quite complex. thing.
07:53:11 So we are verified that Elma, and maintained by script that we have no white spaces of there.
07:53:22 In. In our files the images are being released, used, are released, and not on, and not staging images.
07:53:28 The commit message has a specific format on top of the format.
07:53:31 That is a mandatory for any projection title on app.
07:53:37 And if you are users at some the transition we'd done your system documentation link.
07:53:42 So all of that is performed the agent in some of them.
07:53:47 But we also already use a github, Anna. So micro services to perform gating, so dating is the state of we deploy.
07:53:55 Fool enough with the current change, and we verify that the current change is so deep print.
07:54:02 She's not done by Jenkins for lots of reasons and that's done today with Gfc.
07:54:09 So if we look at the Eigenvalue, we have a several microservices.
07:54:15 We are using internally 2 to 2. Yeah, from the asynchronous as in colusory partner, we are using Mqtt. which is a message queue, a very simple message queue, and and we are listening to
07:54:29 Beerita when there it is. clearing an event, and we are listening to all events.
07:54:37 And guys, We are pushing this event into Mtt.
07:54:37 And the gating controls are on least need to. some topics and some events, and where they are finding an events in pursuit for them.
07:54:45 Yeah, we'll add the review into the queue and if there is a walker available.
07:54:49 They will go and start, and if it's not available at the end of his work worker will ask you there any work, and if it is the we lunch, and at the end of the gate, it will to and some some information
07:55:04 to to get to for the people to know that where we are this is something that we are using for for long time.
07:55:13 So if we want to to move out of that to get level, then we will to.
07:55:18 We need to take Job by German to see what the what is.
07:55:24 So, as we can understand, there are some texts that are sensitive because of a need to have access to institute.
07:55:32 That does. so. For example, this here check needs to have a list of all users if we want to upload to to an X 3 interests.
07:55:42 So that means that we cannot put this credential or this list of signature.
07:55:47 If we were an open. so we need to to have a kind of work that I just watch for the select check.
07:55:57 As nothing was available on a rfid side and maybe It's not the case in your but that's what we did so.
07:56:04 We are using external validation, which is a feature of details that any times you are pushing code into mandatory requests.
07:56:15 2. Then it's a weboop and you are sending a webbook with all the new changes to a specific Url, where we have our externalization from gender that will verify that the message specified is
07:56:31 following: So right, Jason, that Doesn't. and it will send that again to this Mtv.
07:56:37 Sage the and then we will have Cs check that will verify.
07:56:41 That the zoom. So the committers of this match request all of a Cia being signed, so the sensitive part is into a Cla check.
07:56:56 But, as you can see here, I check is not accessible unless you have access to Mqtt.
07:57:00 Which is not open to industrial and that's That's a way we have a tour to have a the least possible opennessa to to this kind of stuff.
07:57:16 For Edmund blood. we will use a protected and environment variables. That's something that is already there in in a in deep lab, and we can use a funny and protected branch, and we also can have a specific for master
07:57:30 and for for tags, for example. And so, this is something that could be done very easy as long as we have the the current insurance.
07:57:40 Of course, so ordering tactics, tasks are performed in dedicated steps.
07:57:47 So we are using dedicated docker containers.
07:57:53 And we are using superst groups that are already merged into A.
07:58:09 And also this Cia Fileer description. The task will only be scared that only if we need to, as you have understand to do.
07:58:09 Vj. sometimes to if you change on only a specific file you don't need to perform the whole linking.
07:58:14 Yeah, this is a the case also for ourselves. So, so, for example, the dark task is that there are the uneves of Durk full.
07:58:23 Do I search all the dating, The ending, which is super long, and so on, is triggered only if the Kubernetes further, where we are all our landmines.
07:58:31 Yes, through the other, and so on. So for their gate we have 2 issues.
07:58:39 We need to to work with Di, because in the integration, and so are also using the get. But we will get it, and we get that.
07:58:50 So. and I will still have this Q system to to have, because we only have 2 dating Csma fugating instances.
07:59:01 So that means that we need to share them between everybody So long.
07:59:05 Story short, we have added a new micro services for Github, and at the end the gate controller in nt worker are the same.
07:59:16 We are only here translating a little bit the request from data till we again, with external coverage to change that, and at the end we are pushed toments into the cab, and not be it and sorry it's the idea but you should
07:59:30 see. you can and oh, no it's a yeah no you it's a it's a github.
07:59:39 Sorry so shouldn't cbi but detail and yeah the things that we are pushing a comment into the live and not recommended to get.
07:59:47 So Adena alcohol is available here.
07:59:53 Everything has been deployed on an app as your toing zone on one communities.
07:59:59 As I said it has been it's it's walking we can be right when we went, and and and as I said, I think it's shouldn't be my decision as I knew at this time that I was not I wouldn't
08:00:14 be involved, you know, in ownap starting April, April.
08:00:20 Sorry, so I prefer to give this decision to to the next people.
08:00:24 So that's pretty much what they have I hope I wasn't too fast.
08:00:28 But maybe I I have a Saman X. So yeah, So I would to push card.
08:00:37 You use a fork, and then, when you create a mad request, it will be a branch.
08:00:44 Here. gaina and so the target transmission must be on a and that's where all the magic and all the Cia will add any questions.
08:01:00 Comments. I'll did I list everybody so the report currently is narrowing the main.
08:01:17 The change that are currently done through 3 we go Demos with.
08:01:22 So the report they O. M. repose a meal in Github, like everybody, but also in bin laden.
08:01:32 Yes, on a deployment school one year. can see this one yeah so of course it's old one.
08:01:40 But if you go today to own app slash poems O. M.
08:01:45 You will see there are zu zoom actually good. Yeah.
08:01:56 So this was being done as a pilot exercise so a couple things since the pilot started.
08:02:12 I'm to the best of my knowledge, easy cla now supports git labs.
08:02:19 So I think that that would be functionality that that the the workaround that was put in place.
08:02:26 I don't think that that would apply anymore. but the the main question to the Tsc.
08:02:38 Is Is this a model that you want to move the rest of the community to?
08:02:51 If if I may it varies over the case.
08:02:52 You to detect that as we haven't proved the missing here.
08:02:57 We have just proved that we can do that but we never prove that it's usable every day.
08:03:03 We never really use it again. I i'm really sorry about that 50%.
08:03:10 But but clearly today no projecting to on app. I have used G. diplas.
08:03:18 The only project that is the clothes, the o end that
08:03:25 Try to see if he can do everything he wants into detail.
08:03:26 But all the committers of the usual person pushing into accessing the workflow and distance and and said it was okay.
08:03:38 It's. Okay, I see, I see values or I feel there it and so on.
08:03:43 So I would. just yeah to say that I think that if the Ts wants to go further erez agmoni, it should at least test really in the field on on some on one project.
08:04:05 Okay, So from the the perspective if if I if i'm understanding what you're saying, the oem pilot really can't be used as a pilot to determine whether or not the Tsc.
08:04:37 Can make a decision. It can be used but the pilot has not started yet again.
08:04:45 That's that's my main issue I would say my generation has done.
08:04:51 But it's not really used by the Om. team or Someone who has wants to make patches on over M.
08:05:02 Chart spread, and before we have improved that I think no other project should start.
08:05:17 You know, I think, before it is really proven the day 9, and also for the project.
08:05:30 Maybe the concern could be a bit different, because, as we were explaining C. O. M.
08:05:34 As a different concerned, and the other project that are more Java and Maven project.
08:05:38 So there's still a yeah being done for omega to meet the apply right away because the other projects have different.
08:05:53 Yeah, that's for sure, After as I am using github every day at my work for me, I owe your work.
08:06:03 I do believe that you you could. You could use a github or Maven super easily, maybe with mathematics to be revised at all, because and from bite on Java when you live in 1 15 and stuff like that
08:06:16 that that is a bit more complicated into Jenkins.
08:06:19 But again sees out walking. now for your agent instant that's really a up to the Tsc.
08:06:28 Ptl to decide the game was it at least I think that That's why I thought I feel that tested with the oem was interesting. Because, again. O. M.
08:06:39 We have no interest to to be, and jenkins but that doesn't mean that we are not We we would move to Github just to to say that we don't want Jenkins.
08:06:54 I really wanted to have a point of view of the different Pcs that are pushing 32.
08:07:00 Oh, am I so like every J like us like to yeah, like all these people like that that that are pushing your regularity according to them, to to see their feedback on the journey into detail.
08:07:13 And to is the C values github without any outfit changing their own projector. that they have been interesting.
08:07:23 That's why I thought the was a good feat, for that and if at the end of the day, and so there, Venus Yes, it's a we prefer yes, it's okay, and and again, the goal was not to put
08:07:38 everybody a change just for changing, because Chinese is good it's really to a to test that, and to see the value for, or an app community.
08:07:50 Unfortunately, again, without a real pilot. we we cannot go very fast so far.
08:08:06 Okay, So I think, then, at this point, unless the Tsc.
08:08:14 Feels differently. i'm would hazard a guess that there's not a big appetite for moving forwards towards Gitlab at this time, at least.
08:08:39 I would say, for at least as a member of of the a little bit of a member of the O. M. team, I mean. I wish I would.
08:08:47 100 suggest that we still would tried it out and see what surveill suggested.
08:08:55 I mean that the people should get let's say used to it and check whether it helps or not.
08:09:04 And of course we would meet and to make some that's a kind of instruction.
08:09:09 So how to use, Then get lap instead of garrett for the reviews.
08:09:16 But I think that needs to be done I think but would keep it at the moment on the oem level, and then try it out.
08:09:25 But that's my but i'm not the ptl Therein lies the problem right?
08:09:33 We need somebody to be the champion of this Yes, definitely I I think it's more of an on app level discussion.
08:09:42 Really it's not simply just I know the oem project was some out of a pilot.
08:09:46 But all projects were to move to github think all projects would need to have experience and had to use git lab and what's involved.
08:10:00 Maybe you disagree unders, but I think it's more of a Yes, of course, I mean finally, Yes, but I think we have not really tested it on even on one project.
08:10:08 So the pilot is not finished in that way, because we have not.
08:10:12 So it was that the preparation has been done, and so on.
08:10:15 But it was never used. Let's say by we owe him even to see if it's useful, or not of course, but I think we cannot now decide.
08:10:25 Now to go every to go completely and and own up to to O. M.
08:10:29 Unless we have 2 proven that it's that it works on at least one project where it is let's say quite easy to implement, because we are just implementing for whatever files which are then compiled and stored in some
08:10:45 artifact, repository, but not not having any maiden files or something made builds.
08:10:52 And these kind of processes I mean that's the easy way the easy thing in the own-up in the oem project.
08:10:57 But yeah, I don't know so how to finish I have to continue that.
08:11:13 Okay, Sylvan. Thank you for all the work. Thank you for pulling the presentation together, and I guess the Tsc.
08:11:27 Is going to need to figure out how they would like to approach this, or if they would like to approach this course, the larger issue of how we are going to handle Om.
08:11:41 Going forward is still looming. so oh, a lot of things in flux here!
08:11:55 If everyone's. okay, i'd like to shift then to the liaison statements with Magnus.
08:12:03 This was something that was pushed forward from last week. Yes, thank you, Kenny.
08:12:10 Can you share the There you go I at least I don't see it? Let me share. Okay.
08:12:23 Hang on saying I'm sorry. Yeah, Yeah, No, Sorry yeah so I talked about this a couple of weeks ago.
08:12:33 But I got to got a request to check with Threegpp regarding some Ipr issues.
08:12:41 I did send a mail to them, and I got a response.
08:12:46 But what I want you to approve today is the liaison statement that I put together to a request to clarify whether there are Ipo issues with using threegpp terminology, and if a information objects and names in in code
08:13:03 contributed to ownup, so it's it's quite simple This one I got help from from Shankar, and others.
08:13:12 We'd be examples, and so on so I mean and i've I've talked about this before, but it is a we request for guidance, and and we've put some incentives for clarity and exams of
08:13:31 potential issues, so showing how we can get a divergence between threegpp specifications and the ownup code, and that would sort of maybe stop us from from having a standard standards compliance.
08:13:50 And it will also be difficult to then monitor code and and see if they, if it follows the 3 Gpb standard in a certain respect.
08:14:01 So there are many benefits with this, and maybe you can.
08:14:07 I i've put this down in a way that that it's the same way that I actually presented before It's just a more formal it's a document and that that formally goes from own up to to
08:14:28 threegpp, and we can look at the next. Pdf! that I put in.
08:14:37 This is a preliminary then reply from the the threegpp legal. I'll learn Threegpp is the trademark of Etsy.
08:14:47 So it's actually at illegal that provided this so we got to one answer on the terminology, and names that they thought that this would be okay.
08:15:03 But when it comes to copyright licensing for threegpp code or files, they had some complementary questions on that.
08:15:14 So we will continue to work with that and meanwhile some having a formal liaison statement will help the the communication. So i'll.
08:15:29 I'll stop there ask if if there are any anything any any ejections to descending this layers on statement I don't know. can, if we need a formal vote on this?
08:15:47 I? this is a a non-binding agreement.
08:15:50 We are asking for guidance, and on this. Yes, right we are. We are asking questions.
08:15:58 We are. we are, you know you've provided you know hey?
08:16:02 This is in your best interest, and any comment from each, and correct Thanks, Magnus, for doing this. and this is already, I think the stakeholders have already looked at this.
08:16:18 Yeah, that is It's a great letter it should be sent I guess.
08:16:25 But the question is, do we need to formally approve it as a board?
08:16:29 I don't I don't think there is there should be objections.
08:16:34 I support this. Thanks, Thanks, Chunkar. Now I think that we can.
08:16:39 We can just ask people here if they have any objections and if we don't hear anything.
08:16:45 I will be okay to to send it then yeah i'll just , Yeah, I think we've had a fairly long It has been very long that we've been kind of trying to get clarity on this so I would
08:17:06 support to just move on with it. And in Magna cell.
08:17:15 I have not responded to your email about those 3 points.
08:17:17 I think I just want to. We could. We should have discussed this yesterday.
08:17:22 Actually I saw that later. i'm not surprised by that question but I think our answers are probably 2 and 3, but but we should do it properly.
08:17:31 Okay, So I'll put up some some special meeting with those who are most affected.
08:17:37 And we came to see Yup. Okay, thanks Okay, So what I'm going to type into the chat window is that the Tsc.
08:17:48 Agreed. The Tsc. approves the release of the liaison statement.
08:17:53 To 3. Gpp: Okay, thank you Then i'll be fast with the other 2 items here.
08:18:09 Number. if you go back to the the agenda I have number 2 here, it's we've do I've put up a meeting between ownup and Tm. forum when it comes to intent based automation and
08:18:28 Dong Wang has kindly agreed to to present the intent use case in in ownup, and we've asked the team forum.
08:18:37 People who have worked with their specifications and they've done quite a lot of work on intent, and to to see how they, their specifications could support the the ownup work potentially.
08:18:52 If there are things that that they can help, they can offer, or sort of clarifications in the specs that would help the work in known up, and then vice versa.
08:19:05 Of course, if there are things in known up that they won't want to pick up.
08:19:12 So I have call for meeting on the sixth of April next Wednesday, and if others here are interested in participating, send me mail.
08:19:23 Allow I'll forward the invitation to you and that is It This is based on the sort of a a Yeah, a proposal from from Tm.
08:19:37 Forum to to listen to their specifications, and and I thought I would turn the the table around a bit.
08:19:46 Here previous meetings. That team form aside with with other organizations has been more of a monologue.
08:19:54 They've told people what they have not that much discussion and not that much question.
08:20:00 So I thought I would try another form here. and and that someone who is actually done something in intent can can show them, and they can react on that so hopefully, that will be a better dialogue.
08:20:16 So that's number 2 number 3 we have been offered to present, and I've talked about this before as well on the team forums multi seo autonomous networks meeting series.
08:20:30 There's something that they organize, that that they have participants from from several Stos, and I thought that we would use this opportunity to talk about owner, and I propose to maybe reuse presentations from the dtf in January there is a couple of
08:20:50 suggestions. but if there are other suggestions as well yeah it's of course welcome.
08:20:58 They're welcome. This is a may timeframe so We will have some some more time to the to talk about this, but I just wanted to inform about this, and I've also sent the mail to few people in the in the
08:21:14 Tc. to to get their sort of to support or or comments on this and team.
08:21:29 I saw your your mail about this so thanks yeah so let's say that this is a point for information now, so i'll continue to work with this and come up with this suggested topic or topics to present to to this
08:21:54 multi sto autonomous networks meeting series. And and, as I said, any any suggestions that you think we should bring up work we have done. Please reach out to me. Thanks.
08:22:20 Okay, Thank you. Magnus. appreciate it. Let me get that drop to into the decisions.
08:22:32 Page: Okay, Dooke Cnf: task force voting progress for a new meeting time.
08:23:16 Yeah, I think that was decided. Yeah, I thought so, too. So maybe that was just a cut and paste.
08:23:26 I think we have a ongoing vote for the enterprise task force, which was the bullet youth, history. How was that?
08:23:34 Oh, it was what enterprise? Oh, yeah, yeah, both under this.
08:23:39 Okay would help. If I read. I would help if I read.
08:23:48 Sorry. Okay, y'all Approve the on app level badge. I will pull the data. get it sent off to Brandon so that the badges can be generated.
08:24:10 Catherine sent out a vote for a call for a Spc.
08:24:16 Representative The email link is there it in chat window.
08:24:34 Interested. Please respond to that, and updates on that stuff.
08:24:43 And got all these happy little events coming up. Yay got to save the dates for the summit and the developer event.
08:24:56 That will be piggybacking upon that for November.
08:25:01 So please save those dates on your calendar. that is it for today anything else anyone needs to chat about.

Agenda Items

Release Status

RelEng/Infrastructure

PTL Updates

TCC / ONAP Liaison Updates

Task Force UpdatesCNF, Wiki 2.0, ONAP Enterprise

TSC Activities and Deadlines

Upcoming Events & Housekeeping

Zoom Chat Log

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise

Browser not supported