Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Current »

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.

AttendedProxy (w/ @name)Gov. HolidayDid Not Attend

Attendance is taken purely upon #info in Zoom Chat 

Agenda Items

Presented By

Presos/Notes/Links/

Release Status

Weekly status update

Jakarta

Sign-Off Review - NO GO



Kohn

#AGREED Jakarta sign off and Kohn M1 will be on June 9th.

ONAP ServiceMesh in Kohn

ServiceMesh in Kohn - POC ?

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Tickets- Waiting on Community:
  • Migration Status / Upcoming Changes

RelEng/Infrastructure

SBOM tools

  • current challenges is around transitive dependencies in Jenkins run It works ok locally.
  • trying to decide if a separate job is needed.
  • Some bugs still being worked through - want those to  be addressed before sharing further

RelEng/Infrastructure

Follow up about MS azure subscription vs new intel lab = question raised on May 12th, 2022 to integration team

PTL Updates

Congratulations Ramesh Murugan Iyer , our new Policy committer !

Subcommittee Updates

Arch, Lab, Modeling, Seccom, Requirements



LFN Cross-Organization Updates

MAC, SPC, TAC, EUAG, LFN Board

Kenny Paul Feedback from May LF Board

TCC / ONAP Liaison Updates

Magnus Buhrgard (Unlicensed) 

ONAP in TM Forum’s Multi-SDO Autonomous Networks seminar series 

I have received interest to present for:

  • TOSCA Defined Control Loop Lifecycle Management Demo – Liam Fallon, Zu Qiang
  • Application Service Descriptor (ASD) for K8s NFs – Marian Darula, et al
  • Orchestration of xNF Based 5G Service - MichaÅ‚ Chabiera, et al

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise


  • CNF Task Force is now scheduled on Thursdays prior TSC Meeting
  • Enterprise Task Force schedule to be re-adjusted since it is now conflicting with the LFN TAC meeting

TSC Activities and Deadlines

TSC Project Life Cycle: 

TSC priorities 

Upcoming Events & Housekeeping

  • ONE Summit NA  Save the Date!
    • Nov. 15 & 16 2022 Seattle, WA, USA
    • In Person
  • LFN Developer & Testing Forum NA  Save the Date!
    • Nov. 17 & 18 2022 Seattle, WA, USA
    • In Person

Zoom Chat Log 

06:59:58 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #info N.K.Shankar, STL
07:00:02 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
07:00:16 From  Alla Goldner  to  Everyone:
    #info Alla Goldner, Amdocs
07:00:31 From  Ranny Haiby (Linux Foundation)  to  Everyone:
    #info Ranny Haiby, The Linux Foundation
07:00:41 From  SaiSeshu (Huawei)  to  Everyone:
    #info Seshu, huawei
07:01:16 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
07:01:49 From  Andreas Geissler (DT)  to  Everyone:
    #info Andreas Geissler, DT
07:02:34 From  Yuanhong Deng  to  Everyone:
    #info Yuanhong Deng, China Mobile
07:02:46 From  Magnus Buhrgard  to  Everyone:
    #info Magnus Buhrgard (Ericsson)
07:02:50 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
07:04:11 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
07:04:38 From  Florian Bachmann  to  Everyone:
    #info Florian Bachmann, DT
07:04:45 From  Kenny PAUL (LFN)  to  Everyone:
    https://events.linuxfoundation.org/lfn-developer-testing-forum/
07:04:48 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang, Wind River
07:05:12 From  Catherine Lefevre  to  Everyone:
    Info Catherine lefevre, att
07:59:36 From  Byung-Woo Jun  to  Everyone:
    @Dave, what was the JIRAs for ASD?
08:00:27 From  SaiSeshu (Huawei)  to  Everyone:
    +1
08:03:12 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED Jakarta sign off and Kohn M1 will be on June 9th.
08:29:24 From  Kenny PAUL (LFN)  to  Everyone:
    https://events.linuxfoundation.org/lfn-developer-testing-forum/
08:30:10 From  Byung-Woo Jun  to  Everyone:
    Dave, I don’t know the REQ-1249, REQ-1248 and REQ-1247 are linked to Epic Link, ASD onboarding package IM/DM?



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:02:52 Thank you, Magnus. Thank you, Timo.
07:03:01 Okay, Folks should have gotten the little note about the recording been started.
07:03:10 Please keep yourself muted unless you're speaking folks on the phone line.
07:03:14 Can you, Star 6 done Meet yourself. You send me a private message.
07:03:16 I will happily cut and paste it into the meeting.
07:03:19 When we are all done here today as usual we'll start by mentioning our projects.
07:03:26 Antitrust policy. You can find this link from both the Lf.
07:03:29 And all of the project websites policy isF important or multiple companies, including potential industry.
07:03:34 Competitors are participating in these meetings. Please review it.
07:03:38 If you have any questions please, contact your company's legal council members of the Yalf. now it's still contact Andrew up to Grove, Llp.
07:03:46 Which provides legal counsel to the Lf. and also important to note that this policy is in place, whether there is a member of Lf.
07:03:55 Staff on the call or not,
07:04:05 On the agenda. We will be talking about Jakarta and cone
07:04:14 Andrea has something about service. mesh. we will talk about several different infrastructure issues.
07:04:25 Brief summer. you know the board meeting from a couple of weeks ago.
07:04:33 Magnus has an update on tm Forum talk about lifecycle.
07:04:38 And Oh, by the way we've got this event coming up i'm gonna drop the registration link right there into the chat window.
07:04:51 If you haven't registered please do so okay we've got been.
07:05:01 I got Eric. Thank you. boring, and only required for folks on the Tsc.
07:05:10 But thank you, anyway. Okay, David, there's catherine Thank you.
07:05:20 David, I will stop sharing and turn it over to you, sir.
07:05:22 Right. Thanks, Kenny
07:05:32 Alright. I sent out the weekly status update yesterday, and it's linked here at the top of the agenda in case you missed it.
07:05:46 Much of that. we will be reviewing today. However, let's just start out looking at the schedule just to remind ourselves where we're at
07:05:58 So you can see down here we have a sign off scheduled for today.
07:06:05 June, second,
07:06:12 Looking at the milestone status. you can see that we still have a ways to go.
07:06:21 We've got roughly two-thirds of the release management Tasks for projects completed with roughly a a third remaining to be closed.
07:06:33 Looking at the requirement owners. made a lot of progress since yesterday.
07:06:42 The one thing I I do notice is that this asd on voting package is made no progress.
07:06:49 I sent out an email to requirement owners that had open tasks but got no response.
07:06:57 I think these are all assigned to Marion. does anyone know what's going on with Marion or with this requirement
07:07:12 Maybe Magnus, can you follow up offline if you don't mind I can do that absolutely.
07:07:18 I was thinking, I will. I will contact him. Okay, Thank you.
07:07:24 Terrific, alright!
07:07:31 Let's see we wanted to talk a little bit about the platform maturity.
07:07:42 We still have some projects that have not updated this.
07:07:49 I think, Catherine? you've looked at this a little more closely than than I have can You kind of walk us through this, and what what you have noticed.
07:08:02 Yes, so You see that no money when we reach the maest and 4, we should have a good understanding about where we are regarding the criteria who did the change since several days, and looking at the table, we don't have the feedback
07:08:20 from the modeling tubes, from the from the
07:08:28 You see teams. So I think these are, and also we are still Sdnc.
07:08:34 The last column for usability I believe it's a leftover.
07:08:40 So there are still some completion to be made here as well as Vfc.
07:08:43 I missed the Sdc. yesterday, because I did a look at the end of the column.
07:08:50 The last 2 2 column to fill up so that's to tackle non functional requirements most of the time.
07:09:02 We? Some of you are progressing a little bit, but not that much.
07:09:06 But we still need to ensure that what has been developed does not dongate the quality which was before.
07:09:14 So. that's what we have and the the exceptions are the items that are either blank or have not been color coded.
07:09:24 Is that correct? No, it's not an exception we still need to have the status.
07:09:30 No? Well, that's that's what I mean I mean the the items that we're concerned about are the ones that are are blank or or not color.
07:09:37 Coded. Okay, there are so my terms in blank the color it's not too much important honestly.
07:09:44 It's the information. Okay, So blank is really the problem, not the fact that the cell is white Alright.
07:09:53 Okay, I can take an action to follow up with those projects offline.
07:10:03 Any comments from project teams about the status of this page modeling or policy.
07:10:14 It. Just this is just I haven't filled it in a few minutes.
07:10:23 Okay, terrific. Thank you. . Thank you. Alright. Any other questions about this page
07:10:39 Let's see we did have we did get new license.
07:10:48 Scan results from Jeff Shapiro. those are published.
07:10:51 I linked the the emails here. I know there was a particular.
07:11:00 I think it was a multi cloud, I think, had an issue in particular that I I had a message into Jeff Shapiro asking about that.
07:11:10 Were there any other issues with the license scan results that we need to talk about?
07:11:16 The it was the list of dependency which was That was the multi cloud . right?
07:11:22 I don't know kenny did you get your chance Excuse me to speak to the ip guys, so we have a better understanding about the concern.
07:11:33 No, they Yeah. David just said that he he reached out to Jeff.
07:11:39 Yeah, Jeff said that he was going to take a look at it, and then get back to us.
07:11:46 Trying to remember. let's see I think i'm pretty sure that was multi cloud , I work too.
07:11:54 We'll decline integration. but I mean yeah let's just see if there are any updates on that
07:12:06 No, no, it must not have been multi cloud It's money Cloud.
07:12:11 It's isn't me to oh i'm Sorry Yeah, you're right.
07:12:14 I I clicked modeling and sort of multi cloud.
07:12:16 Okay, is that ban? Yeah, Yeah. Did you see my node about that?
07:12:28 Yeah, I got it. I'm: waiting for further Update we suppose. yeah, yeah, I I left a note with Jeff yesterday, and I will follow up with him again today.
07:12:43 Any other issues with the license scan that we need to discuss.
07:12:50 The other one was related to eclipse, eclipse, license, which was found in the Sdnc.
07:13:00 Or ccsdk. But again, I think it clips.
07:13:04 License should be okay. I just wanted to see with the second if they have any concern about eclipse.
07:13:11 But I I think it should be okay. Second, are you with us?
07:13:26 We don't have any representation from set con today and I don't see that on the bridge neither.
07:13:39 But i'm pretty sure that we have accepted we did an exception for eclipse, and the only question that I have, is it?
07:13:51 From open daylight or not but I I'm not too concerned about that.
07:13:57 I don't know if anybody on this bridge is concerned about eclipse license that's it give it for the license.
07:14:08 Alright. Okay, let's take a cook a quick look at the open issues.
07:14:20 So as you can see we've made a lot of progress.
07:14:25 We're down to 71 issues. most of them are related to o am. and andreas.
07:14:39 I assume the Om team is looking into these I I and I also appreciate the fact that oh, i'm tasks lag the the rest of the project just by the the nature of how we work.
07:14:56 Yeah, of course we go into that. I think we have to clean it up a little bit, so I I guess that most of them are not.
07:15:02 Let's say, could could have been finished I think team will go through that school.
07:15:10 And then really sorry, cause i'll just raise a quick point to yeah in terms of that project we're still a ptl.
07:15:18 So. is it possible that what what can be done in this scenario?
07:15:24 Well, I guess the you know, the members that are so not invested are still attending the meeting and hosting us right, and but there is no ptl to to drive the project.
07:15:36 Right what we've been working in with kind of an informal arrangement, where i highlight oem related issues to Andreas, and then he presents them to the Om team at their weekly meeting for discussion, and
07:15:55 resolution so that's that's the way it's not ideal.
07:16:00 But that's how we've been operating the last several weeks
07:16:09 Okay, Is that fair? Andreas? Yeah, of course. But but would, of course be nice if, if we would have in the future either support by by someone who could take over the the Ptl role either from Linux foundation or
07:16:28 whatever we would be happy. of course. I mean, we we are handling this stuff, and and and and I think are doing quite a good progress here.
07:16:37 But Still, of course, it would be good to get support then in the future, because I think, yeah, I just I don't think it's sustainable.
07:16:48 If if something bigger comes up and there may be a major bottleneck there, you know.
07:16:53 Yeah. So just I don't think it's really sustainable that the team self manage, or you know, self.
07:17:01 Ptl if you like yeah I agree just the content right but that's that's the result of why there's those Gers haven't been switched over to K.
07:17:13 You know yup fair point
07:17:23 Okay, and then I notice We do have a number of issues outstanding with the Of as well do.
07:17:33 We have the Of. team. I guess that's krishna he doesn't usually attend this meeting or a Shankar.
07:17:46 Okay, alright, I will follow up with them. but in general, we may make good progress here, and you can see that it's been a steady decline.
07:18:01 Since the start of the year. heading toward the end of the release.
07:18:08 Maybe that was double muted. And you you had a question about 4 yeah.
07:18:17 I was just pointing out that We're looking at the remaining open issues assigned to Jacquarda.
07:18:24 We're trying to you know either get this closed or move to Cone.
07:18:30 And I was just pointing out that Ouf has
07:18:35 You see 10 issues here that are open so. and one of the release management tasks is to how resolve these open issues? right?
07:18:46 So I thought the only outstanding thing was to do with the Gpl license thing.
07:18:53 So I don't know if so something else please let me know.
07:18:59 Well, it's just this this set of issues so these just need to be reviewed and either closed or pushed to the cone.
07:19:14 Release,
07:19:15 So that that's if we look at this task cheer, cleanup, that's what it's about
07:19:30 Would be resolving those those 10 issues that makes sense.
07:19:46 Okay,
07:19:47 Okay, all right. Okay, So let's talk about integration.
07:19:59 So we are now getting tests from the adjacarda branch.
07:20:08 And let me cal I think you're on the call I I sent an email to you just confirm that I was looking at the the right directory.
07:20:20 The reason I was asking that was because the the naming convention is a little different from what we've used in the past, because before we used the orange pipelines currently we set up the jakarta
07:20:41 daily that's on Dt. and this is the naming convention from Dt.
07:20:46 You can check that. We have also this kind of directory with that convention for Master and Istanbul, I believe so.
07:20:55 I just followed what we get for from Dt.
07:20:59 And this pipeline is running on Dt. but this is equivalent to the
07:21:04 The daily tests on branches that we did in the past. Yeah. yeah. yeah.
07:21:11 The test suit is the same. yeah Okay, alright, we didn't change anything for the pipes.
07:21:20 The only thing change which is different, that we are not setting the limits for pots, but still we have the limits for pots, limits for communities, resources set for weekly.
07:21:33 So I didn't change that and this is Why, the security unlimited ports test is failing on Dt.
07:21:44 But the rest are the same. We are set up all on up using Co.
07:21:49 And run the same test scenarios like in orange or yeah, alright.
07:21:56 So this is exactly the same. If you allow me to share David, I can share and explain what happened last few days, we've took part of this
07:22:10 See? let's see i'm having a hard time finding you yeah, I'm able to
07:22:28 Yes, okay. So this is from the previous month. So at the when when I set up, we have several issues that regards with the cherry pigs.
07:22:40 But finally we had a quite stable runs on Jakarta.
07:22:48 So we have the 100% on all tests.
07:22:54 And I imagine the security. This this test is failing always, and this accepted to fire and unlimited pots, is also accepted.
07:23:03 To fail on dt. the rest was perfect but since yesterday i've we had a quite big issue, because a whole test to smoke This case is failed.
07:23:14 What i've debugged and checked that's It was related to an ai, but any I didn't start properly.
07:23:23 It's related with that but it's the job bot it's the create Db.
07:23:28 Scama job, which creates that pot, and this spot should, be successfully ended.
07:23:33 But the's. still running. it's frozen all most of the rest of an Ai ports are just simply waiting for that job to be finished.
07:23:47 And that was an issue. Why, it failed yesterday. I talk with Guy, because we had yesterday.
07:23:55 We've guys from integration team We got yesterday meeting and they said.
07:24:00 That can be probably the race condition somehow on an ai that's why this port?
07:24:07 It's not finished but today. we have also not well results as a can see.
07:24:19 Today. this job was finished. succeeded but still we can see that, for for example, house checks.
07:24:33 We have an Ai hold check failed, and also policy.
07:24:37 One which didn't happen I don't know if this go and on the smallest cases we can check.
07:24:47 For example, basic network. This is a common error log from S.
07:24:50 O that it couldn't this is an error exception on any I create task.
07:25:00 I've create an issue as katherine asked me and assign it to session, but i'm not sure if it's rated as all or more with an Ai.
07:25:11 But probably this question for an Ai. and so teams to check what can happen there?
07:25:19 Yeah, I have that. I I saw your email. I added that to the agenda.
07:25:27 I think session is on the call session.
07:25:28 Did you see that issue? Yeah, I believe this was already this question seem to be India.
07:25:35 But perhaps we need to have a mutual call to understand indicated. So i'll if it's possible to actually have a common call with B and A apple maybe that will be better to discuss details and take it forward
07:25:51 No It's Sorry I didn't get your question .
07:25:55 This needs to be discussed, both from So in aa together, perhaps we can do it.
07:26:02 This weekend, or by mutual call, we can discuss details about this.
07:26:07 Yeah, sure. Okay, you might also be able to use the integration call.
07:26:15 When, when is the next integration meeting Miko right? our problem with integration meeting is, I have a conflict with us. so weekly. So since I said Petele, meeting that is on Monday that's better
07:26:26 right? Okay, yeah, we will have also more daily. and but but that issue is not related with
07:26:34 Jakarta only i've i've checked on the master.
07:26:38 Because I I believe it was because of the version change. I I believe it was because of the version change.
07:26:43 Where S. O. is a little head on India and is supposed to extrapolate its patch?
07:26:48 That's what I believe it to be and hence I want to discuss with but I i've checked on the on the Jared and all m changes let me show you and there were no changes for I
07:27:06 don't know a week and i'm not sure if it's related with a change version.
07:27:12 Change. This is quite complicated, because I don't know the thirty-first May.
07:27:19 Everything was fine, and it starts to fail yesterday or even today.
07:27:26 And because, as as you can see, on Thursday first May, it was perfect.
07:27:36 You said I I saw the maid but I didn't get the defect. is it possible to get the defect number, please? kind of have a different number.
07:27:43 It. it's actually on the on Agenda under the release management section for Jakarta without zoom, that is assigned to me.
07:27:55 I that's fine. I was just trying to close all the Jacques items.
07:28:02 I didn't find anything to the way I missed it. If you can help me with a defect number of this, it will be better for me to go through all you 39 49, so 39
07:28:10 49. Okay, i'll have a look
07:28:17 And session. I I think that's a good idea
07:28:23 Sorry. Go ahead Oh, yeah, I was just gonna say that I I think it's a good idea to have that discussion at the Ptl meeting on Monday.
07:28:33 Would you mind sending an email to the people that you sh?
07:28:38 You think should be involved? just to make sure that Let me see that .
07:28:48 I'll take a call record. It Yeah. Let me see the defect.
07:28:49 , Okay, all right, thank you. , no I I went to , to ask if there's any follow up on the The other issue that occurs the day before.
07:28:59 Maybe the race condition that in touch with just because this is this way condition can I come to time and do
07:29:17 Do you have a reference a your reference? part of the the explanation of the the issue that happened.
07:29:28 I think there is one that happened like the day before, and that were called the Ai database creation.
07:29:36 Yeah, and and then did they have to invent or clue anymore.
07:29:46 But just for Renee there is any action to be taken.
07:29:51 Get these startup continue just so i'm clear you're You're you saying that that this issue you think is related to the so 39, 49 that we were just discussing or this is
07:30:10 yeah, maybe from the from my understanding of what happened maybe it's not related.
07:30:16 But so, and if not related, maybe it need also separate. the different.
07:30:23 Yeah, I it. It would be helpful. If we have a Jira reference.
07:30:29 Then we could probably understand better what what you're referring to
07:30:37 He said. there was closed Jira issue. maybe my I think , you help me help point.
07:30:53 Okay. I I thought that Bruno mentioned that there was a closed Jira issue related to that, though.
07:30:59 No, no, no, no, no, no, no! no no no no, no, no, no, no, no, no, no, no, no, no, no, no, no, no, you're thinking maybe if you see 2 different issues.
07:31:11 Maybe with 2 different , to identify. Alright, Me: Cal: Yeah.
07:31:21 Okay, I can create a And you should. Yeah, as especially it happens, both on Dt and orange.
07:31:28 Yeah, I believe that's good idea yeah create a Jared ticket for for an Ai
07:31:43 All right. Was there anything more that you wanted to? cover, Miko?
07:31:54 Alright, let me let me share the agenda
07:32:16 Okay. alright, thanks, Michelle And then Katherine.
07:32:29 There were. You had a few notes here at the but
07:32:34 Would you like to review these? Yes, so I as you said I don't know if anybody from the Setcom is is on the call today, But I just wanted to see if we can have the Hugo.
07:32:48 Even if we don't have if we don't have close all the items of the release yet. but to see from a security perspective, if there's still any concern, because I could not see any but I wanted to have the Google or no
07:33:02 go. and then for the documentation if we can click on the Jacquesa documentation link, and maybe i'm just checking if I see Tomas.
07:33:16 So, looking at what Thomas is, reporting when I checked they were still some open items in the last column, right for the Cli as an example.
07:33:28 It's. maybe normal because we we don't we don't deliver anything new from Cli, and then we have modelings.
07:33:39 You see, there are still some head items in the last columns, and the previous column so wanted to check with Toma.
07:33:46 If he has any concern, or if he should follow up with the with the concern teams.
07:33:55 Yeah, , , So I I can give you short settles.
07:34:00 Yeah. So especially those projects with are part of the release.
07:34:08 But have not breaked So that's for example Cli, or let me see, No, Cli is not part of the I modeling model specification and platform sort service.
07:34:29 They have not created a brand, so that that's the reason why they are missing in the chicago documentation.
07:34:33 So we add only documentation for those in the Jakarta documentation for those projects who have created the Chicago branch.
07:34:44 So, and we are not there with the release notes with the main release note.
07:34:50 So Eric is currently on. So maybe Eric can give also a short status about this.
07:35:00 Yeah, Can you hear me? Yup, Yes, yes, so so so i'm working on it?
07:35:10 I'm just I have some just to be inspired also by the marketing.
07:35:14 Not because to be aligned with the messages.
07:35:18 So I mean I we produce a production by end of the day.
07:35:26 Okay, so that I think after discussion. we had
07:35:32 So we said, Okay, no, we do not need any information about from marketing about the release notes, but we I think it's a good good idea to keep it aligned.
07:35:42 And maybe to detail it in a technical way, or whatever is needed.
07:35:48 So that's a reason why we need the information from the marketing people and
07:35:59 We also received a request from Jill about the architecture description. so there was something about the D diagram, and also the the description of architecture.
07:36:13 Description of audap so i'm not sure I replied to drill what she thinks is still needed, because I have aligned it to the to the latest architecture.
07:36:27 Diagram so, and Jill also has some comments on the architecture description on the text, on the content.
07:36:36 So we are as a documentation project hosting this but I think maybe beyond, or Shaka can can give feedback if they need any changes for this Jacqueta release in this description, or How to answer the
07:36:57 request by Joe. Maybe chacoobile .
07:37:03 Yeah, there's a shocker. So we we we concerned Okay, go ahead.
07:37:06 Go ahead. we could certainly do that i've been working with the Pr.
07:37:16 Person that left the Linux Foundation, his name scape mine, escape me at this point.
07:37:23 Brandon. Brandon. Sorry. Yeah, thank you even though he had left the Linux Foundation. He sent me an email private email saying that he's still assistant.
07:37:35 So i've been exchanging email messages with him so we could certainly work with Joe and answer any questions that she may have.
07:37:42 So that's not an issue. Okay, then, like yeah the new, maybe . can propose , you could send I saw your email this morning.
07:37:53 I'll you know we'll reach out to you directly does that an issue?
07:37:56 Yeah, but that's that's the main status of documentation.
07:38:01 So yeah, here and there we need to to add things, but mainly we are through.
07:38:09 If you think this is okay. Thank you too much for the update, and we will see how we can help you.
07:38:20 By following with the projects that still need to provide the branch.
07:38:25 So you have the documentation if they participate to the release.
07:38:29 Thank you. So yeah, Okay. So it's so current do we have removed the content from from the documentation.
07:38:35 So if we now starting to need, if we now need to include it again, then we need additional time.
07:38:43 So So we we had this discussion. I mean ask for for branching and previous previous meetings since the Ptl.
07:38:53 And also in the Tsc. so I would suggest to keep it as it is and to to ask people to create a branch for for the con release.
07:39:07 If they are part of the release, regardless if they there are, the component has changed or not.
07:39:11 So if a component has doesn't change so please create a branch for the specific release, and your then note in your release, Note for example, no changes in in in in this monk, at least so but always create a branch
07:39:30 So that makes our life much much easier, because remember the Istanbul documentation.
07:39:38 So we had a mix of istanbul documentation of latest documentation from projects which never have created branch, and also some older documentation from earlier releases.
07:39:52 It was a nightmare to to to maintain.
07:39:57 So please, if you are part of the release mean, if you are, if you are deployed, if your component is deployed via O.
07:40:06 M. Then please create a branch. and then Yeah.
07:40:12 This makes also documentation life a lot a lot easier. okay we will rely on your advice.
07:40:21 Thank you so much. We will stay as you have mentioned. Thank you.
07:40:26 . sorry, Thomas. I just a quick question to this scenario kinda like the question way to talking documentation shouldn't live in a single space.
07:40:37 Not that not the Doc team would own us, but that all of the documentation would live in in a single repo.
07:40:46 Would that make your life easier to be honest that didn't thought about this like, I know traditionally, all projects have their own wrong talk.
07:41:00 So . so folder which you guys pull from?
07:41:04 Hmm! , But to say this scenario where you have you know Rico's not Branch, etc.
07:41:10 Would it not make sense to have it in a single repository or single space?
07:41:17 I need to to to have a discussion about this and to to
07:41:22 Think about it. Maybe maybe not. so. We were coming from sub modules.
07:41:28 No, we we have this setup here. but I think the reference to this is the Question's linking is sometimes a pain, not sure if this will be easier if we have it in in one repository.
07:41:45 Hmm. Not sure but may maybe trust a call for me.
07:41:51 Fluory did he? If you have some documentation all in one repository, it would be detached from the projects. and since anybody doesn't like documenting stuff, so it would be even more detest from the original code
07:42:07 and you can't link stuff from the so they should stay in the point.
07:42:13 Okay. Okay, Okay, Alright, Thank you.
07:42:35 Okay. Oh, I think me, Cal. I I did. I forgot to ask about the stability test.
07:42:42 Run. Sorry you you may have mentioned it what's What's the status of the stability Well, the problem is that the weekly is currently only running on the orange pipelines and pipelines are
07:42:59 failing due to, and I I cannot fix that because it's the issue is related with the security groups on an openstack, and I I have no access for that openstack.
07:43:10 We plan to run weekly tests on the university. You can try a lap.
07:43:15 We, when we have a pipelines without it will be possible, but it's currently still not
07:43:25 So yeah, to be honest, and we can run this stability, this on on on the weekly.
07:43:33 This is this is this: I can try to run on daily.
07:43:38 But before hi run the stability test it's 2 weeks ago, and disability test results were very good Yeah, same as the on the very, very similar to to the results we get or istanbul the release But right
07:43:58 Now I I tried several times to run weekly pipelines and it failed.
07:44:08 So I'm not sure if we are able to have some newer stability results in some soon soon.
07:44:18 Simply soon. It was simply soon. Alright, so, Michelle, I think we need to fix the problem that has been discussed previously before turning any new stability test.
07:44:28 Because you could be. you could face new issue because of the problem. you share with us today.
07:44:34 So let's focus to clean and fix the potential problem. that you have been not device since the May the thirtieth with a discussion with Sashu and other team members.
07:44:47 And then let's see how we move forward with the stability. But I think the focus should be on the problem that you have just detected, because these might impact your stability to stability hard anyway.
07:45:01 Yeah, Yeah, yeah, Yeah, for sure, if everything failed Yeah, this makes no sense.
07:45:07 Yeah, that's true. Okay, great thanks. miko all right. So
07:45:15 So the conclusion, Catherine and I discussed this yesterday, and we both agree that we are no go for sign off at this point.
07:45:25 Now, before we talk about a a solution or an alternative schedule.
07:45:31 I wanted to talk a little bit about the cone release, because, these issues intersect.
07:45:41 And let me let me explain why so? if we look at the cone schedule here, it is so.
07:45:53 Just let me kind of refresh everyone's memory here so we we realized at the last Tsc.
07:46:03 Meeting 2 weeks ago that we had an issue with M.
07:46:08 One because it fell on May 20, sixth, which was Ascension Day.
07:46:19 So the solution that we discussed was pushing m one out to June ninth, and then putting M.
07:46:29 2 on June thirtieth, and I took an action to present that to the the ptls and get their feedback.
07:46:38 Well, when I presented that to the ptls a week ago this past Monday.
07:46:48 The feedback that I got was that they thought that the time between M.
07:46:52 Onem 2 going from June ninth to tune Thirtieth was too short of a time.
07:47:04 My concern was, you know, going into July, that we we start getting into, you know, summer holidays, and so on.
07:47:11 But they were less concerned about that than they were. The short time between M.
07:47:15 One and m 2 we we couldn't move it out to the first week in July, because that that intersects with the Independence Day holiday in the Us.
07:47:30 And so what we settled on was a proposal for M.
07:47:35 2 for July fourteenth, and we left the the
07:47:44 M. one proposed date of June ninth, which is a week from today alone.
07:47:49 Okay, so why does this matter So So if we say that we're not going to sign off today?
07:48:00 Then you know the you know. an obvious thing to do would be to push it out one week.
07:48:06 Well, that lands us on June ninth, which then intersects with M.
07:48:14 One for the cone Release Now, Catherine and I talked about this problem yesterday, and and Catherine pointed out that that ptls have already been making progress on m one release management tasks which you can
07:48:35 see from the milestone status page here that they're they've already closed half of them so conceivably.
07:48:43 Then you could do this. you could have sign off for Jakarta and M.
07:48:49 One for Con on the same day. Okay, if we don't want to do that, then
07:48:59 Then it starts to get a little bit tricky because we start running into the our dtf event.
07:49:15 Why don't I have that on here so we start running into our dtf event in in mid-june?
07:49:25 If we push this out past the night like, if we pushed it to the sixteenth, that would be the same week as as Dtf.
07:49:35 So, alternatively, we could push it out to the the 20 third or the thirtieth
07:49:42 So those are basically the choices that we can. We can push this out to the ninth and have it intersect with M.
07:49:48 One of the cone release, or we can push it out 3 weeks to the 20 third, which, given some of the integration issues we have, and so on, which could be tricky to resolve, might make sense thoughts
07:50:09 So. so the choice we're talking about is do we push this out to the ninth, and have it on the same day as cone m one, or do we push it out to the the 20 third or even further the
07:50:25 thirtieth
07:50:34 So just for my understanding having it on the same day would sort of be a problem from a just a time point of view in the Tc.
07:50:43 Meeting, or how do you is it anything else that would well it's it's basically the the the the workload and context shifting for the the ptls and the project teams?
07:51:00 Because they would be scrambling to get work done both on the Jakarta release and the cone release.
07:51:08 At the same time that's my major concern
07:51:17 Okay, yeah. yeah. I see.
07:51:23 Any other thoughts,
07:51:28 So can we just check if we are okay with that I mean whether we'll be able to come to call the remaining task.
07:51:33 But it's timeframe. maybe that is something fun right my only concerns.
07:51:42 If you, if you stand that review point in that moment again, you find some other issue to be one more and one more thing to to postpone also just awarded.
07:51:51 Can you also check the possibility of composition from the stakeholders here? I'm.
07:51:56 Talking of the function I mean the use case owners, or the function or requirement owners.
07:52:01 And then the Pdx with their painting task you you mean for doing and m one on the same day Yes, No.
07:52:14 Just take First, let's talk about sign-off from the perspective of the open items.
07:52:19 We should first call here with a bit what will be timeframe right?
07:52:22 It will be ready with their pride. Yeah, I I You know I.
07:52:27 My feeling is that the the long pole in the tent here is probably integration.
07:52:33 That seems to be a i'm thinking that's where we have the probably the the greatest effort.
07:52:42 So me Cal, do you feel like you can resolve integration issues in a week
07:52:54 I don't know it's not all related with integration.
07:52:59 Only so if it's failing because of tests I can say, okay, I can fix it in some some time. but it looks like it's somehow related with the some components and but i'm.
07:53:14 Not sure if it's the question, for me because we are let me put it this way. The question is surely not to integration team or or to the picture of integration team but all those components,
07:53:27 which are locking integration team right that's where we have to go.
07:53:32 For example, right now we were talking about. So, as you are so engagement as well.
07:53:36 We also have other open issues right So David i'm trying to see what's the conference level of this right?
07:53:42 Perhaps this one issue And then we also have other open items for sure, discussing right.
07:53:47 For example, if you when you open the pie chart there were many issues open right from many projects, so and function Yes, guess also.
07:53:54 So I don't whole stick point. is what We are talking We are targeting for a sign of isn't.
07:53:58 It
07:54:06 Maybe it again, going back to the chart which you're showing some time before the all open items. yeah, the the Jacquarda.
07:54:16 Yeah, your control status report. Yeah, this in that thing, right?
07:54:22 So it's not just integration the integration is finally, the place where we'll march it off.
07:54:27 But we should also take care of all these things together.
07:54:29 So i'm just thinking, perhaps we before taking this call we need to understand what is a logical country Again, we cannot for sure, basically 100% sure that this is what will be the day.
07:54:40 But at least approximate date of based on all these issues.
07:54:45 Depending on what the stakeholders would think of is a better I mean, that would give us a better target date Right?
07:54:50 Don't you feel so. It is actually one input which we have to consider
07:55:04 Thoughts,
07:55:13 Should we just keep going and see how we can, We can catch up. Yeah. So Ka Katchin. Actually, the point was what I was raising is by us.
07:55:29 We can review this again on detail. Call where we to get a better idea and then take a call that will that be makes sense.
07:55:36 Yeah. Okay, alright. So defer a decision on the schedule.
07:55:42 Well, we we know it's not going to be today for sign off
07:55:48 So the question, so we can address the issue of where we can meet.
07:55:54 Sign off on the ninth at the ptl meeting on Monday.
07:55:58 Is that what you're suggesting yeah and also take a stance there? right?
07:56:02 I mean, based on the feedback from the ptls and other stakeholders.
07:56:06 Perhaps we can send a mail. David, I would request you to send him into other functional owners.
07:56:11 Also all use case on us to be there on Pitel call, and then we can take a call to the default depending on the conference level.
07:56:19 Okay,
07:56:23 Yeah, I mean the the the requirements are actually in pretty good shape.
07:56:31 With the exception of this this one requirement You're You're, referring to the requirements for Chicago, or the requirements for cone.
07:56:39 No, no, I'm talking, jacquard the first con we will talk later.
07:56:41 , I'm taking the call because most important is for sure Jacob. Yeah.
07:56:46 So the the Kevin sorry i'm talking Jacques. the release is the most important in hand.
07:56:50 Then we will talk about congratulations. Right? Take a step. Yeah.
07:56:54 In terms of the use cases and other requirements that really the the only one that I have any concern about is this one, and that is, the is Dc based requirement.
07:57:07 I guess right now, , Yeah, Yeah, that's the way that Marion is working on alright great.
07:57:15 So you will see
07:57:19 , Okay, Poc , No, no, No. no. So I mean we call it internal the Poc because it's gonna also have some work on it.
07:57:25 So standards on ps I know what you're talking about here. Yeah, Yeah.
07:57:29 And Magnus is going to follow up Marian about that.
07:57:33 So Hopefully we'll have some information about that by Monday.
07:57:40 Okay, Well, that that seems reasonable. So
07:57:49 So Tsc. members with the idea here is that we won't make a decision on sign up except to understand that Sign-off will not be today.
07:57:58 But We'll. defer a decision on whether it will be Thursday or not until we we meet with the ptls on Monday.
07:58:11 Does that seem reasonable? Anyone object to that plan?
07:58:18 Those good. thank you, Alright, so we will we'll plan to do that.
07:58:28 Then and unless there are any other questions about really status, I I think that's it for me, Kenny and David.
07:58:45 Can I get a 2 min so I could give you an update on where we are with the architecture Reviews before we go there just to on the last session of on the phone day
07:58:57 apologies. Sorry Monday is actually Bank Holiday in Island.
07:59:00 So , yeah, Captain, i'm sure i'm not sure how it is on your side.
07:59:05 But there's a number of countries in the Eu that are off, for I guess it's wit Monday
07:59:27 Yeah, I I guess we'll have to see what the turnout is on Monday, and then determine whether you know we're in a position to make a a recommendation or not.
07:59:45 If we're not able to then I Guess we'll have to do it via email
07:59:52 Both bulk of our ptls, I believe, are in the Eu
08:00:00 Alright, Let's throw out that plan then alternatives i'm not sure how many of the ptls are you looking for Are actually here today?
08:00:14 Do we have a ptl, count, Kenny on the question?
08:00:36 Yeah, no, and there's only 3 or 4 yeah so that photo. I'm not sure how much they are not in total anymore.
08:00:48 But
08:00:59 Okay. So the question then goes back to the Tsc.
08:01:09 Was was that twon it was speaking earlier. Yeah, Yeah.
08:01:14 So do you have an opinion on, you know, these 2 miles?
08:01:21 Yeah. if you look at this as was completed already, I I for my team, I don't have a big issue, with which, closing them on the same day, I have the more close at the moment, as we speak and I think, quite a few are
08:01:34 in the same situation. But yeah, I know can't speak for all but that's my opinion.
08:01:39 I don't have a big issue on closing them on the same day.
08:01:42 So are agreeing that, you know. So making the decision on the same day, Okay, Well, I guess the alternative.
08:01:48 Then, is that we can for now assume that we're going to do sign off on the ninth and do another review a week from today.
08:02:00 Determine our status, and then if we we still haven't met our goals for sign off.
08:02:08 Then we can discuss a new data at that time.
08:02:17 Seems reasonable to me. Okay, all right. so tentatively, Then
08:02:23 We will go ahead with this plan of having sign off, and of Jakarta and M.
08:02:29 One cone on June ninth any objections, and then what we will reevaluate on June ninth.
08:02:44 Alright. Thank you,
08:03:14 And I'm, wondering if we should go ahead and cancel the meeting on Monday.
08:03:18 Then get an agreement on that and today's Tsc.
08:03:35 Meeting,
08:03:36 I think so.
08:03:40 Don't hear anyone arguing to the contrary
08:04:06 Okay, dump that into here
08:04:26 Okay, Catherine. With the 25 min we have left
08:04:34 Where would you like to go
08:04:47 If you're talking you are double muted
08:05:03 Perhaps any small question meanwhile. if okay, Kenny.
08:05:09 So what is the I mean? I know, indeed, we were planning to have a face to first discussion, but unfortunately, many of us who from India at least I can say, are not in his position to take visas so what is the alternative.
08:05:20 For the virtual talk. What shall bridge on the call for the Gtf?
08:05:25 Any update on that from elephant. Yes, there was email sent out to all the Tscs that there will be a
08:05:43 That we are setting up a virtual bridge for the event.
08:05:47 Well, let's go here instead
08:05:57 There will be one virtual bridge people have added topics here.
08:06:04 These are not going to be moderated. basically it's the equivalent of there will be a zoom bridge up for those virtual sessions.
08:06:17 And it's all self-service if people want to give a presentation there.
08:06:25 They so a little bit like live? or will it be recorded?
08:06:32 Or you could meet anyone that's up to the present that's up to the presenter that's it's it's gonna be completely self service.
08:06:43 100%. The rules are there. If you want more information.
08:06:54 On virtual topics specific link is here that says how it'll work.
08:07:02 You go in and you add your create your topic page and Then add it to the Oh, okay, alright, go you missed even even like She's doing is actually to the to the owners. phone.
08:07:17 I got it. Okay, Now every every meeting room we have we'll have a bridge set up and assigned to it.
08:07:26 It will so people can can connect up
08:07:35 The only one we will have tied in to a that that we will have physically tied into the in room av will be the planary sessions on Monday
08:08:02 Outside of that. it is the responsibility of whoever the presenter is to join the bridge.
08:08:08 And then they will use their their laptop as the speakers as to get there to to and the that will be.
08:08:26 That will be the same as we've always done before in advance of the event.
08:08:31 I will. yeah. I will remove everybody from the previous event.
08:08:37 Add all of the speakers for this event, and send out all of the information on how to connect which one include the house keys.
08:08:49 Got it. Thank you you're welcome
08:09:01 So
08:09:02 So, Catherine are you back with us Yes, i'm here.
08:09:08 Sorry I didn't realize you were looking. for me yeah so in the 20 min we have left where we you'd like to go on the agenda.
08:09:22 So on dress. Do you think you have enough time to present your Your proposal for Con, or Yes, I can do so.
08:09:31 I think that's enough time I would like to do it anyway, because i'm away for 2 weeks now and then vacation, and I can also not participate on the portal event to present it.
08:09:42 I hope that or most likely florian who's also on the bridge will make a presentation.
08:09:52 Yeah, if I can. If you give me sharing rights, I can shortly go to that.
08:10:01 Well, what I i'm planning for what do you want?
08:10:09 But I want to give you. Here is the current status of the efforts we spent for getting owned up working on service mesh, and the plans we have.
08:10:22 Oh, yeah, we have on the o one team or support service mesh in the cone release, and what we are trying to do, or what I meant at the moment trying to do.
08:10:34 But most likely we get maybe more support on that. as you might remember.
08:10:41 7 was was doing a lot of stuff already, and they gave a presentation in the Ddf.
08:10:49 In the January. he proposed basically in his status report kind of 4 faces.
08:10:56 To get service mesh running the first one is getting the certificates.
08:11:04 Issues may meaning getting side cars, running, getting automated Mtls connectivity between plots and so on.
08:11:12 Target would be that we get rid of Af basically. So the the components need to get rid of or do not need to to get the certificates from Af anymore.
08:11:23 They will get this. the sidecuts would get the the certificates
08:11:29 Using the ray at the Sto itself, and of course the changes have to be done that the components need to change their communication behavior.
08:11:38 They need to support atp instead of https and and they have to communicate to others using http and not https, because all the encryption will be done by the cycles that's the
08:11:50 first part The next part will be basically and he gave this kind of explanation while he's doing the next part would be authorization, giving authorization policies in the step 2 between.
08:12:07 So who can talk to each other, and so on, and and and and implementing these kind of authorization policies.
08:12:14 And further on there will be another steps that step 3 like authorization policies for 48 for the exterior, 440 for the access.
08:12:27 Simple Our back and full hard work in I i'm at the moment fully concentrating, is still on the step.
08:12:33 Step number one, which is still not working. Yeah, That means a the company.
08:12:40 The components need to get rid of the af integration or the Af dependencies.
08:12:46 If any. Yeah, the second part is that http
08:12:51 They must listen on Http and not on https.
08:12:55 They would need to talk only to to to interfaces.
08:13:00 Http interfaces, and not encrypted interfaces.
08:13:04 Yeah, that's especially an issue on the Stc. communication because the Stc.
08:13:09 Client needs to be configured to use. Then the the non encrypted Sdc connection.
08:13:19 The sound. The I added one part, because this is, was not not part of the of the the initial plan.
08:13:26 Of course we need to in to configure the Sto gateway so that you can, of course, access the the the services from outside.
08:13:36 Yeah. So if you look at that, you you need the the English Controller, which is in our case, the the steel gateway. We need to configure the gateway to get external access either for user interfaces or
08:13:50 for access for the Apis, and so on. So this has to be also configured.
08:13:57 What i've done is i've set up a couple of test environments.
08:14:01 So we have on in our Dt labs to test environments.
08:14:06 I have one using the standard Ohm deployment with certain conditions.
08:14:11 Yeah. So the standard is a setup of like. We are doing it in the daily chains for the integration team with the home releases and so on.
08:14:21 And we have a special one for our team at the deployment where we are using our group, CD.
08:14:26 Which are going on also presented. We have also some special things We don't use share databases, but simple as a single databases, and we are trying to to also test something on newer releases of cuba needs
08:14:41 and sto and the status is at the moment and i'll with the link, You see, then, that's just I try to update this Accordingly, when I when i'm i'm doing the updates here
08:14:57 are basically this status which I have in my lap. and which are successfully working, and the ones where we have problems.
08:15:06 Yeah. So you see, here are the the the change requests we have.
08:15:13 I have created and, with the M. if it's mark that they are already merged with a this is the active ones, and others are still in progress, as you see, there are some components which are not a plot or not
08:15:28 compatible to that. Say the requirements, as you see here, the af dependency on on on the map.
08:15:35 Here, is the heavily working on solving that issue that we don't have the dependency anymore.
08:15:43 We have us all which is working with the patch which we which is delivered.
08:15:47 We have multi cloud at the moment a problem as a set.
08:15:50 So the Sdc. client is a let's say an old version, and has no http support.
08:15:58 It has to be updated, then it would work as well.
08:16:02 Yeah. and what is not checked. But this is something else we have to to check on.
08:16:07 Also when we have sdo we don't use msb anymore, because we have a gateway an api gateway, and we don't need as Msb.
08:16:14 So there. It should be a possibility to disable Ms.
08:16:18 Msb. and and to do not use that this has not not been checked yet.
08:16:23 So, because I know that multi-code has a dependency on Msb.
08:16:26 But it has to be checked. As I said so we I created a ticket for multi cloud, and I think, Wkash, I will take.
08:16:35 Look at that and to get the update for that Cds work simply a policy.
08:16:42 I we are just in discussion. it's basically just it's not completely right here.
08:16:46 Yeah. So we have still at the moment, with the policy distribution and the Clamp E problems that they are depending partly on the Af and encryption.
08:17:01 And we have also here the policy distribution. that the sdc client is not handling that parameter, although it has a new version.
08:17:09 Yeah, it's ongoing the policy team is supporting here to update that cps sdnc I'm at the moment working on.
08:17:16 I have the same issue here with the Sdc handler.
08:17:20 All the rest is now working. I had to update as well elastic to get to be service mesh compatible.
08:17:28 And here we have the same issue that the Sdnc uv listener is not working, or is not handling this Parameter, which is existing for the Sdc.
08:17:39 The rest of them are not yet started, and i'm trying to continue up the modification on the other components.
08:17:47 To get them running, or to get help from others to help me on that.
08:17:53 I know that some are already working on the Dc. I.
08:17:59 Compatibility for service, mesh, and so on.
08:18:01 As I said, the rest will be, Then we need to add, then, the issue or configure.
08:18:05 The Sd gateway to have external access, and then we continue with the authorization issue with the simple, our back, and so on.
08:18:13 The full Abc. configuration so that's the plan for Con.
08:18:17 I would like to to get service mesh comp compatibility.
08:18:23 Or for own up running and i'll hope that we get this finally done.
08:18:33 So the change requests are are marked with with a as specific tag here.
08:18:43 Service mesh for all these. these are only the old M.
08:18:46 Patches. Yeah, which are in progress and we can follow that app later and see how it's working.
08:18:53 My plan is also to have a kind of daily installation, like at the end of the daily deployment.
08:19:01 As finally, with the service mesh option basically, so that we have both, let's say the non service mesh installation and the service mesh installation done automatically, every day So that we can
08:19:16 follow up that it's working that was what I wanted to show you today.
08:19:27 Amy had a question I have seen. Thank you. Yes, good.
08:19:32 You pull the you had a slide that showed the versions you were using.
08:19:36 That was interesting to me, i'm glad to see that in tina app. You're using later versions of things like cube spray, helm, etc.
08:19:49 , I mean, we have issues just to make you aware.
08:19:52 So. we, for example, in Sql. there have some been some changes at the moment, for example, in the in the likeness, probes, and so on.
08:20:02 So most likely we have been to adapt and do the al charts as well. To make them compatible with is with a higher issue.
08:20:10 Really really. So okay, So thank you. I just was curious.
08:20:19 And I guess we need to. we need to get updates to work home to the to all of these various components.
08:20:27 So these these these versions on the left are basically the ones.
08:20:30 Okay still is just in my lab here, but this is the one which which Server was testing on.
08:20:36 So the sto 10, 110 2, and I used it, or we used it at the moment.
08:20:44 So these are the ones which we are using at the moment for the daily installations and alright.
08:20:49 So these are the ones currently in olm yeah okay thank you so we'll we'll just need to get those updated 17 to 18.
08:20:56 Shouldn't be that difficult. Most of them are not big the The biggest one is this: Do you Okay, Great.
08:21:05 Thank you so much. Okay. So one question on the increase part I think that's what you are trying to solve right with respect to the previous slide.
08:21:13 We sure are showing other integration, the ingress.
08:21:18 So basically what I what I would like to start with I mean this is set.
08:21:24 So we would have let's say, the the steel gateway as an ingress controller. and then we would need to configure.
08:21:32 Basically here the gateway and virtual service in the Sto gateway.
08:21:42 I I i'm trying just to reuse the existing in Congress configurations which we already have in our charts, so that we can that I can just try to use them.
08:21:54 For instant for creating. Then basically, then, these this is your gateway.
08:22:02 Set up and and then we will have to check anyway with authentication and integration took key globe. and whatever we we would need, then as well. Okay, because we have always tried the same work on suicide
08:22:18 This was long pending, as I said, one of the I think we already spoke about this in the previous Ts.
08:22:23 Also right like I was actually working on it offline, because, we were half cooked with the peaf for us.
08:22:31 So especially. and one problem which I didn't want to do with if is because I anyway, the project was going I mean it was very good soon gone described, and we were also in in this Poc.
08:22:40 So we have always tried to work on the so Http especially.
08:22:46 It's so it's right to http it's not http set, and we are trying to actually make it in this space for all the communication to have https communication using service
08:22:55 mesh, and in this, of course. Yeah, maybe you have a look at that.
08:23:00 So what is done? it's quite a big one this working in my lap? Yeah.
08:23:05 So. so This is just a contribution change.
08:23:08 It will not be a huge change from the cold and all it's just a change in the Vm.
08:23:13 It's just a consolation change all that I have to do?
08:23:15 Is, I have to remove that Af and I mean clean up the part of the if, and just put in this for my free But one problem is, I have total 3 ports for so and one of them is what is already
08:23:27 done using the spring boot rate, is what is aa right now, and i'll i'll be migrating all of them.
08:23:33 So perhaps we can re look at the change which you made and Andreas, and then we can decide on the best options, and perhaps I can. Also I can also help you with the remaining part.
08:23:43 So that because it's just a change in the vm side which I think of, we don't require to do much of the changes on the code size that's the best part of using this invest way.
08:23:51 Right? Yeah. And to get that, we can actually achieve my better visuals.
08:23:56 I fit that that will be better. Maybe we can catch up offline.
08:23:59 Yeah especially one question you're talking about let's. do communication with the external external client all the yeah, yeah, which should be
08:24:15 http in there is always http, so it still has no problem with in the side that's what he was showing me right.
08:24:18 What , . that is all in the side I'm: Talking of external , , externally spare a F is issue right? I mean, we don't have a problem with email side the afish which addresses mentioned is on external
08:24:29 side, which is all http so we have to. We don't require to clean it up much, because we already kept it in that way.
08:24:37 Because of the way A was going. I took edition.
08:24:40 That will not do it, and that is coming handy to the headquarters.
08:24:43 So We'll just do that yeah we'll just do that on the Soc.
08:24:47 That should be solving both things. I mean one is on his.
08:24:50 Ai will be https ir will be http, and then we can take that as a maybe a pilot project for that module.
08:24:58 Also because everything should follow the same right. that will be better.
08:25:00 1 1 one confirmation issue and not all so subcommittee subcomponent need to access external.
08:25:08 I don't need to the the component exposed service to external debt in English.
08:25:15 Other one is just in Intel, you know. communication through the proxy.
08:25:18 Is that right? right? So i'm, Well, by yeah, what I mean is all the external that is 4 ports which we have 3, 0, 2, 7, 2, 4.
08:25:26 Then admin cockpit, and then the so salt 3, that's something from external sense, Right? only 4 ports this board will be invest based and something the change will not be in is so cool it will be on an oem,
08:25:38 site. so Code will not even have a single end of change, the thing will be only on the Amel files of Helen, charts of oem.
08:25:46 And then the rest ofing that can be I mean I'm just saying that could be a pilot, because we have already started working on it, and then and just can also refer to that.
08:25:55 So that we'll have one difference point that can be referred by the project right?
08:25:59 We can take that as a pilot. Maybe that will help.
08:26:01 Okay, Good. thanks. Okay, Andrea. So you got my idea right?
08:26:06 So perhaps we can catch up on this. Yeah, I I I believe you are going on leave.
08:26:11 You said right for 2 weeks now. Yeah, for 2 weeks it'll be a little bit tomorrow if you're available tomorrow.
08:26:20 Perhaps we can catch up on your morning time. we should be or we can do it once you are back there.
08:26:27 Either way. is okay with me. Yeah, i'd have to check What What's what's in my schedule at the moment.
08:26:33 So sure sure you just drop me , If you are free, then we can catch up for tomorrow.
08:26:38 Alright quick question on that, though in terms. of If if all traffic is default. External traffic is gone through the gateway.
08:26:42 We don't need to expose node ports anymore.
08:26:44 Right? is that not exactly exactly so. don't yeah exactly , , yeah, Okay, exactly So because anyway, you
08:27:02 don't. We will will not get anything from outside. even if you would go for it without ports.
08:27:12 Because the the the the cycles within the use to do that, Julie. So we're not we would not work. so you would have an access to a gateway because this site cut communication as a otherwise
08:27:24 just minor update on the kubernetes version.
08:27:27 It's 1 1 22 4, is up but I have to check what is in the Really, she would be to unwind what is run on the air because that's where we'll have the real trouble
08:27:44 for it. So, as I said it's easy because we didn't do much of integration, but the real problem which you'll face is to our mind what is there all over the Uf.
08:27:51 So we have to clean up the court of air then we have to do the interest. I think that's what we have to do for all the comments
08:28:02 Okay, that's what was my overview. I think you have to also this other office, too. Here, right?
08:28:14 I know your broad spectrum the last like i'm talking to versioning.
08:28:16 There. we need to also take that that is still. then.
08:28:23 Okay, maybe maybe that Also, we can discuss and just let's not take it more Poc: it's already 2 min, so so we can discuss tomorrow.
08:28:30 I mean whenever you're free, I get not to month whenever You're free, maybe you can Okay, Hi,
08:28:43 And 2 min left
08:28:51 These are very great information. and I believe, Kenny, if we go back to the agenda, there is nothing else we can still discuss today.
08:29:04 The I will drop the registration link once more into the chat window.
08:29:12 And encourage folks to please register for the event.
08:29:22 Definitely looking forward to seeing everyone there
08:29:30 Unless there's any last minute. things that somebody wants to bring up out here on the West coast.
08:29:40 I think it's time for breakfast one quick question for Dave.
08:29:45 I send you a text just let us know how about the 3 requirement link to Isd.
08:29:52 I don't see connections anyway, to offline you can conform.
08:29:56 Thank you. It was that to me desktop I sent separately.


  • No labels