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

Passcode: 209247

We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log 

05:54:49 From  Sai Seshu  to  Everyone:
    #info Seshu, huawei
05:57:26 From  Fred Oliveira  to  Everyone:
    #info Fred Oliveira, Self
05:59:45 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
05:59:51 From  N.K. Shankaranarayanan  to  Everyone:
    #info N.K.Shankar, STL
05:59:58 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT (no proxy needed)
06:00:19 From  Ranny HAIBY (Samsung)  to  Everyone:
    #info Ranny Haiby, Samsung
06:01:05 From  Magnus Buhrgard  to  Everyone:
    #info Magnus Buhrgard, Ericsson
06:01:12 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
06:01:18 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #info Yuanhong Deng, China Mobile
06:01:29 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang, Wind River
06:01:31 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
06:03:18 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
06:04:43 From  Catherine Lefevre  to  Everyone:
    #info, Catherine LEFEVRE - ATT - if I am disconnected around 9,15 CST, please consider Amy Zwarico as ATT proxy - thank you
06:05:48 From  Catherine Lefevre  to  Everyone:
    If Amy dropped and i am disconnected then please consider Martial ngueko as my proxy
06:11:29 From  Catherine Lefevre  to  Everyone:
    Thank you ONAP SECCOM for promoting great security practices outside our community and for continuously challenging us to have security part of our DNA. Thanks to all the project teams to embrace it on top of anything
06:12:28 From  N.K. Shankaranarayanan  to  Everyone:
    Kudos to the entire team and contributors for this accomplishment!
06:25:11 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED the M2 milestone for Jakarta will be shifted to Feb. 3rd
06:42:16 From  Kenny PAUL (LFN)  to  Everyone:
    https://lists.onap.org/g/onap-tsc/message/8280
06:51:19 From  Thomas KULIK (DT)  to  Everyone:
    Installation via OOM: https://docs.onap.org/projects/onap-oom/en/latest/oom_cloud_setup_guide.html#oom-cloud-setup-guide
06:51:40 From  Thomas KULIK (DT)  to  Everyone:
    https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide.html#oom-quickstart-guide
06:52:12 From  Thomas KULIK (DT)  to  Everyone:
    vFW Use Case: https://docs.onap.org/projects/onap-integration/en/latest/docs_vFW_CNF_CDS.html#docs-vfw-cnf-cds

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:00 Okay recording has been enabled.
06:03:05 As has the transcript.
06:03:09 So everybody's muted when you come in please keep yourself muted, unless you are speaking please and thank you.
06:03:18 You can use star six to unmute yourself if you're coming in from a phone line, and if you send me a private chat message.
06:03:25 I'll happily cut and paste that into the meeting minutes, and it will become part of the public record.
06:03:33 Eric Thank you.
06:03:41 As always, we'll start off this meeting by mentioning, our anti trust policy. You can find this link from the lF and all of the project websites as policies important when we've got multiple companies including potential industry competitors, participating
06:03:56 in these meetings.
06:03:58 Please review the policy if you have any questions please contact companies legal counsel.
06:04:03 Members of the lF may also contact Andrew up to grow from Gizmo up Grove LLP, which provides legal counsel to the Linux Foundation.
06:04:25 On today's agenda.
06:04:30 Got empty scheduled for today.
06:04:34 Do our normal infrastructure discussion, and
06:04:42 then we'll go through a couple of ppl updates.
06:04:49 Elephant governing board recap the governing board meeting was yesterday
06:04:57 and Catherine I see your note. Thank you.
06:05:02 Although I think, Amy said she needs to drop early too so I was actually going to request that we move this to the beginning of the meeting.
06:05:13 CNF Task Force, and then some of our normal housekeeping things with TLC and lF in anything else that needs to be discussed today.
06:05:33 Okay, Amy, where are you let me give you co host.
06:05:42 I don't have anything to present I'm not going to present. Are you just going to talk to it as that was because it was marked as elephant JP. Oh, you're right.
06:05:51 Okay.
06:05:53 Okay.
06:05:57 So, I've got just a quick update on yesterday's meeting of the elephant GB, it actually turned into a security meeting so that was kind of fun.
06:06:06 Jim Zombieland who's the executive director of the Linux Foundation, review the Linux Foundation initiatives to bolster and with a presentation, titled bolster the nation's most critical open source and software supply chains, and then motorists are who's
06:06:24 on on App sec calm presented his own software bill of materials work.
06:06:32 Because we believe that that's really good what, that's the work that might or did to implement the bomb based on Nexus IQ scans is something that we could extend to all of the elephant projects.
06:06:45 So, Jim's presentation was really interesting. It focused on how as an open source community we can identify the critical open source projects. I think on app would be considered one of those.
06:06:56 And really keep that code free of vulnerabilities.
06:07:01 Some of the pillars that he hadn't talked about for really improving the security of open source, our secure coding training audits on these critical projects, regular security testing meaningful badging, and the development of international security
06:07:21 requirements that can be used to protect the supply chain.
06:07:25 One of the challenges he called out that I think is really interesting and something that we've certainly seen an owner was developer bandwidth. And then, meaning that you know developers have to get features in place, and now we're asking them to do
06:07:41 additional things without really giving them more resources to do that. And he really called out the need for Executive support, which I kind of read is funding for to actually make the security improvements in open source code basis.
06:08:00 And like I said own app recognizes this in spades.
06:08:05 One thing that we kudos came to own up as he called own about as one of the Linux Foundation exemplary projects for fixing security problems, I mean we were at the top of the list they ran a lot of stats on Linux Foundation product projects to see how
06:08:19 well they're doing with fixing security vulnerabilities, and we are at the top of the list. So congratulations to all of the team and all of the PTS because it's a lot of work to do that.
06:08:31 This the material that he presented was also presented and derived from his participation and the White House Summit on software on the software, supply chain security challenges.
06:08:45 Like I said, Mozart presented his s bomb presentation from the DTF. A lot of you have seen this work already. And like I said it leverages Nexus IQ software composition analysis to create this bombs and members of the tack we're also interested in music,
06:09:01 and investigating this for other elephant projects.
06:09:05 And then, not to leave Heather out, she presented the stats on the participation for the January DTF, which really were outstanding I think she said over 300 people registered and over 500 actually attended sessions so yeah, it was just under we covered.
06:09:23 Just under 400 registrations, and then 525 that were actually unique attendees.
06:09:35 And what I have.
06:09:38 What I'm showing here is LFX security so this is basically, if you go to insights and you go here where it says tools, and the security you'll see this.
06:09:54 I did not know this at the time that Jim's Amylin was presenting.
06:10:01 But it to Amy's point where he talked about own app is being an example here.
06:10:11 This is the dashboard he showed at the White House
06:10:17 and own app, any highlighted own app, you know, based upon the, the work that was being done here.
06:10:30 In terms of, we're, you know, we're at the top of the leaderboard.
06:10:37 That's something to really be proud of.
06:10:42 It's a credit to set calm it's a credit to the PTS it's a credit to every on who's contributing to the community. So,
06:11:03 yeah, this presentation was at the White House and own app was featured as a model. So, congratulations, everyone.
06:11:05 And I really want to echo that. This is really, this, this number of 7000 vulnerabilities fixed.
06:11:13 That's 100% the PTS, you know, second we're good at pestering, but this really, this is pure all credit goes to the PTS for getting this work done.
06:11:25 We recognize this SATCOM recognizes that it wasn't easy.
06:11:35 Now I'm just post a note because this is a massive accomplishment.
06:11:42 It's not the first time, right. It's true that we try, I mean, we, it's not really us to TLC but really the project team she bought in by the second try to really ensure that the most important security are on top of anything.
06:12:06 So, being exposed light is, it's really a great recognition.
06:12:09 So thank you to all of you, and I think this is something we need also to share.
06:12:16 During the PTO code because I don't think we have all the project team represented.
06:12:21 But you have to be cold as well. So thank you so much.
06:12:39 Okay, any questions there.
06:12:49 Okay, David, I will then turn it over to you.
06:12:58 Alright thanks Kenny.
06:13:06 Okay.
06:13:09 Excuse me.
06:13:15 Starting with the Jakarta release. So, I think everyone's gotten half a dozen emails from me about him to scheduled for today.
06:13:29 So hopefully that doesn't come as a surprise to anyone.
06:13:33 I just updated the numbers this morning, and we're sitting at that 86%, for our projects and 50% for requirements. Let's take a quick look bad.
06:13:52 So, projects. We did have an issue with Seelye and BDNF SDK hadn't made any progress but
06:14:06 kind of garage got back to me and quickly updated these tickets so appreciate that.
06:14:15 And it looks like we have pretty good progress. The, the one outstanding project that I see here is.
06:14:26 Oh, am
06:14:26 have to have. Silvana or anyone from Joe and team on the call.
06:14:35 Okay.
06:14:37 And then looking at requirements.
06:14:41 You can see that progress has been kind of slow.
06:14:47 We still have six tasks that are in the To Do state.
06:14:55 So, I will need to follow up with these requirement owners get these completed.
06:15:04 So.
06:15:08 So the upshot is that we have not made our RM to milestone.
06:15:16 And I feel like we don't have sufficient progress that we can just simply say, you know, well, will you know to give a conditional approval.
06:15:30 So, I think that we need to push the milestone out. So I'm suggesting one week to February, 3 for him to and keep the remainder of the schedule the same stick a look at the schedule and see what that looks like so.
06:15:51 So here we have him to on January 27. So what I'm suggesting is that we push that out to
06:16:03 February 3, keep the rest of the milestones the same for now.
06:16:09 The one possible hitch there is there,
06:16:15 and reminded talk about this next, but we're trying to wrap up the issues with the essential maintenance release, which you know as the PSC agreed few weeks ago has the highest priority, and we're trying to finish that up next week as well.
06:16:39 However that impacts the relatively small subset of projects, so I'm hoping that there won't be too much interference there but I'm, I welcome input from anyone who wants to tell me otherwise.
06:17:00 Any thoughts, comments about that plan. So again, the, the recommendation here is to shift them to to February 3. Keep the other milestones the same
06:17:17 thoughts.
06:17:24 Well, we, we, I'm a little bit. First of all, I think, considering that the project team need to address the look for the annual show their major milestone to, I believe they did it.
06:17:48 I'm a little bit concerned about the progress made by the user. The user owner.
06:17:54 Just wanted to ensure that this user stories on this requirement are still part of Jocasta, or if some people think that some of them should shift to the PC.
06:18:02 For one nice that's also possible, but I'm, I mean,
06:18:10 I'm just concerned that we have still only only 50% look at finalize. So,
06:18:18 is there anybody who can provide some feedback here, what's the what's the blocking issues or, because we need to decide quickly what in what old.
06:18:31 Even if we have a new process for the PDF it's important to understand the scoop. At one point. So, if we don't have feedback by next week, either on this requirement or not so important and shouldn't be shipped to PC.
06:18:48 That will be potentially a suggestion, so it does not stop people to work but, you know, we need to keep going.
06:18:58 At least that's my, my feedback I don't know if you see members of older opinion.
06:19:11 Second, The third thing looks like that.
06:19:14 Looks like that. But, from the perspective of because we will actually have a question for info, if you don't take a stance right now.
06:19:21 And if it gets too late for that and I think it'll be a big problem for us to deliver the quality product later on. So I think that's a good sense to keep that deadline and then more I second.
06:19:38 Okay, so I can reach out to the requirement owners and let them know that, and advise them, that they either need to complete their requirement or move to PMC or shift their requirement to the next release
06:19:59 and give them one week to respond. Does that seem reasonable.
06:20:05 Yes.
06:20:07 The order of things its own do they didn't feel anything.
06:20:16 Yet, there are, there have been some progress and commitment from the PTA, to keep going. If we look at the view of components so I have the feeling that potentially.
06:20:28 You know, the BTL are already moving for what with some commitments.
06:20:33 But the use case owner did not did not acknowledge.
06:20:39 So, There are still some commitment.
06:20:43 I mean, ongoing investigation.
06:20:46 But concretely,
06:20:50 a lot of them have been analyzed, where we have still an issue, I believe, or maybe it's not an issue is the best practice.
06:21:01 and the global requirements.
06:21:04 Not a lot of feedback in this area. So I think the focus on the video call on Monday will be. This. This. Best Practice global requirement applicable for this release, because the work was done on previous release, or if we have really a gap that that's
06:21:25 the other area of concern.
06:21:30 Because the best practice and the global requirements should be part of the release as well.
06:21:37 And then I don't know if there are any, I know some people we are doing some Bucy.
06:21:43 But I don't see anything reported.
06:21:46 So, it will be also interested to know. This is the Gary Busey to know the beauty, because the focus should be really on the best practice and don't buy requirements and the use case owner to complete the task.
06:22:00 But if the people.
06:22:02 While doing for your seats always nice to learn in advance what is coming. And finally, I just wanted to ask if shocker is there.
06:22:14 I know you were about to complete everything from the architecture perspective, did all the requirement been review, even if the use case owner did not finalize this task.
06:22:41 shocker Are you on mute.
06:22:44 Is he on the call.
06:22:49 I don't see my call.
06:22:53 People here.
06:22:55 I was attending the call this week and I think we have reviewed all but one.
06:23:02 So, see the person who was supposed to present was not attending the call. Tuesday so that topic remained a tribute to.
06:23:19 Okay, thank you, t mo for new update so so we are pretty close so I think it's just a question of cleaning up the dashboard.
06:23:28 And also the focus on the global requirements and best practice.
06:23:34 Thank you, t mo to be the voice of the architecture today.
06:24:15 Okay, so do we. Does anyone disagree with shifting the milestone to February 3.
06:24:19 Okay, I'm going to drop that in as an agreed.
06:24:47 Okay, I'm
06:24:52 on to stumble.
06:24:56 Yes.
06:24:58 So, we had a discussion about the assemble maintenance release in the ppl meeting on Monday. And let me just show you the, the open issues, let's
06:25:19 see we have a total of seven issues that are not yet closed although a couple of them are in the submitted are delivered state, which is good progress.
06:25:33 And so, in discussing this with the, the PT L's on Monday.
06:25:42 There was general consensus that these items could be wrapped up.
06:25:50 By February, 4, And then
06:25:58 the TASC could potentially boat on sign off on February tab.
06:26:04 Now, one of the things that
06:26:07 I don't have a lot of information on I know I received an email from me How about daily testing.
06:26:17 And apparently there been some, some issues that they were hoping to get those resolved soon so I'm not sure about the status of daily testing on the assembled branch.
06:26:27 So we want to have that feedback before we release, obviously, so I don't, is there anyone from the integration team that can comment on this,
06:26:42 you're just looking in the results and I see that, because I think the tests, just have been running on the, on the orange app or on the, on the with the orange parts and on the actual app, I think, and unfortunately I think the last one was from the
06:27:00 24th and I think they had some issues definitely so the test results do not look like look nice, but I haven't been in the integration team meeting yesterday.
06:27:15 But yeah, I guess they they're working on a solution for them. Yeah.
06:27:40 Okay, so that's that's kind of where we stand so we're tentatively
06:27:50 looking at a February tip sign off. Assuming that we can get daily testing daily test results.
06:28:01 And again, we're going to try and wrap up these issues that I showed earlier, by the end of next week so week from tomorrow.
06:28:14 Now, you know, as I mentioned earlier, when possible hitch there is that we, we just moved the milestone out next week. Also, I'm just based based on looking at the requirements, though, I think that the maintenance release requirements affect a small
06:28:45 enough subset that hopefully you know that won't be, you know, a burden for most of the most of the projects.
06:28:47 That's what I'm thinking right now but if anyone thinks differently, and sees a problem there please let me know.
06:28:57 All right, that's it for release status, unless there are any questions.
06:29:10 Thank you.
06:29:22 Okay,
06:29:27 a real challenge.
06:29:29 I know that one of the things that is still open and still being worked is
06:29:39 23 485 which is the Docker bill timeout.
06:29:47 There were
06:29:51 updates made
06:29:54 to that.
06:29:57 A week ago.
06:30:01 Eric thought that he had identified a script that was causing the failures. That was disabled
06:30:14 and kind of waiting to see what happened from that.
06:30:23 Let's see, I see.
06:30:27 Jess on and Kevin.
06:30:33 It looks like from that from the chatter I see in our internal Slack channel.
06:30:41 There was more work done last night but things still see steam steam unstable.
06:30:50 The scripts that were disabled haven't changed the growth. Something changed in October.
06:31:00 And the growth has been very consistent.
06:31:10 Since then,
06:31:10 and gesture Kevin, do we know if that's in a particular set of repose or or.
06:31:21 Where exactly is that that data growth,
06:31:25 showing up, you know, we're still investigating that but at the moment we, we don't know yet.
06:31:34 I know that also Eric was trying to work on the upgrade of the latest version to help out things but he was facing some issues. And the last update he made is the correct version that was updated wrong so that's the last thing that I that I knew from
06:31:56 that process but regards to what's, what, what color, what started causing these data crow.
06:32:05 We're still not sure where is it coming from
06:32:09 Kevin Do you have any other information you want to dimension,
06:32:16 or you know basically what did it really showed when the word that he has been doing and yeah there are saying that I saw is that operate and the versions, but seems like that in instabilities is still there.
06:32:45 So what could we
06:32:48 is, is there a way we can, we can identify where the data is where the growth is happening i mean i guess the question is, are we seeing this data growth across all of the repos, or does a certain side of components, or what because it just not to put
06:33:16 you guys on the spot but I'm going to do it anyway.
06:33:26 Um, it seems like that should be something we can, we can pinpoint, it's it's clear, it's clear something changed in October. Yes. And it's hard to say because we don't see anything that we can tell like oh these particular component, added a bunch of
06:33:40 new jobs, for example, is everything looks still bring normal to what we usually release and what we usually.
06:33:51 Having Jenkins, so that's why it's very difficult to, to understand where is that that a group coming from scenes from the perspective of what we have in Jenkins and what we have building for each component is still pretty normal we don't see, we didn't
06:34:09 saw anything that could tell us a particular component, made a change that is spiking the data grow that is not that is not that. So that's why the confusion is still lingers on.
06:34:26 Where's this coming from.
06:34:28 So you mean you, if we look at Gary, we don't see any gang stalking, a big bump. Now, from, from Jenkins.
06:34:40 The, the growth of what branches have been added by which components is still. As usual I mean, there's nothing that happened in October that could tell us that a particular component might be related, so there's not nothing like that so it seems to be
06:35:04 more internal in the server so that's why it's a little bit difficult to to investigate.
06:35:11 And I was thinking, we were creating branches, so maybe you have the bunch of the release and then the bunch of the master so by default it's my view so it's like although I wanted to say.
06:35:30 Okay.
06:35:30 At the same time, I was wondering.
06:35:32 Oh, go ahead.
06:35:40 Jenkins job title really more on the Nexus and the storage file.
06:35:46 It seems to be on the Nexus and storage.
06:35:49 From the Jenkins perspective yes we have been adding more branches.
06:35:54 For our for our own purposes but at the same time we've been disabling the brokers branches too so it's, it almost like kana balances out.
06:36:06 There's nothing from Jenkins that we can say, Oh, this component.
06:36:13 This for example I mean it seems to be more related to the words properly not getting.
06:36:21 Not happening or not enough properly from winning Nexus. So it seems to be more internal to what Nexus has.
06:36:31 maybe on the next slide, even without more jobs, it could be that more and more attractive or inexperienced and many others by looking at the police record
06:37:07 So, that is that is another thing that we're looking a lot into the that part of the script the cleanup scripts with it related to the snapshots because since, since Nexus does not does not provide a building task for removing artifacts in snapshot, long
06:37:28 ago we wrote this script that takes care of that so that's great needs to be revisited and we have revisited in the past, when there has been problems with artifacts reported being disappeared and when they shouldn't so this this particular script has
06:37:46 gone through quite a bit of changes and is probably needs to be addressed. Overall, so that's the other part of the investigation that we're working on.
06:37:59 Maybe it could be good to have a look I don't know because I don't know which which really makes us really believe it or so.
06:38:19 The next thing that we are using we are able to sit to put some rules beginning at Nexus Nexus administration to, to put the time of the time to leave for the the artifact is structured one.
06:38:24 So they are a Nexus is taking care of clean up with these words.
06:38:31 But that's the future that's, yeah. The other thing that I was thinking is, I'm trying to
06:38:39 do an inventory of what components are making releases to snapshots in a, in a, how do you call it in a cron job. So, if, if our release doesn't need to be done maybe probably we can just disable any cron jobs that are automatically.
06:39:02 Pushing deliverables, but at the same time, if, if a project is making a release of something that is already present Nexus doesn't create a new file it basically overrides any anything that interruptions This is when when rather snapshots really does
06:39:19 happen still, there's no releases that happen in Punjab in cron jobs.
06:39:24 The snapshots are the ones that are at investigated now but when it comes to snapchats if even if there's projects, releasing on a cron schedule Nexus will override whatever is being rereleased again so it's not like Nexus creates as a separate kind of
06:39:47 artifacts. So, This is another thing that I was thinking off but I don't think so this is a problem, to be quite honest, I can still look into that.
06:40:08 might be also in terms of the releasing of artifacts for snapshots, I think some projects may be releasing Maven artifacts, when they actually don't need to.
06:40:18 Correct, correct. That was the case for me like if you only need the container, then you shouldn't be releasing and even after that fact as well. So, yeah, and maybe we can bring the this up in the video call because I mean it's difficult.
06:40:32 Unless we have the representatives for the components.
06:40:35 They, they are the best to know what can be reduced from the artifacts from their Docker images.
06:40:58 Okay, so sounds like we need to do some more drill down schedule that for the add that to the PTO meeting. Yeah, we have a sync up today Kevin and I with Eric as well.
06:41:10 Later today so we can discuss if he has found also anything new, from his side.
06:41:40 Okay.
06:41:45 Anything else.
06:41:50 Cool or ticket related.
06:42:00 Okay, um, we still need your help. Hiring
06:42:06 in the EU.
06:42:10 There's the link I will drop it once again into the chat window.
06:42:16 We can use your help filling that wreck
06:42:26 and wanted to give you all an update on the lab.
06:42:33 University in New Hampshire.
06:42:37 The eight servers.
06:42:43 We have a meeting scheduled in a couple hours from now, to actually sync up on where the installation is.
06:42:53 So folks at UNH will be providing the, the, the hands and eyes to actually do the physical work.
06:43:07 When river is going to continue doing the, the work remotely. And then once setup, we can start planning the migration off of the Wind River lab.
06:43:26 And it looks like Michael is added
06:43:34 a proposal for more as your resources.
06:43:38 I actually added that on the cows behalf eight we received an email started the week.
06:43:48 And I think this kind of comes from Orange. In general I think maybe I don't think make Alice on the call. But I think maybe Eric is Eric Can you comment on this.
06:44:07 I don't see ya are on the call.
06:44:11 Eric you're on mute.
06:44:13 Maybe stepped away. Yeah.
06:44:16 Okay.
06:44:17 Okay, um, obviously that has
06:44:23 that has ramifications in terms of dollars and cents.
06:44:32 So, I guess I'll I will go looking for that email I clearly missed it. Thank you David for putting that in, and we will take a look at it, and I guess, bring it up again here next week.
06:45:15 Okay,
06:45:19 so then moving on, PDL updates
06:45:30 didn't have anyone.
06:45:33 Step up for VP, or Vf requirements.
06:45:40 So where do we go from here.
06:45:45 So I hope you can hear me No. Yes.
06:45:48 Yes. So, as we decided this last week. They were to option, either the vest specification will be taking over by the model is committee or either the DC project team.
06:46:03 So I sent this morning during this Cole request to do not modeling because I don't think we have any representative from the school today.
06:46:12 As we
06:46:18 know, so, I've attached the link to the email, the issue of diversification.
06:46:25 You can see that there is a link here.
06:46:29 And I'm waiting feedback from the modeling subcommittee.
06:46:35 Based on my based on the requests that I have sent this morning.
06:46:39 Not this one, not this one it was a link email sent to do enough modeling below below below below, know that one. Yeah.
06:47:08 Okay.
06:47:14 Then I guess moving on
06:47:19 to mass Are you on the call. Yes.
06:47:25 So there was a discussion about insufficient documentation for installation.
06:47:35 This came from the, from the ptl call.
06:47:41 Do you want to discuss this.
06:47:46 Do you want to discuss this one sure if there is, or if I can discuss it but we have just said, we have this discussion in the previous documentation colon, what I can do is to fall bought some two links to the available documentation, where we have the
06:48:06 the installation for the product and we have something that was done by our networks, think last year to explain the virtual firewall, use case how to install it and
06:48:25 if we have then more information what is lacking, so we can decide who and what can be updated, which would would just be feasible.
06:48:42 Yes, that sounds reasonable.
06:48:45 So, so
06:48:49 one of the one of the specific questions I have is, is, is the documentation that was produced by the contract.
06:49:03 Viewed to be insufficient or incorrect or, or is it just out of date now.
06:49:12 I'm out of date has to be checked. So, but I think it was more on the virtual firewall use case site.
06:49:24 And maybe we have something to do on the install these the owner product side, but
06:49:34 that let me, provide me. Let that provide let me provide the links and then
06:49:42 people can say what information is lacking.
06:49:47 Okay, let me see.
06:49:54 We'll put it in the, in the chat in a minute or two. Okay.
06:50:46 Okay. Um,
06:50:52 so I'm just gonna keep rolling forward we heard from Amy.
06:50:59 One of the things I'm speaking with Allah. We need a new representative for the elephant Strategic Planning Council.
06:51:13 And my question to the
06:51:22 TASC is, should that become a kind of a standing responsibility for whomever is elected the vice chair. What do you guys think.
06:51:45 Don't everybody talk at once.
06:51:49 Why would you want to do that connection.
06:51:54 Right now, the, the Vice Chair position really doesn't have that much associated with it.
06:52:08 Give me a second. Let me pull this up.
06:52:22 to see. And I know these links don't work.
06:52:28 for.to dot five.
06:52:31 What word my mouse go.
06:52:34 But I saw it was a Magnus I think it's, it was, it's not so bad it was. Kenya suggested because when we define the charts, we were expecting that each DSD member will have an active whole.
06:52:51 So, if indeed the Vice Chair have know that we don't know will be the rideshare but if it might be something that device you can take as well as a response, stability, If he has no other activities.
06:53:09 It was not intended as a sort of a critical question I just wanted to know about the background there. But I, I realized it it would be a link from the chair and the waist and the vice chair to to this council, and then that, that makes sense.
06:53:31 Yeah.
06:53:31 Don't worry. We were not considering your feedback. As a kid, isn't it what we about I mean I didn't do it.
06:53:40 I think it's important that people raise anytime any question that every every minute, so feel free to do so anytime you want clarification, Magnus you're more than welcome.
06:53:51 Thank you.
06:53:58 So, yeah, just I mean from my from, from my perspective, it seems like a logic logical place to couple responsibilities.
06:54:10 The, the SPC is a committee of the governing board.
06:54:17 So it just seems like the representation there.
06:54:24 It just seems logical to me.
06:54:27 And what I've got highlighted here folks can see as it currently stands what the Vice Chair responsibilities are. I realized that we are in the middle of nominations for the Vice Chair position.
06:54:45 So, it probably wouldn't be appropriate to change that, in the middle of this.
06:54:55 But afterwards that that might seem like a, a,
06:55:03 Something that that we would want to codify into the technical community document.
06:55:13 So I kind of want to talk about that.
06:55:17 In that context.
06:55:20 The next meeting of the,
06:55:26 of the lF in
06:55:30 SPC is on the, I want to say the six, it's on the, on Valentine's Day 14 to February.
06:55:45 So maybe can we can we capture the dates and maybe the time of the SPC meeting. Is it mostly meeting, so I think it just they information about it. They changed it was bi weekly it's been changed a monthly as of Monday.
06:56:07 They voted to make that a monthly call.
06:56:26 Since the, I think the denomination should be closed by 31st. Do you think that we will have the vice chairs.
06:56:38 Already nominated so the Vice Chair can yeah the election the election is just confirm his interest. Since it's, it's the DNC members only.
06:56:49 It's there there's four business days for voting.
06:56:55 So, We could logically have a new person there.
06:57:03 If, if there's a general thought that that's the direction we want to go.
06:57:08 Like I said, we don't need to codify it but anyone that was becoming in as a nominee should be aware of that, that's kind of the direction that the TASC his, his head.
06:57:30 in when is that 1500 UTC.
06:57:48 I don't know if anybody have any additional so
06:57:56 what we need to conclude on this topic, no later than the tense. During the Tsu of the tense. Right. Yep.
06:58:06 Okay.
06:58:54 Yes, right now that's that's just a community coordinator position it can remain that there's no reason that it can't.
06:59:09 Well, let's see.
06:59:10 Oh, the Vice Chair will react and if there is anybody from the committee interested we might need also to know as well.
06:59:20 Yep.
06:59:23 So, I will send out an email. Basically, announcing that this seat.
06:59:39 The seat this position this this responsibility is open.
07:00:03 Okay,
07:00:08 then moving on CNF Task Force.
07:00:19 Yes. So, so I think there, they are three. I don't know if we are still being with us.
07:00:25 They were playing area where the sniff test course is moving forward.
07:00:33 I wanted to invite Lucas, and also a bu, and Fred to maybe present the different opportunities that we have to partners with promoted by the Senate Task Force.
07:00:50 So we have already team members working on it, but wanted to seize the opportunity to make a call or volunteer to work on the different Bucy, which are ongoing.
07:01:02 So maybe fed beyond Lucas, you would like to present. If you are still there with us today.
07:01:14 I don't see beyond.
07:01:15 Yeah, cover the spread all over at the. I don't have anything to present I think the youngest probably the one that's most active there, I'll contact him, typically least present something or update the group about what's happening.
07:01:45 Okay.
07:01:35 Thank you, foot is I think beyond to leave so maybe we can put these topics.
07:01:42 Next week on top of the agenda because I know he has sometimes some conflict, you can follow up with with him it would be great. And I guess all this topic.
07:01:53 I'm just checking on the first was really
07:02:01 driven by by beyond.
07:02:04 Yeah.
07:02:06 Okay, so let's have this topics next week, and Kenny I might need to hop. But before I just wanted to say that because I need to disappear. I want to continue the discussion that we have other media for him concerning the 2022 on our priorities and action
07:02:28 plan. That's something we like to others. Next week during the next year. See, since. Unfortunately, I cannot stay longer today. Thank you.
07:02:50 Good. Okay.
07:02:57 So I guess we will
07:03:00 shift that to next week.
07:03:09 Unless somebody would like to lead the discussion.
07:03:28 Okay.
07:03:31 Um, other housekeeping topics.
07:03:35 We're looking at doing a virtual oni.
07:03:44 Probably I'm guessing it's going to be early q2.
07:03:51 Well find out there there's work on that that is the executive forum where folks are
07:04:01 presenting.
07:04:04 And it's tends to be more business focused.
07:04:08 There is work, looking at, and
07:04:15 a one summit.
07:04:18 Coming up at some point this year.
07:04:23 But on the schedule.
07:04:26 We have our face to face testing forum.
07:04:30 Fingers crossed in Porto Portugal.
07:04:36 And I am very much looking forward to that.
07:04:40 Is there any other business.
07:04:57 Okay. Hearing none, I'm going to go ahead and close the meeting out then.
07:05:03 Hey Kenny this shocker so if you could give me the presenter rights for a second. I'll give you an update on where we are with the architectural reviews.
07:05:12 Yeah.
07:05:14 The data only. Yes, please.
07:05:21 There you go.
07:05:22 Thank you very much.
07:05:35 Can you all see my screen.
07:05:37 Yes. Okay, thank you.
07:05:40 So, this is where we are today this is the latest and greatest.
07:05:45 We had an architecture review this past Tuesday.
07:05:52 We completed everything except of. So, just as an FYI.
07:06:00 If you're trying to access the, the portal, or the navigator it's a change the URL and I'm in the process of changing the couple of URLs so give me, probably a couple hours today and then it'll be back up but this is a different your URL that I'm using
07:06:18 that points to the same basically portal.
07:06:22 In any case,
07:06:25 everything that you see in green over here has been completed a pic on the policy.
07:06:32 And as I mentioned earlier, it's all clickable when you click on it, it takes you to the JIRA ticket and shows me the intent over here is to be able to look at the JIRA ticket and follow through and be able to access all the documents that were reviewed
07:06:50 and or referenced, and you should be able to get a pretty good idea as to what the reviews all about all the features and the changes that were included in the review, and any FYI eyes that you may need to be aware of in terms of the, the features of
07:07:15 the specific feature for that specific component.
07:07:20 Means, and any dependencies and so on so forth so the intent over here is to make sure that when you click on the JIRA, you get a very comprehensive view of what the feature is all about what the what the changes are all about, in any other FYI is that
07:07:39 you need to be aware of in terms of the, the features, the impact on your component to your respective components. When the features implemented. So I would encourage all of you, including the PDL especially the PTS to take a look at what we're doing
07:07:57 over here and make sure that all the features are well understood.
07:08:03 The only review that we have still outstanding is of trying to reach out to Krishna, Krishna was supposed to present on Tuesday, later this past Tuesday.
07:08:18 For some reason he was unavailable so I will reach out to him offline make sure that we, We do that with complete that.
07:08:28 Any questions before I move on.
07:08:33 OK, so again, all the green boxes are the components that have been reviewed
07:08:40 the blue boxes obviously are the components that have not been impacted.
07:08:45 So at the end of the release cycle at the later stage or later milestones will make sure that everything that we have over here matches all the everything that's been deployed, we just want to make sure that we track, all the changes.
07:09:00 The architectural review level.
07:09:03 Another item that I added to the menu which is the major use cases that have gone through an architectural review.
07:09:11 This is something that we just added again for tracking purposes.
07:09:15 So, if you look at these are the these use cases, only two use cases were modified or chain changed for the Jakarta release and let me pick on the internet use case you click on it takes you to the tracking JIRA ticket associated with the intense slicing
07:09:37 and everything that you want to know about the feature is referenced over here, and it tells you also.
07:09:45 When the feature was reviewed and implemented and
07:09:50 accepted or approved by the architectural review.
07:09:54 If I go back and you'll see song.
07:09:58 So, in which is the self, optimizing networks. I thought I might apply this.
07:10:07 what we've tried to do at the architectural review level, sorry. I'll make, there's a typo over here I made the changes offline.
07:10:18 What we're trying to do at the architectural review level, even though
07:10:23 there were no major features and capabilities introduce for the song use case.
07:10:32 I did ask, Shankar to come in and actually review song just because it's a it's a critical use case I want to make sure I give the details and anybody that is interested in learning more about song, I want to give Shankar an opportunity to present that
07:10:53 there is no new features or capabilities edit over here so it's not a showstopper.
07:10:58 But this is something that will, we will schedule for a future architecture reviews.
07:11:07 So, common factor, of course. So, I welcome that.
07:11:19 We try to do it on one time, one of the meetings and the timing didn't work out. But as you said it's not critical. So, the people who had to present present first never come in.
07:11:24 Absolutely. Thank you.
07:11:25 We had, I mean the, just to back to a point and that's a good point. This is the we ran into an issue and one week when we had a problem with the zoom two factor authentication so the schedule will get all messed up mixed up so we have to reschedule it
07:11:42 and reschedule and so on so forth but again.
07:11:47 The point here is this is an FYI, I want to make sure that I give Shankar, an opportunity to explain it.
07:11:53 Explain the features, or the use case to the rest of the community centers showstopper scheduled for next week and we'll go ahead and do that so thank you for the comment.
07:12:05 Some showstopper scheduled for next week and we'll go ahead and do that so thank you for the comment. Okay. So, going back to the attraction or the dashboard.
07:12:14 Again the color code or legend is the didn't know the agenda the magenta or the.
07:12:21 The purple colors or the components that don't have any details we keep track of those of these components just to make sure that if there's a feature capability this been introduced has a dependency on a component that does not have a PDF or.
07:12:38 We just flag it and make sure bring it to the DSC attention.
07:12:44 Okay.
07:12:45 That's all I have.
07:12:47 Let's will assume that no later than next week we'll finish all the complete all the reviews, or if it's the only one that says outstanding at this point.
07:12:58 So I don't foresee any issues completing everything by next week.
07:13:05 Any comments truck or whatever.
07:13:09 One other quick questions into an slicing is case also had was a different color. So I just want to alert, Eli and Kevin. If something is upsetting.
07:13:23 this one.
07:13:25 Yeah, you had to give a different color. I was wondering. Oh, it's a blue Okay, different color meanings in different colors. Yes, different color sorry I maybe I was not too clear.
07:13:38 But the, the intent over here is to highlight the different color over here means that this use case was changed for the specific release, and it was reviewed by the architecture school subcommittee conceivably you could make a change, that is not reviewed
07:13:56 by the architecture subcommittee. We would never know about it. Therefore, it would not be noted, right.
07:14:03 So, all we did saying over here is that it is there was a JIRA ticket associated with it, there were some changes, a bit, they could be minor changes, and the fact that the architecture subcommittee subcommittee reviewed the, the feature capability or
07:14:20 it could be an FYI, which is your case, or in the case of song.
07:14:26 We want to track it, that's all there is to it in the reason that I wanted to track that is because when I click on it.
07:14:34 Then I click on the JIRA ticket. It provides additional capabilities or additional information, or references to more information about the use case and that would be.
07:14:58 It is helpful for me so I'm assuming it will be helpful for everybody to learn more about a specific topic or specific use case.
07:14:55 Thank you.
07:14:58 Okay, you want.
07:14:58 One of the things just looking at it, it just a little bit of feedback and I know that that this is basically remained on the same format for quite a while now.
07:15:12 but just looking at it, rather than no impact.
07:15:16 It would it be more appropriate to say no change.
07:15:24 He Yeah, I mean, yeah, I mean I'm meaning.
07:15:31 Okay, you're talking about this over here. Yeah. Okay, and and that's, I was just looking at that in the context of the discussion we just had now.
07:15:42 Okay.
07:15:44 Yeah.
07:15:46 I mean, it makes it makes sense
07:15:51 if it's okay with everybody I'll change the way you're talking about the legend over here. So, yeah, exactly. Yeah, yeah, that's that's the intense I'm sorry I'm not really with you there.
07:16:04 Why, why would it be better I mean it could change but it doesn't have an impact on the, On the rest of the,
07:16:13 of the components.
07:16:16 Well, it needs to if there are changes to the use case, it needs to be. and maybe this is my lack of understanding.
07:16:28 If there's a change of the use case, it should be reviewed by the architecture subcommittee.
07:16:32 Even if it doesn't have any impact on the, on the components are affected.
07:16:44 I guess it's nitpicking but one that no that's that's so that's the question and that's where I'm saying, Yeah, yeah, I may not know, but the. Now that you mentioned that though, Kenny, right, thinking about it, no impact assumes that we have looked at
07:17:08 the rest of the components and determined that there is no impact on
07:17:15 on any of the components.
07:17:19 As it relates to the, the component that is labelled
07:17:26 no impact. Right. And I'm not sure if I'm, I'm saying that I'm thinking out loud over here, right.
07:17:32 We, we assess the changes we we basically review the changes. And based on the big changes that we review.
07:17:43 Then we assess impact on the rest of the components, but we don't do it the other way around.
07:17:48 What the no impact meant over here is that the, the use case or the component has no, it's not introducing any changes or any capabilities in this specific release.
07:18:09 So if I look at for example, for look at the example 5g sec VPN transport slicing the way it is listed today, means that they're not introducing any features, or any new features or any new capabilities in the Jakarta release.
07:18:28 That's what the no impact means. Okay.
07:18:35 And it doesn't necessarily mean that that the use case is exactly the same as it was before.
07:18:46 The.
07:18:48 It means that the use case, the, the, the requirements.
07:18:57 And the code associated with a use case has not changed. Right. You could conceivably have a use case that you can change this behavior by introducing a new configuration.
07:19:14 Right. Yes. Yeah, yeah, yeah, without making any changes to the new data. Exactly, maybe a new model. Yeah, maybe no model, but yet, but you, but the Kate you use case itself the code associated associated with use case did not change.
07:19:31 And that's what we're looking for. Right. Yeah.
07:19:36 But the behavior of course i mean if you, if you have a use case that is Model Driven, and you update the model or reintroduced new model without making changes to the use case itself.
07:19:47 That's something that would not would not review on.
07:19:50 I'm not, I'm not saying that we shouldn't be reviewing, but at least we're not reviewing at this point.
07:20:00 Okay. Yeah, that makes sense. So, as, as represented here probably more correct. Okay.
07:20:08 However, though, right i mean this is this, this is intended for a wider audience, right, so if it is something that we need to improve on.
07:20:17 Of course I mean just send me an email and we'll, we'll definitely consider it the intent over us to make sure that it is anything that we present on this or any other subsequent pages are well understood by by or by almost everybody.
07:20:37 So if we go back and look at this page. Anything that is colored in in the bluish and the owner bluish color.
07:20:45 Anything that is colored in in the bluish and the owner bluish color. The assumption of here is that there is no code changes, there are no functional changes.