 Well, Sina are you up for kicking it off or would you like me to do that? Thanks for sharing your screen by the way. I'm all good if you'd like to continue. So let's see. Events. I don't know if these are all in the notes. This call has been recorded and after the meeting it will be published to YouTube. So let everyone know. We have some upcoming events related to the CI working group. KubeCon China. And there's a CrossCloud CI intro. And I'm not sure if anyone else is talking. And KubeCon Seattle. Andrew from DMR will be giving a talk on CI for new platforms. And with his experience using CrossCloud CI, we're also doing an intro and a deep dive for how to add new projects to CrossCloud. And trying to hopefully get work with other projects for maintenance and able to add themselves and use the different tools that are part of the project. A little bit of movement trying to find. I think that's it on events. Can you bring up the slides themselves and then I'll give a quick run through on those and if Watson has any input on the CrossCloud CI. Reach out to you. ATS was one of the new projects that got added. There was some issues with the CI building side and the provisioning deployment that had been resolved. And so that should be going up on production fixes read. And the NA for app deploy badges. If the build stage fails, it's gone into place. So we skip those. Plan on doing something similar. If there's provisioning and other failures. Keep doing the minor improvements incrementally for the UX updates. So regarding those events mentioned earlier. So adding a new project. The intro talk and Shanghai will be related to this. Be updating. There's actually some documentation out there for adding a new project. But now it's primarily focused on maintaining how, how does it work within the CrossCloud CI project. Which could be useful as someone is using all the components. There's parts that are useful if you're only using some of the different software. And aiming towards projects versus new clouds. And we'll keep adding to that. Moving towards a Seattle where we plan on having more information for clouds for external projects to be able to contribute, help maintain and add themselves to CI. And where that works. Oracle integration. Work has been in progress. Some of it's gone up. And is in place. And most of that's being done by the Oracle team. Next slide. Part of CrossCloud CI project and another project. Talk about it a bit. And working a lot with the network service mesh and group. And they are using the CrossCloud, the provisioner portion of the CrossCloud CI project. For deploying Kubernetes clusters from Circle CI. And doing some other work with that. So we've been working with them. To try to roll those changes back in any updates and basically share and spread the usage of that project and improve it so that more projects can use it. And it's also being used for this other project that we're going to the CNF comparison project, which is another CNCF project. So some related events that we've been attending that might be interesting for any other folks would be network service mesh. Which is now moved to Tuesdays. It was Fridays. It's not Tuesdays, ADM Pacific. The Kubernetes conformance working group. And then the upcoming events, KubeCon, China and Seattle. Which some of the team will be attending both of this. And here's a quick overview of CNCF CI for those who haven't seen it. And the dashboard. And the next slide we can see the projects status for the build stage. So this is for each one of those projects we build and compile the binaries, make sure they work successfully or for projects like on app. We use, we look at their builds externally and check the artifacts and the results of their builds. The next slide. This is the provisioning stage where we deploy Kubernetes bootstrap it on all the cloud providers. And the status badge showing success or failure of that and any testing on Kubernetes that we enable. Next slide. This is the app deploy where we take the artifacts from the build and deploy them with home charts to each of those clusters on every cloud provider and then run any end to end test for each project. And that's a quick overview. Okay, I will, it looks like we have a few more folks may have jumped joined. Hey, Chris Hodge. And hey, Denver. I'll jump right into the jump or unless anyone has any questions on the cross called CI project, I'll move on and give the overview of the CNF project. Thanks for reposting the slide links and the note links. Feel free to add yourself to the attendee list on the notes. Okay, so CNF project. So this is a another CNCF project. And it's dealing with network functions and trying to provide cloud native versions of network functions that have been traditionally virtualized and running on VMs. Several goals, including comparisons of the cloud native network functions to virtualized network functions. That would be functional type test. There's a lot of groups that are doing working in this space own out being one of them that we're doing collaboration with. And we've had a lot of focus on the performance side and specifically what's called data plane network functions. So this will be the ones that are normally pushing packets as quick as possible on to other applications and appliances. And doing performance tests on this. So ideally what one of our goals is is to make all of the tests, including setting up the entire environment. The host that the software runs on and everything else is easy to reproduce by someone else as possible, or they can follow the step by step instructions or possibly just run a script. We're doing a lot of this on packet net so it's open for anyone else to replicate trying to replicate it on other places to make sure it's reusable there and document all that. We're also trying to create composable network functions so a lot of the projects they have or companies so projects or companies may have network functions that work in a particular use case or in a particular location. And then if you tried to reuse that same code in another place you may have to do a large amount of work because it's tightly coupled where the way that the software is set up and configured and deployed is dependent on the infrastructure environment and a lot of other knowledge. So we're trying to make those more composable so they could be reused for comparison tests that we're doing and hopefully for other people and tie in with that would be reference code and these use cases. So these are real world examples that hopefully people can take and say, okay, this is something that I'd like to do and here's a working example of that and go from there. This repo is under the CNCF or there's a CNF repo and there's we have projects and issues and stuff tracked on there publicly available for free to check those out. Next slide. I'll give you all a little bit of overview of some of this. So if you have a Kubernetes cluster with or a right here. I think I'm showing a this would be a typical open set cluster so controllers and compute you could say this would be two masters and three worker nodes and this is talking about on packet.net. So you have something like that for our comparison test we have an external machine that's running in a fee bench which is a Linux foundation of source project for doing package generation. And sending it to these. So this is the kind of your machine overview of what that could look like. And if we go to slide 20. This would be an example of a use case. So where you would take the different network functions and how they could go together. So this one's talking about a CPU case which is a customer premises equipment where you have some device at say like a home modem or something tied in providing like TV and audio and other services and it's connecting over the network back to the provider. And then it goes through various devices or software. So this shows the broadband network gateway some multiplexer that handles the different types of traffic. You may have DHCP DNS. So those are different things. The split here in this view the bottom is showing what would be data planes. So those are high performance and then your DHCP and authentication and DNS or your. Not as high performance. They're still important for functionality but they're different layer. And all of these together provide what the end users wanting is to get to some service that the provider like maybe that's audio or TV or data whatever it happens to be so they could go through all these and ask to push. So we go on to slide 21. A lot of our current focus. This is a view of a single worker node. This could be a worker node in Kubernetes. And what are we doing right now. A lot of the focus and related to CI and how do we test this and validate be able to replicate is building the stuff for those high performance. How did how did they connect so we have the someone out on the internet trying to access or it's maybe the the different nodes need to go out. We have your packet net layer. And then we have to create an internal layer to network for the containers to talk on and then you have your normal. Layer three that. Kubernetes is going to be doing most of the talk between the containers and. What's newer in the Kubernetes and what the network service mesh which we mentioned that group earlier is trying to help solve is how do you deal with the layer two stuff and Kubernetes. And you could set up. VPN tunnels and different things of passing it inside of layer three or you can go outside and try to use CNI plugins. So network service mesh trying to solve it. We are trying to work with what's available now and make it hopefully work with network service mesh in the future or continue collaborate. What we're doing here is showing a high speed connection between the containers so the pp is used as a. A switch a virtual switch right there on the edge and we actually give it direct hardware access to some of the ports. At the same. Layer with Kubernetes. So Kubernetes has access to the network via Linux kernel networking your traditional networking inside of the Linux. And then the pp is actually getting direct hardware access so we do the high performance. So there's a little bit of work to say what traffic is going through the pp versus what's going over the regular Kubernetes network. And making that nice so we're trying to do a clean setup that allows something like NSM which provides. Network as a service endpoint like other Kubernetes services to be plugged in later. And this is what we're dealing with with orchestration right now and the testing around this which makes a little bit more difficult. The men my F interfaces. Allowing the high performance between the containers. So this is a memory device. That's provided as a volume mount between the containers. And that's allows them to talk. Over what looks like a network interface but it's it's memory and it makes it very high speed. And this is one of the setup so that what this is called chain network functions so you have them in a layer in a single chain here. And they could be providing different services that are doing stuff with the data packets as it goes through. And you could have something where it maybe pops out and talks to say a DNS or some other service or whatever. But this is an overview of it. And there's other use cases where they could be connected in different ways. Something that we're trying to get automated and figure out CIFR. If you want to know more, there's the repo issues. Like I said, we also have a chat on the cloud native slack and channel C and that's it for me. Looks like H H are you ready to give an update on your informants working group. Sure. Can you hear me. Yes, go ahead. So we've been refactoring API snoop from a statically generated site into an API so that we can have a react native front end to do all the fun stuff that CrossCloud does with their UI bits dynamically updating the things. We have a prototype right now for the API. It's listed there if you don't mind clicking on it and reluctant to share my screen as far as it function. I don't know if there's a plugin you can have that'll actually show you this in a nice way. As far as it's just JSON data. But there's a list of tests and how many times they get hit and their end points. There's a, I forget what the name of the plugin is. But that stuff is now able to be tagged and filtered. We're working on the UI. It's up on grab another URL real quick. Bit of a lag. Turn into a link. And we're having some issues with the sunburst loading. Oh, wow. It's loading much quicker now. But trying to do the selections and I suspect we'll be cranking through that today. So if anyone's a reactor would be love some help with that. We'll be showing these updates with the tags shortly. I think it's tomorrow at the same time. So we're in 2023 and a half hours. So if we come to that and then we're doing our presentation on our data analysis for cross community things in Shanghai. Or anything and we're trying to decide whether we should come to Seattle or not. That's it for me. Thanks. Do you have a link or a name for the presentation and Shanghai. Yeah, if you scroll down in the, in the meeting notes. From last agenda. I believe it's under HH there's the sketch link under discovering untold user stories. We'll see if I can't for some reason. When I'm running zoom, my machine is unhappy is zoom is not the best. Here's, here's my feudal attempt to paste that link, the Fuki. I think that is my talk link. Okay, awesome. It's not we're going to have a four people coming from, from the Bay of Plenty area one is a Maori lady who's actually has some as Faka Papa back to her, her, her, her canoe, which is not called a canoe here, but So we need to have her, her present for that. And then, yeah, Zach and also Devin and Taylor or that Denver is obviously also going to be there. Does anyone want to speak next month for the see our group. That'll be just after the conference. So, I wouldn't try and to show the CI portions of API snoop, because the UI and the other parts are just the data visualization pieces which we're getting to kind of at the end. Most of the interesting stuff is actually happening in the generation through the CI stuff within the CNC F so I might put my hand forward for that. Cool. Does anyone else have anything to talk about before we end this call. Okay. So the next meeting is on the 27th of November, feel free to invite folks and if you have something added to the agenda for next month for showing that how to attend. There's a mailing list since the CI channel and slack. And this is the fourth Tuesday of every month at 11am Pacific time. Have a good one. Cheers.