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:58:41 From  Fernando (Fred) Oliveira  to  Everyone:
    #info Fred Oliveira, Verizon
06:58:58 From  Alla Goldner  to  Everyone:
    #info Alla Goldner, Amdocs
06:59:03 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
06:59:25 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT
06:59:33 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #info Yuanhong Deng, China Mobile
06:59:44 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
07:00:03 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
07:00:25 From  Sai Seshu  to  Everyone:
    #info Seshu, huawei
07:00:30 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #info N. K. Shankar, STL
07:01:00 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang, Wind River
07:01:29 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
07:01:46 From  Ranny HAIBY (Samsung)  to  Everyone:
    #info Ranny Haiby, Samsung
07:02:09 From  Amy Zwarico  to  Everyone:
    #info Amy Zwarico, AT&T - proxy for Catherine Lefevre
07:05:06 From  Magnus Buhrgard (Ericsson)  to  Everyone:
    #info Magnus Buhrgard (Ericsson)
07:05:44 From  Kenny PAUL (LFN)  to  Everyone:
    @magnus thanks
07:07:19 From  Catherine Lefevre  to  Everyone:
    #info, Catherine Lefevre, AT&T
07:08:51 From  Kenny PAUL (LFN)  to  Everyone:
    @catherine thanks.
07:15:25 From  Amy Zwarico  to  Everyone:
    sdnc-callhome is exposing a non-ssl endpoint
07:16:05 From  Amy Zwarico  to  Everyone:
    artifact-broker does not have an exception in versions_xfail.txt
07:26:20 From  David McBride  to  Everyone:
    #VOTE Does the TSC approve the following recommendations: 1) Approve RC milestone with condition that remaining release management tasks are resolved by Sign Off.  2) Move Sign Off out one week to Nov 4
07:26:30 From  Andreas GEISSLER (DT)  to  Everyone:
    #vote +1
07:26:32 From  Fernando (Fred) Oliveira  to  Everyone:
    #vote +1
07:26:36 From  Alla Goldner  to  Everyone:
    #vote +1
07:26:38 From  Sai Seshu  to  Everyone:
    #vote h
07:26:41 From  Sai Seshu  to  Everyone:
    +
07:26:41 From  Ranny HAIBY (Samsung)  to  Everyone:
    #vote +1
07:26:42 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #vote +1
07:26:43 From  Bruno Sakoto  to  Everyone:
    #vote +1
07:26:44 From  Magnus Buhrgard (Ericsson)  to  Everyone:
    #vote +1
07:26:47 From  Eric Debeau  to  Everyone:
    #vote +1
07:26:47 From  Timo Perala (Nokia)  to  Everyone:
    #vote +1
07:26:47 From  Sai Seshu  to  Everyone:
    #vote +1
07:26:48 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #vote +1
07:26:51 From  Sai Seshu  to  Everyone:
    <smilie>
07:27:04 From  Catherine Lefevre  to  Everyone:
    #vote +1
07:27:38 From  Kenny PAUL (LFN)  to  Everyone:
    #endvote
07:28:22 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED the TSC approves the following recommendations: 1) Approve RC milestone with condition that remaining release management tasks are resolved by Sign Off.  2) Move Sign Off out one week to Nov 4
07:29:09 From  Catherine Lefevre  to  Everyone:
    These are great feedback !
07:32:30 From  Amy Zwarico  to  Everyone:
    #info Amy Zwarico is no longer Catherine's proxy
07:34:55 From  Thomas KULIK (DT)  to  Everyone:
    Changes so far because of lfdocs-conf update: https://jira.onap.org/browse/DOC-765
08:06:45 From  Amy Zwarico  to  Everyone:
    pronounced "leaf"

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:01:35 Also the mobile hotspot.
07:01:38 Okay will do.
07:01:40 Thank you, sir.
07:01:42 All right, we're now remembering.
07:01:45 Okay.
07:01:48 creasing assist reminder everybody's muted when you come in.
07:01:54 Please keep yourself muted, unless you are speaking.
07:02:12 If you're using a phone you can use star six to unmute yourself. And if you happen to send me a private chat message, it will become part of the public record because I cut and paste the minutes as a or the chat window as is.
07:02:14 into
07:02:17 into the
07:02:21 meeting minutes. Oh wow.
07:02:24 Lack of sleep folks My apologies.
07:02:27 We'll start off by talking about our antitrust policy notice policy is important. And we have multiple companies, participating in these meetings that are potentially industry competitors.
07:02:38 This is linked from the LS and all of the project websites.
07:02:43 If you have any questions, please contact your company's legal counsel.
07:02:46 members of the lF may also contact Andrew Grove with the sun Gizmo up to Grove LLP, which provides legal counsel to the lF and get who came and Lanny
07:03:02 got Timo got Randy and then
07:03:06 at maybe in China.
07:03:20 Okay, let me stop sharing.
07:03:30 And let me try sharing
07:03:35 this screen.
07:03:45 Okay, I'm talking about Istanbul.
07:03:50 And the recommendation here.
07:03:53 We've got some IP issues that we will be discussing scheduled readout from the architecture subcommittee.
07:04:05 And I don't know if there's any others that would. We're planning on doing a readout today, or, or, at a future date, unless it's a future date you can just type it into the chat window and then all incorporated here make sure it gets put on, put on the
07:04:24 Put on the agenda, because it is chocolate I thought I thought I was presenting today.
07:04:30 Yes you are.
07:04:32 Okay.
07:04:33 Yes Thank you sir.
07:04:40 circle back on the election.
07:04:44 Discuss the life cycle changes to the community document.
07:04:49 And then question that I've got about, when we get down to avenge question about the description we have and whether we want to keep it. Anything else anything else to add.
07:05:05 Okay, I'll stop sharing and turn it over to David
07:05:10 right thanks Kenny.
07:05:17 Alright, so let's start out just looking at the schedule to, kind of, refresh our memory of where we're at.
07:05:29 So, RC was originally planned for the 14th which was a week ago today.
07:05:38 You'll recall that we looked at status, we go and the conclusion was we still had some work to do. We agreed to look at the status again on Monday during the meeting.
07:05:54 And again, there was still some work to do and also some complications, due to problems with Jenkins and also the documentation build.
07:06:06 So, we decided to look at it again today, which we will be doing.
07:06:18 So, if we look at the milestone status. You can see that a lot of progress has been made.
07:06:30 All of the requirement owner tasks have been completed so we're 100% there so thank you requirement owners.
07:06:41 And then if we look at the.
07:06:44 release management tasks with projects, we see that we're at about 95% complete so a lot of great progress in the last week so thank you for everyone's hard work.
07:07:03 We do still seem to be lagging a little bit on the X testing results.
07:07:13 We looked at these on.
07:07:17 Let's see, I guess.
07:07:20 If we look at these right oh I guess I was looking at these with Catherine yesterday.
07:07:27 So it doesn't appear that we had.
07:07:32 Fresh results for two days. and we're still seeing
07:07:38 issues with smoke use cases and security. And it doesn't appear that we've recovered, to the levels that we were at back on the 13th. And I know when we talked about this on Monday at the TL meeting someone think from the integration team told me that
07:08:06 they had to rebuild and that was slow down because of some issues with Jenkins.
07:08:16 Can Michelle or someone from the integration team can you update us on status.
07:08:24 I don't know whether Michelle. Michelle will join I just picked him under the last year. So, as I know, just also from from from from server. So there were issues on the, on one hand on the orange lap, and we have as well in the in DT bigger issues with
07:08:43 our hardware therefore also on our case and or in our environments. Since a couple of days, the belts and the tests have not been executed. So I don't know whether the, the test or the bad test results are still so in the orange lab, still related to
07:09:05 the new setup of the lab.
07:09:08 This is what I understood from from from server, from the om team that they had to had a bigger issue on their laps.
07:09:16 So, but more I cannot say at the moment because I was I'm also was was busy in our laps with performing something.
07:09:25 This is all what I know and unfortunately I could not participate integration meeting this week so no no way that someone else was there.
07:09:33 All right. Thanks Andreas anyone else who's familiar with the orange lab can comment.
07:09:44 Again share what they know yes is there were some programs and infrastructure. So we had some issues but I can check in a few minutes if you want to.
07:09:54 Okay, thank you.
07:10:01 Okay.
07:10:16 So, the status with the orange lab is somewhat unknown at the moment so hopefully we'll get some additional details about that. Looking at the integration tests status,
07:10:26 showing good progress, roughly half of the requirements of completed testing.
07:10:38 And the remainder seem to be released they claim that they're over 50% It looks like we do have some outliers here.
07:10:54 Anyone here associated with requirement night for to
07:11:00 the NFL cm.
07:11:06 And they've been climbing so it's not a big deal to find that ISIS, there's some.
07:11:16 Sorry. Can you say that again, I missed that
07:11:26 you please repeat.
07:11:28 Yeah, they've been some useful co speaking so this is not the big requirements. So, I think, in one week it can be completed.
07:11:35 Okay. All right. Could you update the, the requirement the status on requirement to reflect that.
07:11:44 When you get a chance.
07:11:47 Okay. Yeah, I will.
07:11:49 Okay, thank you.
07:11:55 And D Pika, or anyone associated with requirement 940,
07:12:03 or, or 937.
07:12:10 Okay, I'll follow up with Deepika.
07:12:13 And then I just,
07:12:16 you know, earlier that 948.
07:12:22 Although it says time to complete a three to five days still shows test status it's not started I sent an email to Krishna, asking him to update the integration test status for this one.
07:12:37 But all in all making making good progress here.
07:12:43 Okay.
07:12:47 So, uh, Hey, sorry. In a second to get off mute, I've been looking at the security results.
07:12:53 The versions, and that would be for the Python and Java, there's only one, there's only one repo that that has a bad status on that that's missing an exception and that's for the artifact broker repo, so I don't know who needs to file that.
07:13:17 But if they can get that into if they can just submit it changed the versions ex failed at txt, that that will clear up that one.
07:13:23 And so, and the other one is an SSL endpoint and that I'm wondering if something didn't get pushed yet I think that the only one that was remaining
07:13:33 that I saw that Dan Timoney actually did submit the chat they change so, and it was approved so that may not have been merged yet so I think we're pretty good.
07:13:43 Although the security is not show it is the security stuff is is very very minor at this point it just reflects as being more catastrophic is.
07:13:54 Thanks for bringing that up Amy I actually was going to add that, that page to the agenda and slipped my mind. Do you have the link to that, Andy I think it would probably be worthwhile so the link to which do you need the link to the integration blocking
07:14:12 issues, page, I assume that's what you were looking at. No, I was not looking at that I was actually looking at the tests and going back and seeing what the test results were.
07:14:21 Okay. All right.
07:14:24 So
07:14:29 Chandra service monsoon so yes we still see that some programming now laps or so.
07:14:41 The launch a new, new Tesla just, yeah. The only thing on but just. We are so unfortunately when when our infrastructure was okay. This weekend we face associate some issue on the next use.
07:14:54 That was not accessible so we are not very lucky.
07:14:59 But when user stories as farmers don't are the good team and as you shoot a quick video.
07:15:08 So, so I checked it out on the for the non SSL endpoints. There is one, there's only one.
07:15:18 There's only one content container that is exposing a non SSL endpoint that's not accounted for. and that's SDN see call home.
07:15:26 And I've put it in the chat.
07:15:30 So basically we have to the only reason that security is not at 100% is because we have artifact broker has doesn't have an exception and versions x fail and SDNC call home does not have an exception, and the corresponding file I'd have to look up what
07:15:46 the actual name of that is
07:16:00 what down found the page.
07:16:09 And we've raised the artifacts broker multiple times before.
07:16:15 Again, I'd have to go back in my notes, probably a month or two to figure out who owns artifact broker.
07:16:22 Okay. Is anyone familiar with that component artifact broker.
07:16:35 It belongs to them and maybe I will explain a little bit. What I know there is parts in the room with the changes for the multi cloud components.
07:16:46 Among them there is a change for the artifact broker problem is that this part is failing for other images, then artifact broker.
07:16:55 So, if we would separate this change for the active and broker phone dispatch.
07:17:02 It should be good to go. Right.
07:17:05 Great, yeah because the only problem with the artifact broker, was that it, it's not that it's not using a current for the A, and I believe it was a Java version is fixed it.
07:17:25 So in that one there is a patch, with the good version of that that broker, when it where it is fixed unfortunately this patch is not merged in all due to the problems.
07:17:35 Okay, thank you for other images in the same patch and use that artifact broker as part of multi cloud.
07:17:44 Yeah.
07:17:45 Thanks so much.
07:17:47 All right. Alright, so I guess that from a security standpoint the path forward. If you can't get the good version to merge then I would say that just file an exception and versions x fail.
07:18:03 That will clear up the pot that'll that'll clear up that problem I mean it doesn't fix the problem but at least it doesn't show up is failing. We know, we know that it's still a problem to be fixed in the future release.
07:18:23 And then like I said, the other one is, the other one is a non SSL endpoint.
07:18:28 And that happens to be the SDN see call home.
07:18:52 And the issue with artifact broker is the is Java or Python
07:19:01 me. Yes, it was a Java.
07:19:04 Java issue, it's showing up is still having Java eight in in the container, all that it shows up as having built job aid and Java 11.
07:19:14 But they do have a fix for it, it's just there. They've got other problems.
07:19:30 Okay and then the other issue.
07:19:34 The other issue is a non SSL and point in SDN see called home.
07:19:45 Sorry, what was the.
07:19:51 What was the component again.
07:19:54 For this, the, the container, the container is SD and c dash call home.
07:20:02 And I put it in the chat.
07:20:06 Okay.
07:20:09 All right. Thank you.
07:20:13 Okay, so in terms of recommendation.
07:20:20 Going back to the schedule again. What I'm suggesting is that the TASC approve our RC with condition that the remaining.
07:20:37 Think Nine, eight or nine issues, be resolved prior to sign off.
07:20:42 And that we move sign off out one week to November 2,
07:20:52 any comments, questions, concerns about that.
07:21:02 So, I don't have any concern about the date right i think everybody's currently working to ensure that we are delivering as expected the release with the quality aspect as well.
07:21:19 We just need to continue to monitor, because I understand what has been discussed and bro by Andreas any week. So I hope we can have back to normal, because we figure we're extremely well.
07:21:35 On the night. We're extremely well a couple of days ago. So, based on what they have expressed I think it's.
07:21:42 We need to work on young woman but it's not necessary, but the person data we got it's not necessarily related to the application itself.
07:21:54 But I believe in one week, we would have a better view to confirm the statements that the application, have still a good percentage from a news check smoke test and security.
07:22:08 But we need to give time to the integration team to prepare the default lap. So that's my understanding and based on that I think we can go Sue, except if my understanding is not correct.
07:22:30 So, it can end on the US and Michelle I will finish it is my understanding is correct.
07:22:39 Yes, I see So, yeah, unfortunately me How could not join here, just send me a message.
07:22:47 Yeah.
07:22:50 Do you see the problem at the moment. Yeah, I think that's a problem at the moment so it's right to the last the last I mean quite successful test was on the 16th, and all the rest are then somehow related to this instability issues.
07:23:09 Yeah, yeah.
07:23:09 Yes, so do you think that potentially.
07:23:31 We will have a confirmation of not in one week time. Do you think that we hope we hope that we can fix that until that. Yeah, I would say, okay, at least so
07:23:28 let's have a checkpoint done next week so it gives one week to confirm that we are indeed on the right track. Thank you, Andrea for the clarification, and the confirmation.
07:23:46 All right, Kenny should we have a vote on the recommendation.
07:23:59 Kenny Are you on mute.
07:24:07 I lost my mouse.
07:24:11 Closer weeks on.
07:24:13 I'm like oh my god what am.
07:24:18 Oh my god. Yes, we should put this to a vote.
07:24:24 And
07:24:30 yes, we can just use the text that we've got here
07:24:41 under your recommendation.
07:25:00 And my mouse was gone again.
07:25:04 You want me to put it in. Yeah, you can. I think I don't know what's going on.
07:25:12 This is a hardwired mouse, so it's not like the batteries are bad.
07:25:16 Right.
07:26:23 Okay. The vote text is in the chat.
07:26:28 Please let me your load LOTE
07:26:34 prefix it by lb votes.
07:26:38 And plus one minus one or zero.
07:26:46 H is not a valid.
07:27:03 Come on, David.
07:27:08 Awesome.
07:27:09 To me,
07:27:13 my mouth seems to be working again.
07:27:19 I don't know what the issue was David thanks for kicking off the vote.
07:27:26 Okay.
07:27:27 Good. Another 10 seconds.
07:27:36 4321.
07:27:43 Okay.
07:27:44 That is approved Thank you folks.
07:27:54 And by the way, I received just the links for some of the staging results from my for me. Whoa, and he confirms that at least the results look pretty good as we had it before, it's just these daily results which we should have, where we have these basically
07:28:15 the problems in the orange in the DT labs, these have these kinds of bad results in their quotation marks.
07:28:24 So, that means also the the the the gating results show, in most cases, nearly hundred percent on the smoke use cases and the chance of.
07:28:37 It's just to make at least to confirm that it's really related.
07:28:43 In most cases on the infrastructure problems we have. Yep.
07:28:55 Thanks Andrea so we would try to fix this until next week so that's okay. I know I'm a nice got whether it was you or someone else mentioned that there was part of the problem with bringing the lab, back up was related to issues with Jenkins.
07:29:09 And so, are, are those issues with Jenkins resolved.
07:29:24 So I will nap is not based on jack Jenkins, therefore I cannot tell anything about that. So, therefore, maybe 10.
07:29:35 All right. Okay, Kenny, I think that's it for me.
07:29:41 Okay.
07:29:49 shift it to discussion of the tickets, we've got open.
07:29:58 Starting with
07:30:03 23085.
07:30:10 Thank you want to share your findings on that.
07:30:24 and bang, you're muted,
07:30:32 or Jess, or, Sorry, which one.
07:30:40 Which one was it related to the, the issue that Sylvan reported with a Nexus emerges, the one that dates to an issue in the past, can you share your comments on that.
07:30:56 I haven't looked at this phone number of times now with the tickets that have been raised. We have been looking at the cleanup script was cleaning up all the values in supposed to be gone.
07:31:13 I've also raised issue with solar type, and they kind of replied back to us that we shouldn't use our own script we should just use the default ones, but those will not delete the images we want to delete.
07:31:27 On top of that, three weeks later, we got the patch from Sona top type which kind of fixed part of our issue.
07:31:40 Was that something with the images disappearing, which I thought was very, very good so after after, after I loaded up calm.
07:31:48 That was number of weeks ago we haven't really had too many of these images disappearing was just last week. We've got the new ticket on that.
07:31:58 And that is again correlated with Jenkins and Nexus, having issues of falling over a little bit.
07:32:06 Yeah, and we've had a lot of those problems. Last weekend early this week, which their final migration. Oh, boldness and Jenkins, new hardware instances, and so on but host is this Monday.
07:32:22 So, I would think that the problems that we were facing before that migration happen and a little bit of issues after the migration happened that were Russell, also on Monday, that could have contributed to this problem coming back.
07:32:37 Also on Monday, that could have contributed to this problem coming back. But on regards to Jenkins been an excuse after the migration, everything seems to be pretty stable. So we're hoping that this problem doesn't happen in.
07:32:48 And I just want to clarify till then nice Nicole, this is not happening with release images right this is only with snapshot images.
07:33:03 That's all they've told me a snapshot started. Okay good, that if you would have happened would be a bigger problem but, yeah, a Eric is helping us looking into that.
07:33:21 Okay. Any questions on that one.
07:33:26 Okay, moving on to 2368.
07:33:38 That is the one related to the documentation bank this working with Cedric on this one. Thank you want to share your comments.
07:33:46 Cedric on the line or.
07:33:51 Um, I don't see him I know that you had mentioned that he had said that he might be able to join later so maybe I'll circle back on this one, what I understand is that the configuration for how to generate the documents have not really been touched or
07:34:11 modified in a very long time.
07:34:13 And then a couple of weeks ago it's for sale over Fold over on the swings was way too old worsening couldn't handle it anymore.
07:34:21 So after we upgraded our phone to one of the later versions.
07:34:27 It was working fine for a number of projects, number of repose, but then we started realizing that it started getting complaints that there were some that were not working at all.
07:34:38 And now, we have started looking at it and said recovery to dig into it in detail.
07:34:44 There are issues with the way we are doing things.
07:34:48 And that was working fine in the past but, fortunately, we have kind of gone away from the phone.
07:34:57 So to fix this one seems that we need to go into more or less every rich boy and make some modifications and Cedric is working on that and trying to figure out the best way forward on it.
07:35:12 So do we actually need to modify all the repos or there's, there are some repos that require this and others are are okay. Yeah. Later one.
07:35:22 The other thing is that, if for instance if the way I understand it if you modify. If you update all the documentation for stumbled but you haven't created the brown set, and you continue working on your code and then later on you create the branch, the
07:35:36 documents will not be created for with Bronx is stumble.
07:35:42 So you need to go in off the wall, off to create to the Bronx and update one document with something.
07:35:49 And that will trigger you stumbled Bronx.
07:35:52 Yeah, I'm sorry I did a lot of patches on various projects.
07:35:59 And so it seems the Constitution, but I think also, what celebrities proposing is to be more aligned with OpenStack vitamin gas john, to be sure that we will not face this situation is, in the future, because the program we first was really due to incompatibility
07:36:17 between the values.
07:36:26 Library
07:36:30 quite complex to the natural.
07:36:40 What Cedric is proposing is to follow what OpenStack is doing, because of a powerful process for that, and as a result we, we should be sure that
07:36:47 the package that I use for the two competition will work fine.
07:36:52 Yep. So to my co speaking so I'm paste it into the chat, the ticket that summarizes all the changes, currently done to fix the issues with the, with the problem caused by the left docs can change.
07:37:12 And as to see, it's a huge list of changes already done by fit by bang by Eric also Andreas and especially said like Olivier also guy from Orange, and I like to really really thank you for all of you to do the additional work to fix documentation again.
07:37:37 But we are still not there, and as Eric said we now have a more robust way to handle changes in lF docs cons, but there is still a lot of activity needed to, to build the documentation for Eastern but will end.
07:37:57 Please every ptl of the products, check, check the, the change.
07:38:04 We proposed and check it immediately merge it immediately so that we can continue and check what else is wrong in documentation.
07:38:17 So again, thank you thank you very much for all who have participated in this to solve the issues here.
07:38:34 Thank you so much for your day do you think, because we don't have all the PTS on this call.
07:38:42 Shall we also discuss where we are on the PDL call on Monday, definitely makes sense.
07:38:50 Okay, so, would you mind to also add these topics to the BTL agenda, Thomas.
07:39:01 Thank you so much.
07:39:25 Okay, well.
07:39:39 What
07:39:39 other tickets other rolling related topics.
07:39:53 Okay, um, I will stop sharing then turn it over to shocker.
07:40:06 And I think that I've given both of your accounts. I'm sharing capabilities. Yeah, Thank you. I see that thank you very much.
07:40:16 Okay, let me share my screen.
07:40:27 I hope everybody can see my screen now.
07:40:31 So, Good morning, good afternoon, good evening everyone.
07:40:37 This is an update on where we are with the architecture subcommittee or at least.
07:40:44 What we've done for the past year.
07:40:46 What I'd like to do is to start by showing the architecture subcommittee wiki page.
07:40:55 This wiki page basically points to all the documentation, as well as the reviews.
07:41:04 Everything that you want to know about the release is actually.
07:41:09 Under this page, you have the latest version of the architecture diagram, as well as the general description of the latest release, in this case it's it is tumble or nine.
07:41:24 Then you have all the templates that you need to fill out when you're doing either an architectural review or your doing a document in your components.
07:41:35 And then there is a list if I scroll down a bit. There is a list of all the documentation is associated with the architecture review or reviews for all the components that participated in the release.
07:41:49 So, I will post the link to this diagram, or to this wiki page in the chat so you could access it. You could access this link also or This page also from the weekly architecture subcommittee meeting, and the meeting minutes.
07:42:07 There's a link there to this wiki page so everything that you want to know is here. For example, if I click on the diagram, This would be the latest diagram of the, of the platform.
07:42:27 This is the stumble release.
07:42:29 Anybody can copy this diagram include in their documentation.
07:42:36 The architecture subcommittee maintains this diagram. If you have any questions if you have any comments, just send them to us and then we'll take a look at them, if they weren't changes to the diagram will go ahead and do that.
07:42:52 Okay, so let me go back and now look at the diagram in detail.
07:43:03 So, So now I'm going to switch to
07:43:14 this diagram.
07:43:16 So this is the diagram for
07:43:20 the online release.
07:43:23 There are a couple things to highlight.
07:43:28 One of them is a major changes to the components. The first one is the policy framework the policy framework and clamp merge in the, it was a POC in the global release and then it became official in the Istanbul release.
07:43:47 So, even though.
07:43:50 Now, no significant changes were made to claim but clampdown comes a part of the policy framework.
07:43:58 Even though they will want to dependent.
07:44:02 But so we depicted that or we show that as claim, being a subsystem or sub component within the policy framework.
07:44:12 They're staying current controller, the controller design studio sorry about the hovering,
07:44:18 click on one of them in a minute demonstrate what it does. So the controller design studio used to be a part of the service designing creation.
07:44:31 I beliefs, starting with Honolulu.
07:44:32 We moved it and we made a major component within the platform.
07:44:38 The SDN controller. The SDN controller, and this is something that in and I have been discussing the framework is the CC SDK or the common controller SDK.
07:44:52 They're staying current controller, I believe, is a basically an image or is an essential ation there of the CC SDK.
07:45:02 So it's depicted slightly.
07:45:05 This way.
07:45:08 And then, like I said, Dan and I are discussing and if Dan has any other ideas as to how we want to depict this then we'll go ahead and change it.
07:45:22 The color scheme. The gray areas are all the rage boxes are boxes that have been, I want to say quest.
07:45:36 So, FC is a component that may still be started or by om but it been quiet since last release ASR
07:45:54 is almost the same as the almost the same status.
07:45:59 Login as we know it today, or in the past is some is a component that has been quite as as well.
07:46:07 But there is enough, an effort underway right now to resurrect logging.
07:46:12 There are quite a few folks working on the requirements for the new login subsystem.
07:46:16 So login will change, and then actually is based on the progress and the status of the new initiative.
07:46:26 Music
07:46:26 is also component that has been quite fast.
07:46:33 So moving over to DJ etc.
07:46:36 We separated the homes as a sub component within this a the collectors.
07:46:54 It has its own set of documentation so you really want to hide want to be able to highlight that.
07:47:00 And then if you click on dc, dc will take you to the data collection analytics the vest, which is the collector is also subcomponent then is included within dc, dc documentation.
07:47:17 So, this is the same diagram that I showed earlier that exists on the wiki.
07:47:24 What this portal does as a probably mentioned in the past as a navigator. It takes the diagram the official diagram basically it overlays it with a clickable capabilities so it's easier to navigate we use it within the architecture subcommittee significant
07:47:43 in a significant way so it does help us navigate through all the documentation for the sub components in an easy way.
07:47:52 So this is the.
07:47:56 The official online, Honolulu
07:48:02 architecture diagram.
07:48:06 If anybody has any comments, questions or suggestions just send them to us, to the architects subcommittee and they will entertain them.
07:48:15 This diagram also has a different flavor, I'm going to show you a different flavor.
07:48:21 Just to give you an idea or an appreciation as to what are the changes that were made to the.
07:48:31 release to the Honolulu release in how many components were changed. So now if you take a look at this diagram which is exactly the same as the other one, it's, except it's overlaid with slightly different color scheme.
07:48:46 The green boxes are the boxes that participated, or made changes for the online release. So if we look at it, roughly speaking, I would say 60% or 55% of the components did participate in the release.
07:49:06 And each component, guess.
07:49:11 Yeah, I'm surprised because it's not aligning with result component we are regarding the documentation or following the reason I had lot.
07:49:25 Yes to the project board in Istanbul Jima pursue.
07:49:34 I'm surprised by the know.
07:49:37 No, the everything that you see over here are components that were reviewed by the architecture subcommittee, based on changes.
07:49:48 Ok, Ok, ok, ok.
07:49:52 So, if you make changes, and the changes will not reviewed by the architecture subcommittee. Therefore, a JIRA ticket was not generated.
07:50:03 Therefore they would not be documented nor they would be reflected on this diagram.
07:50:09 Okay, okay, Okay, so.
07:50:15 So just to give you an example what this shows so for example let's go to the policy framework and click on it.
07:50:23 The policy framework will take us to the JIRA ticket that was associated with the work that was done to merge, a claim claim functionality into the policy framework.
07:50:37 And we want it to be very comprehensive so the JIRA ticket that was created for the stumble release was actually clone of a JIRA ticket that was generated or created for the whole normally so we wanted to make sure that that tracing is reflected in the
07:50:56 the JIRA ticket, right, and when you click on the JIRA ticket and this is something that we, we have tried to do the due diligence on where all the details or is to fully document.
07:51:09 The their proposal, and their changes in all these documentation are included in here.
07:51:15 So, if you want to know more about the feature you click on the documentation that were presented at the architectural review, and you can find out everything that you want to know about the, the, the changes so I just clicked on the changes that were
07:51:34 part of the JIRA ticket. And it takes you to all the detailed documentation about what was done, what was changed what remains the same and so on so forth.
07:51:44 So
07:51:47 that's basically one take you back.
07:51:54 So, so this is the policy framework.
07:51:57 And then what we also do is we obviously there's the JIRA ticket, we put notes within the JIRA ticket to indicate when the review was scheduled and then when it was approved, right so we have a trial, we have a way to track all the JIRA tickets associated
07:52:19 with all the changes that were made to a specific component.
07:52:24 So if I go back and let's say for example, let me pick on on the use case your high, the use case UI.
07:52:32 Again, there's a JIRA ticket, it's stamped with the stumble release.
07:52:38 And it contains all the information of the, the references to the documentation that were presented. And then you could also see when the review was, or when the changes are reviewed and the architecture committee approved the BTR ticket.
07:53:01 So, let me go back and look at the platform. So, this is, this gives us an idea as to how much changes we're making, how much time we need to perform the architecture reviews, and to track each and every architectural review, not only when the review
07:53:26 has been presented, or done and approved, but also for planning purposes as well. So, this is the view for the on the art, the assemble release. I want to go back and show you quickly.
07:53:49 What we did how this looks for the Honolulu release.
07:53:50 So if I go to the Honolulu release.
07:53:56 And look at the component reviews.
07:54:01 And now you see that this more. this was more like 75 to 80% changes to the platform and I don't know Eric maybe this is what you're, you're talking about where there were some changes significant changes make to MSP as well as the map in the Honolulu
07:54:19 release.
07:54:21 And if you, if I click on either one, but I'll click on one of them.
07:54:26 And then it should take me to basically the.
07:54:31 The JIRA ticket associated with the preview, or the component to view for download or release for the map, and I could do the same you could do the same for MSP so if you'd like, go back and click on it and make sure that at least the changes that you
07:54:45 just mentioned are reflected in Honolulu in the whole release.
07:54:51 So, going back to the whole normal release and this was. And again, if I look at the let's say click on the policy.
07:55:02 And this was in the early, early on in the year in January of 21. So, so this was done right after the, the new year.
07:55:17 And the one thing that I forgot to mention is that if you hover over this.
07:55:21 It gives you an idea as to what the release timeline was or the milestones were for a specific release so for Honolulu, for example, we started out in November, 5, and we deployed in the April 22.
07:55:38 We cover from an architectural subcommittee perspective, I think we cover between 40 and 50 reviews, and these reviews have to be basically handled within you know four to five week time frame.
07:55:56 I go back and look at the
07:55:59 example release.
07:56:03 The same thing you could look at the you could hover over the release and it gives you an idea as to where was when the release was started this really started in April.
07:56:13 We're in the October timeframe we're about to deploy but this is this is from.
07:56:21 This is basically pulled from the, the milestone timeline that David tracks on weekly basis.
07:56:31 We I put it in here just as a reference for for us from the architecture subcommittee perspective to know exactly where we are in terms of relative to the timeline.
07:56:42 So, at high level this is what I wanted to show everybody, I just want to make sure that at least that gives you an idea as to what we do, from an architect, an architectural subcommittee perspective, how the reviews are conducted, how the platform is
07:57:04 documented the wiki page that references all these documentation.
07:57:10 And also, under the wiki page you have a list of all the meeting minutes from the weekly architecture subcommittee meetings throughout the year.
07:57:21 Everything that you see over here is referenced within the within the meeting minutes or the meeting agenda.
07:57:29 It is a little bit crowded in the competition to find all the information you know if you take your time to take a look at the any of the agenda or meeting minute meeting minutes, you will be able to find all the information that I showed now, or the
07:57:46 information is referenced on the, on these Wiki pages. So, with that, a want to give. I don't know if beyond his arm but I want to give beyond a few minutes to see if he has anything to add.
07:58:02 No, nice to find nothing to add.
07:58:07 Only one thing is the logging.
07:58:11 We propose a new architecture for ragging. So it's possible. We can probably take some function of the partial function of the logging current framework, but not necessarily taking on.
07:58:28 So it's the under discussion because we expect. Under the new architecture we expect to own application generate the logging and send to standard out is that era, and all the collection and analyzer and then all aggregator and then database and visualization.
07:58:43 We plan to use the open source tool and code, you know, so that's why maybe for normalization we may need some function of the logging framework, but mostly steer the discussion so anyway.
07:59:01 So that's the only comment I have.
07:59:03 Thank you.
07:59:04 Okay.
07:59:07 Thank you beyond with that.
07:59:09 I'll pause for a minute to see if there are any questions
07:59:15 or if you do have any questions and you don't feel asking the questions in this forum, please join the subcommittee we meet once a week on Tuesday, 10am Eastern Daylight Savings Time and bring your questions to the meeting and we will be glad to answer
07:59:35 any and all the questions that you may have.
07:59:39 With that, I'll turn it back to you, Kenny in, David, thank you.
07:59:46 Yes.
07:59:48 Check your checker I don't know she can hear me. I have just a quick question.
07:59:52 You don't need to answer immediately. But on this diagram that you are just sharing now you know we we indeed highlight components that are duplicated.
08:00:05 And I was wondering, should we also start to move the one in not defined as duplicated as a coma project life cycle.
08:00:16 That's my question because today from a project lifecycle we have unmaintained.
08:00:23 And we have guys, and the differences was that some component cat might be still be used for release I'm thinking about EF as an example, whatever.
08:00:36 And it's unmaintained when some component has been he plays like like comp after this released and and really will move somehow at one point to a guy so I was wondering because we use duplicated here.
08:00:55 Does it mean that one it is master and confirmed by the architecture team. We should kick off the archive courses so again you don't need to reply today but I would be interested to get your soak.
08:01:10 All we can scrape all we connect the, the architecture diagram with the project lifecycle.
08:01:16 Absolutely, it's something it's a something that's ongoing, right.
08:01:36 Beyond Mir scrubbing all the components that are either unsupported or have been.
08:01:32 I want to say deprecating or no longer being used.
08:01:39 So, for example, as are we trying to see the key for us at least the discussion that we're having internally, is if a component is not being launched by om, then that component is no longer part of the release and therefore, it should be either colored
08:02:05 differently or removed from the diagram. So, and then you have the components that are still being used, and therefore they are being launched by om, but yet we don't have that unsupported, right, so we're trying to fully understand the picture of what's
08:02:26 been replicated in what's been unsupported in trying to come up with the way to better indicate that on this diagram.
08:02:38 So, stay tuned we have emails out to the folks that are responsible for all four for the folks that understand or know the answers better in once we get all the responses back then, we'll make a tweak or a slight change to this architecture to reflect
08:03:01 the new reality if you will.
08:03:04 One small comment is for USA such a shock when I talk about it is approved by TASC to remove from om deployments. So, but we decide if we stumble, it will happen to stumble system but we leave as a great for next release Jakarta.
08:03:24 Once all him to drop to support and that component will be jam ESL will drop from this diagram, that was the discussion, we do shampoo.
08:03:33 Yeah, thank you.
08:03:34 And also, yeah, it will be really great to have this information clearly let's say for example we have cross improvement or cross, cross cutting improvement to know exactly which are the component that should be looked at for this improvement and which
08:03:50 one are really our CAD one so it will be really good to have this, this information, or industry for this purpose. Um, so yeah.
08:04:03 So, would you share.
08:04:07 Can you hear me.
08:04:08 Yes, I can. Okay, sorry, there is issue with.
08:04:12 So, we should capture it as an action item Oh, by default, you will come back to us, how will you know come back.
08:04:21 Okay, we could get we could both capture as an action item, and then we'll come back and give you an update.
08:04:30 Sounds great. Kenny.
08:04:32 Can you just talk, an action item
08:04:38 project lifecycle project lifecycle, and maintain the pig and maintain archive in alignment with the architecture diagram. Is it okay.
08:04:54 Yep.
08:04:55 Good.
08:04:58 Kenny, you good me. Otherwise I would I would try to access to the wiki page.
08:05:08 I'm typing, I'm typing it in.
08:05:10 Okay.
08:05:11 Thank you. Kenny.
08:05:18 Okay. Thank you.
08:05:21 Thank you.
08:05:26 Catherine feedback from yesterday, and the governing board.
08:05:31 Yes. Oh.
08:05:37 So really, yep, can you hear me okay so yesterday there was, there was a it was a song on the of the governance board.
08:05:50 The first day I did not attend. But the second day was DDT dedicated to review the following elephant project.
08:06:00 It was kicked off with a presentation provided by Jesus, about attack accomplishment in then followed by the review of own up and look at Open Daylight fd.io turns things public actually Villa ODM decided super blueprint and go and NTAF for the people
08:06:25 who do not know what it is, LPAF. It's a new open source, which is delivered by a world mask. I don't know who are the key partner of Womack.
08:06:39 If you're interested, again, I was thinking to invite Walmart, maybe to present the LTAF.
08:06:48 Let me know if there is any, any interest and thank you.
08:06:55 I still do to French wait. They call it lead.
08:07:01 Yes.
08:07:02 I hope you.
08:07:04 You don't make too much of my French accent to leave.
08:07:08 So, concerning on up. If you remember I was preparing the different slides, I've used the version, seven.
08:07:19 And we got some feedback from some elephant board members on on the items that we have called out. First of all, I was sharing with them that oh do someone up components Africanized as instrumental in open hands prodigy because they already use somehow
08:07:38 in the organization more technical group. There is not yet a formal agreement with the open sec doc and SC talk for the people who don't know what it is, is the equivalent of the DSC is the leadership group.
08:07:55 We, we, I bro the fact that several companies have a phrase this concern to my attention we have been trying to work best with the Linux Foundation, we do have an agreement.
08:08:11 But I will not say I feeling we are going nowhere, that would not be fair. But if we can have the support of some both representative, it will be welcome, and I've got positive feedback and I will follow up with the orange that's Tilikum and habits, both
08:08:31 representative. This they wanted to better understand offline, the concern. And I hope, since to their support. We might be burning the coming. I will, I will not say we.
08:08:42 But coming x, to where this cottage agreement in place, or please to really see how we can mitigate these requests because, for a lot of you who are planning to minute monetize your own up investments who the commercialization of your VR offer.
08:09:02 I see it as a showstopper. But it's only my personal opinion.
08:09:07 So that was the first key takeaway.
08:09:09 The, I don't know if you have any questions so far.
08:09:15 No.
08:09:16 The seven key takeaway was that I was bringing the fact that I would love to connect with Walmart, because, up to now the 5g Super blueprint, which is one of the major driver to in 95 some end to end by GM, Chrysler gal use use case and even more is mostly
08:09:43 driven by 111 group of an ice customer and more mark is a not can play also be called another. If I can bring a lot of value. So again, the word my representative replied positively, and we will try to make a kind of own up onboarding giving more awareness
08:10:01 of what it is and why not to present a little bit, as I said they believe, and if possible.
08:10:12 You know, maybe we have also opportunities in the retailer enterprise domain.
08:10:24 The field items.
08:10:28 As you know, it was also discussed on previous school when we were analyzing Nichols of Asia, also said location.
08:10:38 We have a need for 2022 to have additional globe results.
08:10:43 I try to engage the Google, both members, but I don't think that he was feeling concerned about at least he didn't indicate any willingness to share any GCB resource.
08:10:58 So I think I'll pass currently is based on having that all basketball what is to be for increase as your services. That's what we will need to do and, and I hold the board, understand there are alternative, it's up to them to make it happen, but if not
08:11:25 will not be will not disappear by musical.
08:11:27 I'm Katrina.
08:11:28 Katrina. Yes, yes.
08:11:34 want to provide some specific just gone because we know for example when we reserve resources for three years.
08:11:50 is less expensive than one year so maybe we can add this kind of discount.
08:11:59 I'm sorry.
08:12:01 What, what company was at that you mentioned, microsoft.
08:12:13 So, so what is so just for the.
08:12:17 Yes, that is correct everything that was said was correct.
08:12:20 But, Microsoft is not on the governing board so there was no representation at
08:12:29 at the meeting.
08:12:32 And we'll try and see what we can do about getting an appropriate point of contact over there, but they are.
08:12:42 I believe they are a gold level member of Ellison not a platinum so they are not on the governing board.
08:12:50 So would it be possible to take an action because that's a follow up. We need to think, to get Can you talk as an action items to negotiate the deal, because I don't think that only will they use if there if there is a possibility to have a three year
08:13:08 deal or whatever, that makes sense because I have a concern.
08:13:14 I confirmed potentially next year we will still be there as a community and. And because I can see, we can find new use case for emerging emerging domain like entreprise.
08:13:28 Let's be positive and consider, we have another three year in front of us.
08:13:34 Good.
08:13:36 So as you can take an action that will be good. And then the last note I have to to to feedback to share.
08:13:46 There was one item so if we will remember about cobalt what we have done so webinar training demo certification, and also promote what we collaborate with others.
08:13:58 The doctor you want thank from China Mobile, I think she's developing chair. Now, and also the, the elephant Maxim present that the Vinci was, was discussing this as a major point to continue.
08:14:17 Not necessarily to extend the adoption of will not because will not become popular, but they feel that we don't have enough owner production deployment success story.
08:14:30 Similar family, to what Bell orange DT have been sharing in the past to a honey if you're on the call, they might reach out of you to see what type of success story we could build discussing with the TASC members as a start.
08:15:04 the promotional bone appetit will. So he made an important topics for the board, which was represented by Dr. July and then train them will buy it, of course, are supported by the elephant Maxine.
08:15:12 And finally, but not least, the board, and the Linux Foundation was really give us kudos for all the accomplishments and the heat maps that we have been building.
08:15:28 I mean, not only for cloud native or we can also consider the CNS.
08:15:34 We have also the roadmap of enterprise but also the whole map you are building to the release to evolve network slicing to Decker the internet based networking domain with the HTML, and all the hopelessness, or the Kelly T the security that we continue
08:15:55 to put in in on up so big kudos from their side, including the fact that we are the community with the high participation in the five is about blueprint.
08:16:11 So thank you to all of you. I transmit the the the kudos to all of you. So that was mainly.
08:16:19 All I know that Amy was tough to read because she's our elephant committee representative Can you were also there. Is there anything special, that I missed that you would like to bring to the team.
08:16:33 I want to bring one topic from Monday to the team and that was a presentation by super car on two initiatives that are being developed within the Linux Foundation.
08:16:47 The first one is the first one is an lF insights that gives a lot of trend information and kind of at your fingertips. The other one that was a particular interest to me was the ill effects Security Initiative that that they're working on.
08:17:09 I'm going to have him come and give a presentation to sit to sec calm, so that we can get deeper dive into this product, but it's doing a lot of the things that we're doing today with our commercial tools.
08:17:22 In terms of software vulnerability testing, third party code testing.
08:17:28 They're using some different tools.
08:17:31 It looks like a very interesting platform, and that it could be something that we could potentially replace some of our code with our security testing with, but I want to get, I want to come to look at it first.
08:17:46 Thank you, Amy to give us some insight about the one, because I was invited but you were so it's good to also do not community. Anything else, there was a discussion about the ona conference, the one summit conference.
08:18:07 Really, basically, what should we be doing with it, how, how should it proceed.
08:18:14 And I think that there were some pulling the slide up so that I have it, that I get it right, that they want to drive ones in 2022 again as an elephant event, and it would be very similar to the CNC f cube con plus HL plus a GL.
08:18:38 But I think that they want to task force. You know there were some concerns that this year it overlapped with cube con so they're going to be studying how to move forward with the event that the event will remain but just how to make it better.
08:18:59 And those are the only two pieces. I think the only two things that are relevant for this group. But, as both of them were interesting.
08:19:11 Thank you, Amy.
08:19:36 Right.
08:19:40 So we, let's let Kenny to finalize the notes.
08:19:46 Yeah, sorry, I just want to circle back on something that that Catherine had mentioned about the response from the governing board.
08:20:06 Oh nap was the most discussed project with the governing board. There was the most interaction on on topic specifically related to own app.
08:20:18 There was some additional conversations that for advocate related to tool usage and things like that that were the kind of spun out of it. But in terms of direct q&a from the governing board own app, have the definitely the most interaction there.
08:20:45 So, we are we are highly visible and highly important clearly.
08:20:54 There's no other questions or comments, and Amy thanks for chiming in there, appreciate it,
08:21:07 a shocker want to go back to you you were going to share your thoughts on election thoughts.
08:21:17 Shakur want to go back to you you were going to share your thoughts on election thoughts. I'm a yes.
08:21:25 I still haven't logged on as a,
08:21:25 As a team member.
08:21:27 I do have a, an internal call today.
08:21:32 I expect to send an email out either later today or tomorrow.
08:21:38 To the TASC distribution list and we'll let you know how to proceed.
08:21:47 My, my thinking right now is
08:21:53 still the same as it was before the fact that there was a
08:22:09 question, which translates into concern, which may become a distraction so it's something that I, I'm thinking through very seriously and then like I said, by no later that then see will be tomorrow I'll send me below.
08:22:19 Okay.
08:22:21 Thank you. Cool. Great.
08:22:25 Great, thank you so much. Okay, thank you.
08:22:33 Um,
08:22:33 so we've got about eight minutes left.
08:22:37 Oh, I need to actually hit the share button to share my screen don't play.
08:22:44 So with eight minutes left tackle this start tackling this or push the next week.
08:22:52 I think I will give another opportunity to the new TLC members to review and edits the project life cycle because we might need more than eight minutes so can you put the new targets to 28.
08:23:07 So, if you didn't have a chance to look at it, especially the new team members.
08:23:13 We have been working on the DNC chair.
08:23:29 To prepare the election, but we didn't review all the full of chapters, especially the chapters and the related to the project life cycle.
08:23:30 So, let's have a little weak.
08:23:33 But I would like to face that before the sun's giving no sense giving its next month before Halloween.
08:23:41 So, if you can have a look provide your feedback. Really appreciate.
08:23:47 But the deadline will be next week.
08:23:50 And we will ever read together. Yeah.
08:23:56 Good. Okay.
08:23:59 quad changes coming up, um, Europe is on Halloween date.
08:24:07 And then, The US follows week later.
08:24:11 So we are entering the most painful part of the year.
08:24:17 As far as everyone's calendar goes.
08:24:20 So just be aware of that.
08:24:24 I have not yet kicked off the TSP votes for the community awards.
08:24:30 Sorry about that. The board has had my pretty much my entire attention for the past week or so.
08:24:39 I will get that done.
08:24:45 One I got an email from Brandon that he started to try to pull the information together for the January
08:24:58 developer and test for him.
08:25:01 And what I wanted to ask of the CSC is do you want to keep this as our description for our participation or did we want to change it up.
08:25:19 I think we could announce it, because if we look at the contain provided by the own app community over the past two session.
08:25:34 It was great. We see a lot of people sharing some demos.
08:25:41 The task force also share the fact that we are still feedback from the different task force in the definition I don't see anything related to the requirement team.
08:25:53 So I I don't know if we can change know, but maybe if we have one week more.
08:26:01 And I will ask of macro presenter, to enforce, maybe Maybe we could have something which consider more than this definition. So, that's my feedback. Feedback to the THC does the THC feel differently.
08:26:30 And I don't see honey on the bridge so I cannot give you an action one is not there are sure we can get notified.
08:26:37 But I was thinking it would be nice to send that to the TASC mailing list.
08:26:42 Maybe some community members have different ideas well. And it's not only about that I forget we mentioned security, but all the time the integration, all empty.
08:27:02 All the non functional team are sharing new tools, new way of working so I really feel that the answer is no. With the contain, we need to work on it.
08:27:08 So can you also add the work of the team because it's not only about security it's also the team, the integration team. The team for the people who are helping us to each collection, who are presenting.
08:27:28 The next two things. The progress with the end to end ci CD and disabled things.
08:27:47 Yes.
08:27:49 And while you are doing this. Um, so, let me see who is on the bridge today.
08:27:57 So first of all thank you again to sugar for the presentation you were the first of committee to give us a veto double the activity, perform by your team.
08:28:10 Have we Allah have Timo on the bridge today don't disappear.
08:28:16 I don't see Allah.
08:28:18 Maybe I'm missing her.
08:28:21 So Timo.
08:28:24 Have you an ID when you would be able to give us a 10 minutes.
08:28:31 He told to summarize a little bit the activities performed by the requirements committee.
08:28:41 We haven't discussed this with Allah yet.
08:28:47 But.
08:28:55 Yep.
08:28:55 Would you mind to add it to the next requirements committee agenda as a topic of discussion.
08:28:58 That is a challenging question.
08:29:05 I think I can have it on Monday.
08:29:07 Great.
08:29:11 I don't say you need to present something on the 28.
08:29:16 But what about the Forbes.
08:29:20 As an example, same question for power and Amy, I know you share a lot of insight during the years about your request, how you are improving us as a community, but would you like to make up about all the good things.
08:29:38 You've been doing with the security subcommittee.
08:29:41 Of course covering, we are always ready.
08:29:45 Great.
08:29:47 So, should I challenge when when you, when would you like to get the info.
08:29:52 I don't know I think we have already the 28 for shocker Is it correct I see 28 Oh no shocker just went the 28 This is the action item that came out of.
08:30:04 What do you feel you can give us an overview on the 28th
08:30:12 Not for myself. I would be on PTO, but we can prepare something with a Me, me would you be available on the 28th 28 days is too too soon for me just, I have way too much on my plate right now.
08:30:29 Could we push it up, week after week after.
08:30:35 Maybe we can potentially. Oh, maybe, you know what, I will give a little bit more time to T Mo.
08:30:43 So, Take the November force.
08:30:47 If it is possible.
08:30:48 And then Timo Can you can you target the November, 18. I'm a little bit cautious because I see that November, 11th It's a Thursday. It is true that we are thinking to not have any meeting on the 25th.
08:31:05 But I'm a little bit concerned that we might not have the CO home on the 11, because 11 might be bank holidays for some countries.
08:31:17 That's something we need to check you there will be enough DSC members on the base on the European celebration sure nobody from Poland.
08:31:32 And nobody from Belgium, and probably from France.
08:31:37 Yeah, I mean, the bulk bulk of the THC is actually I think made up in, in Europe and Asia.
08:31:50 Okay.
08:31:55 So maybe we cancel the meeting on the 11th.
08:31:57 Maybe we should do and if there is an emergency we can have always a next call.
08:32:04 Is it okay for all the TC members that we will not have November, 11 November 25 because we have a high risk to not page to Koran.
08:32:22 nobody see anything that social stuff to see so that the 11 will be concerned for the TASC.
08:32:33 I don't think we have any representative on the call for the modeling team.
08:32:39 And if we don't have the chair and the vice chair. Does any of you attend the modeling subcommittee and could provide the could share the requests that we are from a design perspective.
08:32:56 Nobody's attending modeling.
08:33:03 I don't see fed, and I don't see beyond anymore.
08:33:08 Okay, we will follow up offline to host a readout from the modeling.
08:33:16 Okay.
08:33:19 The only thing I need to check I know the CNS Task Force was also planning to review some ido lead, be sure that we are not over booking.
08:33:42 The time.
08:33:38 We can check offline.
08:33:43 Okay, we just need to check offline if we're not overlooking one of the GC because I know the CNS Fredo still some piece they wanted to share.
08:33:54 But by heart. I don't know, which they have been picking.