661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2022 TSC Recordings	2022 TSC Decisions	Anti-Trust Policy

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

Attended	Proxy (w/ @name)	Gov. Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Alla.Goldner	AMDOCS	Fernando Oliveira	Individual Contributor
Andreas Geißler	DT	Magnus Buhrgard (Unlicensed)	Ericsson
Bin Yang	WindRiver	N.K. Shankaranarayanan	STL
Former user (Deleted)	Bell Canada	Ranny Haiby	Samsung
cl664y@att.com	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/
Release Status	David McBride	Weekly update Jakarta Release TSC agreed last week to push schedule one week Jakarta Milestone Status Priority High or Highest Jira Issues #vote Does the TSC approve Jakarta M3 under the condition that the following issues are resolved by Jakarta M4? INT-2063 OPTFRA-1034 HOLMES-518 MULTICLOUD-1443 SDNC-1661 CCSDK-3585 VFC-1924 DMAAP-1712 OPTFRA-1031 ? (has been sent to onap-tsc-vote list.) Other Submitted gerrit review for new relman repo, approved by the TSC on Feb 17 Istanbul Maintenance List of new issues for the Istanbul maintenance release. Note that these issues were created after publication of the weekly update.
RelEng/Infrastructure	Jessica Gonzalez	Tickets- Open showstoppers: Tickets- Waiting on Community: Migration Status / Upcoming Changes UNH Lab
Task Force Update ONAP Enterprise Task Force	cl664y@att.com	#1 ONAP/EMCO Alignment - This presentation will be shared during the LFN DDF on 2/15 2 sessions: 5.15-6.30 am PST (EMCO/ONAP Architecture alignment Deep Dive) and 6:45-8:00 AM PST (Orchestration: EMCO and ONAP ongoing operations alignment) Thank you Lukasz Rajewski , Ranny Haiby and Bin Yang . Seshu Kumar Mudiganti shared feedback about ongoing POC between EMCO and ONAP CNF O. #2 SABRES/ONAP Integration POC
PTL Updates		Congratulations to JC , our new CCSDK committer!
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	cl664y@att.com	Latest Updates about ASD Modeling 2 ways to proceed: #1 Clean State v1 based on current IM associated to ASD Model and continue the dialog as part of v2 discussions #2 Perform the mapping and mark ‘preliminary classes’ what it differs from the current model Application Service Descriptor (ASD) onboarding IM CNF Design Time IM Mapping Proposal from Yang Xu CNF IM discussion presented at CNF taskforce Marian Darula
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Paweł Pawlak Amy Zwarico	SECCOM update on insufficient progress for Packages Upgrades in Jakarta release. SECCOM update for Istanbul Maintenance Release Notes - missing info from projects with log4j transitive dependencies - Jira tickets were opened to fix that.
LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board		SPC - ONAP Strategic Planning Committee (SPC) Representative - Call for Nomination
TCC / ONAP Liaison Updates
TSC Activities and Deadlines	cl664y@att.com	ONAP Community Awards: Istanbul Release 2022 ONAP Priorities / Action Plan LFN Board follow-up actions -no update this week Prepare TM Forum presentation (April 11th, 2022)
Upcoming Events & Housekeeping	Kenny Paul	Clock Change: March 12th (US) and March 26th (EMEA) LFN DTF Workshop March 14 & 15 Virtual Single track focused on cross-collab follow-ups to the Jan DTF Open Networking & Edge Executive Forum (ONEEF) April 12 - 14, 2022 Virtual 6LFN Developer & Testing Forum EU June 13-16, 2022, Porto, Portugal In-Person Topic Proposals:
<Available Slot>

Zoom Chat Log

05:54:36 From Sai Seshu to Everyone:
#info Seshu, huawei
05:57:13 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
05:58:39 From Magnus Buhrgard to Everyone:
#info Magnus Buhrgard, Ericsson
05:58:52 From N.K. Shankaranarayanan to Everyone:
#info N.K.Shankar, STL
06:00:12 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
06:00:16 From bin.yang@windriver.com to Everyone:
#info Bin Yang, Wind River
06:00:25 From Yuanhong Deng (China Mobile) to Everyone:
#info Yuanhong Deng, China Mobile
06:00:35 From Bruno Sakoto to Everyone:
#info Bruno Sakoto, Bell Canada
06:00:55 From Fred Oliveira to Everyone:
#info Fred Oliveira, Self
06:01:09 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
06:01:10 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
06:01:12 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
06:04:52 From Eric Debeau to Everyone:
#info Eric Debeau, Orange
06:05:03 From Catherine Lefevre to Everyone:
#info Catherine L, ATT
06:05:15 From Kenny PAUL (LFN) to Everyone:
@eric, @catherine - thanks
06:31:18 From Kenny PAUL (LFN) to Everyone:
https://lf-onap.atlassian.net/wiki/x/m7r7
06:57:05 From N.K. Shankaranarayanan (STL) to Everyone:
Comment re. EMCO_ONAP Alignment Proposal: Slides 1,2,3 mentions Non-RT RIC (SMO). The SMO is an entity defined by O-RAN and it has the O2 interface to the O-Cloud. The alignment of EMCO and O-RAN should be addressed. This comment is related to the O2 question on Slide 7.
07:15:43 From Zu Qiang (Ericsson) to Everyone:
rh
07:16:02 From Marian Darula to Everyone:
rh
07:16:06 From Thinh NGUYENPHU to Everyone:
RH
07:16:13 From Magnus Buhrgard to Everyone:
rh
07:16:20 From Byung-Woo Jun (Ericsson) to Everyone:
Rh :)
07:16:46 From Catherine Lefevre to Everyone:
Dear all - i suggest that we start the questions after Xu finished his presentation
07:16:53 From Catherine Lefevre to Everyone:
Thank you
07:18:20 From Kevin Sandi (LFN) to Everyone:
I’m sorry I have to leave the call to take care of an urgent personal matter
07:20:10 From Timo Perala (Nokia) to Everyone:
+1 Shankar. Fully agree with you. That's why I have advertised the event since mid Feb to the community meeting on Wednesdays,, the meeting "ONAP/O-RAN-SC Alignment for SMO/NONRTRIC/OAM/SIM"
07:20:19 From Fred Oliveira to Everyone:
I support this approach to map the ONAP IM to support ASD.
07:22:59 From Andy MAYER (AT&T) to Everyone:
Mapping is a great approach for the parent class. We need to make sure that any new classes introduced by ASD are reflected in the Information Model as well.
07:23:49 From Thinh NGUYENPHU to Everyone:
I have prepared a slide set to clarify ASD concept rationales and highlight some of the IFA011 ETSI MANO differences
07:24:10 From Andy MAYER (AT&T) to Everyone:
The ASD Data Model (implementation) can map only the pieces of the information model that are part of the implementation.
07:24:58 From Andy MAYER (AT&T) to Everyone:
The important part is to capture the Data Model mapping. Plus augment the Information Model where there are gaps.
07:25:14 From Xu YANG to Everyone:
Yes, Andy is right. And actually the Mandatory here is not mandatory for the onboarding model, but to the orchestrators.
07:26:03 From Andy MAYER (AT&T) to Everyone:
RH
07:30:26 From Fred Oliveira to Everyone:
I agree with Andy and Xu. IMHO ONAP IM should only need minor changes to support the ASD needs.
07:31:46 From Fred Oliveira to Everyone:
The ONAP IM references the IFA011 but is maintained independently and doesn’t require ETSI input/agreement
07:37:18 From Xu YANG to Everyone:
What Zu and Thinh shows are still from the perspective of implementation/DM, we shouldn't mix them with the discussion of the IM.
07:40:52 From Marian Darula to Everyone:
DM model reflects the architecture of IM. If we adopt ETSI MANO in ASD, than we need to implement concepts of ETSI MANO architecture in ASD. This is exactly what we wanted to avoid, and reason why ASD was invented.
07:41:46 From Xu YANG to Everyone:
No, merging the IM doesn't mean you need to use the ETSI MANO in implementation.
07:42:13 From Xu YANG to Everyone:
It doesn't mean you need to modify SOL001 as a DM.
07:45:07 From Bruno Sakoto to Everyone:
Sorry, I have to drop
07:46:01 From N.K. Shankaranarayanan (STL) to Everyone:
Important discussion. I will catch up with the recording. I have another critical call to join. Thanks.
07:46:25 From Xu YANG to Everyone:
rh
07:46:52 From Lingli to Everyone:
RH
07:48:53 From Bruno Sakoto to Everyone:
Back
07:49:23 From Thinh NGUYENPHU to Everyone:
The problem is that current ETSI IFA011 IM model is tightly couple with their own architecture (NFVO and VNFM).
07:49:46 From Byung-Woo Jun (Ericsson) to Everyone:
Xu, now Andy understood why the separate ASD IM makes sense
07:49:55 From Zu Qiang (Ericsson) to Everyone:
Xu said: "mandatary does not mean you need to support it" why it is mandatary?
07:49:57 From Byung-Woo Jun (Ericsson) to Everyone:
You are talking about his previous comments
07:50:29 From Byung-Woo Jun (Ericsson) to Everyone:
ONAP IM mandatory and optional changes do not reflect to ETSI NFV specification automatically
07:50:36 From Byung-Woo Jun (Ericsson) to Everyone:
Actually ETSI NFV did not approve it
07:50:40 From Thinh NGUYENPHU to Everyone:
removing mandatory, which mean no VNFM and NFVO. right?
07:51:18 From Byung-Woo Jun (Ericsson) to Everyone:
As long as ONAP IM refers to IFA011 which links ETSI MANO, it won’t work for ASD
07:51:53 From philiprobb to Everyone:
From what I’m hearing the underlying architectural drivers between the existing ESTI based IM/DM and the ASD IM/DM are significantly different… one tied to ETSI and one driven by contemporary container/CNF tooling. Given the different architectural drivers, it warrants different IM/DM Modeling implementations
07:53:16 From Fred Oliveira to Everyone:
@Phil. I actually think there are very few architectural differences.
07:54:14 From Byung-Woo Jun (Ericsson) to Everyone:
@fred, I disagree, considering impacts on SOL003, SOL005, VNFM and NFVO. We are bypassing those ETSI MANO components
07:54:40 From Byung-Woo Jun (Ericsson) to Everyone:
IFA011 refers ETSI MANO (e.g., VNFM)
07:55:00 From Fred Oliveira to Everyone:
@Byung Those are implementation aspects not conceptual/architectural.
07:55:19 From Byung-Woo Jun (Ericsson) to Everyone:
It is architectural
07:55:57 From Xu YANG to Everyone:
@Zu, the "mandatory" means the orchestrator needs to support processing of such information, not means the onboarding NFs need to support or use them.
07:56:03 From Fred Oliveira to Everyone:
Seems to me that the VNFM functionality has just been incorporated into the NFVO.
07:57:21 From Zu Qiang (Ericsson) to Everyone:
@xu your statement is misleading
07:57:41 From Eric Debeau to Everyone:
Sorry, I have to drop.
07:57:57 From Thinh NGUYENPHU to Everyone:
rh
07:57:59 From Xu YANG to Everyone:
I think weeks ago, people are arguing we should not wait for SDOs, and not bind to certain standards, and now we are arguing that we need to wait for ETSI's decision...
07:58:59 From Xu YANG to Everyone:
@Zu, that's the intention of the mandatory property, and what you want to refer to is the Cardinality
08:00:38 From philiprobb to Everyone:
@Fred, I think that the VNFM/NFVO difference is one instance, but aligning more closely with the tools/features available from the K8s/container ecosystem allows for different evolution paths *into the future* between the two architectural underpinnings.
08:01:37 From Bruno Sakoto to Everyone:
I have to drop for another call
08:01:45 From Kenny PAUL (LFN) to Everyone:
https://wiki.lfnetworking.org/x/hJEZB
08:02:45 From Fred Oliveira to Everyone:
@Phil The ETSI approach uses the same “native” tooling, including Helm Charts for K8S support.

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:02:07 Okay.
06:02:13 The meeting is being recorded. All participants are muted when you come into the meeting, please keep yourself muted unless you're speaking to unmute, please dial six on your cell phone, all private zoom messages sent during the meeting will become part
06:02:28 of the public record
06:02:32 my net radio announcer voice will start our meeting by mentioning our anti trust policy. You can find this link from the lF and all of the project websites there's policies important where we've got multiple companies, including potential industry competitors
06:02:45 participating in these meetings. Please review if you have any questions please contact your company's legal counsel, members of the elf may also contact Andrew appt growth at the firm up Grove LLP which provides legal counsel to the Linux Foundation.
06:03:06 On today's agenda.
06:03:13 Discussion of release status.
06:03:18 We'll touch on any relevant issues.
06:03:21 The Enterprise Task Force have an update their ASD is on the agenda, I think folks are familiar with that.
06:03:33 We've got discussion about the SBC, and then basic administrative year is there anything else that anyone would like to see added.
06:03:48 Okay, David, I will turn it over to you sir.
06:03:54 Alright, thanks Kenny.
06:03:58 Can everyone hear me okay yes sir You sound great.
06:04:01 Okay, good. I just got a new headset so making sure that it's working.
06:04:12 Alright, so I sent out the weekly update that has details about various release efforts that are in the works specifically today.
06:04:29 We wanted to focus on the
06:04:33 Jakarta release milestone three.
06:04:38 As a reminder, last week.
06:04:43 The TASC agreed to push the schedule out one week I updated schedule. Yeah, here it is.
06:04:59 So as you can see, We have em three.
06:05:04 Today, on March 10.
06:05:06 And then also, am for release candidate and sign up for also pushed out with sign off, moving out to may 12.
06:05:21 So let's take a look at where we're at with the milestone status.
06:05:27 The project teams have been working hard to get caught up, but as you can see, we still were at around.
06:05:38 I don't know 80% closed.
06:05:43 We still have looks like 13 issues in various stages of completion.
06:05:54 One of the things that I wanted to point out that seems to be a little bit of a struggle and Matt is
06:06:05 just the, the jury issues that are high and highest priority.
06:06:18 So right now we have 15 issues assigned to
06:06:26 the Jakarta release that are bugs that are higher highest.
06:06:34 And this seems to be something that is has been an issue there been a number of
06:06:44 requests for exceptions and pushing issues out to the, the next release and so on. So, that's one area that I've noticed that has been a bit of a struggle.
06:06:59 But, in general. My feeling is that we're still not quite there, there's still more work to do.
06:07:09 So the question is, you know, how do we want to manage that, you know, the most obvious thing would be to push out another week, and I'm afraid that would mean pushing out the entire schedule again, another week,
06:07:28 particularly with him for falling, so closely after him three.
06:07:36 It would be difficult to, you know, just move him three so I think we're looking at pushing the entire schedule out.
06:07:47 Any thoughts, comments.
06:07:52 Maybe there is another way to look at it. Just wanted to confirm so the remaining task are really affiliated only to is it you know not only but that that was one of the predominant issues.
06:08:11 The other one was related to
06:08:15 global requirements. But, For example, you can see
06:08:21 these to open issues are both resolving high end highest priority.
06:08:30 Let's take a look at the.
06:08:43 And here we have a couple more that are high in highest priority jury shoes but then we also have a few that are resolving global requirements.
06:08:55 Okay, it's a mix of global equipment, and high highs. So, question of photo is when you were sharing the list.
06:09:05 Some of them are not relevant because I could see that some projects are not part of the ladies like the universe Nikki.
06:09:14 Some are related to due to the team so I believe that these might be fixed when we do the milestone for, or maybe, I don't know if maybe this is issue the team was racing against themselves does something I don't know.
06:09:33 So, we should ask the team the project team and their reports of to see if these are really necessary Cody skinnies I see a hobo despite on to that seven but it could be duplicated with some global requirements requested by the security team.
06:09:54 about it's a testing framework. Do we really need to do it. Now, or can we keep going and make progress during the release so that's the type of thing that I'm looking at, it's the Indonesian team the OMD gets my honor way.
06:10:25 winner. Because of the GPS. So, so, same for the map. So we really need to do some coalition see ally is not part of the release as an example. So, we need to do is it to list of not based on what I've just said.
06:10:34 So that's one item know for the global requirement, which is not met, called a team could not met the the haze or Weaver, is it accepted by the security community should committee.
06:10:50 And that's how we would progress. So consider that in the case where pts have submitted
06:11:02 issues as you know they're either in this submitted or delivered status, those are cases where exceptions, have been requested.
06:11:14 But in these other cases that we looked at earlier. No exceptions have been requested.
06:11:21 Okay, so that's maybe the next items. So, if we pass the 80%, considering there are a lot of issue, associated Indonesian OMTO might be clearer or not, or postpone.
06:11:40 We might decide to put an exception that the team.
06:11:44 Complete the remaining does as part of their mind soon for.
06:11:49 Would it be possible or not.
06:11:55 Well, the problem is is that the, that project teams will be building the containers and so that fixing those issues will delay that.
06:12:13 And
06:12:13 as we've seen in the past that requires you know significant amount of time and so I'm just concerned that will fall into the same problem that we've we've seen before where we arrive at em for, and the containers aren't available.
06:12:33 And that's why we added them for to begin with. So if we, if we make that the due date for these issues than that, just ends up pushing out and for anyway.
06:12:47 But when you look at the nature of the issue.
06:12:50 The integration team does not need to build any doctor. The problem that has been Hayes is more related to the automation testing framework. So it's up to them to decide, do they do it now or later.
06:13:05 So there are at least two three issue associated to that based on what I've seen Seelye University Dickie.
06:13:12 The, have a look participating to do healings. So it means that this ticket by default, are shifting to the cornfields. Now, we have you empty the have a couple of tickets.
06:13:30 Right. Their objective is to do something at the end for now we know the challenge that we have with your team. We need to ask her to survive, and to the other team member or whoever, this this ticket, are really relevant for this release, or can we postpone.
06:13:45 So if you eliminate ci integration.
06:14:03 Right. Same for the Movie Club, they can decide to raise a waiver by Monday because these are complex six if they didn't start at the f1, they will not make it until the next two months.
06:14:16 And I don't think we want to delay, another two months the headings.
06:14:20 So, what there's, you have the end I write the end I I like LVF modern design later sure I'm not exactly sure what it is, but it's an issue which has been raised last week, so that we could have an exception for this to get something up for the D my up
06:14:41 close keeping an issue in our defense on our club.
06:14:45 Okay. That's so nice clothes issue.
06:14:49 The my again I that's that's the one I don't know we need to look at your car. Can you do it by me or not. It's an issue it's not, it's not an issue related to the container.
06:15:02 So, no impact on the info.
06:15:07 Sorry, just on the to to to buy tickets I'm just waiting, awaiting reply from either me or, or Tony on 1624 and then 1500, I think, Alex is is Morgan has assigned italics to look at the project PLV three.
06:15:35 So be great if you get it get a response on 1624, so we can close
06:15:32 it. So that's great feedback. Thank you so much.
06:15:37 I'm so then the only one left. It's a or b D or F is etc access fail. Well that's, that's something they need to change. That's something assigned to see Vander on team.
06:15:54 Yeah, this is a bank.
06:15:57 I raised, and I think that I don't know whether we can fix that there is a workaround for that so.
06:16:11 But, yeah, this is maybe has is related to some external that stuff we have to check. So, we are trying to fix that from Tech move on from dodgy telecom point of view, because we have to thank you so much so.
06:16:23 So honestly David, when you really look at the nature of the issue. Some of them will never be fixed, you can give five the studies, one months, it's too complicated.
06:16:36 If you don't start at the beginning of the series. Some of them, it's, I'm pretty sure our issue raised by the dimension to improve themselves. So again it's up to them to decide if they can make it or not.
06:16:51 So, looking really at the issue, and anybody on this call can challenge me, or even the Peter can see I'm wrong.
06:16:59 I mean, delaying another week will not enough, right. So, or maybe some of the items are important, but not critical anymore.
06:17:10 So I maintain the fact that my request would be that we proceed with the team, with the exception that the project team of the view their current status and take a decision.
06:17:33 They open a weaver, especially for those up or three, because that's not a one day job, they wave a weaver the move to co op, and then they move to the next series, but something needs to happen that all the project team review and tell us what they can
06:17:45 do.
06:17:47 If it is a two days job, they might be able to do it. If it is a two weeks job, no point to try to fix because we need to start to stabilize the release, at this stage.
06:18:02 So anybody else wants to tackle this differently or ever another ID is the moment to raise it here.
06:18:11 I can't agree with your ization cotton based on previous experience I think of products are still working on.
06:18:17 So perhaps it's a battle but we can take it as a parallel work where people are working on it, and other projects may be can be removed from there to just see where we are.
06:18:25 The current pie chart which David was showing was interesting all the projects are during procedure like we enough is tricky and other protocols. No.
06:18:36 Doesn't Sorry, I then I think we can just see that, where we are standing with respect to this and we can take it as a public with that should be fine and just,
06:18:49 just to rectify what he said. So David, you are right in the pie chart, there is no see alive universe decay. But in the query, you play to share with us the remaining is these two project was to attack.
06:19:05 I think that's what say she wanted to.
06:19:09 Yes. Yeah, yeah I'm aware of that.
06:19:12 Okay. So, if the TLC is okay, we tend to say we go for what was empty, with a condition that the project team, including the special project like integration and no one, it's up to them to the side, if they can do it or not, and complete by end for the
06:19:35 cannot.
06:19:36 I don't need equipment with a weaver because second need to be aware if it is not a security issue if it is not a license issue, then the document, because it takes two three weeks whatever the one that they will not be able to meet by info.
06:19:54 And if we can already have a vision of that on Monday. If each project team can walk to the end to mobile panel today in anymore because in China, it's already quite late, but I would say, if people can work to mobile accepting these lions and Monday
06:20:16 before a BTR call. Then we have already of you who have been clean up and express the fact that the the will move the issue. So usually I agree with never shift the is an evil and I, but when I look at the type of concern, either there is a workaround
06:20:34 or either it's not so critical.
06:20:37 When I'm only deriving my life of view, based on what I read here, I can be wrong into detail.
06:20:46 So we moved to July with the movie and I was lucky. The GPS, three people need to open a weaver. The om and the integration team need to discuss together because I think they were opening tickets for improving themselves.
06:21:02 Right.
06:21:03 If I'm wrong I'm wrong, and if there is a workaround. It's even better.
06:21:08 And then for the other issue document, please. That would be nice. But I think we should always be the exception and move forward.
06:21:21 I would also agree with you completely. I also have seen that.
06:21:26 I think I have missed here my too close for example one one ticket so and and these kind of things I mean we have not gone through the tickets in the last.
06:21:37 In the last meetings in om so I think I will check it but actually you're really right so integration and om is in these cases are mostly.
06:21:49 Let's say improvement items which are not relevant for the content and for the stability of the content. Definitely.
06:22:01 Any additional feedback and we proceed, we approve the milestone three, we don't change the schedule, we ask the teacher to clean up as an exception for the until the end for.
06:22:21 This is actually just about this manifests because 755, could you scroll back up to the top please David.
06:22:29 Don't know why this is assigned to me, I can't fix it.
06:22:38 At least I don't think I can, I mean,
06:22:43 come on, maybe you ever.
06:22:47 You know I could try.
06:22:50 I'm not sure who would be assigned to know I know what it is assigned to me, because I remember in his issue.
06:22:59 The VNFSDKVS agent is.
06:23:04 It was removed what's in it, a move. and I see so this should be.
06:23:08 This was, it was if the NFL SDK best agent was removed, then we should close this out, it doesn't need to be. Yes, it'll never released be released again.
06:23:16 Yeah, exactly. And so that's why I think it's potentially me who are assigned to you received, and to ask you have to need to close it.
06:23:32 If I mean you can do it. Now you can certainly do.
06:23:35 So you say you can Yes, I can. Thank you so much.
06:23:38 All I go look at that. Oh I love
06:23:42 to Tony because on that week I think Tony was on holiday, and then I never check again right so sorry Tony, if I, over, over, go on you I don't know what to say in English.
06:23:55 So anyway, let's clean up of line, because I think we have a lot of topics that we want to discuss today. And he beat myself up if you okay David, does the TSP approved the milestone three, with the exception that the remaining task is complete by m four,
06:24:17 and especially asking PTO to clean up the remaining issue, either. Weaver for the GPA, that everything that I've said no, I don't know if we need to eat all the exception.
06:24:29 But I think we need to proceed. Except David if you have a big big big concern that I'm completely by.
06:24:38 No, that's fine if the if the TASC is behind that proposal that that's fine with me, and I'll help drive that.
06:24:48 Excellent. So, do we need to do something is everybody agreed we need to do a fork my road to put a list together of the accepted tasks.
06:25:07 Yeah, we should probably have this as a vote since there are exceptions that are being requested.
06:25:14 So if you know that can be dropped into either slack or chat so I can compose the vote.
06:25:22 And then I'll put it forward. I don't think we need to wait for that for the meeting.
06:25:27 Okay okay so let's let's finalize that offline because I'm a little bit concerned we have significant topics that people who attention to the as usual.
06:25:44 The only thing that I will ask you, David and my apologize because I don't lead. Is there a quick update about the maintenance is stumbled because I will look at the weekly day, and I don't recall, where we are with a stumbling stone.
06:25:58 But,
06:26:06 yeah, please just take a quick look at that. so the simple maintenance release section control confirmed I think it was last week or the week before that all instances of lot for j were removed.
06:26:13 And also, As of, when I wrote this yesterday.
06:26:19 All the remaining issues that were related to release notes, had been closed. Also, but then late in the day I got a email from Pavel that he had opened up several more new issues against the main that's release related to release notes I believe so.
06:26:43 So we're still, we're still trying to close the maintenance release.
06:27:08 Okay, yes they do confirm. It's just for the transitive dependencies to ensure that each project that is impacted by look for the transitive dependency provides small sentences in its release notes, and it was discussed on Tuesday with.
06:27:17 And with Thomas and at the second.
06:27:11 So this is like a joint initiative with the documentation in.
06:27:20 Okay, So I'm glad that this is just right.
06:27:24 It is just the remaining activities. I'm glad is that so I don't know if we have too much on the call, but it's feel that we are reaching the bottom of everything right.
06:27:36 Somehow, I think what is at the moment missing is attack for 901 on the om project.
06:27:45 Oh, ok.
06:27:51 So we only have a tech for 900 but not for 901. So whenever someone tries to install explicitly 901. I mean, at the moment he can only take the latest installation from Istanbul but not a specific 901 so this has to be I think
06:28:10 this was done by, by.
06:28:13 Release Management, right.
06:28:16 So, lunch is needed.
06:28:21 We'll have to check that.
06:28:24 This is the list of new issues that I'm showing right now.
06:28:50 Yes, for sure. Not that not affecting at all, just these release notes accordingly.
06:29:06 particular comment on the map on 715.
06:29:09 Simon thanks.
06:29:10 Yeah, Yeah, I will give you the comment. Sure.
06:29:13 Good.
06:29:26 All right. We'll keep going you know we can create a next week.
06:29:32 Hopefully.
06:29:34 Alright, so I'll wait to work with Kenny to put the vote text together document and all of the exceptions, and the only other thing I wanted to mention is that TLC approved the creation of a new release management repo to three weeks ago.
06:29:56 And I just want to mention that I had submitted a carer view for the creation of that repo so that's in process.
06:30:12 All right, I think that's it for me Kenny.
06:30:18 Okay.
06:30:26 going back into sharing land.
06:30:29 Do we have anything from railings or for real Inge.
06:30:44 Okay, quick update on the UNH lab
06:30:50 McHale I don't know if you're on the call I saw your mail this morning, haven't had a chance to respond to it but I will.
06:31:02 But I, if you have questions about the UNH lab.
06:31:11 I got information here.
06:31:15 I'll drop that link into the
06:31:20 chat window for everyone and link it into the minutes
06:31:28 for people to look at.
06:31:32 And so that we can try and try and get things rolling their Intel would like to get the existing lab shut off as quickly as possible so I will link that in here.
06:31:56 That's it, then I guess for bellinge or infrastructure.
06:32:04 I guess in Kenny, I know that maybe Michael excellent question concerning the internet. Will you follow up offline.
06:32:13 Yeah, that was the mail I was referring to. Okay, okay, okay, so I connect the dots now.
06:32:21 And I'm really sorry that.
06:32:23 So, yeah, I'll do that.
06:32:26 short answer is yes it's online unreachable.
06:32:30 Getting the account setup for the VPN and all of that is what's, what's necessary.
06:32:38 Anyway, so if there is nothing else there I do know that will need to revisit the thoughts around migration to get lab at some point in the near future, but not for today.
06:33:00 Okay enterprise Task Force.
06:33:06 Alright, so next week as you know we have the elephant EDF, I'm one of the topics where the owner community will participate it's a topic about gardening grounding aligning the ownership and the code together.
06:33:22 So, in order to prepare this presentation.
06:33:27 I've been working with some of you, I need you guys and I'm also engaging. Being young because being is a multi cloud pts.
06:33:38 And we have not yet finalized the presentation so that might not be the final presentation that will be presenting next week, but the proposed was really to focus between the two communities to, I like to find that we are complementary to each other.
06:33:57 We may act independently. So meaning by that we can ever configuration where we don't have on up, or we don't have em Co.
06:34:09 With these will be exception. When we think about the fiery supermarket, moving. So the willingness with the MMO community is really to build our stay a story where we demonstrate that we can complement so maybe can if you don't mind, you can click on
06:34:24 the presentation I can go quickly.
06:34:27 And then we have welcoming any feedback. Right.
06:34:31 We have not yet received all the input from mq. So this presentation was share on different meeting. So that's the meeting where if you are interested, there are the recording of all the meeting.
06:34:45 And if you go back Kenny, you click on the PDF, I hope. Okay, great. I was concerned that we will have a cryptic. This is a presentation where we are where we are thinking about production ecosystem, right, a petition ecosystem meaning by that you need
06:35:03 to scale, of course, it's not a prototype anymore. It's something which will fly.
06:35:09 The first slide to present the different open source community that have been created under the lF networking. The meeting on Tuesday, in particular, will also be discussion with no kids.
06:35:27 In addition to what what what ma do not align. Right. And in desire grind and we're trying to live with them the difficulty and their high level home.
06:35:32 Just a note, or do em co initially was also called Smart edge management. The name my change in demo key function, because it's also the product of one company as well.
06:35:53 So that's the overall ecosystem, we, if we combine all the NF networking project at different levels.
06:36:03 So moving to the seven slides.
06:36:06 So moving to the seven slides, the ID twin to highlight how they can, they can complement each other was first to do an exercise where the M cook team and the team is our writing the key capabilities.
06:36:22 And also, in the context of ferocious you play a blueprint, what will be of added value. Ok. So again, this slide have been built based on what we knew about tempo to finally input from the team.
06:36:36 I hope it will be shared with us later today. I think there is a meeting at 1pm PST if some people are interested to join.
06:36:48 Feel free to drop an email to David Kenny myself, and we will add you to the discussion as well, but I wanted to share what it is ongoing so you are not surprised.
06:37:00 And again, the story is not frozen in the stone. If something which is written there is not what you think it should be.
06:37:12 There is space for changes. Any times, and the proposal of the Tuesday call will be also to share to the audience as well.
06:37:23 So, the next slide, it's one it's tough to becoming a Boston, it's a kickoff it's not finalized. It's where we try to I like om CO and owner can complement each other.
06:37:37 One area of complementarity is really related to the fact that, because I'm cool is somehow our edge manager of focusing on the edge, and only focusing on communities workload.
06:37:51 We might decide to convert what we did at in the multi cloud in the living project. What was formerly called own app for Ks.
06:38:04 I don't know if we have kept the name.
06:38:06 And that's why I wanted to be sure that Ben is comfortable with anything we are discussing.
06:38:13 Because if we convert.
06:38:15 We might take more feature from the MMO, and he plays what we have been doing with own app for Ks when Im coo is at the same level as well.
06:38:27 The other area of convergence was also, when we speak about enables product to operation.
06:38:35 Em co might be able to offer to configure some content new highs application in conjunction with our own up CDs controller design studio and is.
06:38:48 And again, exactly like we have been doing today. When we use your nap Kf login and and that's why that's what we try to Twilight, then we try to highlight the fact that own up is not only about the beauty of him it's not only about the service orchestrator.
06:39:08 There are other capabilities like the onboarding, or we can also play. If we go back to the time we need to go back now but if you look later on the first slide, you could see that I was putting me in a box and then you have all the controller.
06:39:25 Because, the idea was that at one point all that could play the whole of a super administrator or an end to end orchestrator whatever you call it, so we don't need orchestrates so much that we know we are already orchestrating some aspect of magma, that's
06:39:43 the purpose of the fire super blueprint.
06:39:49 We don't have any things again being done, please don't take public today. But if you talk to them to money, I'm sure that you will be able to tell you what is doing with Open Daylight, and so on and so on.
06:40:00 So, just to give you an overview can be the centralized active inventory for net office also, it's, it's a list which is not exhaustive, but it's a starting point for the description.
06:40:11 And then when we move to the next slide I try to accelerate. Again, I want to thanks for all the support. You might recognize the diagram that we use when we speak about the CF orchestrator.
06:40:25 The only thing we did was to integrate the Kubernetes blogging about the MMO. I'm sure that info can potentially provide additional information like KPI that they collect from the different edge, or even from the private club where later on own app can
06:40:44 take some action from an automation or cook for Lou perspective, the ID, was that we face different integration. The first one will be MnO nap start from an integration perspective, with the focus on the service orchestrator, and the onboarding aspect.
06:41:04 Then we move on face to where we extend the owner project to not only so as DC, but we also have the centralized inventory with ANSI. We have also the CVS for the D to operation, and we have the DMC for the controller.
06:41:24 And then moving to the next slide and then I will give you the floor for questions feedback.
06:41:42 The another phase would be indeed one of the strengths of grown up it's not only the gas station of the network, but also the fact that we can have discovered for loop mechanism which which is the premises before we start to speak about aim and at the
06:41:46 end. But the control to be something. Anyway, which is already offered by the platform, we can bring it, bring some Service Assurance capabilities on top of the platform and I think Steve two slides, or one slide.
06:42:02 The next slide is about the fact, which is probably my last one. The next slide is probably.
06:42:09 We don't want to end on the five complex use case because originally these two is a frozen up a blueprint at one point we want to control drones and assure that one Dawn's that we can pull via via WiFi via 3g 4g whatever system that we put in place will
06:42:36 not be intercepted by somebody else so that's why, as part of the enterprise Task Force, there is given me some work to integrate with several others, which will give the security aspect of a little slice.
06:42:50 So, we were trying to define some use case, easy to do. Not really.
06:42:57 Where we need to buy your own way we need to buy a lot of equipment. So we were thinking about a use case just, you have a trailer, you upload it in the private cloud.
06:43:09 And you also uploading the private edge, and you measure the trader experience so it's a focus on the bandwidth. The next one, it can be a gaming experience you upload the top the latest on high during the private cloud.
06:43:23 And you can also upload it into private edge just is not new skills.
06:43:29 We understand with these are easy use case that you can demonstrate how we can complement each other, and how we can start to do some integration. So we are not doing anything nation from a legal building blocks.
06:43:42 We are trying to have some use case to demonstrate the fact that we can complement each other. And the last one is something which was getting inspired from Walmart, which is to consider a stock inventory.
06:44:01 And finally I start to collect some question that they've received from some of you.
06:44:07 And when I have the answer is stuff to it.
06:44:10 So that's the end of my presentation so I know I've been speaking a lot.
06:44:15 Again, I have been myself. The objective is to focus on the alignment and not on the exception of this case to demonstrate that we can complement each other and and and avoid the overlap, as much as we can.
06:44:30 Any question, or feedback from anybody.
06:44:36 And you guess you want to add anything as well.
06:44:40 So we figured somebody cuts in this great Actually, I'm sorry I was off late, little busy and I mean I'm having a conflict with extremely close to the same time so I'm not able to make enough Task Force.
06:44:55 But on the other hand I'm actually working on the internal to see, I think I even discuss this about last week old school with him cointegration.
06:45:03 The intention was actually to have a PLC done first and then showcase it to senior class goes to the direct sales are coming back so I'm expecting that by then I'll be ready with that so that I can showcase it to you with the complete API's and the flows,
06:45:18 which are which are designed in that from your presentation I can say that the first slide part of it the instrumentation part were there so I'm going to creation, along with the basic management or LCM part of the CNS which are brought up by is what's
06:45:31 my target right now.
06:45:33 I'm glad to say that we have started with the basics of it with a virtual firewall itself, because there's a use case which is Dave in both the both these things.
06:45:41 Also we have internal to see face recognition app.
06:45:44 Again in line to what you said, h based app. Because employee small looking at educators part.
06:45:50 So, this is what is our target right now.
06:45:54 If time permits again I'm sorry, I'm not able to accomplish enough task force with to contract but if there is some chance or something I'll first try to surely come there and present my idea.
06:46:03 Perhaps that will also leverage it. In fact, to put it the other way. CFO has been my baby has been acquainted with the economy and he started his activity.
06:46:12 So I want to take you to the next level where we also want to have autonomous or intangible orchestration Sedona.
06:46:19 So this is something which I'm driving from So this year, every year we have one per agenda the 2020 agenda for 2021 was to have optimization in the, in the way so works and you can see after that.
06:46:30 So is no more the blocker right in normal blocker for the releases clinic clinic clinic who are my target is for having intention orchestration.
06:46:39 And with that employs also in the plan of integration. So this is my current work which I'm doing internally, but surely I'll get back to you with details when I get when I get a chance to catch me.
06:47:04 Thank you say shoot to share what you are doing with XVG will not. I hope that you also understand that the ecosystem is, it is not an exterior. I want to correct Catherine because I was saying that he's I have a conflict with extremely low.
06:47:07 So I'm not able to make the CFO Task Force meeting actually what I'm doing.
06:47:18 Yes, yes, yes.
06:47:20 Okay.
06:47:21 Yes So and I want to seize the opportunity to sing.
06:47:36 I tried to be the voice, but they are also the master on the domain.
06:47:43 I don't know, honey, Lucas, are being you want to add anything so far.
06:47:47 Just a question to Sasha, will you be able to join the workshop next week, joint or is it again and I lost track so when is it actually when is the workshop, I should live I mean I'd be more interested to join us shortly.
06:48:18 about tempo is on Tuesday at 5am Pacific I don't know how it translates to India time.
06:48:10 Okay, I'll actually try to be there, Ron.
06:48:15 I'll try to. And perhaps if it's possible to catch up because Monday is pretty short I know if it's possible to catch up.
06:48:22 Me and location us in touch so perhaps I can grab two things from a crash and also go to the recordings which I've done before.
06:48:34 I can also find my two cents on the, on the slides, which are already available, perhaps that autism is something which I can do I mean when it sure so so yes if you look at the link.
06:48:41 The link. The link is wrong for some reason so I'm going to drop the the correct one. I'm not sure why,
06:48:52 but here it is.
06:48:58 There we go.
06:49:12 Sure right I'll be deaf.
06:49:05 I can, if it's Monday and Tuesday I'll try to choose when I have a conflict, but I'll try to skip the exhibit a call this week, and I'll be surely trying to come to this meeting.
06:49:15 I'll take it on bread.
06:49:18 Oh, Catherine was a shocker, I'm a common.
06:49:22 I noticed on the, on the questions on the last slide, is about.
06:49:28 How does this all alignment, or run, or to interface.
06:49:33 So it's not clear from, from the, from the on the other slides exactly how it plays out and.
06:50:05 And it shows non real time Rick and SM Oh, so that's those are very much around concepts.
06:49:56 And the other question is how much of em CO is with the last slide has a question right. How does mq integrate with Orion Oh cloud though to interface.
06:50:03 So, if this is about alignment, then we're talking about
06:50:12 orchestration and control of cloud resources and in Oregon. All that is bundled into this auto interface. So I'm just saying that question in green is is very valid and that should be clarified, and the related question is how much of em CO is is not
06:50:32 just Orion networks.
06:50:36 Because, so, so that's good question as well and again I didn't know the answer or give this question. I know he smoked a 30 link to do nap alignment, all those hormonal component after you all as part of your organism.
06:50:53 So, I'm capturing what people say, if you have question, maybe shrunk I would you mind to put in the chat, and I will complement the slide as well.
06:51:04 Or you can you can.
06:51:07 If you have question later. You can have up to the end, or whatever, but I don't want to lose track of any question because more clarity we have better it is.
06:51:19 Okay. All right, my employees.
06:51:21 Currently, are in discussing all cloud interface I think the current discussion is a cloud basis. So to DMS that's one of the things they are still under discussion, but if they decide this client base.
06:51:51 to follow that interface. I think that's the input so I think the currently the CFO when they talk multi cloud coupon a plug in plug in, when they talking to the component, if you consider that as a cloud and they have to conform to the interfaces, which
06:51:54 which currently I think you know coordinate based, but we need to get confirmation. Anyway, thanks. That's my input.
06:52:03 So just to clarify, what you're saying is, depending on what what cloud implementation choices are made for all cloud, there is a there needs to be particular alignment.
06:52:19 I see no crowd they're defining some interface, there are no spy interfaces so I think they're one of them is coconut based. Okay, native cloud native so that's, in that case, whenever they need to talk into our co crowd on the Oregon architecture, they
06:52:34 have to confirm their interfaces. So we for this discussion we may need to contact a working group of six or 10. In olden days, I participant. Yeah, I participate in there they discuss about that.
06:52:47 There's one of these or two DMS that's interface and they made auto dm is dash k eight, which is covenant based. Anyway, that's my input, anyway.
06:52:56 Okay, thanks.
06:53:01 Catherine, this is soccer so I heard you mentioning the,
06:53:07 The 5g Super blueprint.
06:53:10 I think what would be helpful
06:53:14 is to try to collectively understand where the new orchestration platform
06:53:26 sits within the.
06:53:29 All of the lF edge
06:53:32 projects or ran own app.
06:53:38 And account in the rest of the infrastructure components.
06:53:48 Yes, so so for example, for example, sorry, for example, would we be able to plug the many of the projects, if
06:54:05 Zephyr open horizon so on so forth into the MMO infrastructure, so that they all behave the behavior is common across all these components or projects, even though they're, they're totally individual projects that, you know, support.
06:54:28 Totally different functionalities within the cloud infrastructure, but I think that connection or that relationship needs to be defined and well understood, so that we know the role that mo is going to play between the master orchestration which is own
06:54:53 app, and the cloud orchestration slash overran support if you will.
06:54:55 And the bigger picture of the 5g Super blueprint.
06:55:05 So these are really varied feedback chakra, and again we are to be no of the Jordan where we we try to indeed in on the foot hole and school for each of the open source community.
06:55:22 The idea was to have some material to to reflect on the elephant def.
06:55:30 I will continue to add them, your question as well. But if you are available on Tuesday, that's really the place where we will consume the material and again it's not the final election because, as you can see, there is still a lot of material to be provided
06:55:47 by the eight core team.
06:55:49 But that's the place where we discussing need all the ecosystem, but terms of major focus that on em coin on up for the moment, but you're coming. All right, we need to have the complete story.
06:56:02 So that's why the first slide was okay, what's the complete story behind the fact that we, we have so many communities, how we can build use case where all the different open source community I engage.
06:56:18 Absolutely. We have a story to kind of try and shark I think I understand where you're coming from and I kind of share your desire to see a big picture on the other hand, remember it's open source and there are many different use cases so what we're seeing,
06:56:34 even within the scope of the offense.
06:56:39 There are different ways to build the 5g Super blueprint maybe more than one, and maybe there is not one solution that fits all. So it's, let's let's treat what you just suggested and as a reference integration it's not the only way, what, what I'm learning
06:56:57 is that people come up with more creative ways to integrate our projects so we need to welcome all these initiatives and not be too prescriptive because that would be too limiting.
06:57:11 That's it. Absolutely, absolutely. and, and my comments the comments I just made.
06:57:17 We're not meant to be the only approach.
06:57:23 And the reason I made them is because I sit on the edge tack as well.
06:57:29 And I hear the discussion that is going door and going on there and they have a left edge has some unique and very interesting, interesting projects. Right.
06:57:40 California has some unique and very interesting, interesting projects. Right. The. So, as I listened to the presentations I'm trying to figure out how to bridge.
06:57:48 All these projects that are cloud based. Sorry, they are edge based into a core own app orchestration blended with a.
06:58:01 The new edge orchestration platform.
06:58:08 So, So it's an interesting story. And to your point right there is no, I don't think there is only one answer.
06:58:17 I think there, there has to be an overall approach that says, I have all these pieces that are somewhat unrelated but yet you know they we could come up with the use case that can use all these pieces together and tie them all together in such a way where
06:58:37 it becomes a very very interesting use case or an interesting business solution shocker this is this is Heather and, and these are all great points yeah these are you know we've touched on some of them in the context of 5g Super blueprint as Catherine
06:58:54 mentioned, you know we've been trying to get a lot of the basics of, you know, a, a, an infrastructure platform, a core of ran and into sort of physical radio, so that we have a functional 5g sort of network, and then we've also been focused on some of
06:59:17 these architectural issues with respect to and CO and, oh nap, mostly because we feel as though we need to get these somewhat in place, but we really do welcome the edge communities in the 5g Super blueprint I think right now they might find a few of
06:59:36 the very sort of core and ran and orchestration discussions, maybe, I don't know, a little not not boring but you know what I mean like not quite their wheelhouse but I did go and address the lF edge tack.
06:59:54 At some point last year. But we haven't really followed up but you know I think as we're getting to this place of, you know, getting some of these pieces, a little bit more settled than I think we really do sooner rather than later, you know, as you mentioned
07:00:07 some of the projects like like horizon, you know, if we're talking orchestration alignment, probably we do want to start thinking about horizon and its
07:00:22 role in you know oh nap in a own up and in CO sort of created worlds also one of the use cases that we know we've been asked for from at least a few service providers or end users, not necessarily telecom operators, is the sort of the interconnect between
07:00:43 the sort of, you know, Internet, and local industrial IoT and we really haven't made a ton of progress there. To be honest, it's on the things that look really cool and have shown up on the slides, but haven't had any real technical attention paid to
07:01:01 them. So agreement.
07:01:04 Yeah, probably that and that probably we don't need to have all the pieces in place to maybe start some of those architecture discussions, so if you want to ping Lj Lucy I don't know if you know him he's one of our community architects here he you know
07:01:22 he's on the team with Kenny, and he is providing the main program management support for 5g Super blueprint and myself, and just talk about how to get some of those conversations now going in active form, so it's a little bit, you know, also.
07:01:40 Yeah, but those let's take it offline but I think it's important to continue to create these connection points you know amongst own up in code, and a kit.
07:01:52 You know, overran various CNS vendors and then you know getting more and more of the edge players involved with us. So that's good point I'll reach out to you offline.
07:02:02 Okay, Cool. Thank you.
07:02:04 Thank you.
07:02:05 Yeah, yeah and Randy or Catherine or anyone else here who who does a lot of five do super blueprint stuff do you have anything to add to that last comment.
07:02:16 No, I mean, it's, it's, you only thing is I think we need to the internet is good, right to try to have this story across all the open source communities, demonstrating that all of them complement, but we need to demonstrate by use case.
07:02:37 I understand a lot of work is done today to integrate the different Lego blocks, which is a first step from a deployment perspective. But if we don't have concrete use case any does not need to be immediately flushing.
07:02:53 It needs to be the right things to demonstrate to highlight the capabilities of all of these open source together, then, then we can build on top of that.
07:03:04 So, so that's why it's important to have concrete requirements so each open source community knows exactly what they have to do or support and these type of things but it's a great project, but it's rely on the willingness of the different communities,
07:03:20 but there is a bright future. On the enterprise market.
07:03:30 Okay.
07:03:32 So, we will continue to collect feedback, and I will continue to update as well but honestly if you're interested. Join us on March 15, and thank you again to Lucas honey, and also to been with been helping to build this presentation.
07:03:49 Now, just want to celebrate a little bit, I will not speak about sub own up today because we are running out of time. Just want to celebrate a little bit, Joseph who has been promoted as of new cc SDK kilometers, so that's great.
07:04:08 We continue to go the Honor Code community for this project.
07:04:14 And then, let's move to Saigon in Boston topic about his shirt because of it is is also important.
07:04:23 Something that we have been discussing intensively over a couple of weeks but it's not a new topics because the story starts in September, which is the introduction of the ASD modeling.
07:04:38 I will try to make a summary of where we are.
07:04:43 I still believe there is a path to move forward together, I stick invincible that, too. I have been, they have to pass that I've tried to document here.
07:04:54 One was the fact that we move with what we know today. This is what I call the vision one, we need to have the clean state of what we have today, based on the Quran is associated to the as the mother and again, if I speak something which is not pure technical.
07:05:13 You are free to correct my words. And then we continue the dialogue regarding the modeling concern as what we call the V to the signal the way that I want to suggest because I had only one way so far as the goal knowing that I want to suggest because
07:05:30 A single knowing that I want to suggest because honestly Zoo did a great job.
07:05:35 This week trying to learn about the model and trying to make a muffin, that he has. He is about to propose to do I like the fact that we are not so far with the own uploading that we have in place today.
07:05:51 They are not so much to do, to align the IM and to make it as the modern. And then I would like to extend when you will see his presentation in particular the slide seven, we can continue to proceed and potentially math as preliminary classes are using
07:06:09 the right technique and word because I've been advised to highlight what the fear from the godmother and to move forward, but the sickness. I think there is an agreement we all want to move forward with the major question is about clean state in my Dennis,
07:06:26 how can we get the clean state, either option one, or either option to. And to be fair, I want to give the floor to glue, who make an attempt to do the mapping, which was the next step to have formerly the clean state.
07:06:44 And let's see, this step can maybe ally all of us.
07:06:47 If not, let's discuss about that so you are you still with us today.
07:06:56 Yes, that's right.
07:06:59 So maybe Can you can launch the presentation,
07:07:15 please. upload PDFs.
07:07:18 Oh, it's my but it's my bad. I didn't know I didn't do it
07:07:27 next time, here are.
07:07:41 Here, or what okay well that's not gonna work.
07:07:47 Hang on, sorry. It could see the presentation. Okay. So, yeah, we're just we're we're, we're just going to go with that.
07:07:58 Okay.
07:08:00 Okay.
07:08:02 First thanks Kenny him Catherine on tight beginning begin
07:08:07 to before I introduce the actual proposal Let me briefly introduce why we have a conflict here, and it's important to know this concept of information model, and what's the difference with state in the model here.
07:08:22 So I take a reference from the artsy 3444 here, which the title is actually a difference between information models and data models.
07:08:32 And what I want to highlight here is. First, the information model is to model the objects as at a conceptual level, or we can say that information model is to use to describe some concepts.
07:08:47 And it's independent of any specific implementations or protocols, or if you see the right figure.
07:08:56 We can interpret it as another way that one information model can be implemented in different ways, or in different data models.
07:09:07 As for the scene as an example could be.
07:09:10 We will have one information model for the steam neath, the concept, but we can implement it in different forms like pure work bananas, yellow, or a pure ham talked, or a combination of this, or like pure Toscana template or, like, what as DNC way is
07:09:34 proposing a postcard combined with hashtags, so they are all different ways of implementation, but for the information model we will only have one concept that the seat that is this enough.
07:09:47 So, on the other hand, the data model is used to describe the implementation specific protocol specific details. So for the data models, it will be.
07:10:05 When you really how to implement it, it will include all those details so like if you like. Now we have one postcard was charged and some information may be included in Tosca model, while the others will be needing to help Trump's.
07:10:14 So there's some basic differences between information modern data model.
07:10:19 Next slide please. Any.
07:10:26 And then, I want to highlight by we have a conflict, and why we suggest this way.
07:10:32 So according to what I just said, when we designing an information model.
07:10:38 We should hide all protocol and implementation details, and actually also written in the RFC there.
07:10:45 So, based on that we shouldn't expect certain, certain information from the information model, simply because it's implemented in like Kubernetes native for home charts and.
07:10:59 So, Imagine that case.
07:11:01 If some day later, the native have charged covered all the information we have doesn't mean that we don't need any information model here in our own app to describe this enough.
07:11:14 I don't think that's the case. So, now, here I want to emphasize that information model and data models of different purposes of information model we need to capture the concept, while the data model is to capture where the information should be implemented
07:11:33 in different protocols and actually having, like, different models for different implementations may lead to some modeling problems like first one.
07:11:47 It means we need to create multiple information models of the same object here like for the scene as we need to have different models for the same object.
07:11:56 And the only differences is
07:11:59 from the different implementations, maybe some information is in Toscana some information you see in Charleston we just use different models, or in other ways, if people think ym impatient would not need certain information we will have high that in a
07:12:18 corresponding information model.
07:12:20 But actually, those different models are trying to describe the same thing. The cnet's.
07:12:28 And the second one is inflammation model would have thrown dependency on the Indian patients, which means, whenever we have changed into implementation we need to change our information model as well.
07:12:39 And the third one is, is it will be confusing for the designers and operators.
07:12:45 These are the target audience of the information model.
07:12:48 Well, the CO developer sort of target audience of the data model.
07:12:53 So, the audience of the information model is when writing this information model is trying to learn what is the concept. So, take seen FNC, as an example, when he or she rates, the information model.
07:13:09 He wants to know, what does it mean in all that means and what concept, or what components, would be composed of that scene. And what a relationship of different components are in.
07:13:27 So, that is the information model serves. And well, if you need to know how its implemented in how its processed.
07:13:36 You need to read the data model.
07:13:39 Okay so this to our for the basic principles.
07:13:43 Next slide please.
07:13:48 And this is the current status of the modeling spec. So actually we have already an existing cnet's model, and owner modeling specifications is approved in art eight, And it's basically referencing from the sci fi 11 information model.
07:14:08 Actually we already have. Most components, they are describing what is seen as composed off, and the relationship between those things, like you need computing resources for containers, and also network between those pause for container resources and
07:14:26 different deployment policies. We have all those stuff there, and the relationship described.
07:14:34 And according to the information model the design principle I just mentioned, it will be a preferred to modify this existing model to fulfill the SD requirements and.
07:14:46 Next slide please.
07:14:47 So the next two slides are the actual proposal from my side, on how to modify the current model to fulfill the XD model. So on the left side is the, the existing model, we have, and the right side of the state yesterday information model proposed.
07:15:06 So, as you see, we can see from the right side on Basti one.
07:15:13 It has the descriptor ID descriptor version and like provider, and the application version application names those kinds of concepts.
07:15:25 And we already have similar one in the existing model.
07:15:30 Then you can read the left side we have enough the ID we have provider.
07:15:36 We have software version. Those things are corresponding with maybe one exception for the SD schema version that is a new concept,
07:15:47 but I think it can be easily added to the existing model.
07:15:52 And another one is for the enhanced a cluster capabilities RSS a new concept English.
07:16:01 Not really new concept, but new requirements introduced.
07:16:05 And so it's trying to describe what a cluster, a scene that requires and describes those characteristics and properties of those requirements.
07:16:19 And actually in the existing model in the last container descriptor we have a resource requirements attribute which can use to describe what the containers are required for certain clusters sort of sources.
07:16:37 So, think we can add those requirements to there.
07:16:42 And another thing I want to mention is, As you see the left side, the way we have an info product right.
07:16:52 So, it is required.
07:16:55 Now in the information model.
07:16:58 And actually I think it's not really required by the SD, as we are not in that name in the implementation we are not required to use the Etsy mental architecture here, so there's no we never required.
07:17:13 So as a result, maybe we can relax that constraint on to change the wind FM info to optional make sense to cardinality to one to multiple to fulfill the requirements from the st.
07:17:27 Okay, next slide, where we have a similar mapping for the last two attributes.
07:17:36 One is, as the external connection point, which is used to describe the connection point where it's a external connection requirements of this enough.
07:17:49 describing the external connection the requirements of the, of the winners.
07:18:02 So I think we could include the SD requirements into the winner external connection point.
07:18:10 And similar one. We have department items in the st describing the artifacts are here we say how trucks, related to this cnet's.
07:18:32 We have any existing on in the, in the current model that is MCI op definition, which is also used to describe this those external hump trucks on artifacts that are related to the thing that's.
07:18:39 So, Again, a similar concept.
07:18:42 On, maybe we are, we don't have exact the same attributes and requirements but we can easily add them into the existing model.
07:18:52 And the last one is for the left side to define flavor. Again, it's a required attribute now in the existing model.
07:19:02 And it's not requiring the ASD patient now, so maybe we need to modify that to optional as well.
07:19:09 And besides this too I think all the other information are either optional. That means you can meet them in the implementations, or the unnecessary information on are required by the SD already.
07:19:27 So, the merging should be easily done and Kenyatta page, please.
07:19:39 where I have summary.
07:19:38 So my suggestion is to use this monetizing that model as the version one, the basis for the future discussions.
07:19:46 I think it would fulfill the requirements from both sides.
07:19:51 One side is we.
07:19:54 Following the information model the set design principle to keep it one information model describing all the implementation requirements and easier for the readers to know what is enough, it was in on.
07:20:08 And on the other hand, we support the SD requirements and necessary racks, to
07:20:15 provide on that sa implementation there.
07:20:20 And within the modifications are straightforward. And if we need, we can quickly do it, and approve to clean model.
07:20:32 Yeah, So that's basically what I propose. Thanks.
07:20:42 Thank you so much. First, because I think that you try to understand the is the model and the requirement. You try to do the mapping that was expected from the modeling team based on the as the requirements of what ever it will happen in the next segment,
07:20:59 I just want to thank you because you make an attempt to do the this mapping which was crucial for some of the people who are concerned about the CNS modeling change and in particular the information whether or not we will give the floor, because I knew
07:21:18 a couple of you. And I want to thank you to to be patient and to let you to go to the end of this presentation, we will open the floor for question, but the idea is really.
07:21:32 Are we moving in the right direction from a mapping, or is there some concern. I can see a lot of optional parameter that might help to move forward so let's try to remain constructive.
07:21:47 But as always, we work on feedback so the first one wanted to talk I think it's my turn. Now it's your turn.
07:21:52 Yes, It's a.
07:21:56 Shoo shoo, shoo going had her happy.
07:22:01 I will make some introduction and then we'll then continue, if you can make me presenter because I would like to show also something.
07:22:12 Okay.
07:22:14 And I hope to you okay because I didn't go. I'm okay with that. Mr. Thank you. Sorry. So there you go, man.
07:22:22 Okay, so I will share my screen.
07:22:27 So, before I will show any slide, I will show one page, and then this, the phone up modeling specification.
07:22:37 And the reason why I'm showing you this, that shows that very well that the Information Modeling should be abstract, and then data modeling and implementation should be do then technology specific implementation of it.
07:22:57 But there is a key concept which come up with the own app modeling specification and then the so called VNFD model. And if I open that VNFD model. I see here a lot of classes, and I see here VDUV the connection point definition of you and all other classes,
07:23:16 which needs to be reflected when we do the implementation part. That was the main reason why we said that we are decoupling the ASD concept from Etsy Mondo sold 001 alpha 11, because we don't want to use those constructs, which are mandated here, there
07:23:49 is a if you scroll down, of this part, then you will see that there is a
07:23:49 majority of them are mandatory. So I don't I buy to argumentation from sure that it is easy way now to change the at semana model so it will be the ASD model because, as the model is not using those constructs at all.
07:24:10 So means that we wanted to avoid to do the implementation.
07:24:17 Following the structure, which is a mandated by Etsy model. I think that I'm a little bit sorry that this concept, what all the intention of what we did with our cloud native proposal was not understood we try to explain it several times, but it seems
07:24:35 that this was not understood Of course we can try to do making we can try to do alignment. But with that, we basically kill the idea why we invented ASD why we wanted to have that independence of or to have it as an alternative to Etsy model approach.
07:24:55 So this is the, maybe a small summary of this, and I hope you get the impression that life is not as easy as it was presented by shoe. Because if you are focusing only on a few items on few attributes.
07:25:13 Then of course, it looks very simple, but those attributes are much more of them. And that is a whole concept behind. And I think what we also have been expressing ourselves is that we try to use the modeling, or information model which is coming with
07:25:31 Kubernetes itself, so that we are not repeating descriptors containing the concept which are coming from Kubernetes, and that if we are trying to do that of course we will end up with a tomato approach.
07:25:48 And then there is no point to have a SD.
07:25:51 So if you want to have some alternatives, we want to have a cloud native approach, then we should forget the Etsy model, architecture, we should forget, doing the mapping and aligning, otherwise we will end up with the same with the same part.
07:26:09 So therefore, before too we'll get the, the divorce, so be, we have small presentation here, but I will not go right now through it, maybe two will highlight that the show it in modeling Subcommittee on Monday in detail.
07:26:27 So I was hoping that we could bring the message over, but when seeing now the presentation from shoe, it is apparently that the message was not understood from us.
07:26:40 Therefore, we as Eric sown and I think the Nokia who was co signing us. We are insisting on that we would like to see the ASD models as an alternative to current Etsy standard proposal, not to be derived from it, not to be aligned, not to be mapped to
07:26:59 it.
07:27:01 Because we see that if we want to have a benefits, what we want to achieve with this concept, it shall not be coupled to excellence, because otherwise we are appealing those benefits.
07:27:16 If we want to proceed in own up with this concept. We want to have some sort of security behind our back so means, we are trying to follow the process.
07:27:28 So we want to get this model, put it in clean state, which will then put a stamp that he is the owner is behind our intentions are they are not trying to close the door.
07:27:42 Of course we are welcome to be for discussion so we are doing presentation we spend a lot of time to explain our concept, and we are open to it. I think this is enough show the summary, as a reflection to what she was presented here, and as a reflection
07:28:00 to what the modeling subcommittees trying to spread since Christmas.
07:28:09 Okay, so to do you want to see any slides from our date or you know just stated verbally.
07:28:15 Yeah.
07:28:17 If you can show slide eight. I have some comments there to respond to shoes presentation.
07:28:22 Okay, good.
07:28:25 Yeah. So this is a picture which I created together with Fred. Okay, so we'll just show what we have and what is the purpose for the ASD. I understand from the middle.
07:28:37 So this is a own app internal data model, which we have this, we have descriptor based on the open income that we have margin. And this one is based on this open econ information model.
07:28:50 And then we have the second one which is a, we have descriptor based on the soldiers are one. And this is a one based on this so called internal Tosca model, which is i phi 11 based.
07:29:03 And this one is not working so far. Right now, inside own app is only that we have module is working.
07:29:09 And then if we look at the left aside, that this is the onboarding data model, we have the open income model which is a template based. And then we have the so one data model for, which is iPhone 11 base, and the one this onboarding both a template and
07:29:28 the so one data model has to be transformed into the Vf model. In order to make it work in the runtime, and ESD is just another data model which are based on the as the information model for the onboarding package.
07:29:43 So, what what she presented in his comparison. Basically you're trying to compare apples with bananas, because you try to compare the onboarding model with this internal model is they're not the same.
07:29:57 We always do the transforming, that's my first comments. My second comment is that if I look at your table that you try to. I think that this table is some kind of misleading.
07:30:09 You You claim it is current CF model, but actually that is the, the one based on the iPhone 11. So the one that we see in this picture is if I 11 information model.
07:30:21 And that information model has a lot of mandatory the attribute, for instance of Bdu is a mandatory attribute. We FM info is another mandatory.
07:30:32 you based on what you propose if you want make it an option. I don't think we can do it, because we're not the owner of FI 11, then we have to go to IFA to change it to option.
07:30:46 From what I understand, in the past few weeks I've added some discussion, and there's no agreement. So those discussion can take some time. My question to to Catherine, is that if you think this is a way forward.
07:31:00 Basically, our own up decision has to wait for IFA to decide how to move forward. It could take quite a long time.
07:31:09 The other option is to propose we go with the Martian one off as the information model, and we wait until either has some decision we come back say let's work on the abortion to try to see how to do the alignment.
07:31:25 I would prefer the second one.
07:31:27 Yeah, that's my comments. Thanks.
07:31:33 Thank you. I know we have ordered the members wanted to express it. I think it's important to hear all of them. Let's look at the election we have zoom again.
07:31:44 Tim, is there anything in addition to what zoom, my handset or is it the same thing, though I have actually have I prepare multiple slides but I want to share one important slide to clarify some of the issues, I see in the proposal.
07:32:03 Now I have the presentation right.
07:32:07 I stop the sharing that.
07:32:09 Thank you.
07:32:11 I'll share.
07:32:19 Share. Okay. That's really tiny.
07:32:21 Oh, There we go.
07:32:24 There we go.
07:32:26 I want to show one slide, and then the other slide we can talk later because I know it's a limited time. First I want to clarify, put it in presentation mode so that everybody can see well.
07:32:40 I can see possible way forward. And then I use this slide to explain some of the summary that Ericsson Nokia trying to achieve. So the left pictures, is the famous picture of the ASD concept.
07:32:59 When it's really implied this picture is say orchestrators own app so NFL any other orchestrators.
07:33:05 Right. So, it can be used with NFL, and I'll show you the picture to the right. Explain that. But one of the key fundamental here is that it also this concept requires a functionality of Helm at the orchestrator level.
07:33:26 Today, didn't matter how much to show map flip flop mandatory or, or, you know, optional on the inflammation model from an architecture is different.
07:33:42 It requires some new functions at the Etsy, and the feel capability.
07:33:50 Right. so that's one key important. The second key important, as you can see here, there's no vn FM in the pictures.
07:34:00 That's the second architecture eliminations.
07:34:05 So, Today, the iPhone 11 is tightly integrate with the Etsy manual.
07:34:14 And I can go through the spec, and cut and paste page by page. To illustrate how integrate they are.
07:34:22 But I just want to show you that that's the fundamental difference between ASD and iPhone 11, is that architecturally functionally difference.
07:34:35 Now, moving forward.
07:34:37 We can socialize with Etsy men or Etsy team to see that we can coexist on version one is the concept that we actually develop part of this in the early stage.
07:34:51 That's the ASD can coexist with the service.
07:34:57 And we treat the ASD in here, I have, you know, a concept of NSD, which I fell 1114. And so one described, you got DNFD, you got been a D, and you got nested all this has some value add under the NSP, the ASD design so that can still coexist in the SNSD
07:35:25 concept.
07:35:26 And this is a native approach, the way we treat this, it just like a PNFD it provide external connection point to send this PFENFD, so that a service can still able to use two different alternative one if you want us at the Mandel.
07:35:46 you can still use that. Or if you want to use it. I mean use ASD without being, Emma native approach, you can still do that in the DNS level.
07:36:00 The beauty about this concept is that we, we begin to decoupling some of the advanced tooling for cloud native independent from other technology that will resign eight years ago when the Etsy Mendel was was established a almost eight years ago, when we
07:36:23 create this concept. Things have changed, and we need to evolve. And this is one of the steps moving forward to beginning to adopt some of the new tooling that we have today from open source community.
07:36:38 And that's why we have this concept. We did not want to push this into Etsy because we didn't want to disrupt the work on so one.
07:36:49 But since there are some members that are motivated to do this, we can bring this concept into Etsy to let them know that they can coexist, a weekend as ASD can coexist with NSA and then we can work forward as part of the version one.
07:37:07 And I believe in pop today.
07:37:11 They are doing some of this part, I remember I beyond.
07:37:25 Yeah.
07:37:24 To be able to use part of the NSP this picture is illustrate what they are they're somewhat doing in the park, also.
07:37:35 So moving forward. I think version one is very critical is that the architecturally different is not this inflammation model.
07:37:44 It's is that we are trying to go after we have changing the architecture.
07:37:51 Now, one quick clarification. When I saw shoes sly. One One thing I kind of want to ask TLC.
07:38:02 This committee is own now.
07:38:07 Currently, the way the sly imply to me that own app has only one CNS inflammation model and own app will only use that model, which is the sci fi 11 base.
07:38:20 Is that true or false.
07:38:29 Someone clarify that.
07:38:33 Serena think I can you repeat the question I'm not sure.
07:38:38 I'll show you the slide that shoe show today.
07:38:45 This one, the existing approved DNS modeling oh now is that mean there's only one seeing that model and own app, which is based on iPhone 11, that everything has to be here to this one for cloud native.
07:39:03 I don't think it's a case today. today we have generic bus. I'm not sure.
07:39:09 I'm pretty sure we are not using the similar.
07:39:12 Yeah, I think,
07:39:16 Sorry, I don't sing that everybody's using this one because they are to approach. That's my understanding, so even if one I've been approved by a group from an implementation perspective I don't know that people were aware first that it wasn't approved
07:39:34 one, and they might have done some deviation from the upper one but I'm not engaging of in the modeling to have a concrete confirmation about that but my feeling is that, potentially, not everybody is using it in order.
07:39:53 So to me, if I, if I may damage the acquiring one CNS more information model in owner. This is that case is not good. It's not open source we are not the standard organization I think that that's what the scenes, after because Sue clearly said one.
07:40:11 I am for CNN, which is not good. I didn't see him continue please, I have a my section two yeah that's that because I follow his presentations, and I, and then when I get here, I just kind of fall off the chair I thought we didn't.
07:40:27 I never know that there is one, but I know that we have approved at CNBC next model, that's one of the model, one of many.
07:40:48 One of two I guess right now.
07:40:40 So I think Surely if you can clarify, update your slide to clarify that way we don't have this debate again. Appreciate it. Well, there's also we don't want to confuse information and data models, right so if we have an SD data model.
07:40:56 Is it manageable to this.
07:40:58 It doesn't have to take this in its entirety. It just has to be, you know, makeable Can, can you reuse aspects of the existing model to map in today's the data model.
07:41:07 And if they're working.
07:41:11 And there I think they're just, I tried to have common so we're not talking about as the data model. We introducing another as the information model, and then is the data is SS SC based iPhone 11 based information model, we don't we don't think he's a
07:41:40 fit because he prior to us as the model architecture, we don't want huge esteem and architecture we want the model. The model doesn't so you have to use the architecture just being Frank of information, and just say structure is really following picture,
07:41:47 But if you look at this the, if you look at the SD class and the class that has the mapping to side by side, there's not much difference right now. Pretty much.
07:41:58 It's in what I supposed to propose that we would change the mandatory and optional characters in the base model, and then that then same class can be applied to both, but the end, you need to make VNFD optional.
07:42:15 And the way forward. So, Let me ask one thing right.
07:42:33 If you ask the SENFQ team, they talk about this date, there is a covenant is no doesn't matter only have the information model we're going to make it.
07:42:35 Make it, they could they can make it mandatory and their data model.
07:42:38 No, no, No, I'm saying. So,
07:42:44 here we are learning the SEC NFP specification right that's the only doing it. And then also, the ASD information or is not standardized by owner. He standardized at all and that's our target, so only align with the Orient specification right.
07:43:01 That's why, putting every map into only internal information model is not standard, we have to have a no information model can be presentable to other community at all and they going to do is that standardized, that's the function.
07:43:16 That's why mapping into own internal model, you know, information model and then we let this you know this vn FM, doesn't matter sci fi doesn't take it, we just not the standard.
07:43:27 We just making all you know some changing it okay to make it happen but without aligning to sc alignment, or all in, as the alignment, we are doing it, we not just the you know only of internal change it okay fine you know it's not, it doesn't walkway
07:43:48 There's another approach to where you can actually subclass from this, and refine the attribute descriptions to be optional where there might be mandatory, or you can have it eliminate specific attributes if you subclass from it.
07:44:00 Yeah, yeah.
07:44:02 That is another approach, and the that we do it completely separated from it, and then we have a freedom to use it so we are not dependent on the changes in the bar no and it's all 001 and alpha 11.
07:44:16 So, I mean that's it that's a good point because, yeah, because if if we're saying that the NFC is aligned to it and it makes changes on this field and he has to change which would report down.
07:44:26 So that's, that's the, that's, that's why we are doing it we separate from the beginning and then we put presented to our other standard organization we really don't mix it because I find out when they just are carrying the that's the model, architecture,
07:44:41 we don't want to do that we don't want to using the NFL, we didn't want to do vn FM, and then we using the emerging into iPhone 11, they said, Oh, you said when you serve you and your family so NFL, we don't use it, why not because sci fi, they didn't
07:44:56 make it optional. That means you're not aligned with the SEC model. Okay, sci fi. That's why the currently internal discussion like mapping this, there's really not constructive, to me, that's why that point, but that's a good point.
07:45:13 So, so, with respect with respect to that point, I think it makes more sense to have a parallel class where you state that you're not mandating alignment to the Etsy model.
07:45:28 Although it is, you know, somewhat parallel and related. So I think that would be to me that would be okay.
07:45:33 I think, I think, And I think you have a good.
07:45:51 ASD descriptor model. But that's a future thing.
07:45:55 So I can make Marion suggested pleasure one that you know couldn't stay in any discussion of Fred and the SU and the other three about inflammation you know lying desta virgin to, we don't want to spending the, you know, not constructive way because we
07:46:08 think we spend like you know since sep tember, you know, Ericsson Nokia spent a lot of engineering time to make it happen. So anyway, that's how we all ask, Catherine proposed have to make sense to me.
07:46:22 But, you know, again the again the stereotype should be plumbing, right, because it's it's subject to change, but it's being used for implementation which is the definition.
07:46:31 So I would like to conclude on this call, if there is still, I don't know if we give the, the nope opportunity to everybody to speak.
07:46:42 Let's see Magnus you didn't speak but I hope you okay.
07:46:49 I'm okay.
07:46:48 Okay. Who else did not speak on the you speak.
07:46:53 So I would like to conclude out there still. I also do it legally, so we listen to glue and Lindley.
07:47:01 But before we do that I will tell you what we will do.
07:47:04 I hope that no wilderness, and I want to really give the floor to grow and Lindley, so maybe I will express myself so Zoo and Lindley Can you share your soul, then I would like to conclude with the next step, Zoo, carry on my tomorrow, Marines, points.
07:47:25 So first, I want to say the mandatory in the existing model does not mean that you need to, it's mandatory to have those attributes in the actual descriptor.
07:47:40 The mandatory means the orchestrator or the mental need to support those attributes.
07:47:49 So, even in NSC you define those attributes does not mean every provider will need to define that attribute, that's not the case.
07:48:01 So,
07:48:04 actually, you need to see the cardinality column where you only have two mandatory attributes that are not necessary for the SD now.
07:48:15 One is we nothing info, and the other is the debunked flavor, which I propose to relax. To fulfill the SD requirements, I don't think if they change.
07:48:39 And then a second one is about mapping between the DM, and I am actually I agree with what Andy sets in the chat on the data model can choose what it needs integration model.
07:48:43 It's actually you can implement only subset of the information model.
07:48:50 It doesn't mean you need to implement everything in it. And I don't really think the data model needs to 100% of precisely following the architecture of the information model there, you captured the necessary information you have.
07:49:05 And it's enough.
07:49:07 We have a concept level mapping, not a structural level mapping.
07:49:13 And then to sin on.
07:49:17 I think my presentation shows the current status. I will not.
07:49:22 Maybe you don't agree but it's the case in the current owner modeling specification.
07:49:28 That's the only thing that model we have.
07:49:32 And again,
07:49:35 it's inflammation model. So, please.
07:49:39 People do not make that makes that was the implementations, we have. I agree we have different ways of implementation. Now you know now, we have seen enough direct past, we have, as the alignment and now we have a SD, but it's different implementations.
07:49:54 It's not for the information model part.
07:49:57 Even we are using the native Kubernetes. I think we are describing similar information that we have now in the information model, we have the, the pod container resources to CPU, memory requirements.
07:50:11 And we have the network requirements. Those things already covered in the advancing the information model.
07:50:21 And so I think generally will we still think this way it's workable. And I don't think it's Take, take too much time.
07:50:32 So I would still suggest we use in this way.
07:50:39 Thank you.
07:50:42 Thank you. And last but not least, Lindy.
07:50:47 Thank you, Catherine.
07:50:49 And I've been learning a lot during the last two weeks, hearing, you know, all different types of opinions and also looking back two years ago. Well, well we started modern subcommittee.
07:51:02 We believe that mothers of committees actually has a place in in casting industrial.
07:51:17 Our guide lies, and I believe information model plays a key role here.
07:51:18 And I in my heart. I like to say this in the beginning, so make it clear.
07:51:26 I believe in this community that in a running code is the Bible for mothers of committee, I also suggest that most of committee should always reflect what is written, and in, and running with own app code.
07:51:46 And if there is any model that is not actually reflected in running code. It should be obsolete.
07:51:55 And that is my suggestion number one.
07:52:00 And as for the current situation I believe that, for the SDP part PLC to go. They had an implementation.
07:52:09 It is not implement is not information model in the way that is the data model as well stated by shoes presentation.
07:52:22 So my suggestion is actually to move forward with the data model.
07:52:30 And thirdly, I would like to prefer going on discussions with the unified information model, and I'm trying to tell you why I'm thinking this.
07:52:44 Looking back, that we were being going.
07:52:50 Pushing heart.
07:52:50 Also with Ericsson, and we spread implementation with FC alignment approach.
07:52:57 And I think I think we uncle he's also here. She has been working hand by hand. With be one with that approach.
07:53:17 Personally, we tried, and we learned a lot, which is really learned, I believe is that if we sincerely believe that our own app should be aligned with our external SDO and not running code, not approved by running code, which is doomed to fail.
07:53:40 In some time, because those external stos cannot be more clear about what is actually realize in running code within a nap. For example, as I think Maria showed in his slides, they are actually onboarding models and internal models.
07:53:55 And in order to those transition, those considerations are not in scope or those external stos, but it has to be taken consideration. While we are actually doing the coding inside a nap community.
07:54:16 And I'm really concerned here also you know hearing.
07:54:21 I don't recall who says that but there's a strong preference.
07:54:27 Inside this community now that we should be aligned with around community.
07:54:33 This is not that I'm taking any preference over one or two external stos, but I would like you know our sensibility for this community to think whether or not we should add this part two is to be aligned with a second text or no as the iOS.
07:54:55 And, you know, separate from the risk that they might there be ative from the running coach from a nap community.
07:55:03 So, for, for me, I'm not taking from any technical perspective. I'm just saying that it is an instinct from me that own app shoot has a unified information model, which actually, you know, abstract, the way any of the implementation specific technical
07:55:25 details.
07:55:27 And also enable the independence from any external SDO specifications and living, you know, only documenting what own app as a straighter offer from the northbound interface or from the designers, said by she and living the flexibility and in data model
07:55:56 with different implementations.
07:55:59 And even, you know, taking the further step back, I should believe that this unified information module should capture what is already, you know, encapsulated in house chat, and why I believe this is because that if we are actually dependent on in system
07:56:23 insisting, you know, separating our information module from ham charge. It would also mean an indication that we are also dependent on what is documented in home chat.
07:56:37 So, wherever Hampshire changes, then it should be reflected to the data model. But luckily, not information module, so that we could keep our stability, and also redeem the flexibility with different implementations.
07:56:57 Thank you.
07:57:00 Me, I'm sorry, I, it's not too clear what you're saying I know you manage cover the many area from in this topic so you allow ASD version one and move forward.
07:57:13 That's you're saying or are you saying, otherwise, it's not clear to me. I'm not sure you still only me or.
07:57:21 Okay, I'll make a summary sorry, this. I didn't expect it to be this long. I was there just that we actually having a discussion with within modeling subcommittee whether or not we should approve as the data model as clean so that the PLC can go ahead,
07:57:51 in the same time, we're actually having a further discussion for a unified information module that should also capture what is inside Hampshire. That is what I'm suggesting.
07:57:54 Okay.
07:58:11 And so Ericsson can move forward. Otherwise, you know, reject us we tried to get it not going back to a more calm and make them make a decision. I think that we already brought here TLC and TLC make decision for us.
07:58:25 That's my understanding Marion Magnus, I so that's my understanding is a lot.
07:58:31 I will need to stop all the discussion because I think it will be sooner.
07:58:37 Extremely late that what's on location so I want to hop up and I want to define the next step right. So, first of all I want to thank you all, because I think all of you have been expressing himself or herself.
07:58:51 Based on what the understanding from the modeling and what we should fall for what I think it's over the last two three weeks.
07:58:59 The different team the mothering subcommittee, and also the as the model team, pull the task force, have been providing a lot of information to the TASC was not really aware or not really cautious aware of what's going on and also from a technical perspective,
07:59:20 I think there's been a lot of information, a lot of mature young share.
07:59:26 So what I would like to suggest as your own up to see share. I want to hear to hate, a new route, and we will perform this vote offline because we have lost already your senior began to see members.
07:59:39 There will be no zero. So it means that the TASC members will need to vote either press one or minus one on the question that I will formulate it, and whatever will be the answer.
07:59:53 of the vote, we will move forward.
07:59:57 Based on the votes.
07:59:59 So that's what I will do, and I will invite again to TLC.
08:00:03 I will give a couple of days so if some people wants to have additional information from the motoring team or from from the end team they can contact you know know all the stakeholders.
08:00:17 And I would like to have the conclusion of the vote, I would say, by the 14. So it gives us.
08:00:27 At least one full day because the team is I will be off, but a full day to reassess think. And that was a TLC, we need to conclude so that's my way to move forward, because I need to understand about where we are.
08:00:43 If we're sitting in these agreement to pursue. Or, if we're in agreement to continue with some condition so let me formerly the offline room.
08:00:55 But I think they've been a lot of feedback lot of material that now the TLC can review to make their next decision. So that's how I want to proceed, based on where we are today.
08:01:13 So, Kenny back to you because I don't know if there's anything important that you want to say before we close this call since we have over, 30 minutes today.
08:01:24 And my.
08:01:28 COMM team. We will try to apply, apply to your concern about the issue is the packaging offline and see what we can do with a project team.
08:01:42 Catherine I don't think there's anything pressing we've got the workshop I'll drop the link to the workshop page into the chat window which folks can look at briefly and grab if you want, if not it's linked from the minutes, and it's also available directly
08:01:55 from the LFN wiki page.
08:01:59 This is next week.
08:02:02 If you are interested in participating please do. If you look over the posted topics for the workshop and you don't feel that it is applicable to you or
08:02:16 not of value in terms of where you should be spending your time.
08:02:22 There's that because it's a very focused event on a, on a select number of topics.
08:02:28 That's all I have Catherine.
08:02:31 The vote for the M three has been sent to the vote list.
08:02:38 Thank you, Kenny, and I will kick off soon. The vote for the about what we have discussed today as well.

[data-colorid=gk5o43vllw]{color:#1d1c1d} html[data-color-mode=dark] [data-colorid=gk5o43vllw]{color:#e3e2e3}[data-colorid=arsdc7i2cg]{color:#333333} html[data-color-mode=dark] [data-colorid=arsdc7i2cg]{color:#cccccc}BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Agenda Items

Release Status

RelEng/Infrastructure

Task Force Update

ONAP Enterprise Task Force

PTL Updates

Subcommittee Updates

Subcommittee Updates

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

TSC Activities and Deadlines

Upcoming Events & Housekeeping

<Available Slot>

Zoom Chat Log

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

Browser not supported