Happy Lunar New Year!

BRIDGE: https://zoom.us/j/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) proxy Byung-Woo Jun	Ericsson
Bin Yang	WindRiver	N.K. Shankaranarayanan	STL
Former user (Deleted)	Bell Canada	Ranny Haiby	Samsung
cl664y@att.com - proxy for the last 30 mins: Amy Zwarico	AT&T	Seshu Kumar Mudiganti	Huawei
Dong Wang	China Telecom	Timo Perala	Nokia
Eric Debeau	Orange	Yuanhong Deng	China Mobile

Agenda Items	Presented By	Presos/Notes/Links/
LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board	Heather Kirksey	DTF open topic and follow-up discussions. Discussion of having a smaller event focused purely on topics that came out the January DTF. Focused on cross community strategy. 2 days smaller groups, Question or topic based brainstorming that are collaboration based. likely would need to cxl standing meetings, but far fewer people would be attending the sessions Ranny Haiby volunteers for the planning committee. Sometime in March
Release Status	David McBride	Jakarta release M2 scheduled for Feb 3 CLI and VNFSDK projects remain active but have withdrawn from the Jakarta release Milestone Status Projects - 96% Requirements: 100% ArchCom Reviews M3 scheduled for 03 Mar 2022 #AGREED TSC approves the M2 milestone for Jakarta with the exception that MULTICLOUD-1431, SDNC-1648, CCSDK-3552, CCSDK-3547, CCSDK-3551 & MULTICLOUD-1429 are closed by the M3 milestone. Istanbul Maintenance Release Open issues VNFSDK-827 - Getting issue details... STATUS - Former user (Deleted) requesting help with fix Proposed release date - Feb 10 (assumes that issues are closed by Feb 4) Status of daily testing on Istanbul branch? Michał Jagiełło Ongoing stability issues. Some issues in the lab, some issues with Nexus. (see comments in RelEng section of the agenda) Schedule risk due to remaining open issues, as well as lack of stable daily test results.
TSC Elections	Kenny Paul	TSC Vice Chair Election Kick-off - No self-nominations - ended on 31 Jan 2022 - extend or leave "as-is"? #AGREED leave as-is with no Vice Chair in 2022 New ONAP representative needed for the SPC SPC meets on the 2nd Monday of the month at 15:00 UTC open to any community members for the community coordinator Alla.Goldner notes that the SPC is currently reviewing its role in LFN cl664y@att.com work with the community on closing on the SPC representative 01 Mar 2022
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements, Marketing	Brandon Wick	Call for ONAP Proof Points for 2022 marketing Badging program launch Slides TAC Badging Page: https://wiki.lfnetworking.org/x/vYu5Aw ONAP Badging Page: https://wiki.lfnetworking.org/x/b4YZB #AGREED Kenny Paul will work on the badging program criteria and then bring the criteria back to the TSC for ratification.
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise	Byung-Woo Jun	CNF Task Force - CNF/Cloud Native - Call for Volunteers to work POC Onboarding: Application Package Onboarding to SDC, Orchestration: ASD-Based CNF Orchestration PoC, Distribution: Application Package Distribution Presentation Slide deck: ASD-App-Onboarding-LCM-PoC-Update-20220203-2.pptx Wiki 2.0 - Call for Volunteers
RelEng/Infrastructure	Jessica Gonzalez	Tickets- Open showstoppers: follow-up to Nexus3 instability IT-23485 IT-23559 Michał Jagiełło reports that master branch seem to be stabilized test for master branch, should have istanbul branch running by tomorrow Tickets- Waiting on Community: Migration Status / Upcoming Changes Intel → UNH-IOL lab migration
RelEng/Infrastructure	Michał Jagiełło	Proposal for an additional lab on Azure to run daily tests on Azure so ONAP community would have it’s own and independent schedule to execute tests.
PTL Updates	Thomas Kulik	We are lacking Thomas Kulik Recommend adding a new section to the docs, maybe https://docs.onap.org/en/latest/guides/onap-operator/settingup/index.html Installation how-to video would be helpful Prior contract work was focused on vFW use came primarily. and a bit out of date now. Installation via OOM: https://docs.onap.org/projects/onap-oom/en/latest/oom_cloud_setup_guide.html#oom-cloud-setup-guide https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide.html#oom-quickstart-guide vFW Use Case: https://docs.onap.org/projects/onap-integration/en/latest/docs_vFW_CNF_CDS.html#docs-vfw-cnf-cds
TSC Activities and Deadlines	cl664y@att.com	ONAP Community Awards: Istanbul Release - nominations open through 14 Feb 2022 2022 ONAP Priorities / Action Plan - next week TSC 2.0 - Project Life Cycle: next week 2021 Project Lifecycle Proposed Edits - tight to the Unmaintained project discussions - see action items from TSC 2021-12-09 Weekly meeting on Monday (let David McBride know if you'd like to be added to the invitation) LFN Board follow-up actions - will resume after the LFN DDF - next week Prepare TM Forum presentation (April 11th, 2022) - next week
Upcoming Events & Housekeeping	Kenny Paul	Open Networking & Edge Executive Forum (ONEEF) April 12 - 14 Virtual LFN Developer & Testing Forum, Week of June 13th 2022 Physical Event Porto, Portugal

Zoom Chat Log

05:55:09 From Sai Seshu to Everyone:
#info Seshu, huawei
05:57:20 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
05:59:34 From Byung-Woo Jun to Everyone:
#info proxy Byung-Woo Jun, Ericsson
06:00:53 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
06:01:00 From N.K. Shankaranarayanan to Everyone:
#info N. K. Shankar, STL
06:01:11 From Fred Oliveira to Everyone:
#info Fred Oliveira
06:01:16 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
06:01:17 From Bruno Sakoto to Everyone:
#info, Bruno Sakoto, Bell Canada
06:01:37 From Eric Debeau to Everyone:
#info Eric Debeau, Orange
06:01:38 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
06:02:35 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
06:03:08 From Catherine Lefevre to Everyone:
#catherine lefevre, att
06:13:27 From Amy Zwarico to Everyone:
question: will non-participating projects update vulnerable packages in their applications?
06:20:28 From Kenny PAUL (LFN) to Everyone:
#vote does the TSC approve the M2 milestone for Jakarta with the exception that MULTICLOUD-1431, SDNC-1648, CCSDK-3552, CCSDK-3547, CCSDK-3551 & MULTICLOUD-1429 are closed by the M3 milestone. +1, 0, -1
06:20:47 From Andreas GEISSLER (DT) to Everyone:
#vote +1
06:20:52 From Timo Perala (Nokia) to Everyone:
#vote +1
06:20:57 From Sai Seshu to Everyone:
#vote +1
06:20:58 From Eric Debeau to Everyone:
#vote +1
06:20:58 From Bruno Sakoto to Everyone:
#vote +1
06:20:58 From Fred Oliveira to Everyone:
#vote +1
06:21:16 From Dong Wang (China Telecom) to Everyone:
#vote +1
06:21:23 From Catherine Lefevre to Everyone:
#vote +1
06:21:30 From Byung-Woo Jun to Everyone:
#vote +1
06:21:52 From Kenny PAUL (LFN) to Everyone:
#endvote
06:21:53 From Ranny HAIBY (Samsung) to Everyone:
#vote +1
06:21:56 From Catherine Lefevre to Everyone:
Happy Lunar New Year Dong to you and your family !
06:21:59 From Alla Goldner to Everyone:
#vote +1
06:22:19 From Dong Wang (China Telecom) to Everyone:
Thanks a lot!
06:22:30 From Heather Kirksey to Everyone:
Happy New Year!
06:22:33 From Catherine Lefevre to Everyone:
#vote +1
06:23:43 From Kenny PAUL (LFN) to Everyone:
#AGREED TSC approves the M2 milestone for Jakarta with the exception that MULTICLOUD-1431, SDNC-1648, CCSDK-3552, CCSDK-3547, CCSDK-3551 & MULTICLOUD-1429 are closed by the M3 milestone.
06:27:33 From Catherine Lefevre to Everyone:
Congrats ONAP Community on M2
06:28:49 From Heather Kirksey to Everyone:
Congratulations!
06:37:31 From N.K. Shankaranarayanan to Kenny PAUL (LFN)(Direct Message):
#vote +1
07:04:03 From Catherine Lefevre to Everyone:
Thanks Alla ! I need to drop - Amy will be the AT&T representative for the rest of the TSC Call.
07:05:43 From Catherine Lefevre to Everyone:
Dear TSC members - if one of you will change his/her mind about TSC VC position next week or in the coming month(s), we can always re-discuss with the TSC board and potentially re-open this role. Thank You

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.

06:03:36 Okay.
06:03:38 Yep, that's going.
06:03:46 Welcome everybody.
06:03:50 You muted when you come in, please stay muted unless you're speaking.
06:03:53 If you're on a phone you can use star six to unmute yourself, and then send me a private chat message I will cut and paste it into the minutes when I cut and paste the minutes.
06:04:06 the chat into the minute.
06:04:08 We'll start off by mentioning, or anti trust policy for the project.
06:04:13 You can find this link from the LFN, and the lF, and all of the project websites.
06:04:18 This policy is important when we've got multiple companies including potential industry competitors, participating in meetings. Please review if you have any questions please contact companies legal counsel, members of the elf may also contact Andrew
06:04:31 appt Grove at the firm gives her up Grove LLP, which provides legal counsel to the Linux Foundation.
06:04:38 Also worth noting that whether or not you have a member of staff on the call this policy still applies to your meeting.
06:04:52 So what do we got going today. First of all, Happy Lunar New Year. Year of the tiger, know that many of our contributors that are in Asia will not be on because it is.
06:05:10 Spring Festival. So
06:05:15 that's, that's what we've got going on there but yes, you're a tiger so happy new year.
06:05:29 So going through, I don't see.
06:05:35 Heather on the call I will give her a ping.
06:05:38 She wanted to discuss
06:05:44 some follow up topics for the DTF will talk about the releases.
06:05:50 Want to talk about the elections.
06:05:53 Brandon was going to join
06:05:57 to talk about a little bit about marketing young Lou will be going over the CF task force will cover our normal infrastructure issues Michaele want to talk about the Azure proposal.
06:06:15 Tomas documentation.
06:06:19 Catherine has a couple items I know that she needs to drop off the call early so if not I will kind of cover those most of those we're going to be moving down next week anyway.
06:06:29 And then housekeeping pretty full agenda. Anything else anyone wants to add.
06:06:36 No thank you, Kimmy and again Happy New Year to a colleague in Asia. I think they will join us next week and I want to be sure that we, we do have a good time with their family.
06:06:52 And as you said, have a conflict can only stay the first hours so I just wanted to validate if Amy you can be a proxy from an at&t side, if I will leave a message in the chat room that I wanted to see Amy could be the at&t proxy.
06:07:12 When I will do that D or Masha, right, one of the two.
06:07:20 I'll be here for the long meeting Catherine. Okay, well thank you so much to confirm.
06:07:24 Thank you.
06:07:30 Okay.
06:07:36 David, do you want to go ahead and start and I'll see if I can get a
06:07:41 thing Heather.
06:07:45 Sure. Yeah, no problem.
06:07:47 Can I share.
06:07:55 Let's see. Cindy permissions.
06:08:05 I thought I just made you co host but it didn't change, oh I had all I'm sorry.
06:08:20 I thought I was sharing. Can you see my screen. Yes.
06:08:24 Okay.
06:08:25 All right.
06:08:27 Okay Hello everyone.
06:08:30 So, just to refresh your memory.
06:08:34 Last week, we still had quite a few release management tasks left and done. And so, the TSA approved a one week slip to them to milestone to today.
06:08:55 And
06:08:55 so, things have improved quite a lot in the last week we reached 100% with our requirement owner release management tasks. And we're at 96% of the projects.
06:09:12 One thing to note, I was just alerted this morning that the CLA and BFS decay projects are withdrawing from the Jakarta, beliefs, they plan to remain active, but they are stepping back from the Jakarta release.
06:09:31 So let's take a look at the specifics
06:09:41 for milestone status.
06:09:50 So as you can see for requirement owners were at 100%.
06:09:52 And with the projects at 96% would still have six remaining tasks.
06:10:02 You'll notice that all of these are real fun tasks so this. I went, I went through the all of the tasks and reviewed the responses from the PTS and found a few problems and been opened a number of tasks.
06:10:20 And so number they still need to be closed.
06:10:26 And
06:10:29 we have looks like, I don't know, I think both of these folks are not on the call today. It looks like.
06:10:37 But all of these issue.
06:10:40 issues reside with Dan, and then.
06:10:49 So hopefully we can get these resolved soon.
06:10:53 I think some of these, there were some questions about what needed to be done and so on. So, I think most of these can be resolved fairly quickly.
06:11:04 So that's where we stand with regard to the milestone status, and I just wanted to confirm with shocker shocker Are you on the call today.
06:11:21 I am.
06:11:23 I just want to confirm that we did in fact complete all of the architectural reviews for the projects.
06:11:31 Yes, we did. I did send an email out. I want to say Wednesday.
06:11:36 Okay yesterday. All right. Okay. Excellent. Good.
06:11:41 Okay, thanks.
06:11:43 So what I'd like to suggest, excuse me.
06:11:52 Have a tickle in my throat today.
06:11:55 What I'd like to suggest is that the PSC approve em to with the caveat that these remaining six issues that Ben.
06:12:12 And Dan have are resolved, prior to him three.
06:12:19 Any questions, comments about that.
06:12:26 All right. Kenny, do you want to do a vote for a conditional approval of empty.
06:12:38 Yes, and I am sorry but I am.
06:12:44 I should have been typing that in and ready to go and I'm not.
06:12:49 Does the TLC Jakarta.
06:13:04 Yes, I just a question to the next section with the sub w closes item before the next milestone, it is what you said.
06:13:06 Yes. Okay. Thank you. Thank you conditional approval. Yeah.
06:13:10 And I can read these off to you, Kenny if you'd like.
06:13:15 If you can actually just cut and paste those into the, into the chat window or to slack would be probably quicker.
06:13:25 Yeah, I don't know if I can paste it out of a table. Okay, so table very well. Yeah.
06:13:32 What, why don't we continue.
06:13:34 If, if you can
06:13:38 copy the search.
06:13:42 Yeah, it's actually in the agenda
06:13:47 or well actually you you can get to it from the milestone status, okay that. Thank you.
06:13:53 Yeah.
06:13:55 Just click on the six in the milestone status and Amy has a question about
06:14:10 has a question about getting things fixed.
06:14:17 Yeah. What a project, when a project is non participating.
06:14:22 Does it mean they will still fix security vulnerabilities, or are they are they just doing nothing in this release and they will just use the same, the same distribution as for, I guess assemble maintenance.
06:14:37 Yeah, that's a good question. My. Sorry, go ahead, Catherine.
06:14:43 Yes, good so typically one project is move to unmaintained whatever we only consider the, the latest current that they have released. So if I take the case of this as an example.
06:14:59 I know the team is working to provide a new doctor. I mean, the form of commuters have been contacted to approve the changes that have been pushed. So it means that the doctor that need to be used to be the latest one which is the one from the amendments
06:15:18 as an example.
06:15:20 Okay, thanks for that clarification but follow up on this one.
06:15:25 This is specifically about the non participating projects, they're still active. that's what Kenny, Kenny and David mentioned at the beginning that we have two projects that are not participating but they will remain active.
06:15:50 So, it's a little bit dip so I was wondering about the status of those two. I think it was VNS SDK and what was the other one on that sale I see, okay, because they said they still are remaining active they're just not participating in this release.
06:15:57 So first of all it's cloudy Bible this one so up to now on apps Eli, and also VNFZK will participate thing to all those leads, they have been some exchange.
06:16:11 This morning, because even if the detail of finally addicted on the task, but since there is no new adding value.
06:16:20 no new requirement.
06:16:24 In, did not make sense really discussing with the project teams to do a release. No. Same story. I mean, the latest previous branch was Istanbul man.
06:16:38 If they're fixed in Istanbul maintenance, and somebody needs for their functional testing the end of the VK of the light, they need to take the Istanbul Docker because the latest version that has been
06:16:54 75 by the integration team.
06:17:03 Right. So what we are saying is active projects. I'm just trying to read to read back what I'm think I'm hearing, but an active project with an active project, not participating in the release will not fix security vulnerabilities in the current release,
06:17:26 is that what is that what we're saying.
06:17:32 An active project will fix their issue in the latest CD that has been certified, which is in this case is some bold and then you stumbled maintenance.
06:17:45 So for example sila has the sila needs to update their JSON.
06:17:52 The version of JSON that they're using because they want to donate to, and it has a vulnerability they need to update to two dot eight, nine, and that was their task for package upgrades, which is a global requirement.
06:18:06 So what we are saying is that will not happen for the Jakarta release because they are not participating.
06:18:14 That's good. Correct.
06:18:18 But they will be on the Istanbul Magnum pretty well the only six of the only thing we ask them to fix on assemble maintenance was the log for Jay and they were not affected by log for Jay.
06:18:30 Okay. Well, so what.
06:18:34 So, I'm just trying to understand what's going on that so an active project, not participating doesn't fix vulnerabilities, for a given release. I don't see that we need to check with the project team again.
06:18:49 We have just been in from this morning that they were withdrawing from the release we need to follow up and see what they can do. But the most critical, is that the latest versions of defy and us by the community should contain me any vulnerability, like
06:19:10 locally, because that's the request.
06:19:15 So, I don't think that we can make you know sweeping generalization about this I think it will have to take it on a case by case basis because you know projects withdraw from releases for a variety of, you know, reasons everything from something you know
06:19:33 catastrophic to, you know something, you know, I'm just busy, you know.
06:19:43 So, that being the case, then that means that they're going to have different levels of flexibility. So, you know, I think we have to take it on a case by case basis as Catherine said and check with the project and say hey we've got this security vulnerability.
06:20:00 We know that you've withdrawn from the release, but we would it be possible for you to fix this one thing, and maybe they can maybe they can. So I just don't think that we can make, you know, a sweeping generalization about, you know, whether they will
06:20:17 or not.
06:20:21 Okay, thank you for the clarification.
06:20:27 All right.
06:20:32 So,
06:20:38 Kenny I guess you're working on the boat text.
06:20:39 Once a year July. Yeah. Once I can get my mouse move to the right window.
06:20:45 Yes, the vote text has been dropped into the chat window.
06:20:50 Okay, great. And you got the list of issues, I guess. Okay.
06:21:25 I should have said, darling. Thank you for joining during the holiday.
06:21:39 Okay, I'll give it a couple more seconds.
06:21:51 We'll call it ended. Okay, well, Randy came in.
06:22:00 That is approved, thank you folks.
06:22:10 Okay, okay.
06:22:14 With that done.
06:22:20 Oh, go ahead.
06:22:23 with
06:22:27 temple maintenance being the next one. Can we break here.
06:22:32 Heather has been having calendar issues which I tried to help her with yesterday, actually.
06:22:40 I was being my personal Help Desk I must say but apologies for being late for my time slots.
06:22:46 Yeah, I didn't start off by asking her if her computer was plugged in and turned on so as a help desk I failed right off the bat.
06:22:58 So yeah, if we can just quickly shift to talking about open topics from the, from the DTF, and then go back to assemble if that's okay Catherine
06:23:14 definitively, that's okay. Wait, come Heather.
06:23:18 I think it's been a while since I've been on though not to see it's it's great to be here, y'all.
06:23:24 So, I'm kind of here to talk about sort of the possible possibility of a smaller interim virtual DTF.
06:23:35 If you were there on the sort of the daily summary for our last day we talked about it a little bit and it also came up at last week's tag with the sort of suggestion that we go to all of the, you know, individual project to cease to, sort of, assess
06:23:52 their interest, sort of wild talking with some other folks and kind of reflecting about the DTS, and some of the open sort of issues and questions that came up.
06:24:03 I actually sort of had, I had a bit of an idea, which is that, you know, rather than sort of trying to do sort of a shrunk down version of what we normally do because I'm not sure that that provides a lot of value, that it might be really useful for us
06:24:22 to think about some of the larger topics that came out of the last DTS and really just maybe have rather than tracks of an app and a kid and kind of etc.
06:24:34 We have some topic based tracks that are really really cross community. I know that you know CNFCNF testing related topics have been touching a number of communities, and that seems to be an ongoing topic of discussion.
06:24:54 I know there are some issues that a number of folks have raised around some info and and own up alignment.
06:25:04 And basically some issues that we can certainly work yet a sort of, I think, on an ongoing basis but we might make a lot more progress. If we sort of just have another kind of set aside, you know time, just for two days just to dive into these important
06:25:22 topics. You know, Kenny made the analogy that it might be a little bit like some of the joint subcommittee meetings that own up once had where it was sort of, you know, kind of a smaller group of people it was more strategic topics, and it was a little
06:25:37 bit more sort of, you know, get a bunch of the committee's together to kind of wrestle with some things you know, impacting own app overall. And this might be similar, but, you know, sort of, across more projects.
06:25:51 So, what sort of that as a possibility in mind, kind of wanted to assess the interest because if there is interest in sort of diving into some of these meaty topics, we can definitely pull it together, there was interest expressed.
06:26:07 When I talked to advocate on Tuesday, as well as by the CDC, I basically sort of had this crazy idea that causes business on Friday and thought I would pitch it.
06:26:17 So there is some interest, but I think really. Yeah, sort of, oh nap been there, you know, and and finding some topics that would be useful for for this community as well would be pretty key.
06:26:30 So anyway I will be quiet and kind of just, you know, get a temperature on the room, obviously you know not everyone would need to be there we probably wouldn't have those more technical sort of deep dive sessions that we do at the, the longer events
06:26:44 and that will have again in June, but this just, it seemed like there were some very interesting questions and this seems like a way to sort of further progress to those especially since there are so many communities that touch on some of them.
06:26:59 So thoughts or questions.
06:27:09 So practically Heather what you're proposing is kind of having two days I'm hearing.
06:27:30 Where we'll probably have to cancel our weekly meetings, and some of us will attend those cross community meetings that will be organized. Yeah, that yeah that's what i would i would sort of thing.
06:27:33 I mean, it kind of depends on which meetings are going on and maybe what what topics are there and if kind of some of the regular scheduled daily operations meetings, you have a lot of people that would want to be in some of these, you know, cross community
06:27:50 topics or not.
06:27:53 But yeah, I mean there were just a couple of things that have come up that feel as though they. I don't know they would merit kind of a couple days of focusing on them as topics.
06:28:05 You know off the top of my head CNF testing, and some of the, you know, kind of, onboarding and architectural linemen across 5g Super blueprint em CO and own app is another topic.
06:28:19 You know, open to other ideas that those are just things that sort of occurred to me and that I think could benefit for from a little bit of just more, you know, longer than an hour meeting, kind of, you know, deep dive for a couple hours to maybe across
06:28:33 two days.
06:28:40 Sorry, my allergies are acting up just a little bit this morning.
06:28:46 Alright, so.
06:28:51 Would our folks concerned about the two days are folks concerned about the prep that goes into this this really wouldn't be a set of presentations I don't think, Heather now know and honestly I think it mostly probably want at most like two concurrent
06:29:20 and as I said they would be sort of, you know, question or topic based tracks, the, sort of, spanning the the communities of interest, other a lot of the topics that I yeah I would see would be sort of as an advocate input some own input potentially some
06:29:29 em co input, some five D super blueprint and maybe some of those associated projects, but really kind of coming out of some of the big open questions I think that we still had at the end of last month, activity.
06:29:50 Anybody have any further comments regarding the proposal.
06:29:54 Yeah. And if. And basically, if there is some interest or there's maybe more, sort of, there would be more interest when you see what sort of the the topics are, if there's a volunteer or two who would like to maybe brainstorm on some topics that might
06:30:10 be useful.
06:30:13 You know, we would love to hear you and then we can maybe make a more completely fleshed out proposal and get going and take that to ya to the attack and kind of get it set up as Kenny said I think that this should be a much lighter lift, especially if
06:30:27 it is just a couple of questions. Yeah, some question based longer discussion.
06:30:37 I think what you are proposing indeed editor it's really pathetic because it will give us you know we know we have the even community. I know it was a challenge to participate in presenting some session but these type of summing up, extremely important
06:31:06 in order to ensure the alignment across the different open source communities. And it's the best way to, you know, understand the end to end flow. In theory, at least, and then we can move to the practice, or maybe the practice will help us to understand
06:31:19 the end to end flow. So, I believe I don't want to speak to all of the people on the call, but I guess it's indeed important session, and the proposition to make it at the same time.
06:31:34 That's great, hoping that it does not overlap with other session that people might want to attend as well but the value proposition is is great because it will facilitate the course community collaboration ship.
06:31:53 Awesome. Thank you.
06:31:55 All right, well, let's start moving ahead. I'm sorry going with someone about to ask a question.
06:32:00 Oh yeah, there is running to work with you I'm proposing the topics from the website. Thank you. Thank you, Ronnie.
06:32:14 Alright cool so thanks so I've got a volunteer will work on getting the topic proposals, you kind of hammered out pretty quickly March, I will be here before we know it, unfortunately, looking at the calendar there.
06:32:28 Shockingly don't seem to be a ton of other you know kind of big events that month. So, you know, we can just figure out, you know, sort of to date two consecutive days we want to grab there and we can look at the calendar together with income with a couple
06:32:56 Thank you.
06:32:57 Okay, all right, and congrats on him to have for Jakarta, and I will let y'all get back to your regularly scheduled internet business, take care, y'all.
06:33:10 Thanks.
06:33:16 Okay right back to you, David.
06:33:19 Okay.
06:33:21 All right.
06:33:23 One thing before we move on from him to, I just wanted to say thanks to the PTS for their response.
06:33:39 See if I can find it.
06:33:43 Yeah, here we go.
06:33:45 There was a late change to the tasks that color coding task.
06:33:53 Around the this table best practices and global requirements.
06:33:59 The problem was is that the instructions.
06:34:03 As I had stated them in the JIRA issue was to look for the Xs for your project and then color code those.
06:34:12 Well that's fine for the specifications features use cases. But,
06:34:20 excuse me, because the best practices and global requirements don't have an owner per se.
06:34:29 They did not get axed.
06:34:33 And so if you're following the instructions you basically just ignored this table because there weren't any access to color code. And so I was having a conversation with Catherine last week and suddenly realize that and so I had to send out an email,
06:34:49 and then go in reopen that JIRA ticket for all the projects and say hey you also need to do this anyway the.
06:34:57 As you can see the, the projects, really responded well, and we got this table.
06:35:05 Updated that nearly 100% of still, still need to get been to update this one column but overall for something that was changed, you know late
06:35:19 in the cycle for him to my thought the response was really good. So thank you to all the details for your response on that.
06:35:32 Okay.
06:35:35 And then I just wanted to. Since we're moving past him to just alert everyone that M three is coming up on three March, so one month away.
06:35:49 All right. any questions about Jakarta before we move on.
06:35:56 Okay.
06:35:58 Okay, so a standard maintenance release so just to refresh everyone's memory. This is the release that we determined that we needed in order to resolve the log for Jcv, and the TASC made a determination.
06:36:15 I think about a month ago that, that this is actually the highest priority task for us.
06:36:23 So, I've been tracking the, the issues. Let's see if I can find them. No, not that one. This one.
06:36:33 So, this is the list of issues that we need to close we had proposed a February, 10 sign off for this maintenance release, meaning that we would complete these tasks by Friday the fourth which is tomorrow.
06:36:55 Unfortunately over the last two weeks.
06:36:58 This list has not seen a lot of movement, I think, you know, in the last week and a half, two weeks or spend maybe one or two issues that have been closed out of this release.
06:37:13 So, we're, we're at risk right now for our February, 10 sign off on the side I've sent an email to the ppl and said that, you know, hey, we need to get these done.
06:37:31 But we're.
06:37:35 It looks like we have some, some risk there because I, I think that it's unlikely that these will be closed by tomorrow so we'll be discussing this in the, in the PTO meeting on Monday so I should have an update for you next week on status.
06:37:54 I did want to mention in particular,
06:37:59 VNF SDK eight to seven, I received an email from kind of garage. This morning, saying that he doesn't feel that he's able to fix this issue on his own.
06:38:16 And he's asking for support. And I think he said that the integration team was going to help them out.
06:38:26 The cow, I think you're on the call Can you comment on that are you are you working with Connor garage on eight to seven.
06:38:37 No.
06:38:39 No. Okay, no. All right.
06:38:46 It's still the same to me I don't know if there's an economy. No No No, I didn't.
06:38:54 Okay.
06:38:56 Okay, maybe, maybe. Yeah.
06:38:59 I just want a bit on that I spoke to me.
06:39:06 He said he will approach the senior management team as well as the integration team based on for him as for his analysis right now it doesn't seem to be a project issue but something to do with this so he said he was unless it and then get back to this
06:39:18 team space on the.
06:39:31 Okay, if, if he was able to come to the ptl meeting on Monday. We could talk about this more and approaches, yeah sure I'm actually inform him about that, and if he has any messages something about the past.
06:39:36 Okay.
06:39:37 All right.
06:39:39 Yeah, so.
06:39:42 So this is our list of issues to get to maintenance release.
06:39:48 And as I said I've alerted the, the PTS but this just does not seem to be moving as quickly as we had hoped.
06:39:59 So just. All right, I will.
06:40:02 With. I will follow up with the, with done and, and I can see that being there, and they have been some exchange some luxury, the latest status has been updated in JIRA, but I will work offline with Dan vj that I mean the line in them.
06:40:17 But quick question.
06:40:19 I believe we are doing a quick run right with the integration love just to be sure that we didn't open anything else.
06:40:32 What the step one we have all the doctors will perform a quick check with the integration team.
06:40:41 Yeah.
06:40:43 I think that we need to have daily test runs at it at a minimum, and that is actually the next issue that it was going to bring up.
06:40:57 We discussed this earlier this week on Monday.
06:41:02 And the integration team has been having ongoing stability issues.
06:41:09 And some of it was related to the Nexus issue, which I think we may have resolved.
06:41:22 Earlier this week, it took some action and
06:41:32 Kenny Do you want to talk a little bit about that about what what it team did and what we know of, you know what the results were.
06:41:42 Well that's like a whole separate topic we can insert it here.
06:41:48 Well, I yeah I don't want to get down into the weeds about it.
06:41:53 You know, just like a kind of a high level summary.
06:42:02 Okay, let's see.
06:42:06 Kevin I say that you're online.
06:42:12 Kevin Sandy.
06:42:15 Yeah, how you guys can you hear me.
06:42:16 Yep. Yeah yeah can you just give us, you know, like a 32nd summary of what you guys did related to Nexus and what the results were.
06:42:26 Sure.
06:42:27 So long story short, while we were trying to do and operate on the next just three version, like a previews on the previous days.
06:42:46 We're facing a blocker that for some strange reason when the upgrade process rich, the Docker data snapshot report. It did like some scanning, but it failed.
06:42:50 Like it was getting a stock because of the size of the of that repository.
06:42:53 So we analyzed that repository, we saw that it was hosting like terabytes of data that actually are ephemeral data that we could get rid of.
06:43:05 So the decision was basically to claim that repository, like, leave it empty.
06:43:27 A configurator again with all the required permissions, all the settings, and basically retried awkward pauses, so that a unblock has turned outward process.
06:43:23 And actually that that was also a part of that stability that was missing. So that big repository that was hosting terabytes of data was providing that honest stability to the whole Nexus three installation.
06:43:38 So that's basically what we did. And it's working so far we have been monitoring the service, and so far we have not heard or seen any, any issues on that site.
06:43:49 Okay, great. Thank you, Kevin.
06:43:53 So,
06:43:56 so that that was at least one of the issues related to the the problems with daily tasks.
06:44:06 And I wanted to check in with Macau, to see if there's been any movement, have you seen any improvement than the last couple of days now. Yes. Yes, for sure since Monday.
06:44:20 We have only enabled muster test, but the results were fine. From today, we don't have any results because of some issues with the connection, but from Monday and Tuesday.
06:44:35 The results were political some minor have issues with with in some minor errors, but that's our up and running, but that's for master not stumble, because we we've seen we didn't have any images because of Nexus issues.
06:44:54 And notice we're I have no recent results for Istanbul. We decided to just disable that stabilize master. And because the master is less stable.
06:45:07 We enable this test, and I hope tomorrow we will have a fresh results for for Istanbul.
06:45:17 And so does the State, I believe, but still we only can based on the results from the orange lab, because we have some, some lack of the last test on tr not running.
06:45:33 Currently, today but two labs also sometimes there's some, some issues. So that's why I'm not sure.
06:45:46 We will have results but we enable we centralize best for monster and decided to enable again test for stumble, so probably tomorrow, have the results.
06:46:02 Currently we have no recent results for for some.
06:46:08 Can you can you project when we will get results for assemble.
06:46:14 Tomorrow, tomorrow. Okay. Yes, okay, I do. I believe tomorrow.
06:46:19 Okay. Terrific. So, So that was the other issue that would potentially block a release, you know, not having daily tasks so it sounds like, maybe that that issue is becoming resolved so if we can get our open issues, closed, then, then we may be able
06:46:44 to get maintenance release out the door. So that's where we stand with this gamble maintenance release and the log for JV mitigation.
06:46:57 Any questions.
06:47:02 As I mentioned will be discussing this more on Monday with the details.
06:47:09 All right, that's it for me Kenny. Thank you,
06:47:15 David one small question on low on the maintenance lyst part. There are some projects where they were no record issue report for law coaches so should they also participate with a new, fresh Docker for this maintenance release, or it's not required.
06:47:32 Well I'll defer to Macau on that but I don't think it's required I think you would just use the, the, the Docker containers that were released. The major, is that, can you confirm that Macau.
06:47:52 Sorry, can you repeat, what's going on.
06:47:56 If it is for.
06:47:58 Is there any requirement for projects that do not have a log for ja issue that don't have, you know, that don't have one of these six issues to do anything for the maintenance release.
06:48:13 From my point of it. Oh, yeah. Okay.
06:48:17 Yeah, so I think that's your answer.
06:48:33 Yeah.
06:48:30 The we.
06:48:29 You're breaking up me was actually pointing one is so issue which was related to other minor issue because not related to our project.
06:48:36 And I was under the impression that we don't require to release so for this release.
06:48:43 You're talking about issues.
06:48:46 Yeah. Can you hear me, there was no in the list with you. Yeah, I can hear you
06:48:55 Funny so sure which was a minor issue was not a little awkward, and it was a functional issue, little minor.
06:49:00 So, for that I was waiting for some other response I don't think we required to actually make a release of so for this maintenance case with it.
06:49:08 Okay.
06:49:09 Yeah we encouraged.
06:49:11 Because this is, you know, kind of an emergency release you know Originally, we were not planning on having understandable maintenance release, but the log for ga issue came up, and because we wanted to release it right away.
06:49:28 We, we discouraged pts from, including any other issues in the maintenance release that were unrelated to log for j unless they were absolutely necessary.
06:49:41 Right, but the list actually include one so minor issue so I have removed it right now.
06:49:46 Okay.
06:49:48 Okay. Yeah, that's the right thing to do. Yeah. So I just wanted to confirm it.
06:49:54 Okay, yeah. Understood. Yeah, thank you for for doing that because when I look at the list, you know it isn't immediately clear to me. Yeah, that's fine it's high priority or not, I even left okay.
06:50:07 I also left a comment for that issue so that it doesn't confuse you, but I just wanted up. Okay.
06:50:14 All right. And you, you removed the.
06:50:18 release.
06:50:20 Okay. But he also speaks to for Jakarta but notwithstanding maintenance so we don't require to worry about right now.
06:50:27 Okay, okay.
06:50:27 All right.
06:50:29 Very good, thank you.
06:50:34 Okie doke
06:50:37 then moving on to the elections.
06:50:42 I put out the self nomination for the vice chair. No one responded to that. My question is would folks like me to extend this for another week or leave it as is with no vice chair.
06:51:03 And what I would like to have I open the discussion from last week about SBC was not blocking people to, to give their nomination of what because we still need to see the SPC but we can dissociate it was just a proposition.
06:51:18 So I want to be sure that people who were intended to play the device whole, where he looked after the discussion of last week with the proposition that maybe they can help the THC having another role with others PC.
06:51:43 Okay hearing nothing I'm going to mark that as an agreed leave as is
06:51:52 could mean, we don't need Vice Chair for this with you. All right.
06:52:07 Okay. Um, so the.
06:52:12 Then, shifting to the question that was raised. We are looking for a new representative to be own apps.
06:52:27 Strategic Planning Committee Rep.
06:52:30 The meetings are now monthly on the second Monday of the month at 1500 UTC.
06:52:38 So if there is someone that would like to
06:52:43 volunteer for that.
06:52:47 For that community coordinator position,
06:52:53 please let me know.
06:52:58 And we call Kenny Can you can you can you be open to people who are not necessarily pass on the DSP.
06:53:05 Correct.
06:53:06 This is, this is own apps representative, so you do not have to be a PSC member there is no provisions for that. It is whoever the community decides is the representative.
06:53:27 Okay, so maybe let's also send a note to on a BSc and on up discuss and make a call for the nomination, and until the nine because the first meeting is understand so if we have a volunteer by nine at least we can be represented on
06:53:54 our smaller bit on that. I mean it's mostly because of some of our colleagues from China, from Leeds, but as we can conserve constraint from an external beta little more silverback cutting by this weekend.
06:54:03 Cutting by this weekend. For the vice chair or you mean for
06:54:15 the strategy committee part.
06:54:12 Okay.
06:54:13 Okay.
06:54:18 Please do.
06:54:20 Yeah, this is all.
06:54:22 I just wanted to add that I think that, you know, the whole role of strategic planning committees been discussed right.
06:54:31 And I would say that at least to me as you know as I was that representative for the last three years.
06:54:50 Each is not what very clear and I would say I'm most likely not the only one, which is currently the role of strategic planning committee, and specifically related to project and this is what one of the reasons that I don't think, you know, I asked that
06:55:01 should have to have a replacement on this role, but I think, actually, a more wide discussion should be taken. I don't know where perhaps on the government board level which is, which has created strategic planning committee right, we haven't created
06:55:17 that government boat is the one which created that but I would say that right now. My personal feeling is that SBC is not really contributing to the progress and this is why also under specific there was a discussion that we need to see a revised list
06:55:33 of goals and see where he is going so I would say that firstly that needs to be resolved and then probably you know, in all of we need to discuss who would be representative and what would be the role because you know, they're all which was there three
06:55:49 years ago, two years ago, you know, probably has changed and SPC role is being discussed.
06:56:00 So that's a good bond I love because it's too we were making this call to the community will explaining maybe the objectives and the goals.
06:56:10 Considering that maybe people knew already what the person was doing.
06:56:17 So, who can who can. Is there a chair or a cc or somebody could provide some clarification, or is it not they are waiting.
06:56:39 Please, and they will also provide the.
06:56:32 I'm trying to make the latest status, the latest status basically and can you please correct me if I'm wrong but the latest status is indeed the SBC need to read discuss its own charter, and decide what would be the next stage for the SBC, this is where
06:56:52 it stands right now can you please, please correct me if I'm wrong.
06:56:59 The S.
06:57:14 Know the SPC is currently looking at its objectives, how it should be structured to meet the needs of the governing board.
06:57:17 And,
06:57:17 you know, basically, you know, re, re evaluating the role of the SPC, the SPC was basically established to be the portfolio, manage Management Group, more or less, I will put that in air quotes for the governing board because the Governing Board does
06:57:37 not get down into does not drill down into the level that the SPC should be going.
06:57:46 The chair of the SBC is Jaan Asana from Nokia. He is a governing board member.
06:57:54 There are other governing board members that sit on this committee at as a joint committee of both community, and governing board.
06:58:04 And as Allah said I mean, starting off 2022 with discussions of Okay.
06:58:12 What does the role of the SPC need to be, what are the what are the core objectives that we're going to try and achieve, how does it relate to the KPIs that are being set to a great extent the, the, the SPC sets the key performance indicators for for
06:58:37 LFN. So that's one one area that we know will continue.
06:58:45 But there's other areas that are currently being evaluated.
06:58:52 So own app having a voice at that table. Personally, I feel is extremely important.
06:59:00 regardless of what ends up happening. If the SPC decides you know what we do well we did what we needed to do or no longer needed.
06:59:10 That's great. If the SBC decides Okay, we're going to focus our areas in this focus our attention in this areas, that's great.
06:59:20 But we, we, I strongly feel we need to have own app as a voice at that table,
06:59:31 helping to make those genius continues to exist.
06:59:36 I know not.
06:59:40 I believe that own app needs a voice at the table it to help make the decision whether the SBC should continue or not.
06:59:50 So what I would like to request because unfortunately I will need to look up on humans, a lot, would you mind me, potentially to attend to the meeting on the 10th to ensure that we don't have this country unity.
07:00:03 And then I think we need to discuss offline, with the CSC to see what we do.
07:00:10 But I would like to be sure that there is no discontinuity on until we conclude, and my commitment to you. All right, because you, you may agree to stay another call to find a solution, yes or no, without PC members before the next meeting.
07:00:27 It's a monthly meeting right, it's not every week Yeah, it was. It was bi weekly in, and the first decision that I made was, was that it's moving to a monthly call.
07:00:37 That's fine I will participate in the meeting. On February, okay.
07:00:46 So thank you so much. Allah, you can assign a task on me.
07:00:49 Regarding the SBC, and the whole conclusion as soon as possible with the DNC members.
07:00:56 Okay.
07:00:59 Thank you.
07:01:01 Thank you so much.
07:01:03 And maybe we can extend us to just advice issue in the meanwhile, like, I think. Let's do two things. But I think until we.
07:01:13 If somebody wants to step up understand the goals based on what you're explained today, or the wise, we can have the to action invalid because we might have somebody interested to play the whole.
07:01:24 But I think we need to be evaluate.
07:01:29 Also, what we want to accomplish as an open source community.
07:01:32 So thank you so much.
07:01:36 Allah, to give us more insight.
07:01:38 And we should start with, with the whole. I did the wrong assumption that everybody knew was the SPC.
07:01:47 All of us. Thank you so much.
07:01:49 No, catching chest chest one comment right Esposito was absolutely clear, let's say, two or three years ago when it was established right. I think that this specific event for certain processes and now it she's a you know reevaluate in or, I don't know
07:02:08 how to put it in the McCleary its role, and its job to be performed and its relation to the project, and pretty much everything right. And this is why I'm saying that you know, we probably need to see that process.
07:02:26 Prior to deciding, you know, if and who should represent on up there. That was the reason, right, because as visceral was clear to me. It was not that clear anymore and I'm not doing the one is clearly that was also communicated over email list and you're
07:02:44 the meeting last meeting of this be say that you know that probably SPC should reevaluate its role. This is why I'm saying that you know, and head in the winter, or election something that's not sufficiently First they need to see what SPC continuation.
07:03:02 If, and what a specific continuation is but, you know, in the meantime, of course I will, I will participate in the meeting, and let's see how it progresses.
07:03:21 Okay, so we're leaving the discussion, open until next. Until next month, so that we can figure it out so I'll just mark it as the first.
07:03:37 Okay, can you one question, you know, was it actually raised during the last government work meeting or not, you know, the job that this is supposed to take, because you know government bought created this DC right so during the governing board is want
07:03:53 to discuss the charter of this city. So I guess. Yes.
07:04:02 Yes. Yeah, he brought it up on the governing board he
07:04:06 basically said that the SPC is currently looking at its role, and what it's going to be doing what it should be focusing on.
07:04:18 So, yeah, that was absolutely discussed at the board meeting last week, but no decisions, take
07:04:28 moment to know, because the SPC needs to make kind of the decision on that and then roll it up to the governing board.
07:04:38 I'm just so if the SBC decides that it has run its course, it's no longer needed.
07:04:46 Then that would go up to the Governing Board and the governing board would would vote on it if the SPC decides, Here's the things that we're going to focus on.
07:04:54 That would be rolled up to the governing board, and you know the governing board would would would look at that and then give it a thumbs up or thumbs down.
07:05:17 Yeah, I'm just.
07:05:15 Okay.
07:05:17 Brandon.
07:05:20 Let's see here.
07:05:25 discussion of the proof points.
07:05:29 Yeah, thanks Katie, I'll touch on proof points and badges.
07:05:36 This year, I do.
07:05:42 Right.
07:05:42 After we spoke yesterday I ended up creating a couple slides, just to help facilitate the discussion here on these two topics.
07:05:50 I pulled these slides from the marketing Advisory Council meeting we had yesterday.
07:05:57 And as it relates to the projects, there's two things that we want to point out here sooner rather than later. To get. First of all, awareness into the projects that these initiatives are happening.
07:06:11 And then secondly to ask for your help in facilitating them.
07:06:16 So the first one is around collecting LFN project.
07:06:23 points. Now by proof point we mean instances, and examples of our members, using the artifacts produced in the elephant projects in their products, services, deployments proof of concepts, etc.
07:06:45 so late last year, we were able to develop some great proof points with some end user members here, and those are what are displayed below. Two of them are own app.
07:07:00 One is from Open Daylight community.
07:07:03 But these were an example of members coming to us and saying that you know they had made significant progress with project, and they were ready to start talking about it.
07:07:18 And in those instances, we get together with subject matter experts from the projects. And we interviewed them talking about how they're using an open source approach, and how they're using the open source project in their initiatives, based on that interview
07:07:40 we then turn it into a story, and we develop a variety of media assets around it.
07:07:48 So we published these in q4, which is fantastic.
07:07:54 But now looking at 2022, we want to try to avoid dips in our editorial calendar for the year. So we're making a strong push here at the beginning of the year to get as many proof points in from each of the elephant projects as we can in order to start
07:08:12 those conversations, find those innovations schedule those interviews, and get the content developed so we have a little bit more of a steady state of content release throughout the year.
07:08:26 And in fact, this is one of the primary goals of the back this year and it's very much dependent on projects such as one that stepping forward with instances of own app innovation that we can talk about.
07:08:41 So if you have an idea around these around an initiative please bring it to us we could brainstorm with you talk it through, see what we can do around fleshing it out in communicating it in some instances we understand that there may be confidential elements
07:09:01 elements to the, to the story and we will we will respect those and work around it. But please keep this in mind, and please exploring and these ideas with us as we look to get this going here for this year.
07:09:22 Alright, next topic is the badging program.
07:09:26 So, we've worked with the Technical Advisory Council to come up with a structure for a badging program that will recognize key people inside the lF and umbrella and feel fn project communities in December we set up an initial pilot program with the group
07:09:50 of ambassadors from the new kit project.
07:09:54 And that went well. So we're now looking to send out the next batch of badges and those will be the LFN level leadership badges, or leader mentor and mentee.
07:10:08 An example of that badge is on the left, and we're looking to get project level badges programs going for each one of our projects, specifically to the own app community and to each of the project communities.
07:10:24 We want you to help us finalize the badging categories and criteria, with which we would use to create and distribute badges in a structured program. So if I could all move to the wiki page, developed by the Technical Advisory Council.
07:10:46 That got this started. So, these grids represent the information we need filled in, in order to populate our badge distribution tool called credibly and listed here are an example, and a section called the project level badges, and this is where we would
07:11:07 need to finalize those categories, and those criteria.
07:11:13 And so I've gone ahead and created a sub page, under this called a map nap badging program and I'll do this for each one of the projects.
07:11:24 And here's where I'll need to work with some folks in the community, to determine and fill in these criteria.
07:11:32 So as part of the attacking part of getting this going, I think, Randy can provide an assist for me here. But anyone else that's interested in helping put a fine point on the categories, most relevant to the O net project in 2022, please let me know and
07:11:52 we can bring you into that discussion as well. Kenny I think you mentioned that we wanted to do something around, recognizing own apps fifth year anniversary and five years of contributions to own up, we can explore that along with any future integration
07:12:09 into an own app awards program.
07:12:15 So with that I'll stop and see if anyone has any questions or anyone wants to step forward and help us flushes out.
07:12:33 So if there.
07:12:36 If there.
07:12:50 Would the community prefer that that I just work on this and make the decisions on your behalf.
07:12:50 For the own at badging.
07:13:06 I don't know if that's a yes or no.
07:13:13 I'm going to take it as a yes.
07:13:20 Okay, great. And then maybe that those categories and criteria can be ratified here before we launch, and then as soon as we get the Go ahead, we'll plug in the program into credibly, and we can work to identify those who qualify, and then we'll be sending
07:13:41 out and distributing those patches.
07:13:45 After that point and then I would just ask the folks who are recipient of the badge please do help us communicate the, the badge far and wide on your, in your networks and on your LinkedIn profile, there's a very easy way to add your badge.
07:14:04 With just a couple clicks on to your social media properties and that helps us get the word out about the great work we're doing here and Oh no.
07:14:17 All right, Kenny, that's all I got.
07:14:20 Thank you so much.
07:14:21 Thank you.
07:14:56 Okay, I'm young Lou, CNN Task Force.
07:15:07 Yes, yes. Thank you.
07:15:08 Okay. Stop. There we go.
07:15:17 Let me know if you see my screen.
07:15:20 Yes we can.
07:15:21 Okay, this is update for as the package onboarding distribution, as you know castration PRC update and good news is, Erickson contribution to this PLC is confirmed.
07:15:34 Officially, this week.
07:15:36 So now we have a team.
07:15:38 So Mike was Michael Morris team, and team and upon handle the onboarding, and then walkers and others, and Erickson so team will handle RCM.
07:15:51 And then I and Maria and we can assist them as needed. And if you need additional information you can look at this link, today I just provide the status to deal with some of the highlight, too.
07:16:03 So, here we go is st was designed to simplify CNF descriptor. And also, not just for own it.
07:16:27 Also, all in. So, all and took it as an owner going to provide a reference implementation through this PLC. And then we'll apply to the OC in the future.
07:16:24 So that's why we when I just make some decision, and we made some kind of conscious decision to make it compatible. So anyway, so we have three sections.
07:16:35 As I mentioned as a package. And for now the focus on the network function, and ASD is only to also support, support still accept an RF in Oregon, but we focused on the NF first first initial RPC.
07:16:52 So STC we doing SEO package onboarding two sec. This one we highlight some of them. And some of them is the onboarding as the package. And then also doing this PRC, we tried handle large size images.
07:17:09 As you know, STC if the incoming the CC is more than two megabytes, it talks. So that's why the Mike Morrison team has some solution, how to handle large size, we are going to implement leveraging that capability.
07:17:25 And also we are talking about transform onboarding S model and package into internal owner modeling and packages to minimize impact on at one time component, and then same as always supporting the STC resource service design.
07:17:41 And second one is the distribution that we need to I would like to dispute under Caesar and have them chart and ASD and images to the certain parts we are going to explain more detail in the sub, sub chart.
07:17:53 But anyway, we have a second area. Once sec to validate distribute and then someone some component need to handle the rest of the distribution. And then third one is.
07:18:06 So Model Driven orchestration. We are continued to support the SEO Model Driven orchestration for ASD online, we minimize the impact and delegate most of function to is optional program new functional capability and so that's the plan.
07:18:22 Like, we apply the same architecture for Etsy. So to adapter and so NFU. So we're not touching too much on the so core code, and we creating the plugin.
07:18:32 So, we are, we are going to discuss more with our session, and Lucas, but for now we have some plan. And then, and we also designed a simplified ASD sem restful protocol, based on those sort of API, but we much simplify for ASD.
07:18:49 And this is to handle instance rebel how pyramidal and extension so I'm going to give you more detail. So here as a status.
07:18:57 Currently Ericsson and Nokia team they designed the information model for ASD and packaging protocol. And then they they provide a, you know, pretty good, decent walk and then they are going to propose this is the information model and packages.
07:19:15 and this data model is almost done. And then we are discussing next Monday, had the owner.
07:19:28 Marketing subcommittee we are boring for the ASD data model, that's the current status. And also we are we are discussed more with the Olin team. And we introduced this as the concept and the information model data model, we are working on that part.
07:19:44 And then data model Erickson team is to contribute. The data model. And then as I mentioned before on it modeling on the subcommittee we're both for a STD data model Provo on next Monday and excellent propose this one, and then you can find more detail
07:19:59 and this which pages.
07:20:03 And then, talking about SEC is the package onboarding, as I mentioned Ericsson sec team will work on this and to support as the onboarding to STC, we have a several other item high level concept and design, and we following the soulful structure, which
07:20:22 is, with some extension.
07:20:25 And then STC will do internal processing to transform and generate the resources you know what your function, and their services and distribution, and you can take a look at the one important thing is, we, we take advantage of ASD under the monitoring
07:20:41 structure. So we will be able to map between ASD to owner Vf and deployment item to Vf module to minimize the impact, we use some of the owner components, such as AI.
07:20:56 And then also, we continue to support to the D midway poor pattern, the SEC not gonna push the Odyssey sir, they still are providing team through notification.
07:21:08 And then each component need to pull the information. So anyway, during Jakarta micro most teams were handled this as a PLC. And then we have a some on the epics which is story plan to do that.
07:21:21 And then this is kind of a design decision.
07:21:24 As I mentioned se, we have some issue, se doesn't have Vf module structure, they can, they can define as a policy so policy so flexible so we have module cannot handle.
07:21:36 Well, so we we tabled that because we couldn't support that. And Fred and I work on this but we decided to hold it.
07:21:44 But ASD they designed the from the beginning, the ASD and deployment item, which is very similar to VFNVF module we can map internally. So we think we can do this one.
07:21:58 And because of once we have internal model we can leverage a and I genetic. And then we have module concepts.
07:22:04 So this is the current now the design go and design concept and then this is what we are talking about how are you going to implement. So we have a team for doing this sin, and the design goal as I mentioned we tried to minimize own internal monitor dependency,
07:22:20 to be used by the Orient orient team specifically asked about our worry about the dependence too much. We probably use some of their own IP core component, but not all so we have to discuss all in team which which components interest.
07:22:34 So anyway, this is the what we are working on it.
07:22:37 And then package distribution in se the project used the China Mobile and GT used to have here, but I don't think they're going to work on this for Jakarta.
07:22:49 So we took it as Eric since strategical on the part of the other so we're going to stretch Cool, well, what we should provide a simplify solution possible.
07:23:01 So we're going to handle. If we don't have enough resources we can using the simplify solution.
07:23:05 And then the next release, we can provide this one officially anyway. We are still thinking we can do this.
07:23:14 But the bottom line is that we extend the counter manager, we handle as a package at pies three. And also we providing Helen artifact repository from the ASD.
07:23:23 And then image artifact capacity we can store. So we have some discussion with the Michaels and his team, and then I think we can handle this one. So this is what target for the California District.
07:23:38 And then this so Model Driven as to what pro selection. And this one in the new app as the package, a metadata, we defining entry definition type, which is ASD and then you can add additional one in SC, we didn't have this kind of what type definitions.
07:23:55 so in SC to distinguish this is se package or other package, we have to use some, we look into the packages inside and we have to find it there is the directory structure and then we choose it but there's really cumbersome.
07:24:11 So we decided to using some metadata.
07:24:14 And we defined entry definition types so that means, you know, so are some of the other one time component they look at the metadata only doesn't have to Interscope the inside the package.
07:24:26 They said they find this is ASD based on ASL information.
07:24:31 We plan to store this information in the research we have in owner and resource we have Tosca meta data, we asked the under discussion. Once you do that, so you just understanding the metadata, they can decompose, and they can determine which workflow
07:24:46 they need to launch. Anyway, we have some plan, and the design and the concept, and I'm going to discuss assess you and Nicholas, and get the insight, but we have some we mostly, not to touch too so core minimize a core impact.
07:25:01 And we try to add additional SEO plugin capability. So, anyway, this is the idea, we don't it, but this one, we are working on it, Ericsson SEO team is working on it, Jakarta.
07:25:19 So whoever resources, but only resource we don't have our we come from is the distribution. So definitely, if we, if there is some volunteer from owning communities as great we can be a willing to work with them.
07:25:27 Otherwise we're going to take a stretch goal when apply simplify solution.
07:25:32 So this is a kind of architecture here in popular line, this is a new plugin. So plugin is optional plugin so we're not touching the core. This is optional protein, very similar to what we did for the project so and if you saw the.
07:25:49 So basically we are the.
07:25:53 We are just, you know, during decompose we for the vast level, we calling the new protocol right the salty, we invoke the SOC an FM, and then SOC NFL designed to get the ASD pastry.
07:26:10 And then also, you know, if we look at ASD possibly they can see the link to which have them chart, and they are holding to the according to Helen repository.
07:26:20 And then they get it, and also through the, the rest co information we can get the input parameter. So then so CNFM can mix together and generate the new, the very file injector input parameter into him, so we can get creating the component resources,
07:26:37 before are invoking the coordinates. So, here there are several options we are considering one is the Helen client, this is the original constant using Helen client because Helen command can do many things.
07:26:49 And then also, we are considering Sienna plugin but CNA plugin is the right thing, adapter passing through and actually tried to helping the multi cloud, this is a CFO mechanism.
07:27:03 They put a lot of information to here, they get ASD and the images everything's here but we have a more automated and more automated fashion we try to achieve from here.
07:27:15 The reason is, we're not dealing with a just have them chat, we are dealing with a booked in ASD. So we, we try to represent their complex are the application.
07:27:26 One ASD can consist of many of the helm charts so we want to provide a service network link between two parts, and we try to put the replacement value for instance, so there's as he has a lot of beating capability we want to leverage.
07:27:43 We can formulate some other in a finalized instance table, under the information they can we can remove any way we can see the program despite we want to discuss the session and Newcastle, to see their input.
07:27:58 But anyway, we're looking for some simplified in some other way, so this is the PRC. We are looking for some simplified way. Okay, now we are taking their existing the implementation.
07:28:11 Also we are considering you know, on new way, doing PRC we can prove. So, this is one of the idea. And as I mentioned the BPM in for So, and talking to the NFL, we are developing the swagger file, and you swallow for you can find from here.
07:28:28 As a status, you're building the workflow in the BPM infra and workflow in the. So, the CNFM. And then here Erickson so team plan to work on this as a culture, and then.
07:28:42 Okay, so additional input so anyway this is defined what function we're going to provide for this operation. So we define this one.
07:29:01 So, and this is the current status so we have a two main section onboarding cm. We have a team. Okay, so if owner community they're willing to, to help working together on this great, welcome.
07:29:06 And then, distribution, we have, we looking for resources, but if we don't get it. And we're going to do a certain way. So that's the current quick update and next week I plan to discuss this issue and then when Lucas coming back now we're going to have
07:29:21 additional discussion with Lucas and Sasha, and we do so Ericsson so team. So this is a kind of a status funding wise so resource wise.
07:29:32 We have a lot, and about 70%, except for distribution. So we have a team to do that. And so anyway, so this is the report to TLC today. Okay, if you have any volunteer.
07:29:50 Additional volunteer please let us know. That will be great.
07:29:51 Any question.
07:29:57 Okay, this is a quick update for TLC.
07:30:00 Okay. More detail will be the fall, will be follow up to internal discussion and also discussion of decision.
07:30:10 Get lied to, we will find in the, in the wiki right so it wasn't always said, I sent a wiki and this one this week or two and this, this is kind of a summary.
07:30:21 I provide similar presentation at the elephant, 2020, more detail and wiki has a very detailed information so anyway, I'll see on this wiki page and put into TLC.
07:30:34 We can do after this meeting. Okay.
07:30:36 Thank you.
07:30:41 Okay, Great, thank you so much.
07:30:46 We are,
07:30:50 we are currently at time.
07:30:57 So we've got documentation topics.
07:31:02 The discussion about Azure.
07:31:05 And some of the community stuff that will be then getting moved to next week.
07:31:14 So if there's nothing else pressing.
07:31:19 I say we go ahead and close it out.

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

Agenda Items

LFN Cross-Organization Updates

Release Status

TSC Elections

Subcommittee Updates

Task Force UpdatesCNF, Wiki 2.0, ONAP Enterprise

RelEng/Infrastructure

RelEng/Infrastructure

PTL Updates

TSC Activities and Deadlines

Upcoming Events & Housekeeping

Zoom Chat Log

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise

Browser not supported