 Hey guys, welcome folks. We'll get going here in a few minutes Usually we start about five or actually probably in about a minute. We usually start about five after and Frederick has learned Titus today and so sadly won't be able to lead us and as asked us if I'll stand in I've gone ahead and put the link in the chat for the Meeting minutes if folks could go ahead and add themselves to the attendee list. That would be fantastic And folks hear me. Yeah. Yeah, I hear you Well Yeah, there's always that uncomfortable moment when you start talking on a call on everyone is being politely quiet and you're just really Not sure if you're being heard. All right Thank you for sharing I appreciate the person sharing the agenda and it's five after so let's go ahead and dive in So again, please add yourselves to the meeting attendees list and we'll drive into the agenda So we do have this recurring Meeting which you can get to on the community page in addition the CNCF telco your tug Also is a group that we work closely with and we should probably take a look at the CNCF networking working group It's currently being rebooted So major upcoming events This actually is now a past event the October 2nd webinar I know that we've been tweeting about that and pointing people to video. It went very very well. It was extremely well received But I'm gonna go ahead and release that since it's no longer an upcoming remove that since it's a longer an upcoming event We also have coming up the open-source summit in Lyon, France And Ivana and Radislav will be talking there presenting an introduction to NSM and There's also a telco introduction to NSM Coming up November 18th of the 21st. That's kubernetes kube-con We do have a talk on the main stage there for five cool things you could do with network service mesh in addition NSM con is there You should go ahead and please add that to your kube-con registration We do you do need to actually be registered and it is filling up very very fast And we have quite an impressive lineup of NSM related talks So strongly encourage folks to register for that And then coming up in March kube-con plus cloud native con Europe is coming up in Amsterdam The CFP is currently opening closes November 22nd. Although they've now updated that to December 4th, which strikes me as wise Closing your CFP in the middle of your running conference is probably not the greatest thing in the world. I Heard that they have moved that. Ah, yes. Yes, it was a bit. Yeah, okay Yeah, I I'm sure someone did some very sane calculations who arrived at 22nd and then people realized. Oh wait That's the right Maybe it's not the best choice Okay, and then Taylor has actually put together a CFP list if folks would like to be listed there And then one of the other things that we will commonly do For CFPs or things like kube-con is will often put together a Google doc that the community can collaborate on For crafting a series of proposals to go in. Yeah, obviously you don't have to participate in that process It's primarily there to be helpful and provide support. Awesome. Cool. So Then next up we have an update from our social media community Before that if I can just just throw something in here Forced them There has been some some exchange about this. So, um, I don't know. I I was trying To evaluate if this is something that we want to attend What's kind of event is that I think that is kind of generic open source event But yeah, but it's a very dirt under your fingernails kind of event, right? So Fos-Tem traditionally is an event that is really hardcore hacker And it's also a fairly large event. It's got about 8,000 people involved Everybody I've not been depressed at Fos-Tem personally, but everybody I've talked to who's ever been to Fos-Tem has been Super happy about the experience. It's it's a pretty cool community So, you know that you know and the the folks who run the SDN room there the SDN networking room are actually interested in seeing network service mesh represented there So they are interested in having some network service mesh talks So and it'd be It's the actually the software driven networking room is actually who's reaching out to us Okay. Yep. So but I thank you for reminding me to add that Okay, cool So, thank you very much Anything else on events before we move on to social media? Awesome. So Lucina, how is social media going this week? Okay, it was it went really well Yeah, about 10 more followers than we've been having per week so 23 more followers and Followed almost 40 more accounts and tweeted retweeted about 30 times Was able to post the NSM kind of lineup thread. So that was a 13 part thread Thanks to every every time bracket and as many of the speakers that had accounts and That was well received the speakers Primarily liked and retweeted their their reply or their topic. So that was good And also posted on the five cool things that kubecon Sent a second thanks again to the sponsors and that was well received as well And I also pinned that thanks again for the NSM come sponsors to the top of our So that's the first thing people see when they go to end service mesh and Also posted a reminder of today's two calls and retweeted a few of the VMware open source blogs This week the telecom TV interview came out yesterday I was out of office So I'll take a look at that today and this week and promote the session at OSSE you Reminder to register to NSM con promote the individual sessions and speakers the NSM con Outside of the thread. I'll do a spotlight on each speaker. Maybe do two or three a day for the next couple of weeks a week or two and Promote again the session at kubecon. We're almost at five hundred followers for the Twitter account So try to post something when that hits almost that 300 stars on the github account So post something when that hits fantastic and I haven't seen a video of the ons 5g panel. So if that exists Please be sure to ping me if I don't if you see it before I do like to share that and I think I already retweeted the oh on se you keynote, so I'll remove that one and Contributors podcast is that available? This tomorrow. Oh Okay, great. Yeah, so I don't know what it's gonna be rebroadcast, but we do have the We do have it scheduled actually for tomorrow but we have we had CNCF webinar The webinar is actually definitely out. We've been doing quite well actually on the viewership on that. I can share that again if you'd like Yeah, well Yeah, so basically, let me see what the viewership is like on the webinar this point We're at 608 views on the on the webinar video already in two weeks in so we're doing quite well there Awesome. So this is going well. Now one of the things I do want to bring up We also have a LinkedIn page for network service mesh that we haven't really done much with I'm curious if folks are interested in doing stuff with that I Realized this because somebody actually posted a really nice post on LinkedIn about Finally understanding when network service mesh was about after the webinar And so and that actually got a huge amount of traction So it occurred to me that LinkedIn might be an undiscovered country for us But we can sort of figure that as we go I just wanted to throw out that that resource is out there and if there are folks who are interested in working on it I can definitely make the keys to that available To other folks as we expand our social media community. All right, awesome So next up is the announcements. I don't think we have any announcements this week So moving on we do have an attempt to capture good beginner problems So we do have these fuzzing bugs So if you're new to the community and you're just looking to get your first commit into network service mesh I'd strongly recommend looking at these because they're pretty clear about what the issue is We're intentionally leaving them unresolved for the moment so that they they can hang out as good beginner bugs If need be we'll probably just fix them going into zero dot to release Cool any other good beginner bugs that people are aware of they want to list here. All right, excellent Status of the project So we've got a bunch of things that have landed this week You may recall for the last couple of weeks. We've been talking about a shift in the API And in particular we Previously it had this split between the remote and the local API and we brought them together into a unit we're bringing them together into a Unified API so that we have you know, this vastly simplifies the world And we talked about that for the last couple of weeks there's a whole slide deck at the API discussion link if you want to go and review that conversation and Think what has landed this week is We had the breakup of it into three patches the first was the API itself Which broke up the local and remote network service API and brought them together into a unified network service API The second is Compatibility helpers so basically We wanted to make sure that we had some helpers that we convert things between the remote and local APIs and the new unified API It turns out that was relatively simple and straightforward because the API's are structurally almost identical Um, but this is that patch is going to be super important If you're migrating any code that you have that doesn't exist in the network service ministry Poe because that's exactly where you're going to go and grab any compatibility helpers that you may want to apply and Then the third patch was applying those adapters throughout the code base and again If you're looking to adapt existing code to the unified API, this is also going to be a Super important patch to look at because it applies those adapters all up and down the code base And effectively all it ends up doing is wrapping any servers and then applying a wrapper to any clients So it's a very structurally simple patch to you know things to do But again, if you're looking for a step-by-step, this is how you do it go look at that patch. It'll be super clear Also landed this week We migrated to using GitHub package errors instead of just errors the reason we did this we migrated to using these everywhere in the code base Because when you do an errors.new it will capture the stack trace And also it allows you to wrap errors So if you've got a returned error and you're going to return an error yourself with additional information You can wrap the cause and this ends up making the code enormously easier to debug as you're going through and trying to figure Things out and so we moved made that movement and we also put in some very basic ci So if you try and use just quote quote, you know open quote errors close quote rather than GitHub package errors the ci will complain to you And likewise if you try and use FMT format dot errors instead of using errors.new Or errors.errorf Then it will also complain to you in the ci Just to make sure we keep the the motion consistent Any questions on that? Cool Other thing that we brought in this week is you may have been following the last few weeks We had a shift in the build system to spill the build containers and oh my god that it speed at build containers I Don't know what other folks experiences have been I would love to hear them But for me on my local box it took a cold build from 15 minutes down to a minute Has anybody else had similar experiences? Yeah from Russia, it's from half an hour to one minute Okay, yeah, no, I'm I'm I'm almost the very model of optimal build conditions over here. So, you know, I That that's good. And then the The other thing about so we migrated to having the ci use that build containers and we're now to the point where the ci Is able to build all the containers in a single job at about a minute Which is really quite good and then Finally and landed this week We didn't really have much testing the ICMP Colonel forder in the ci and so I know Denise was mucking about with forwarder things and Felt it was important that we not break the Colonel forder and so contributed some helm ICMP tests To the ci for the Colonel forder. So many thanks Denise Anyone else have anything they want to add that's landed this week. Okay, cool I somehow lost the line for in progress in here. Let me go put that back Okay, so in progress. This is stuff that's going on right now in the code base So the API stuff continues Now that everything is shifted over the new API be adapters There's some work afoot to adapt the SDK to use the unified APIs directly That hasn't quite gotten together yet. In fact, it's currently failing all kinds of tests It should be pointed out if you are using the SDK The SDK itself is using the adapters. So they should work with the new API just fine but it would be good to root out the old split API and Actually start natively using the unified API So any any questions on that as that's going on. You know, there's a lot of movement on the API stuff He's that it's it's clear to folks. What's going on there? Does it does it feel comfortable? Any sort of comments on that? No, sounds good cool, and then of course once the SDK is been adapted to using the unified APIs will want to migrate the examples repo over to using the unified APIs Yeah, cool. All right Another thing in progress. So Alex, do you want to talk about Azure Pipelines? We are progressing and now we have a nearly successful, well, it's completely workable and currently I'm thinking about moving it to the original repo from my fork repo and it starts to integrate it to the main repo Cool, could you could you stick a link in here so that we can go take a look and see what Azure Pipelines would look like? You could stick a link in the chat I'm on the phone now, so I'm not too really comfortable with this. Okay, that's completely fine Could you just repost the link I posted you today? Yeah, let me go grab that real quick. Hang on Thank you Yeah, I know it's crazy late for you guys over there Um, let me go ahead and get this Linked up and I will put it in the chat. Actually, I'll even I'll even do one better. I will Put it on the meeting minutes Cool excellent so If you could click on the example of the clean Azure run just so folks can see it here on the call briefly Did you mean this? Yes Okay, it's saying the request that build could not be found Is this perhaps something that's not publicly visible yet? Um Alex It's possible that I don't care if I exist Yeah, that's one of the things we need to figure out because we do need people to we need the general world to be able to Follow the the links and get access to their builds. So we will need to figure that out That's strange really now. Yes. I haven't seen that screen before Oh, now we now I can see a screen and it shows the pipelines can we Yep Oh, this is not wrong I think when we put it into the mind Yeah, yeah, yeah Which of these uh, yeah, just click on the green one Yeah, yeah Okay, I may have just forked the link then So You can see all this running here I mean, you may want to go back to the builds and click on our red ones Just so you can see what an example of a failed job would look like because that's in some ways Failure good failure is better is more important than good success. So it basically says, okay, we've got the sanity check Um Well, this is a Debug run. So it doesn't really helpful to introduce a failed We may pick up an even earlier build to see actually failed. Yeah, for example cloud tests Okay, so but effectively, um I think though what we've basically got is we we've let me fix the link to In the meeting minutes. So we effectively folks can go ahead and poke at this little bit and see um I've now fixed the link in the meeting minutes to see what kind of what it would look like You know, Alex is trying to move this to a place where we can transition One of the nice things about this is that the um as we're pipeline folks are donating a lot of time to see NCF So that is very kind of them awesome Shall we go back to the agenda? Cool. So there's a little bit of stuff. Um as a work in progress on adding go-header linters. Do you want to talk about that, Denise? Yes, sure. I've provided PR. Also, I've provided uh demo inside PR So please take a look and that's it Yeah, the the the basic idea here being that that we're not always great and I'm actually the worst um about remembering the license headers in our files Um, and it's quite ironic that I'm the worst about this because I actually understand viscerally why it's actually super helpful to people downstream And so the go-header linter as I understand it would simply Fail the ci if you added a file and you did not add a a license header to it Um, just as a gentle reminder that you need to include your license headers um So good housekeeping um, so Andre, do you want to talk about the never service mesh? The never service manager sdk like refactoring which looks like it's getting very close Yeah, it's very very close at the moment just one unstable test And it also could fail on master. So I mostly finish it and I hope it will be landed this way And it includes some additional improvements in different areas like cloud testing tool And retrieving of the logs so in general should be very positive on stability because during this refactoring I found and fix it few different issues with the healing And with establishing of one connections with the monitoring of the remote in smd Monitoring of the data plane and how events are passing through the system So in general should be more clear and more stable Excellent So that sounds great Very cool. Yeah, I refactoring often. I find little buds as I'm recovering so that makes total sense Um, so Denise, do you want to chat a little bit about the ethernet context issue? Oh, yes, uh, on last week, uh, we faced this bug related to the agent Uh, but was related to incorrect behavior with dump request And we have updated the agent last week, uh, and this new version dump request working fine And I've continued to work on this issue. That's all Cool Excellent Excellent Uh, Rudislav, do you want to talk a little bit about the kernel forwarding plane? I'm sure you have. Uh, after merging the the metric support, uh, basically I'm involved more on creating an example For for the demo for the open source summit stock that we have with Ivana, so Yeah, in terms of features there there are no more features developing In the time you think, yeah, okay, so do keep an eye on things. There's all the refactoring that's going by I want to make sure that we don't destabilize the stuff you guys want to show Um at oss summit, so do check and make sure that master is is staying stable and do also make sure that, um You know any testing you want to get into keep the stuff that you care about stable gets in as well Uh, because if anything goes bump in the night, we want to get it fixed asap Okay, sure So hopefully we won't have any of that but but we all moral adults. We've all been through this before We all know how the world works So Cool, um, then we've got an in progress thing that you put together really quickly Denise for Uh renaming data playing to forwarder. Do you want to talk a little bit about what you were doing there? Oh, I just provided new proto and I just wait for An assignment to collect the fact and because I need to change the same cost So this is actually a question and since we're in the phase of refactoring some api stuff, it makes sense Do we want to go ahead and do this rename of data playing to forwarder? To match things it will mean for example having to go fix examples Because various downstream imports may shift that kind of stuff My my instinct is if we want to fix this now is probably the right time Um, do other folks have thoughts? Oh, I think we can provide so I can provide two pairs One two and the same And another example Do other folks have opinions or thoughts particularly folks who are downstream working on things? It's better to do earlier than later we If you do so dramatic renaming and refactoring Yeah, I I I kind of agree with that. Um Just Just if there are some priority PRs that are weighted maybe they can go first so that they're not used to be Yeah, do you have do you have some that you haven't mined in that regard? Um Um, no just sing Okay. Yeah, because I mean Do speak up if you've got a PR that you feel should go in with some priority Um, because I I I'd like to there are a couple things that I'd like to avoid One is I don't want people to get stuck and so just pop up pop up on The slack channel if you feel like you've got something that you think should go in with priority The other one is I don't want people to get stuck in in sort of having to rebase and rebase and rebase Um, so, you know, we'd like to avoid that as well Actually, I have those two in the metrics of servability, but I'll talk about them when we reach there. So Okay, cool. Cool. Excellent. Um, and then uh, again, Denise, you've got some work going on with to support multiple simultaneous lenientism borders Oh, yes, uh, it is in progress. Uh, it is also depends on uh, the same is the guy like a patling Okay, and this is you know, we've had this issue up for a little bit of time Talking about how to support multiple multiple simultaneous borders Um, we still have some interesting open questions about how you handle the order and priority But I know you took a look at this right of slav and other than the order and priority question It looked good to you. Correct the the suggestion for how to handle it Yeah So you keep an eye on the pr Because what I'd like to be able to do is I I want to make sure that we can deploy Um, you know, both the kernel forwarder and the bgp agent forwarder at the same time Um, I I having sort of like hard configurable switching between them is less than optimal Plus, um, as we start getting folks working on the hardware and x solutions Those are also going to require NSM forwarders. So All right, cool. So, uh security Um, ilia, do you want to talk a little bit about the things in progress there? Oh, yeah, sure. Uh, the first one Uh It's introduced tokens. I think we already discussed last meeting Uh, there are several comments after review I think I going to fix them in a while, but we also decided to merge it after an sm like sdk like an sm refactoring From and three and the second one is ready. Just require rebase as far as I know Okay, you enable security and entertainment. That's also that's fabulous news. I'm glad that we've finally gotten that sorted. Um cool So, if Anna, do you want to talk about metrics and observability? Uh, yes at the moment merging Prometheus integration is blocked because It first requires merging the The other PR that exposes pot names in the cross connect Because Prometheus is using them and the other PR is blocked by merging the agent dependency issue That I'm trying to resolve for a couple of days. It's uh breaking the ci And was this the vpp agent 2.3? Uh, it was yes with 3.3 with 2.3 I have the same issue Uh, as I had before It's uh, when I update with go generate all the mod files Uh The cn info is added there and then the make format is failing I cannot reproduce locally and if I it's failing by removing that fine And if I remove it go generate there in the ci at sit and Then the default from go generate fails and it's an infinite Circle I tried a lot of work around Still still didn't find a solution Are you having this issue? Is this issue you're having on 16 13? Or is this a machine? I always forgot which one which is uh, let me check Apologies, I I had originally out of your pr respect before I just started copying and pasting No, it's the So it should be here 16 13 or Yeah, I think it should be 16 13 Okay, so yeah Reach out over over slack and let's let's see if we can get you unstuck because I Very few things actually bug me but the thing that one thing that does bug me is people being stuck So I try and figure out how to get them unstuck Okay, I I think I've reached out last week and But we couldn't find any solution This caused the update of two lot three But still we didn't have so I'll try to I That's good Blocking this one because no the permit was needs this merged Yep. No, I I totally get that and I want to make sure we get you guys some block because you've got cool things You want to show off here shortly so um Yeah, let's definitely follow up with that on slack and we'll go ahead and and figure out what what if anything could be done there Because I'm very excited to get the metrics and observability going cool, so um on srv6 support Um So this is stuff that artem is working on. I think artem is currently on vacation Which is good. It's good for people to take a little time off. Um, and the VPP fix that we needed for srv6 has finally gone in upstream and so I'm currently talking with the vpp agent guys About getting a stable respin that includes that fix and vpp agent and so hopefully once we get there We'll be able to um Get srv6 support working So cool anything else in terms of in-progress uh that folks want to discuss All right, cool. Uh anything else that folks would like to discuss that isn't on the agenda I see wane here yeah We Yeah, hello How's it guys? How are you? Hey, welcome wane. Welcome to the community Thanks, man. I mean I try to make the cruise meetings, but be tied up with some other stuff lately So, um, yeah, I kind of just barge my way in in here and start changing guys Trying to help out. I'm actually looking at some of those those PLs to fix those first issues Oh, that's fantastic. Uh, do you let us know how that goes? We're trying to make uh beginner friendly Issues and and those with the linter you would did the fuzzing tend to be good for that The other thing is that the kind gentleman from the fuzzing community came and started fuzzing things I think once those start getting fixed he'll get enthusiastic again and start fuzzing more stuff Um, okay, cool And feel free to reach out over slack, uh, you know or talk there or here or wherever about kind of what brings you to the community what you're interested in Because my experience has been that you know, it is absolutely god's work to roll up your sleeves and help with things like fuzzing clubs and You know documentation of that much appreciated beginning people lined up with stuff they're passionate about and to be the one for the sustainable path So figuring out what really excites you here is going to be very helpful Yeah, so I mean, uh, I don't write a lot of go we mainly uh, elixir and python shops So there's a bit of a learning curve there. So just bear bear with me But we're keen to and my engineering team as well as keen to help That's fantastic The suggestion I would make there is don't hesitate to ask questions on slack because there's there's a lot of situations where um It could take days or something out and if you just ask someone can point you to exactly the answer in two minutes um So go is an excessively pleasant and logical language, but it does have a few nits in it that you got to wrap your head around like any And When you you send me a question about enabling I'm sorry for not answering. We're just crazy No, fuck a couple of days. Uh, so maybe maybe you can post this in the nsm def channel so that You get like because it's more or less a vpp VPP Command that needs to be there, but probably people will be able to answer more accurate than me Okay, no problem. I've just got it like I've got another use case and I know edgy love use cases. So one of our things is um We connect via vpn into the tolcos in africa and what we're trying to do is instead of having upbound based vpn Like in your secure instrument example We want inbound vpn, right where we dial we we in at the connection into The tolco and then we use it as a pipe to then shape and have echoes on In the cnf's as as we push traffic through the pods So that's the worst Oh, okay, that's interesting. So you you're essentially running the reverse of sarah's correct. Um, exactly. Yeah, exactly That's awesome and feel free to it again. Happy to chat I don't know what time zone you're in Um, but you can have a lot of folks who are active in your time Plus a lot of the folks in north america like me get up early Yeah, I'm gmt plus two so and I'll send you guys a picture of the of the Of the use case and maybe we can Use that as a discussion Excellent All right. Okay. All right Talk to you later Otherwise, I'm implying to yield back the time But if folks have something else they want to discuss this is absolutely the time for it And I was love do you want to share because we have some time here? Do you want to share the the picture that you're trying to implement? I think that taylor might be interested Um, yeah, sure. Uh, let me just try to to share my screen Yeah, um, basically I'm trying to to recreate the the network topology of forgy network I'm not seeing a shirt just yet. Um, yeah, just trying to find it Okay, that's fine As long as you didn't think you were sharing we're all good No So is it showing? Yeah, yeah, okay so Yeah, um, basically this is the topology of the network that I'm trying to recreate with the network service mesh. So I I'm basically recreating the the picture that is widely available in the internet, but I'm using the nsm concepts so Yeah, you can see I have I have chosen some of the blogs to the endpoints. Some of them are clients um, the idea is to have a single client and a single endpoint and not have a A point that is both a client and an endpoint So, um, it was successful actually until I rebased ladies master So, oh my so to do ping the unslack about that because if if I want to make sure we get that cleaned up um You it may just be that you need to use the adapters if you were based this morning, for example, you may see Yeah, so so ping me will get you hooked up with the adapters and that should fix you um, plus as soon as I can as soon as I land the, um The native api stuff and the sdk. I'm going to go ahead and and uh shift over examples as well. So, um But I'm delighted that you've gotten this working. That's actually really exciting Um, yeah, uh, basically it's just a skeleton of this picture for the For the images of that of those blocks. I'm using the opine images. So It's it's it's up to whoever tries to implement that to change the images But the clients and the endpoints are configured to to create those this network tutorial No, that's that's actually It also sounds to me like a potential North America, which is probably Sorry, there's some background noise someone Yeah, that's exciting. It's also probably a really good talk proposal for something like os north america. Um, which is opening at cfp soon so Oh Yeah, hopefully also, uh, oh you you want to see excited telco operators coming in and saying here's the skillets and Of your 4g with that work service mesh. That's exciting Uh, so Taylor, this is also partially meant to help with the cnf testbed and the The idea about, you know, having uh, something to be the demo based on the packet towers and etc So, uh, what we wanted to to actually show here is how you can use network service mesh to interconnect all those boxes We don't have the content of the boxes yet because we are not that deep into the telco stuff But we assume that if someone capable of understanding how the Open air interface or some of the other open source projects that do implement these things Can, you know Take over then then they can feel the the right services inside and And put put the things in place. But this is like just saying yeah, if you wanted to enable This solution is based on nsm. This is how you will do it So that's more or less The idea here That's great I'm interested in following up and and we can see Maybe how we could actually implement this On the packet locations with the sprint 5g connectivity Yep, so this is this is very very good This diagram is really exciting for me as well. So because this is some of the stuff we try to do around the pcrf and the packet gateway cool Okay, I didn't So who said that but Okay, uh, so if we If you have anything that That is open source and can feel some of these boxes with some real content would be We'd be glad to to to work further and try to put something together. That's that can be, you know Can do some real work not not just, you know Having things back and forth between boxes Okay, yes for sure. That's awesome anything else folks want to talk about before we conclude and and by the way, uh Radislav don't be shy about putting things like that on the agenda That would have been dead center of in progress, right? What if you Oh, I was uh, I was actually disappointed that it broke just before the meeting I am so sorry Like I said, I'm pretty sure it's just a simple matter of Grab the adapters and away you go. Uh, there's a literally an stk compat now And and so if you go look at the prs that are actually in the meeting minutes The one about how to apply them is probably going to be super instructive Oh, okay. All right. Cool Anything else talks to you guys later? Yeah, bye. Bye everyone Yeah, bye Bye my chairs