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

Passcode: 209247

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

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log 

06:56:02 From Fernando (Fred) Oliveira to Everyone:
#info Fred Oliveira, Verizon
07:00:18 From Byung-Woo Jun to Everyone:
#info proxy Byung-Woo Jun Ericsson
07:00:22 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
07:00:45 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
07:00:51 From yuanhong to Everyone:
#info proxy Yuanhong Deng, China Mobile
07:01:11 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
07:01:13 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:01:50 From SaiSeshu (Huawei) to Everyone:
#info Seshu, huawei
07:01:57 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
07:02:02 From Srini Addepalli (Intel) to Everyone:
#info Srini Addepalli, Intel
07:02:23 From LoreLei Rouvrais to Everyone:
#info LoreLei Rouvrais, AT&T
07:03:06 From Jason Hunt to Everyone:
#info Jason Hunt, IBM
07:03:11 From Catherine Lefevre to Everyone:
#info, Catherine Lefevre, ATT
07:03:11 From Martin Vezeau (Bell Canada) to Everyone:
#info Martin Vezeau, Bell Canada
07:12:53 From Kenny PAUL (LFN) to Everyone:
#AGREED change copyright to read: ©️ Copyright 2017-<current year> ONAP. Licensed under Creative Commons Attribution 4.0 International License Revision 5862ac2c. Pending review by LF legal.
07:36:01 From Byung-Woo Jun to Everyone:
Great work!!
07:41:05 From Kenny PAUL (LFN) to Everyone:
-Guidance from LF Legal on copyright notices is to remove the year altogether. Info on copyright notices here: https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/
07:42:38 From Kenny PAUL (LFN) to Everyone:
- Prior #AGREED on copyright is rescinded.
07:43:34 From Kenny PAUL (LFN) to Everyone:
#AGREED where the copyright statement names ONAP specifically remove the year.
07:49:26 From Kenny PAUL (LFN) to Everyone:
#AGREED ESR UI/ESR Server is to be removed from ONAP beginning with Istanbul
08:09:28 From Martin Vezeau (Bell Canada) to Everyone:
I have to drop now.

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

07:03:49 can do that one class.
07:03:51 Andreas Thank you.
07:04:01 Okay, transcript and recording has been started.
07:04:09 Need to keep yourself muted.
07:04:11 Everybody's muted when they come in.
07:04:14 If you're on a phone you can use star six to unmute if you send me a private chat message it'll become part of the public record.
07:04:22 And as always, we'll start off our meeting by mentioning, our anti trust policy. You can find this link from the lF and the project websites.
07:04:30 Policies important we've got multiple companies including potential industry competitors participating in these meetings.
07:04:35 Please review, any questions your company's legal counsel is whom you should reach out to members of the lF may also contact Andrew up to grow the firm gives up Grove LLP, which provides legal counsel to the lF.
07:04:55 Stop that.
07:04:57 Start
07:05:04 not
07:05:08 have a release.
07:05:14 Update here want to talk a little bit about the integration blockers.
07:05:20 That, that we have going on.
07:05:34 Bro, inch PGL update from the doc project
07:05:34 And, Hans amass joined.
07:05:42 Oh, yes. Okay.
07:05:45 And, Tomas had expressed an interest in going early due to a
07:05:53 existing conflict later on in the meeting so Catherine with your permission. I'd like to start there.
07:06:07 He doesn't have audio yet, I think.
07:06:13 Can you hear me now.
07:06:15 Yes we can.
07:06:18 Yes, so just wanted to thank everybody.
07:06:24 No sorry you asked me a question for a second weekend can start with the DOMA items. If it was the question. Yes.
07:06:39 Okay, yes please let's do, yes. Welcome DOMA.
07:06:39 Okay, let me give you.
07:06:44 co host loss.
07:06:47 Okay, so thank you first
07:06:52 for the opportunity. I'm so sorry, are three doc topics two more to keep you informed, but.
07:07:03 The first one is about the change of the footer. We currently have in.
07:07:21 you.
07:07:27 Okay. Can you see the screen around, it's showing.
07:07:32 Okay, okay, okay. So currently we have this year.
07:07:35 Copyright 2021 own art license.
07:07:40 And I noticed that, for example ODL has a different one.
07:07:56 So this area see.
07:08:01 Copyright 2016 2021, because I think they started in 2016. So, so I thought okay that would be maybe a good deal to have it this way for on up and erase the ticket at least engineering, and I learned that this should be agreed by the TLC to change this
07:08:25 photo here, and this is what I like to propose to propose to change it.
07:08:34 like we have a tear in at the audio project.
07:08:36 If you as a TASC would agree to it.
07:08:40 Maybe with or without the copyright, with the with the, the license information, mature if we need it.
07:08:48 This place but, yeah, this is I kindly asked you to decide on if we change or change it not.
07:09:00 So, do we need to also double check with the Urban League word, I'm just asking the question because I know all the copyrights were driven by an IP like world like Apache to the OKRD for the documentation.
07:09:20 So I was wondering if there is not something special that we also need to ask it like what can he do you know, or is it just the TASC decisions.
07:09:31 I believe this one will be just the TLC decision. I think this is one where we would just inform legal I'm gonna let me reach out to Steve Winslow while we're on the call and see if I can get a feedback from him on that.
07:09:48 But so so much I think you will feel need to keep the, the note here that you share license under prt, that's something we cannot delete, because I remember we have to be scalable know if you want to do what the audience is doing it.
07:10:07 We can be have a discussion here and be confirmed by I believe what I can stop for for my perspective, having a copyright. We probably need to kick up that in 2017.
07:10:20 Until now I don't see any concern but maybe my peers.
07:10:25 From the CFC. My, my, my see some concern but I don't. Right. If we start from 2017 which was the debate where he created the project that, for me, I will take the detail, but it doesn't disturb me.
07:10:44 Right. So, anybody wants to give their opinion so even if Can you will double check.
07:10:50 And again, I repeat myself what it is, what was previously I lighted by to master license, we will need to keep it I guess we cannot because it's faster for IP courses, but if you want to extend the date.
07:11:08 Does anybody from the DSC see some objection of concern.
07:11:20 Okay, I'm going to mark that as an agreed pending. lf legal review.
07:11:27 Okay. Excellent, thank you very much so then if agreed in the final step then I like to add the year as you mentioned it gets when.
07:11:40 Okey dokey then just a tool, short things to. For your information, so we had currently a discussion with also the architecture subcommittee, and you will already have heard about the architecture navigator and hit, he hit the architecture navigator from
07:11:58 and the subcommittee architecture subcommittee had it quite good feature in it. So, he had this kind of navigation map where you can click the elements of the architecture and you will be guided to, to, to documentation, or maybe use case related information
07:12:20 or something else so we thought okay that is a cool idea, and we like to have it also in.
07:12:28 In, read the docs.
07:12:30 And so, Erica did the initial work on it and I have finalized it. So now we have created this interactive map here in.
07:12:44 In Rita docs, you currently find it only in the latest version of the documentation and you find it in.
07:13:06 If you have a with your mouse over the elements of the map. So, you get to every most every element, a short description of the element.
07:13:23 Even of, even for the more broad elements in this architecture diagram.
07:13:28 And, for example, if you click on the element, you will be guided to a richer doc section. For more detailed information. For example, He has a controller design studio, or even let me go back, or even with the nice information here.
07:13:51 You will be guided to the Belizean information of on up,
07:13:57 and so on, and so on. So, for all the components.
07:14:03 We have created this descriptions, from, from project description from architecture descriptions for from whatever source is available, and which makes brings value to people that.
07:14:24 Yeah, like to know a little bit more on in the first step from the architecture, offer on up, so and we placed this map this interactive map, when the.
07:14:38 Yeah, and the intro the introduction part for the architecture and also this map has alignment with the architecture subcommittee, because they, they have the guidance on the, on the content.
07:14:53 This is what I want to show you, and present to the TC today.
07:15:02 And it was
07:15:05 a great job. I mean it's really nice to have it now integrated with all the capabilities of can understand and clean down so it's really.
07:15:16 Wow, it's really nice.
07:15:21 I have a slight coma.
07:15:21 Although I'm not a cosmetic lady. there is only 111 suggestion or proposition.
07:15:30 Since the gray.
07:15:39 I was wondering, right, because when there is not truly a color coding information on this page. I was wondering if it would be okay. I think I need to go to bed.
07:15:51 The only thing I. If the color coding is indeed what you share there. Right.
07:16:05 Then, does it not give the impression that the utilities and maintain the management moment, and things.
07:16:11 So my Bond was can we just change the colo.
07:16:15 So unmaintained we know exactly what it is on mundane and we don't mix with the column of design time and bonds interface and my apologize for missing diligence.
07:16:27 But my phone was same color means different things, and each can maybe mislead when I sure I was looking your objective, not know I thought, even if we should state, the unmaintained state of competence in this map here, because if they are deployed in
07:16:59 a standard in a standard or not.
07:16:59 deployed deployment so they are part of the architecture, regardless if they are unmaintained but we can keep it as it is and will change the color for the shared utilities that they do not that, that this would not be misunderstood, that they are unmaintained
07:17:19 Sure, I will check
07:17:22 and get a nice color that fits to this.
07:17:29 So that was a sign here. Yeah. Oh, since you have a lot of great for utilities design of boy the face you see on this picture a lot of great, maybe just change the color of the and maintain and take a light orange.
07:17:47 I don't know you you pick another favorite color, but I would repeat, use a different corner, not only for the utilities, you see, so So, maybe only change the, the unmaintained, that will be the easier.
07:18:01 And as you said, as is still mandatory. So I would not remove it completely from the diagram poster for for mass spec is still needed. So, I will not remove the one which is still by default mandatory, even if we don't focus too much anymore on it.
07:18:22 And then the other question that I have, which is we use a different color for the message booth.
07:18:30 Maybe you want also to add it as part of diligence because you use the white.
07:18:36 Yeah, you got me. Yeah, right.
07:18:39 No, no, but again, I'm usually cosmetically.
07:18:46 But just to be sure that people do not know so well nap or I'm not so close that all of us we are not misled. And this is the only common otherwise I really like that, we took the benefit of what the tools from Shakur was offering we integrate directly
07:19:04 to do these nodes. I love the drill down option because it gives more inside if people want to.
07:19:14 It will probably be the architecture picture that we were using a lot of industry talking so it's very, very greatly done. And I just want to thank you Thomas and also shocker because I know you, you are teaming up, as well as the people who have been
07:19:35 helping you to make it happen so very great job. So now I give the flow because I've been speaking.
07:19:42 Thank you. Hi,
07:19:46 Tom Bell Canada.
07:19:48 Again, Saskatchewan, awesome, awesome feature. Any, any components, not reaching not reachable from this any, so do we. Did we do the opposite also trying to figure out things that are not reachable that should be from here.
07:20:09 Not sure if I understand it right but I can, I can click on the box and reach the component of the destination documentation, any documentation not reachable.
07:20:20 Should we update this diagram yeah there was, yeah there was a thing.
07:20:27 There was a dummy because it guides you to, to, to read the docs but in recent oxy find a link back to the wiki which will we with with which we do not like to be honest, but not sure what what company ended was but I will give you.
07:20:51 Yeah, I'm not sure. I don't mean to have every component diagram, but maybe some.
07:20:58 I don't know if you did the survey, maybe to add additional boxes either shared services, or other area, might I might be missing.
07:21:12 What I want to say is so you'll find this this diagram, and also some complaint complaint complimentary information about the links embedded currently, and the the text you all find this also in an editable format in in the doc repository.
07:21:32 So and I will give you some.
07:21:38 Yeah, I will approach, at least a few projects to maybe to revise the explanation text because we have a few there that we need for example the model activities are to be revised and Tosca powers to be revived that that could be improved.
07:22:00 And, but from the component view, so that we have a lot of documentation already in reads the docs, in a very few cases we have only documentation for a for an older release I think we are linking also to Frankfurt documentation because we do not have
07:22:21 any more up to date for some components.
07:22:27 But,
07:22:30 at least for the, for the unmaintained one, I mean that we already. Let's see.
07:22:36 Yeah, we have any way also the the the links in that definitely I think what what Thomas was doing is, he figured out what are the links which are what are the documents which are existing so there, they are only pointing into read the doc stuff that's
07:22:51 that's one definitely clear point so there is no link to be done yeah so it's all, including. It is all pointing to documents which are included in the package.
07:23:04 I think for most of the components we have architecture documents.
07:23:09 But I think one one issue I think which is ongoing still is the migration of all the documents of architecture.
07:23:19 Let's say descriptions and so on. From the wiki, to the read the docs I think this is not completed yeah so if you. So this these, let's say an opposite to check out tool which is pointing to the, to the architecture documents inside of the wiki, we are
07:23:37 trying to do, or here it is only pointing to the documents within read the docs, and as.
07:23:45 The problem is that the as at the moment the architecture documents, which are in the wiki are not migrated yet to read the docs Of course they are not let's say instead of at the moment.
07:23:57 Yeah, so the next target would be then to. And this is what, what, what, what we are targeting for to let say migrate all the documents from the wiki from the architecture subcommittee to read the dog so that we have, Let's say or up to date.
07:24:13 All components, up to date with their architecture documents. Yeah. And let me, let me say that Kenny I can give you a short list of components, I like to be revised by the by the projects.
07:24:28 Can we do it this way, then and you can add it to the, to the notes for the TLC meeting and then people can go through and maybe provide me some more up to date documentation or more, more.
07:24:42 Yeah, would be away.
07:24:47 Did you already present this to the ppl call, because I think it would be great also, because not all the bidders attend the TSP by default, but if you didn't do it yet.
07:25:01 Maybe that's a topic for Monday. Yes, I can do this. Yep. And we released it as this week and.
07:25:12 So, you see, was first in the schedule but I would definitely do it in the PDL call. Yeah.
07:25:19 And you do it one you want right but it's easy to find it could be the 16, just add the items to the ppl agenda, if you don't mind what you feel already.
07:25:31 And I had another. I have also another question that might also interest, the details. So while we can also have this question for next week or the week where we present.
07:25:42 So if, if a team wants to do what's the process right if they want to announce the.
07:25:51 So, he just click on a box, as an example, just click on this one as an example, just quick so so it goes directly to the read the doc of the components so the expectation is that the team is telling you that they have changed this page, or I will not
07:26:12 see you don't care because I know you are, you are really a cautious man but what would be the processing the team is changing something.
07:26:20 Is it something we can also document, or at least we know you have the information or, or maybe if they don't break the link between your high level diagram and this is all good.
07:26:35 I'm just trying to see how we can in the future have more capabilities or more mobile data to what they do. If there's a process or is it passed on to milestone or how do you sit by I'm not sure I'm clear with my question to be honest with you, so I hope
07:26:53 you get it now but maintenance of this diagram and also links and the description is definitely a point, Catherine, and currently I'm a plan to do it.
07:27:07 So, But let's see how they that the usage of the map will evolve. So maybe we can also have some programmatic solutions to change links or change the descriptions in this
07:27:26 in this diagram. So it's an SVG so can be replaced.
07:27:33 So, but currently I will do it. And yet we are using a lot of links for the component and function in the in the component and functionality section year in which the docs, but if things are changing.
07:27:52 Yeah. I'm, maybe I write a check routine that tracks the availability of links or something like that, but it's not.
07:28:02 It's not finally decided on the, the, The, the maintenance but I will do it.
07:28:11 Okay. I maybe I need to relate a little bit my question. So, when the team will finalize their release, they will probably need to update this release note, This is still there.
07:28:25 You think under code to do it right. So the content of some page, they still need to do it, or they need to send you the information.
07:28:35 I believe they still need to do one part of it, or.
07:28:41 Nobody. I think most of the times we are using links as the the entry point so if for example the release note will change.
07:28:50 So there are no links to release notes in this in this in this map. So, there are more or less the entry points for for the, for the components for the component
07:29:10 descriptions.
07:29:12 So I think there will be there will be no need for informing Thomas about that, so it will just point to, let's say, the, the index certain index notes usually or index number or index labels in the in the in the docs, of the, of the other projects so
07:29:36 if we have architecture. For example, it will point them to the architecture and it will not, it will automatically be on the right page so it will not, you don't have in the in the SVG document explicit links to a specific version of a, of a file.
07:29:56 Although, when we release a certain.
07:30:00 Let's say a certain version of own up, then we have to specify the exact version of course because otherwise it will point to the latest and this is of course something, we will have to take care of it within the release project process.
07:30:17 So when we release for example, then the the Istanbul release it has to point. So, let's say here for SDN see it has to point to the SDN see. So the to the Istanbul release of this document so that's the that's the only difference, or the only thing which
07:30:37 we have to do in the SVG, description, but not anything which is related that we have to, let's say explicitly now call a specific document or whatever form that, and we don't need to be in all the documentation team does not need to be informed about
07:30:57 that.
07:31:02 appointing Tuesday to the correct place for information as it comes to a release specific documentation we are already doing it because we create we creating the index for every release specific documentation.
07:31:14 And this is also something we can use and in the, in the map, the links, as I said, for example this year, then must replace to Istanbul or whatever comes next.
07:31:38 Thomas one question is any configuration file. You can put the older configure will change with the data into the sum of the file, and they don't have to change the actual SVG.
07:31:41 I like to have this kind of solution because currently we have a CSV or maybe an XML file where the lake, the links are stored and weather explanations are stored and we can put in.
07:31:55 also some, some index for the SVG elements. And then this can be used to replace it in a more programmatically approach. Yeah, but it's not available yet.
07:32:09 Okay, it's not there yet, and it is something that the team is looking at.
07:32:17 Nicholas creamy who some of you may have seen on some of the calls, is our summer men. He has been working to help some of this. And that's kind of the next phase of this is looking at how we can put automation into, into the maintenance model.
07:32:40 Sure. Thank you.
07:32:41 It's good idea.
07:32:48 Okay, something else too. For the interactive map here.
07:32:55 Just question you know right top corner, you have to reduce night Eastern.
07:33:00 Just a question you know right top corner, you have to release now Eastern Oh, well this is only for release night, or is that going to be maintained release after release or, because I think in the reader dark right now it's the latest version.
07:33:12 Yeah, that's right. so it will be maintained.
07:33:16 First, so they the changes will be done by the architecture team.
07:33:20 And then we sink. This graphics to what is done by the architecture team and then we released for a release specific for a stumble and for the upcoming releases we have done a dedicated map.
07:33:40 Yeah.
07:33:41 But the right now I think the link, you put inside the picture is always pointing to the latest version.
07:33:49 So if you really want to maintain release by release. You have to change each link. Yeah, that's what I said so when we have the release process, so we do not have that yet yeah so we are still let's say the official version is the Honolulu if we if we
07:34:05 have done the release date so when we create the release, is that will release the links in the in the in the in the map need will be changed to the Istanbul versions of the, of the component documentation.
07:34:18 Yeah, okay. Okay, thanks. So that you don't of course mix up that's clear so it has to be always then, if it's released, then point to the right release specific component document.
07:34:29 Yeah.
07:34:31 Okay.
07:34:32 Yeah.
07:34:41 Okay. And then I worked on, quickly to, to the last topic, I just want to say there is a setup guide for a documentation development system.
07:34:54 It's very detailed and also suitable for beginners and it creates a documentation system was a very good preview. So, if you edit rst files for your projects documentation, and you can have been quite good preview, and it looks like.
07:35:19 So you have it in, read the docs, more or less.
07:35:24 And so, so we have this.
07:35:27 Yeah, detailed description for setting up this kind of system. This is just to to inform you.
07:35:44 So that's good. That's really good too.
07:35:50 Okay.
07:35:52 If there are no questions, then the only thing. Thank you.
07:35:57 Yeah, I did.
07:35:59 Thank you so much, Tomas it's been just great work here and shocker thanks for all the work that you've done on architecture navigator that helped drive some of the help drive the discussion and the introduction of the, of the clickable maps.
07:36:18 I did get feedback from Steve Winslow on the copyright notice his recommendation is to remove the year altogether. That is the recommendations that they are giving to the projects, because then it avoids the January 1.
07:36:35 Oh man, we need to update everything now.
07:36:40 So the guidance that they that. lf legal is providing is, is to remove the year from,
07:36:48 from the doc from the copyright notice man just leave it as copyright own app.
07:36:57 Okay, make sense.
07:37:02 So since we just had an agreement on the previous change.
07:37:06 I am assuming that, given this feedback, the TLC is okay with the change recommended by Mr Winslow.
07:37:22 No we don't. Yes, of course, you think that I think they, they are the people who are representing us, formerly perspective so it would be wise to challenge them.
07:37:32 That's fine.
07:37:34 Thank you, Kenny for the follow up.
07:37:47 Okay. If there's nothing else on the dock project, Tomas thank you very much and I guess we should shift to release status.
07:38:07 Thanks Kenny.
07:38:09 So I published the weekly
07:38:14 review.
07:38:17 Update yesterday.
07:38:19 Hopefully all of you receive that. And we have a couple of other items,
07:38:27 just to highlight. No it's not, it's not being that sticky.
07:38:35 Remove that that's the manifesto Kate's been completed. So, we're still trying to get status of CLA and multi cloud
07:38:44 for the, the best practices, and that global requirements, and I've sent email to to ban and kind of garage.
07:38:57 Yeah, if I haven't heard from kind of garage.
07:39:02 If any way, if anyone on the call from Huawei.
07:39:08 I can.
07:39:11 Great.
07:39:13 Thanks issue.
07:39:16 So it'd be helpful if you could go into that table and and update the commitments for CLA.
07:39:26 And then, Catherine. I think he wanted to talk a little bit about the integration certification.
07:39:36 And the ASR.
07:39:41 Yes, so.
07:39:45 So, I'm just 14 days until summer vacation. Just wanted to provide big kudos to the team.
07:39:52 Because we have been able to don't fly a stick at a couple of blockers.
07:39:58 So, by Blue Cross we mean things that we will not accept.
07:40:03 If it is not fix those links will not be will not happen. So, because of critical issues.
07:40:10 So a couple of them have been cleaned up so thank you to all of you who have been contributing to fix them.
07:40:17 We also want to notified that the orange daily lab is currently don't I didn't check this morning if it. If it was up again. But currently we are using the tech on beta gating.
07:40:32 And so far, everything was also green from an insect perspective so maybe Andreas and my girl. You want to provide additional, a big concerning the integration activities.
07:40:48 Yeah, so, also we have challenges in our laps. So the day the orange lab is also is at the moment not up to date or not not working. We have to wait for Morgan to be back.
07:40:59 Check this integration meeting, but also in our laps we had issues. So the like the last run was on the 30s and it looks quite good. So, everything was basically green.
07:41:17 Just one issue between, which was more related to, let's say, a configuration issue in the in the pipeline, which causes the failure of one of the end to end tests, but the rest was green.
07:41:31 but after that we had also some lab issues in the lab.
07:41:37 As we are also moving parts of the labs and we are just about to, to rerun the daily tests, and hopefully we will have today or tomorrow, a stable outcome and we can can report that it's working again.
07:41:56 And hopefully I can also publish them the results in the known status page.
07:42:03 So, as I said, so I was able to restart the pipeline today and, but it's just still ongoing and I will follow up then that it's working and we have at least and some daily results.
07:42:20 Yeah. The rest as I said for the orange lab will have unfortunately to wait till server or Morgan will be back, because we don't have access to the initial or the cloud environment, because they are at the moment, issues on the infrastructure.
07:42:46 Thank you, Andrea for the update, and now we will move to the ESRI discussion answer server. And also, yes, you I don't know who would like to drive the discussion from there on, Cassidy and maybe I can keep, maybe, Amy, can you can do, too but from my
07:43:05 side, there is some maintenance.
07:43:23 There, I think, so far being so he asked you not gonna maintain the UI as a server and you don't go. And then also Bill mentioned about a and I gave a similar picture so so at Okta subcommittee.
07:43:25 We discuss this issue and we identified this you know, three, use cases using the external component restoration and but two of them as the alignment and network slicing, they used the API interface directly for external component registration, only one
07:43:44 remaining was sec VPN use cases but honey you conformed, they can use the API interface directly bypassing your UI and server. In that case, we can.
07:43:58 We have no active, the use case you leveraging the ESL. So that's why I see me. Otherwise, Amy. Second, they need to file for exception for the security, checking vulnerability.
07:44:14 So I think if we can remove the ESL or UI in server and then she doesn't have to or to see that in half to five exception. Amy you have any additional input here.
07:44:25 Oh, no, not really, um, I would like to to see to approve just removing SR from the release beyond has done a great job of running this down to finding out that nobody actually needs it anymore.
07:44:37 So, makes the release, tiny, slight bit smaller, and removes a bunch of vulnerabilities
07:44:47 and Christopher confirm that he wants to approve it and he can be moved.
07:44:55 I'm more than happy to remove one more Helm chart
07:45:02 stuff but we need to decide on om what that means. Does that mean only the disabling so in to put the, the helm chart on disable or do we remove the helm chart or put that into another folder whatever where we if we would like to reactivate it again.
07:45:22 From the om delivery. This is one issue I think I would like to clarify because, should it be on purpose. If someone wants that still that it can be activated by at the helm chart so by by ROML chart by activating it, or should it not be available at
07:45:46 all in the helm charts.
07:45:50 are. So, the reason why we are considering removing that is because of lack of maintenance right so the team is unable to fix security issues. So, in my opinion, keeping a dead code, because that that would be the fact that code that we are never testing
07:46:08 in the repo, that we know that contains security vulnerabilities, would be able to be unwise. That's why I would just recommend doing get around and removing all the health plans, if someone really wants that.
07:46:23 It's all in the geek, right, nothing is lost, you may always revert that commit and, you know, take care of all the vulnerabilities and deployed in your lab.
07:46:37 Yeah, and also do your beer can confirm but anything we can do with ESRI, they can do we do AI interfaces so actually from your device, they can you know safely on the movie so I just thought, yeah.
07:46:51 Of course we would then in the documentation project will have to dig through our code, especially the end to end code. I think we have some chapters in the documentation, but he is our is mentioned Of course we will have them if 40 instead is double
07:47:09 release to, let's say, check the code or to check the the rst files and we moved in everything which is showing you is our gooey or something like that.
07:47:22 Yeah.
07:47:24 Okay, but that's fine, I agree.
07:47:28 So I believe we should update denotes unless DSC wants to make a decision on that.
07:48:14 So is, is what I'm just want to confirm my, what I'm hearing it Do we have an agreement from the TASC that ESRUINESR server, or to be removed from own app, beginning with this demo.
07:48:35 Yes.
07:48:41 Sorry, what does that mean in the context of project lifecycle states.
07:48:48 Well, it is those are both sub components of AI.
07:48:57 Both of the repos have been
07:49:02 have been set to read only for over a year.
07:49:08 So it's, it's not a standalone project lifecycle doesn't directly apply to me.
07:49:20 Okay, I'm going to mark that as an agree.
07:49:26 Yes.
07:49:57 Okay.
07:50:02 Anything else release related.
07:50:15 Okay, Then let's
07:50:27 see I was, I was on mute. I just want to mention that I'm going to be on holiday. Next week. So, if you have any questions or anything that you need for me to do, please let me know by Friday.
07:50:35 Thank you.
07:50:37 One question, David. What's about the.
07:50:41 I know we have this discussion and on Monday. What's about the maintenance release a phenomenal.
07:50:50 Yeah, it's, it's, you can refer to the status weekly update, but just in summary, excuse me, we're down to about 10 issues now and I'm, I'm pushing on the, the issue owners to wrap those up, as well as to asking
07:51:16 folks not to add any additional initiatives so yeah so right now it's basically down to, pushing on these real issue owners to.
07:51:33 And I believe most of these are related to policy. So, getting those wrapped up.
07:51:41 And I don't know.
07:51:43 Chris staff or anyone from the integration team do you have any additional thoughts about the maintenance release of Christophe is on.
07:52:01 So that does that answer your question address. Yeah, I think that means, so we will be off for one week so more than one week, so we don't expect to have the maintenance release release out during your vacation I guess then.
07:52:23 So most likely you would need to agree then when you are back from holidays.
07:52:23 Yeah, everything is delivered and not not necessarily, you know if if the TASC believes that everything has been completed.
07:52:37 Then, you know the integration team is more than capable of, you know, wrapping up the release and delivering that so I don't think it's necessary for me to be present to complete the release, but more than likely will still be wrapping it up by the time
07:52:54 I get back because yeah so we're probably looking at not completing the maintenance release until probably the third or fourth week in August is my guess.
07:53:08 Okay.
07:53:17 Okay, Then moving on.
07:53:24 Anything else fit related.
07:53:32 From my side Guinea.
07:53:41 Okay, I'm wondering for lab, the
07:53:51 security update is is taking place right now labs down.
07:53:56 We ran out of
07:54:10 our luck ran out there. So they're forced to do it.
07:54:07 The new lab hardware.
07:54:10 Steve IRA from LFIP has received the
07:54:20 has received the quotes that he needs from colo facilities.
07:54:25 And this is being ramped up needs to go to the.
07:54:29 lf board for budget approval.
07:54:32 We had a finance committee meeting that was scheduled for Friday and I just found out folks aren't going to be available, so that needs to be changed, that's probably going to be pushed two weeks
07:54:47 on that on that decision.
07:54:52 Steam good from Wind River said that, once the new gear setup, they'll be able to continue providing the type of remote support that they've been providing to the community in the past.
07:55:06 So that's good.
07:55:08 But we will be reliant on wherever the colo is for folks, actually, at that colo to be providing us with the direct
07:55:21 hands and eyes service on site that Wind River won't be able to provide so that is the current update.
07:55:46 Just, just.
07:55:49 Can you repeat again for the security patching which was scheduled yesterday.
07:55:54 Will they will send a note when it's done or has it been done and completed.
07:56:02 Or it was just a few hours yesterday.
07:56:06 I didn't see any notification when it will be completed so media expect it was a few days or one week just to have a notion of all the timeline.
07:56:19 Are we need to add them
07:56:23 on here let's see if I can find different male.
07:56:32 So they put in the last extension.
07:56:37 And that was,
07:56:42 that was denied.
07:56:54 Let's see here I'm reading, another male
07:57:00 new digs current service out of service tried to report a truncated security fix to limp along for another month or two.
07:57:09 I don't, I
07:57:12 don't have clear line of sight to when it will be back up.
07:57:23 You been said that. Let us know when
07:57:26 when things for backup and I haven't seen
07:57:30 a response to that. So,
07:57:38 I believe, good deal deadline was the seven, they need to finish everything by this weekend worst case scenario. Yeah.
07:57:48 That's That's my understanding.
07:57:50 Can we have these are still be on the call on Monday.
07:57:55 Okay.
07:58:26 So good. Oh,
07:58:35 thank you.
07:58:39 The word award still to be done.
07:58:44 And if you can click on the link, because I would like to discuss the, the action item which was captured during the event catalog find my slides are we go directly to the source.
07:59:01 To start with, eight. So, when we have been trying to provide some quick notes during the last Stephen interview. and I think there was some action item that was tucked as well as part of the challenge that we have not defined during the different presentations,
07:59:24 and I just wanted to see there is so much
07:59:32 that we need to follow up on to look at together so the first item that was captured.
07:59:39 And I'm only looking at the challenge so I hope I will not miss any looking at everything with you though.
07:59:48 So we, the challenge was a boat for giving up for entrepreneurs, was able to find that we deployed my my CFO Is there anybody to deploy McMahon Vienna.
08:00:00 This question has been answered as fast of own up on the price that falls, you to the availability of the magma sinovation. Somehow we have tried to put a few of magma own up integration with the magma VNF, there is still on the know of anybody the date.
08:00:20 Concerning the magma cnet's so we just plan to consignor the magma VNF, the magma Vf have one five did not include any 5g capabilities.
08:00:33 So we try to understand from the maca community a little bit more better their hope map so that's that's the feedback I wanted to share maybe other people wants to provide more updatable distrust items.
08:00:51 Okay, thing that was the only comment from the session of the eighth decision of the ninth.
08:00:59 Let's meet with something particular.
08:01:03 So there was a present I don't think I saw Magnus on the bridge today maybe I can be wrong, but they have been some discussion in the context of the network management committee coordination, and they were a couple of action items.
08:01:20 so if anybody who's working with Magnus, that could provide an update.
08:01:41 Otherwise we should translate the challenge into something we need to follow up with Magnus,
08:01:43 and why you are doing this. Kenny are moving to the other ask which was raised by the, the CNN for crude Nazis, but also for the reminder we are meeting every Thursday before the end goal.
08:02:04 And we are currently working on the, on the messaging and the that we want to bring to the industry about what we are doing. Nevertheless during the June, even we were doing a cool, right to the CNN vendors, because up to now we have the five, five PZCCNF
08:02:27 that we are trying to use to demonstrate some of our own app use case. And I want you to take the opportunity of this meeting to make again a call to the CNS vendors to hatred.
08:02:50 So at least we can extend, or at least they can tell us what type of requirements, we need to consider a spot the wound up to onboard their CNS also its infancy, also orchestrate.
08:03:01 So, so no action to anybody that we can capture together, but it's really a cold that we, we want to hate the hate It's not the first time we want to work within a vendors in the context of of castles.
08:03:16 And I know we have some DNS task force members, is there anything else they would like to add regarding this cold.
08:03:26 Nope.
08:03:29 And as, as always, we have a hitch hope map where we want to progress in in this domain. We haven't done define Cooper of single at the time that we could do like another sentence control loop plan and integration with z Villa, do some merging negative,
08:03:51 and as the flow.
08:03:53 So, if anybody is interested because the roadmap is quite interesting. So, just feel free to join the task force.
08:04:02 Either the one of the CNS because we're speaking here the CNS so we, again, one hour before the call on Thursday.
08:04:12 And we had also see me now slow between the senate productive Task Force and younger crisis force.
08:04:20 but I would suggest maybe help us on the cloud native cnn first, so we can benefit from what we are doing there for the enterprise use case as well.
08:04:31 Does anybody from the cloud native DNS customer wants to add anything to what I've just said.
08:04:41 Cassidy one input about the st.
08:04:44 Find me.
08:04:46 Yes, yes please do. Bianca what one thing is to the Nokia and so the companies they are presenting the ASD information model to orient Working Group, 10 and six.
08:05:01 So, looks like. This is one of the input looks like, Oregon, they are doing some specification. So, if they adapt the ASD probably they want to walk on the inflammation model and data on the data model.
08:05:20 And for creating some specification there means the only upside. We leveraging the as the specification, probably.
08:05:31 I'm not sure all in and they're going to thoroughly define the specification are we are we still, we are still contributing to Oregon and then walking through 10 and six.
08:05:41 That means, in that case, owner, we are aligned, like as we align se we align with the origin as the specification, or we would we want to step up and then we can know participating the specification, as a co co author, or.
08:06:03 That's the one that's currently we are you know owner. We are contributing DST information model heavily. And then also, and then but anyway so who's going to publish the specification this one open question.
08:06:20 Oh, thank you, beyond to bring that so I think, or Ohio own appraisal is with us today, as well as his cool team members so I'm referring to Timo, and I know sugar was also standing up as well as order to act as a liaison with the Orlando now community.
08:06:42 Is it something you can also share with the open source community teams.
08:06:49 Can we pick an action for you.
08:06:54 Are you talking to me.
08:06:56 No, no I'm talking to two Timo who is own up organism.
08:07:01 And also, and I see just did a piece.
08:07:06 I know
08:07:09 your idea, sorry.
08:07:12 So, you can do.
08:07:15 Or maybe it's already under discussion, the feedback from beyond, beyond.
08:07:24 I have to admit that I don't know, it's eight hours into work after vacation so not really up to speed, but I can check with, I think we can we can discuss this.
08:07:37 You'll be on offline and make sure that
08:07:43 I think we are working together definitely and then just owners for specification this question. Okay. Yeah.
08:07:50 Okay, and welcome back to you.
08:07:59 Thank you very much.
08:08:02 But I have to say that again was really representing you well, so no worries you were fully covered during your holidays and we hope we hope you have a lovely time with family, that's the most important.
08:08:15 Thanks, attach that to W.
08:08:19 Yes, please do, but that to them. Yeah.
08:08:24 So the next item. I hope vj did not disappear. It was one of your action items that was discussed during the LDC confirmation.
08:08:37 Do you want to add any updates, provide any update BJ about the performative
08:08:46 dramatis integration, not having specific work done on this or this release there was some discussion to add support for it but I think there was part of the CF flow discussion but I did not
08:09:02 progress for beyond that initial discussion we had, Catherine, but he had the transformation work is ongoing. I mean, As the other open items.
08:09:12 I mean, we had we had a good good support from data so the committee to complete on some of the transformation initiatives we had started so we are progressing well we are on target to complete what we had planned for Istanbul, so that that that workers
08:09:25 going forward, feel for the property as they need to see if there's a specific use case.
08:09:31 In own RP we need to add for PC enhancement to that.
08:09:38 Okay, so that's all good, then I'm moving to the security activities. I'm saying that don't see any action to Joe would be infected.
08:09:53 Know that by done a great super is available, I think there is nothing particular except if I'm wrong.
08:10:01 By Well, a meeting.
08:10:05 Don't think we've covered everything Catherine on earlier things so we're just progressing along. Only one thing for the TASC to know we opened tickets for we opened JIRA tickets for the projects that need to submit waivers or fix problems that are being
08:10:20 found in the integration security tests. So that's all progressing.
08:10:25 Okay, that's great.
08:10:27 Thank you, Amy for the date.
08:10:30 And I think that's what the only items from the June 9 Let's move to June, then back to the DNS.
08:10:40 Yeah, same common, we need you see a vendors to help us to understand how you're behaving, especially how we cannot get paid for will not come back on that.
08:10:57 Yes, the open license is not Apache, I don't think we took an action yet double that. So the question was, I believe, own Abby's Apache to that ONOBSD or cannot remember.
08:11:14 Is it, is it something.
08:11:17 We need to talk again with the Sikh community.
08:11:22 I'm looking at the license issue.
08:11:28 Well, I heard
08:11:32 last Thursday.
08:11:36 Maybe it was this week I don't remember might have been this week that Iran is introducing a third type of license
08:11:51 that I don't have enough information about yet.
08:11:55 So, it seemed like
08:12:00 rather than than simplifying things things may have just gotten more complex so I.
08:12:07 That's as much information as I have on it I need to dig into it.
08:12:13 Would you mind to target because since they were concerned.
08:12:18 He's doing a session we, we want to maybe track it and update the community when we have additional.
08:12:27 Yep.
08:12:30 Okay.
08:12:33 And there was also a request,
08:12:38 especially for people who are more and more using some own app component in production.
08:12:45 It to have justification on the upgrade from one village to another one on the house and Michelle is it something we would like to discuss the integration team I don't recall we have that in the whole map, maybe we have.
08:13:04 And you go about these items.
08:13:11 Could you repeat shortly because I was just typing No, no.
08:13:18 Well, nice being here.
08:13:20 So yeah, we have been doing a lot of progress is that began to functionality over by Om.
08:13:26 Nevertheless, we are still challenge to have a kind of certification to upgrade from one end to another one.
08:13:35 I think we might want to add this topics as part of the indignation discussion and see if it is part of the roadmap probably not for a stumble, but at least we want to talk and discuss and maybe collaborate with the TPM.
08:13:58 Yeah, I do think, yes I think that would be really important I think all of us which are targeting for production definitely that an upgrade.
08:14:17 Certification would be would be would would be really great and we should focus on that yet that's what
08:14:16 does it mean that they are mature only for my tell nothing but the beginning of the show no donation and also have certification on it, that will be adding value.
08:14:26 So I wouldn't market festival agenda on Wednesday, Andrea, and we just put in my.
08:14:35 Oh, Next one day, which is 11.
08:14:38 So if people wants to join the integration team it's happening every Wednesday.
08:14:50 I don't have the time, in my UTC 1pm. Okay, thank you, thank you, to feel free to join us, we always need great demo processor, or I would say full stack developer with great the same mindset.
08:15:02 Okay.
08:15:06 Just put the know.
08:15:18 Alright, what's next on the list.
08:15:23 Oh.
08:15:25 The next one is indeed about the own app integration ppl.
08:15:31 So that was one of the biggest concern both currently.
08:15:38 We have a couple of companies couple carriers working together so YDT, China Telecom, orange, of course.
08:15:51 Bell Canada and also at&t has committed and also Verizon so refresh f committed to work and support the team.
08:16:01 When they will need it. It's working with the sofa, at least from my perspective, Don is a representative to help us if we have an issue in the APAC time zone so thank you again.
08:16:17 And then we are meeting every Wednesday. So, for the women, the identity solution is working well. But we still hope at one point maybe to have one PDF or two ppl because the scope of the own app integration is not small.
08:16:35 So more to come in the coming months, but I would say we survived nicely.
08:16:40 I don't know if any of the team members want to, to bring anything at this stage but I think we are doing well.
08:16:52 As I can say, Okay.
08:16:54 The other question that we are saying to the CBC was how, what will be the future own app and what will be the rules so I think we started to answer to some of it of this question.
08:17:07 First of all, thanks to the positioning of some own app component as part of the service management orchestrator. And as you can guess a lot of young girls why we are still working on a network automation we are starting to shift to the industrialization
08:17:24 of the hand.
08:17:25 So it's an opportunity for us having someone a component as part of the service management orchestrator to already the past or the future
08:17:38 as well, and then the uniform The prize is also given us a lot of consideration so concretely, we don't have a list of feature that we planned from today, up to 25 that's true we don't have concrete premium hoop map like I would love that we have.
08:17:57 But we have a lot of opportunities which will reposition own app for future football so they're still an action items on the requirement architecture subcommittee to help us to look at the details, but the task force.
08:18:13 Really, including the senate passport as well. Help us to be this vision so I think we are still this as the TSP a mission to ensure that the own app in 2025 will have been a mission.
08:18:29 That's something we need to continue to track and to implement.
08:18:32 I don't know if anybody from the DSC want to add something regarding this topic.
08:18:45 All right. And the next item was cc SDK as DNC is done is still with us the money.
08:18:57 I saw him before.
08:19:01 don't see him anymore.
08:19:06 So I think there's no particular action, it was just some findings challenge that they were sharing.
08:19:14 And that's it. So, we ever review all the items which was captured during the last event, I think it was important to, at one point, sit down and follow up, because otherwise it makes no sense that people provide constructive feedback and we don't consider
08:19:30 it.
08:19:32 We are still some continuity of some of items and we we have tagged up thanks to Kenny today, and we expect additional follow up in the coming weeks.
08:19:44 I will not say days because some countries are still on vacation or they just found their vacation to September we probably will look at the will, we will look again at the remaining action items to see where we are.
08:20:02 The phone regarding the review of the daily summaries from the elephant even of June. Back to you, Kenny.
08:20:13 Okay.
08:20:15 The only thing.
08:20:17 We've got left on the agenda reminder about one summit coming up, and I am blocking everything out to finish PSC to auto documentation, my board stuff done.
08:20:35 And I am going to be focused on that now.
08:20:42 And I get skinny, in one week or so, we will create the pages so people will be able to nominate their, their.
08:20:54 We are still back where we nominate for the owner worked while a couple of things should have generated automatically. So maybe next week we could already announce the winner for the hour, we can based on the matrix that we are collecting.
08:21:14 Yep, that can be done.
08:21:16 Yep.
08:21:20 Good. Anything else from anybody.
08:21:28 I'm glad we were able to cover all the topics, except except, including the daily summaries because I've been trying to put on the agenda, couple of times.
08:21:37 And we never succeed to look at it.
08:21:40 And last time I had to ask myself so my apologize for that but at least we make it.
08:21:46 So I just want to take the opportunity to welcome back, all of the members who I hope you have enjoyed their vacation.
08:21:55 And if you didn't take your holidays via whoop you will enjoy soon to take some time off.