 Okay, I'm going to go ahead and kick things off. I'm on a train to Red Hat Summit in Boston, so I'm not going to talk too long because the connection is probably going to drop out. The main thing I wanted to announce is just that we're going to be, I guess, rechartering this group and changing the name. So instead of the CNF testbed, it's going to become the Telcom users group, and the CNF testbed will be one of the subtopics that it covers and is responsible for. And of course, if things heat up enough on the testbed that doesn't work well to combine into the call, then we can always split off and have a separate meeting again. But we do want to appropriate this time for the Telcom users group going forward. So beyond that news, I just wanted to suggest that we go ahead and cancel the meeting on the 20th because we're going to be having our kickoff of the Telcom user group in Barcelona. And that's going to be, let's see, sorry for the noise here. May 23rd. Yeah, May 23rd at 11 AM. So I hope folks will be able to attend that. And then I look forward to diving back into this meeting again on, it looks like June the 3rd. So I'll try and stay on, but I'm going to mute from here. So we'd love to get updates from Taylor and others. And thanks for the call. I've run through some of the related announcements. So there's several mini summits that are happening right before KubeCon Barcelona on Monday, May 20th. Two of the, I think very relevant for the CNF testbed and related for the Telcom user group that's coming together as FDI and mini summit and the LFN's Cloud Native Network Service Day. Those are happening at the same time. They are in the same facility. So if take a look at those, the schedules, I think there's going to be relevant talks and both. And if you register, you'll be able to walk back and forth and look at some of those. There's various people that have been involved on the CNF testbed. They're going to be presenting, including myself. I'll be actually both presenting FDI mini summit and the Cloud Native Network Services Day. Regarding the CNF testbed, there's also some network service mesh talks that are happening as well as FDI CSIT talks that are going to be there. I think my check, you may be on the line and if that's your name, that's a little bit funny there. And I think those are the big ones that I know of. I don't know if anyone else has announcements that are right around KubeCon. KubeCon China, Shanghai, there's going to be additional talks as well. That's going to be June 25th to 26th. And those are the main announcements I have before we go into anything else. And there's some people from the various groups like Frederick, Yeloran. Does anyone have any announcements or feedback? OK, thanks for dropping the sketch for the Shanghai. So we mentioned this at the last one, but I'll bring it back up again. Network service mesh was introduced as a sandbox project and CNF test for CNCF. And the CNF testbed is going to be including network service mesh soon for stitching together the use cases for connecting all the network service mesh. That's one of the goals and the primary goals that we're going to be working on over the next several weeks up through KubeCon and probably after. There's some relevant use cases that are being worked on on both projects with regard to showing integration and the hybrid setups that are in production with OpenStack, V&Fs running on those, Kubernetes running new CNFs as well as other workloads and being able to talk and make connections between those. We've been doing a lot of performance tests and how things work. We'll be showing some integrations between those. We've added some early support for Sintos, Fred Sharp and Robert and some other folks are on the call, I think right now, been working a lot on those. So we'll be having more support for host OSs that are on the different clusters. Those are coming soon or not. Right now it's Ubuntu, but we'll have those pretty soon. That matches up with what's available at packet. Right now it's the Ubuntu host OSs, but we'll be having the Sintos, which ties in with what a lot of the telcos have. Right now we're not looking at directly supporting rail, but we'll have Sintos, which will give direction for doing stuff like that. And the other items are related to getting things updated on the projects like VPP for using the newer releases, which not only gets us some of the newer features in general, but allows us to move away from the binary only drivers for packets, Melanox network cards, but going to the built-in for both VPP as well as DPDK. And that's in the works to get that support in place. And that makes deployments a lot easier as well on to packet as well as keeping things moving towards open source from air metal all the way up. That's an overview of pretty much everything from the CNF test bedside and the options. I'm open for any questions, answers, if anyone has anything, as well as if someone else has items they'd like to discuss. I haven't heard anything from folks for a while. I'm hoping that y'all can hear me. Yeah, we can. Yeah. Okay, great. As more folks have been getting involved, all the documentation and testing, the repeatability of the CNF test bed code, different stages for cluster deployment, deploying the use cases themselves. That's getting a lot more work and we're updating the docs themselves. Definitely want to get feedback on areas where it's not repeatable or something may be missing, but that's coming together. The more use cases, I think we'll start showing up as a result of this, including the integration between Kubernetes and OpenSec. That use case I was talking about will also be adding SRV and some other ones. On that, if there's folks that are directly involved from either a vendor side or a telco and knowing here's some production use cases, either documenting, getting specific on those, or helping with actual PRs for adding those is encouraged and welcome. Yeah, I guess the thing is getting to a point where the stuff we're doing is open sourced and available to be consumed by this. So, you know, from my perspective, there's stuff that would eventually want to get into this test bed but might not yet be at a point to do that. What sort of stuff would you want to see in there? I mean, as in actual CNFs that we could deploy into it. Right now, the CNFs that we've been testing with are based on... They were originally based on code in the ONAP VCP use case, which is on a repository. And if you break it down, essentially those are VPP-based CNFs. Very minimal and then you can configure them as you could with VPP. And they've been focused on the high-performance data plane testing. We definitely like to get more. Do you have any ideas of specific network functions that would be good to add and test with? I mean, I think ultimately it's anything that uses what VPP can do. So, you know, whether it's just routing, natting, firewalling, IPsec, you know, whatever VPP can do. Ultimately, yeah, it's just just getting a broad range in there. So, I think that's what fights the longer term. OK, great. Right now we've been doing... Oh, go ahead. I'd prefer to look at the ones that you have for VCP, like what's in there, you know, because presumably those have basic sort of routing and natting in them already. Oh, actually, yeah. They've been primarily IPv4, IPv6 routing. We are looking at some of the others. The firewall side is something that was already done in some of the ONAP use cases. So, that would be one that we could pull over and test. Ideally, we'd look at smaller use cases, or if it's a large one, then we break it down into its component pieces so that we could isolate those, implement them, and then you can add those as a composable part. Yeah, no, completely. I mean, the whole point should be to chain quite small functions. The other one that might be worth putting, the load balancing. OK. Because I know there's that kind of maglev style code in VPP, how usable it is, I'm not sure. But it would be nice to throw things like that in there. Great. Anything else folks want to add or discuss? Well, we can end it early, and that's fine. So the next call, we won't have a next call. The next will be an in-person meeting to kick off the tug at KubeCon on Thursday, May 23rd. And then we'll have the next Zoom meeting is going to be in June. And that's June 3rd, Monday at 8 a.m. Pacific. Thanks, everyone, for joining us.