 Yeah Hey, I need a lie Hello, I am not sure if it is going to join I think he said something like You won't be able to I Don't know if you have any other information about it. Sorry was muted. No, I don't have any information about He's intent to join or not Can wait few minutes I think Yeah Who who shares usually I mean It's first time actually We do it with a zoom Usually adds shares his screen Okay If you want me I can share Browser with the issues and we can check what's going on. Yeah. Yeah Sound good, I guess we we don't have an like any notes meeting notes, etc. So yeah, yeah Let's just go into into this We should wait, but I don't think that anyone else is going to join Okay, let's go and see what happens here with the issues so first of all We did merge the yeah, it seems like it was passing Okay, so that's good master is green that's a good start How do you know which are the new okay, so I assume that these are the new issues like since the last week Matrix doesn't report You know my cmp Okay, is this something about the VP not sending Okay, so this is clear like okay, this we know what we should do Okay, I read through this and I green general That we probably can and probably should slim slim the example down But on the same time we need to probably have another dedicated example where we can examine a Little bit of scaling. Okay, that's not a great scaling, but still it's like six six containers With the side cars and etc. So it's it's something Probably it's not the best way to test it. Maybe we should have something that's dedicated that runs only on the bear metals so, I don't know what the plan is here, but I Do agree that probably we can just go and slim this down and if this helps The CI passing this would be good Trying to think if we can have a more dedicated scalability testing which is just Targeting How do we scale we just need to test it with our integration tests instead of the helm meant for it seem to be just have different cases, which is More easy to check Yeah, yeah, I do agree. Yes Only add a comment to it. I'm going to not forget But I think it's important to have example test now No, no, we could have an example test, but we've no not the four clients and point points You mean we should scale ability with go Yeah Go but not with helm That's not with shell script. That's okay Is this a result already or no no just mentioned Yes, that's the reason why That's something strange and sometimes I see it on master Oh, I Didn't find the root cause is this something quit Because only one note sounds like something that cloud test should be dealing with I'm not sure I need to check but I see that only one spire agent deployed It means that probably only one note exists. Oh, so I don't know why I need to check Investigate a little bit more. Okay. Yeah, okay wait for port available can spin The question is With canceling I think the cancel should be properly handled first case Kind, okay, the latest kind is zero seven I think it's Don't depend on version of a kind Oh question of how we handle requests. Yeah Okay So part of the yeah, it's just Corner case that usually Okay, do we want to do anything specific any assignments and labels Let's assign it to our team. I think is working ton way into the main and Probably it will be easy to check if the counseling is properly handled Okay, so these were the the new ones and are there any From the old ones that that's not need some discussion Do you have anything that you want to discuss from the from the previous ones? I think we have just one Request, which was still pending. It's a Interdomains and they wanted to add to say all or Frederick to say a final word Should we merge it already or not? Or did you have a chance to rebase it to the latest as I remember last time I'd fail it because of Some Testing progress, okay, we just rebased it last time it just fail it because of some examples shell scripts, which is Yeah fix, okay So is there something here that that you want Or actually that's there are a lot of won't fix labels after Stalebot, I guess, right? Yeah, I think we should in that issues at least this spire in the title. I mean 2005 2006 Just notice that there won't fix Yeah, yeah, this probably is the bot as you said Also these are Maybe we should close close this one Because it doesn't happen last time and there were a couple of fixes for similar problems That's quite old actually Okay. Yeah, indeed. I haven't seen this this lately. I mean don't get me wrong There are a ton of fathers, but this one particular now Yeah, I do agree any objections about causing this one So So, you know, is there something going in this direction is there a PR? I don't see anything Yeah, yeah, I think it should be PR. Yeah Yeah muted. Sorry. I was muted. No, there is no PR yet, but I'm working on it right now Just didn't start the changes. Yeah, just put we need to put. Yeah, okay. So I Yeah, yeah, I think it's better to add pin pin or something like that Yeah Okay, we were slow to register. I guess this one is also going to be pinned All right, yes Okay, okay, it's something Just waiting for feature becomes better Do you know when this is planned to become Actually, I didn't find you could search the name of the feature that was Yes, it's alpha. Yeah, it's alpha since 13. Yeah There's no information about Okay Go for it Okay Good Also, so we're talking about the floating in the domain Fred we are just wondering what we can do with the floating in the menu which is pending So we have two approvals But I think that these the people on this call actually kind of agree that this can go in so Maybe it's yours or it's cool on when this This one is merged. I think it should be merged because since we in progress of a decay refactoring's and It's a plenty of changes they're not very complicated, but yeah Probably just should have to make all this code in sync My So Yeah, I was saying that not this this specific PR which is a floating in the domain is here for some time And Okay, so we were saying that once this this PR Finishes it's Check it's strange. Yeah, what's the docker target? It might be related to my recent changes that released is the target I made recently How is changes could be here? Well, it's a base store. I don't know I Will look at this Okay, please sync with our job. Okay Yeah, so my intent is to wait for it to be at least green and after it merged Because it was green some time ago before The more we wait the harder Let's just see Okay What else was here? Cloud test test doesn't get this here to include sales. Is this something that is fix it and we can close this Okay for the service to common package my friend comes with the common package What about this? Is this something that is ongoing? I Yeah, pull request but I'm not sure if we still need to Push it since we plan to switch to a new SDK. It's just some refactoring and cleanups in the current Is the implementation so probably just I Will just remove the won't fix and leave the question here so that we can Go once more against it. I Don't know This is For those who go on package. Okay. Is this the same? But for the forwarders Yeah This will give us some time to think Let's see Again, and of course, I guess that once we switch to the new SDK this will automatically become obsolete Yeah Single JPC server socket for all clients Okay, is this blocked on something? Well, the feature is blocked because the there are some slight but architectural changes needed and We were waiting while Ed would Ed would something suggest us whether we should move with that architectural changes And it just still in that states since like Weeks three weeks or more. Yeah, okay. I would just remove one fix for now. So that If we forget about this the stalboat will remind us by parking it again So, let's keep it like this Please remove one fix here because poor request is already Ready just isn't pass few tests Okay Yes, I will Oh So which of these are Actually So this is that we have to open PRs for this So these are the fixes that come from team And these are the fixes that we are trying to Okay, I Have to obviously do my work here too, but Should we obsolete this one and say that it effectively suppressed by I Think my chair just already include his PR with little bit Changes, okay, I'm closing it Okay, I obviously have to go and check It also has some Does it need a rebase? Yes, it needs a base. We Yeah, I think We already made fix for broken tests Okay, then let's go with this and then we will okay, so given this We have only one one fix that we have here this issue is fix it and we can Okay, do you know where it's merged here, okay, right, okay, so Yeah, we don't have any Won't fix this See the chart. Yeah, so this is something that Discovered and so Okay So one of the things about we're going to Right ago is we had the project board where we had it within the network service mesh project itself. Okay, I'm trying migrating issues and PRs that were tracking Then across especially if they cross multiple refoes onto a project level on rather sorry I'm an organizational level board rather than a project level board So I wanted to point people at this to take a look at it Not if I'm over it right now but this is a This is a spot where we can use to track some of everything that's going on as well Okay Oh Is there something in to do that we need to move to in progress here Oh, this is the first issues is in progress This one Yes, and second one also in progress Okay, I see so this is on the on the top level. Okay, I get it So that's yeah, I have visibility. I see. Oh, okay Yeah, and the purpose of it as well is is It's less for this for this group. Although I think it'll be helpful for this group It's also where we're gonna make an effort to get the community We're involved over time. So this will give them an easy place to to jump in as well and work out like what What major things are pending that they can try to To make use of and especially with the SDK factor refactor that should like I know it's a little bit Bumpy right now, but once all that's that's done. It should be a lot easier And so we want to make it as easy as possible on board people. So that's part of the part of the idea behind this Okay Good, I guess that we have to just flow into the next call So, okay, thank you, I think that was that was useful We've managed to streamline this maybe a little bit more Okay, I will leave this one for me to follow Okay, so yes And any ideas the team has to to help with overall processes and management And it doesn't have to be adding it can be removing things like definitely let us know so we can Try to try to make everyone's lives easier Okay, I see people started to join just share meeting minutes I'm just curious. Will it be the one video on YouTube or two? How it works Okay, do we have any pressing topics that we wanted to discuss Except for the floating inter domain Fred do you want to take over here? Sure, just waiting for a few more people to join in So we'll start around around five after just a reminder that this call is Recorded and we will be posted on to YouTube. We'll get started and In about a minute or so Great, let's get started then so welcome to the next network service mesh meeting We have this meeting Monday at 8 a.m. Pacific time We also have a Asia friendly meeting at the 3 a.m. Pacific time The last call was Today And the next call will be Two weeks we also participate in the CNCF telecom user group and I apologize my mind Not 3 a.m. Pacific time Bob could be I'll get the actual time in a few moments We also participate in the telecom user group which occurs every first Monday at 8 a.m. Pacific and every third Monday at 3 a.m. Pacific we also participate in the CNCF signal network, which occurs every first and third Thursday of every month at 11 a.m Interlaced with the Kubernetes significant meeting We have information on both these in the agenda We are participating in cube con and cloud native con Europe in Amsterdam We are waiting for the CFPs, which should be out tomorrow There is a list of CFPs, which we are trying to keep track of what was posted So if you could add your talk if it is related to telecom networking or CNS To Taylor spreadsheet, which is also listed in the agenda. That'd be fantastic We also have NSM con which is a cube con EU Which is a co located event on May 30th Highlights include we have a larger room and We have prospectus and information for CFP on The on the website that is linked from here. So the CFP is currently open closes February 21st, and if you also if you posted a talk that is NSM related and if it does not get into the NSM Sorry to the Hubert Nettie's main track we highly encourage you to resubmit it into the NSM con as well the number of talks available at at cube con tend to be percentage-wise The number of talks accepted is very low just simply because of the number of slots that they have and We also have sponsorship information there as well There is also the open networking and edge summit North America, which will be in Los Angeles That is coming up in April April 20th or 21st The CFP closes on Monday February 3rd So make sure you have your talk ready to submit there if you intend to be in Los Angeles Before before we move on And Nikolai, are you able to post the the CFP new project board under the announcement page? Sorry Thank you very much and so there was a new project page that now exists. So we were in the process of separating out a network service mesh to multiple repos and so a project level board no longer suffices and GitHub has a new feature which is organizational level project boards that continues to work with with issues and so on so There is so this new project board It has a couple of nice things which is where we're keeping track of issues and pull requests with this and so that'll also That'll also make it easy. So if you're wondering about what can you jump in that that will help push the project forward in a in a timely way, then these are these are currently active currently Wanted PRs that that can help guide you in as well. So The new SDK that's been created should make this stuff a lot a lot easier to work with so With that we have the social media community team The social media community team are you are not able to attend when there is a CNF? Sorry and a CNCF Talk meeting and so I'll take over for Them today We have an additional 14 followers We are following Six more people Now this is particularly interesting because this is an inflection point where we got more people follow following us then Then as following others in terms of a number of changes So that's that's a nice inflection point that we just said We also had a 12 more 12 more tweets and Finally we also We posted multiple things on Kubernetes transparency we report the CNCF announcements about CFPs for various open events more on an SM con and and more information on our on our Austin meetup which maybe the first NSM Meetup it depends on whether it's an SM related or if it's a cloud native meetup. I'm not sure which and with and finally with that there we also posted information about the new weekly PR review meeting Which which also reminds me I under the announcements Well, I'll add this in as well at 7 30 a.m. Pacific time right before this call. We are holding an issues who request Meeting so these this is purely for things that are actively being worked on. They're not architectural Decision meetings there. We kept the time Down to 30 minutes to prevent architecture from being discussed and so if you if you would like to Join in and help and ask questions or do you like to join in and and Try to take on an issue or PR and you need some guidance This is the meeting to do it. It is on the same bridge As of now it is on the same bridge as the network service mesh community work group meeting So please feel free to join us. It's right before this one and And With that We also have some some additional followers on on LinkedIn We have seven additional followers and we cross posted everything from Twitter on to link to LinkedIn There are some plans to to post more about the sponsorship or NSM con to you. So you should see some information on that and When the contributor podcast comes out that we will post that as well And with that we we don't have any hard items on the agenda. Is there anything that anyone would like to discuss? I Would like to call for a date on what's going on with SRLV. I know that the three people that Are kind of you know interested in driving this are on the go now, so Maybe some update if you want me I can open the PR or whatever just I Think it's it's a really important feature that a lot of people are interested in so any form of update would be Yes Yeah, so some short update for me, so I finally managed to find some time to work on that PR, which is Huge success by itself. Anyway, I've dated this PR today. I Basically I revised on top of the latest master. That's the first update beyond that I Introduced the new connection mechanism API for SRLV user space and started working on the Implementation on the on the forwarder side as well And those of us starts working on the graceful release of the well function after it's no longer needed Beyond that made a couple of changes in regard to fixing some issues reported by CI Obviously the interface as there are some to-dos in the code Yeah, that's that's about it. I Managed to find some time to work on that Hopefully continue to work on that as well in the following days Hey Prozemic this is Ryan With Suza I've been meaning to reach out to you Haven't had a chance yet. I guess while we're here What what can I Jump in on to help you with this to help it move forward. Where is there anywhere that you can use some help? Well, the biggest challenge I think now Something that I haven't really started working on yet Would be the the client sites stuff. So for example the NSM in its site sidecar needs to Properly request SRLV interface. So currently under the master branch. There's a lot of hard-coded stuff in there doesn't allow for that and What's currently included in the PR? It's also kind of hard-coded at the moment to request those SRLV interfaces So we need some higher-level generic mechanism that will allow us to request Any supported type of mechanism let it be SRLV interface or kernel interface or VPP or or whatever, right? So currently this is the biggest challenge and Something that I haven't started working on yet and I could use definitely some help on that Okay You'll have to forgive me because I'm still trying to orient myself here you envision that refactoring coming in the form of a separate PR from what you have or were you thinking that needs to get added to the PRs that you already have out there or Well at the end of the day We probably have a number of PRs related to that because even at this stage you can even see currently what Nikoi is sharing There's over 1,300 lines at that in this PR. So we should definitely break its separate PRs already have four commits first three of them Relate to various sections, right? So for example, the first one is related to the to add in connection mechanisms to the forwarder API then we have SROV forwarder itself and then we have some additional commit that adds Genres in the SDK web who can so on but these are temporary and more of a proof-of-concept changes that Definitely have to refactor. So I don't know. It's just a matter of preference at the moment probably at this stage to be there to keep everything in a single PR and to have a single Place to cooperate on that but once we once we are happy with what we developed We definitely have to break it into smaller PRs to make the reviews and so on easier That's my opinion. At least I'm also new here. So maybe there are some smarter people in the bridge Yeah Yeah, but my feeling is I actually kind of take a different approach to this if we're looking for some collaboration and to get some traction here amongst a number of developers it might make sense to Figure out how we can break apart what you have into smaller more consumable PRs But maybe I'm in the minority here. I don't know what others are thinking right now or Maybe prismic you feel strongly for a reason that I'm not aware of So I have some advice on this as well that they can wear if Prismic's not ready for immediate help because of current state something that could use them help is Potentially so we're migrating things from the network service mesh primary repo into an SDK set of SDK repos and one of the repos is an SDK dash kernel repo and a lot of the things that needs to be done in the srlv use case are Done exactly the same way as you would in the kernel space For example, like how do you set an IT on a on a interface if you're using kernel mode? Is it how do you set routes and so on and so my my recommendation? would be Until Until he's ready for additional help on the PRs and patches might might be to help with the SDK dash kernel getting it into a good state and helping with with that because there's a moment that That this particular patch comes out one of the things that we're that we're going to want to do is We're going to want to move create an SDK dash srlv repo That can depend on things or when we compose what we compose the srlv Plug the runnable plugin then we will be able to to interlace the the two things together and not get duplication of code so that may be an area where we're you may help and I believe there's people on this call who are working on that SDK dash kernel and can speak more as to whether Whether they need help in that space here as well. I Had chatted with Ed about this yesterday. I was actually going to take a crack at that. I don't know if anyone else is Working on that I may be out of the loop there, but I I was actually going to start looking at that To go along with this so if that's if that's useful and Sounds like this kind of dovetails with SRIO v work. I guess I'll just focus my efforts there right now and yeah Prismatic just yeah, when you're ready reach out Yeah, sure you can think even offline on Slack or When the elephant involved rather thought probably as well, I think so Yeah, and and we'll we'll think of we'll think offline on the sda SDK kernel stuff and what we'll do is Well, we'll make sure that things are populated in that project board that we posted in the announcement section We'll make sure that those things get populated there as well And we'll we'll see if there we can find an easy way to label them or to make it clear that this is stuff in the in the kernel or Or other Projects as well Because or other other sub repose at least my My my my point of view here for for for this PR is that this is a Very very very experimental for the time being I get that I also get that it slowly is trying is kind of taking shape and Getting into some form that can be merged. I would really prefer if we can have this split it into Smaller at least chunks Oh Keeping the cock commits in as a separate PR's also can be a thing so Thank you. Pregemic for taking care to keep these things separate and well format it like this I Get what you said about Improvements in the way that we handle different mechanisms Um, this probably should be a separate PR that's not related to this one from what I can tell um, what I probably would like to see is because you Like you have these ideas, etc. Etc. And Maybe it would make sense if we have this somewhere this cry it Like we used to do these specs Etc. Like things that are here So Maybe if you just Takes some time. I know that it's it's hard for you to to schedule this but If you can share your ideas of what you would like to see Maybe we can have And just just drop it in a Google Doc Um Then we can share it here Probably we have some some common place where we can discuss these ideas Because I agree that seeing code is is the best But maybe before we go and delve into codes we need to discuss the ideas Otherwise it could be Kind of we can end up some losing time in doing things that not that don't get upstream Sure take some time and prepare Some sort of design spike or It doesn't need to be anything formal, etc. Just just dumping your brain and saying okay I see that this goes here. This goes there. We need we have these and these gaps in the existing code That's that's that's something that we can then share here in this world group go and talk to it Yeah, absolutely, I try to prepare something before the next thing. Thank you. Thank you. That will be that And then from there we can we can figure out issues assigned to people that want to do this and Try to move this world. It's really really exciting I'm sure that a lot of the people that are here on the call and probably will be watching this I'm going to be excited about all this work and everyone is anxious to get this upstream as soon as possible saying this and also Taking like this idea for having a spec into account Can you please consider if if you're not able to share this now? To dump your thoughts on what is missing and how we want to change or you want to change Like the upstream s3 will be device plug-in because I know that there's there were some things going on there Some changes that we wanted to happen some things that you did in your private branch So I'm not sure what's the status there regarding this But at least if you see any other gaps that and things that needs to be improved there Maybe this could be something that that we can also talk about Yeah, regarding the survey network device plug-in I opened a new pull requests And that's the service was plug-in repository yesterday. I think I linked it Somewhere in the comments under the PR. Yeah, that one. Yeah, correct Yes, you need to fix tests in that PR. As you can see, there is there are some small to-dos but it is the the accompanying here that I Definitely have have it merged before an SM is an SM PR is major enough Let's see. It should be in place before we need it These are kind of changes that were more or less influenced by the work that you do with us Yeah, okay Do you have anything else that's in the pipeline or this is all for now? and so for now as some time ago I discussed with that Possibility to also add something like new mechanism there for Automatically binding and unbinding Devices from the from the kernel modules For the moment, I don't think we need it Maybe at some point the future it would be a nice addition But it's definitely not needed to progress PR for an SM at the moment. I do I do agree. Yeah Let's make this work and then we'll make improvements. Okay Okay, I think that we are in the half hour of the call We had a good chat about this anyone else have any questions or any Thoughts about this This work any suggestions Any expectations So just for the people who are working on this stuff This is one of the most asked for feature. So thank you all for for helping on this like I Can't begin to describe how much this is gonna make a lot of people very happy if we don't have any other questions You may be on mute if you're trying to say something But if there are no other questions Are is there any other topics that anyone else would would like to discuss? Okay, and one last thing we'll see about putting together some good information Made through either blog post or video on the new NSM SDK that we're putting together. It's a it's a very simple mechanism But it's a but it's proving to be very powerful in terms of composability and testability and If you would like to jump in sooner or later and you're looking for something to get started with as a as a first thing Most of the Modules that we've that we've posted are In need of unit tests and so that's a great way to learn how the new SDK works so if you're willing to hop on and write unit tests up on any of these things that are be hugely usually helpful and If you want any information or help being started with that, let us know and we'll help you out and With that I don't have anything else on the agenda if anyone Last call for any additional items Okay, well with that I want to thank everyone for your time and we will see you Next week at the same time or possibly earlier at 7 30 a.m. A.m. Pacific time If you are joining us for the issues and PR meetings. Thank you much. Thank you very much everyone and see you next week Bye. Bye. Thanks. Bye. Thank you. See you. Bye