 Okay, I'm gonna make sure so I'm gonna go ahead and start. I'm hoping everybody can hear me Is that the case? Yeah, you're fine great All right. Well, welcome to the telco user group. My name is Watson and This is the I guess the European and China friendly time So I'm for everyone else that might be in other time zone. Thank you for joining Like I was saying earlier if you have any topics go ahead and add them to the agenda I'm gonna go ahead and give a update on the cnf conformance project There's there was a new release on Friday 0.8.4, which really concentrated on doing platform tests versus Workload tests. So there's a test in there now for doing node or testing node failure as well as And it is really testing it but if the node recover from an unexpected Reboot it also test to see if the runtime that is that the platform is using is OCI compliant and Another test that's partially under that's underway is testing to see if cluster API is enabled in order to See if the nodes can be managed automatically You can I put the link inside of the Of the document there, but the release is here and you can download and and run it there's also On the main GitHub URL there's the installation Documentation so on and so forth I'll take some time here and see if anybody has Anything else that they add as far as updates and we go a while people are thinking about that I'll go ahead and I'll talk a little bit about some upcoming events our next meeting of course is on October the 5th and That's going to be at the over regular time 15 EPC We've got We've got a couple of other conferences virtual conferences that we're going to the attending community One of note is the open networking and Edge Summit We have some people within our community presenting there so we have the Birds of the feather telco user group and we also and that's on Wednesday We also have on Wednesday a panel discussion which is going to be talking about a cloud native principles Within telco as they're tied to telco and also there's there's going to be a key on November 17th and So be you know be ready for that So does anyone have any other updates that they would like to share or any questions? Maybe questions about the performance week or anything in general pretty silent crowd here Okay, well maybe if you all What have any comments on? What all should be tested as far as platforms or platform tests and workload tests? I'd be great if you could maybe Send some of that Maybe put it in the chat or go ahead and maybe send it to me directly or Dan Because where we have a bunch of different tests that we have planned As far as testing a cloud native networking and performance and so on so forth But what we work on first Matters based on the community so We're looking also for contributors so There are things that you'd like to work on we have feedback. We're really Trying to get more information from the community on that All right, that was actually a question that I have what since so when you say we who's like what is the What's the the group of people and where do you implement these? Tests rather is it like in the end-to-end tests weed or is it a separate thing or how does that work? Maybe you can briefly monitor sentence summarize that Okay, so when I'm talking about the the tests in general I'm talking about the this CNF conformance suite so This is a suite that goes through and tests Conformance to say networking cloud native principles really or concentrating on Kubernetes so making sure that the A workload that's installed on Kubernetes. So I see enough if that's Playing nice let's say on Kubernetes and it's portable or has all of these Capabilities and properties so compatibility statelessness security Make sure that it's a microservice scalability configuration of life cycle tests observability Installability and then also test if it's on the platform to see if the scheduler has been modified different from what? Kubernetes Expects like the Kubernetes on Test and also test resilience. So that's some of what? this Conformance week comes or it's trying to do and it comes out of this community. So There's a bunch of different community. It's an open-source project and there's a bunch of different contributors to it I'm one of the contributors, but the as far as What tests the it's really community driven on what gets prioritized. There's lots of things That could be tested, but we really need The community to come forward, but there's been a lot of interest in platform tests. So there's the the Kubernetes conformance test which this Suite is kind of based off of it gets draws inspiration from and That actually runs within this suite. So you'll make sure that it's a whatever platform is running it's going to be conforming to the using the with respect to the Kubernetes conformance the son of Louis But there are other things that people are interested in In conjunction with that So Like I don't think the performance suite has tests node failure So the Kubernetes conformance suite so there are the this test suite is really for the concerns of service providers and vendors and Trying to make sure everybody's playing nice with each other and trying to be when we say that it's cloud native that it's cloud needed Does that answer your question? Yes, it is. Thank you Okay anyone else has Any questions? We're also Trying to work with other projects that we consider maybe upstream so with CNTT and the OVP projects from Lenox Networking Group where we're trying to have The CNF conformance project be a downstream so being one of the set of tests that get run so really Really focusing on the Kubernetes side and we're gathering also requirements from CNTT and Trying to facilitate Some of those things too if everyone's sensitive to those requirements so things like eventually Things like multi-tenancy is going to have to be addressed security those types of things and see Tom's in so maybe he can Speak a little bit about that if you want But there's a big spreadsheet of requirements that are We're trying to Whittle down. What are the common ones between all? All groups involved That's another thing anyone else have anything Hey, what's I'm sorry? late Yeah, on that work you just mentioned there is a learn in the In one of the court scenes tier calls last week. There's a weekly meeting which I know Oliver and Taylor and Frederick have been Setting up it's it's been running for just a couple of weeks now To kind of try and collate those CNF requirements I will try and find a link to the D to the document agenda and I'll put it in the I'll put it in this agenda here. So people can see it Because if you're interested in kind of trying to collate those standard requirements around Cloud native network functions, then that's probably a good group to work with Think this one is it Yeah, that's a scrunch. Yeah, there's a there's a there's a Google Docs, which has their weekly meeting details in as well Okay, I find that That in there Yeah, some of this work is going to be really useful or all of this is going to be really useful trying to get the Community together And any do you have anything else Tom? No, no, not on this one. No Okay, and just again, sorry. I'm like, I'm always super early here. Yeah No problem here Siling group this time. I Think that might be it might be it and we've gone over the updates that I had and the events that are coming up so I think that might be it. We can get people back there We've got Someone's writing in as anonymous Okay, there we go Okay So we've got the we got the Google Doc in there for everyone, but I guess we'll give people back 30 minutes of their time Thank you. Thanks everybody. Oh question Yeah A lot is what's noted here is very, you know, technical in terms of the, you know, conformance of CNF and Is there any like Concern on the kind of more business side of this so And what I mean was inside of this is like if you look at a lot of, you know, existing taco vendors They would have, you know, multi-year vendor contracts and then you want to introduce this technology Which means they're going to have a multi-vendor kind of Makes where there'll be some open source components on top of the otherwise, you know, supported stack And, you know, these So cooperators will come across at issues where the Support would say, oh, sorry. That's you're using, you know, CNTF stuff. No, we don't support that That's that's not a kind of support But then you find that the development team went through a massive effort to make it work I mean, how do we address that? How do we Address the fact that we're going to have a multi-vendor kind of taco stack Yeah, well one thing is the conformance suite works with binary downloads. So it doesn't necessarily have to be Open so the platforms we're envisioning CNFs that are closed source and platforms that are closed source However, that's possible or pieces of platform that are closed source. They'll be able to be downloaded installed and still tested So it's a good question that you're asking, right? So If you have multi multiple vendors One of the reasons why you want to have Some kind of conformance suite that you can put in your pipeline So let's say you're a service provider and you have multiple vendors One of them made a platform And then they have a CNF and you have another vendor who just has a CNF And you in your pipeline. So those stages before you go to production, right? You run Let's say you also have code that you've built So you build your code. You may or may not have coded you build You grab the artifacts, right? So these are the binaries you take those You also take the artifacts from let's say CNF vendor one that has the Their platform and their CNF and then you have CNF vendor two take their artifacts So their CNF, right? You're putting them all together. That's going to be built On in that second phase of your pipeline that and then this third phase So you have a working environment or supposedly working now you're going to be applying integration tests and other stages the CNF conformance That's where you would run that And so if some other vendor comes in and says, well, we don't support The CNF stuff. That's well CNCS stuff. That's what you said It really comes down to you And you saying well, we're interested in these Tests if they fail or if they don't fail Um, so they could say that they don't support but it could be Maybe it doesn't violate the contract. Maybe it violates your contract with you Um, however, you if you were to say you didn't have any type of conformance testing at all It seems to me that you would still be going out there manually Seeing everything work on a new version of a deliver of an artifact delivered to you And this just automates that right or if you have a you know This is one scenario injecting it into your pipeline. It's also an vision that The vendors run it themselves against their own So the same way has a kubernetes conformance works individual uh So wait, um, I said CNF conformance, but kubernetes conformance works A kubernetes conformance works Is the individual cloud providers if they have a kubernetes offering they run The conformance suite against their own offering and then they'll post it up the results They'll post it up to like it's a github repository, but anyone else can run the uh kubernetes Uh conformance suite Uh, it's not really that hard to install But anyone else can run it against an a kubernetes offering and then say hey, this is the results we got so it's not like Only one person can run it so it keeps everyone honest I guess everyone can see every what everyone else is doing. That's where it kind of um It's it's good if everyone runs a type of conformance against their own Platform or CNF or their own artifacts in general But you also Can run and I would recommend you'd run some type of tests against um Dear, uh, whenever you get any type of deliverable, right? So Uh, I don't know if does that am I getting at the heart of your question? Yeah, yeah. No, no, no, that's trying to answering it I'm just thinking that this information should feed into some sort of dashboard or some sort of, you know Requirements or or shared responsibility matrix where You know, give you the given example, for example, you know, see amazon's on the call here, but let's say you have Outposts with Certain things in the region and you run this conformance tests the form test can tell you that Well, there's nothing wrong with the virtualization layer Or the kubernetes layer, but then, you know, your applications still face Failing above the kubernetes cluster uh, there needs to be Some output that's basically before you submit us. Let's say support request that says that You know, these these partners are not They're conformed. There's that the issue is not there. Um, so that it's not about a From a support's perspective They're not just, you know, trying to push the I don't want to say blame. Blame sounds too negative But it's like You know, it says all your outside outside of the conform stack per se It's that okay. Let's work on the problem here. We know it is Listed down to, you know, these three four components Uh, which probably includes, you know, this vendors which is outside the cncf Kind of conformity test, but again, it's you need to give this reassurance this reassurance to to management that, uh You know that that that that it's there's a shared responsibility matrix there It's agreed on and the conforming tests kind of shows how it ticks the boxes of that and uh, and doesn't allow The classic support from some vendor underneath to, um, You know to to push the problem somewhere else Could be part of that investigation Definitely, uh Yeah, a dashboard would really be nice and you know, if if there's People that want that we could definitely try to put something like that together But right now the underlying artifact that it is a cli so it gives you Um, you know gives you, uh, you know red if something fails green if it passed for every one of the tests and has a name So you can actually see it but rolling that kind of thing up to a dashboard for all of the rest of your um tests that you probably should have For your environment. Yes, that's something I think I personally think that's important and yeah, it is, you know, we try not to say it's a blame game um in you know, it really shouldn't we really should be trying to It's really a handshake someone gives you An artifact and you're running and you want to put that in your environment You have some things that are a little bit different You as the quicker that you can give them back information info As a this doesn't work your new security patch It's great on your test, but we're your main consumer and you're breaking us So can you please give us another patch that doesn't kill us pretty quickly? Um that the faster instead of that happening in emails and things like that, but it happening In almost real time where people can get the information like it was a dashboard or some type of automated feedback on failure That that makes it to where your whole pipeline is faster. So yes, I really It really is a type of handshake between upstream and downstream projects Um Does anyone else have any questions or comments on this? Yeah, so we're really interested in these types of uh, this type of pain. So any feedback on how people are actually consuming their Uh, the artifacts their products and everything from their vendors and how they do How they give back their information how long those cycles are taking and when how we can help tune that with the conformance would be great Um, so If there's nothing else, uh, unless someone wants to ask some other questions, we'll give back, uh, 30 minutes of your time And uh, thanks for joining You know, we'll see you next time All right, take it easy