 Hi folks. Just in recovery from COVID but I'm feeling pretty good today. Hi guys. Hey Ben. Has anyone added agenda items to the meeting that shit. I posted the link and zoom chat. I can share my screen. If you can add your name. And any agenda items to the meeting notes. Let's see upcoming events. It didn't look like we have anything yet. Does anyone want to verbalize anything that they'd like to add or. Just type it in. Taylor's all over. I'm not, I'm not sure I'm looking at the. The meeting notes here now. I know we typically go through. A lot of people. I'm not sure how much has happened. Probably lots of people are busy as we've come back from the beginning of the new year, right? But I think that we do have some. That have kind of stalled. Maybe just need to. Just remind us all to. To review them. Including myself for bringing it up. All right. We'll check out. Anything else? A couple of weeks ago. You mentioned the spreadsheet. Which I've shared before about cloud nativeness. Cloud native assessment questions. I have found. Yeah. It may be the same one. You're talking about. That's what it's. I'll share the link and check if it's the right one. All right. Request access. Is it limited access? Requested. Refresh. No, I think it's because I created it under my phone account. And. Make it viewable for everybody. Not that I can see. I'll try. I'll just put another link on. All right. Oh, I see it. You need permission to access the document. Published. Okay. Sorry. No problem. Let's. I'm just going to add it to the. Is it something about ops? Ops. Or. Targeting. Like ops teams. I T. Everything cloud native. I can't remember exactly the title. Oh, sorry. No problem. Let's. I'm just going to add it to the. Cloud native. I can't remember exactly the title. So it was. It's called just cloud native assessment questions. There we go. It was around the cloud native and it's a solution pool. A scene by the platform. That's what it was. Yeah, that sounds right. So just drop it in there whenever you get to it. Yeah. Thanks. Does anyone else have anything? I'm not sure. I'm not sure. I'm not sure. I'm not sure. I'm not sure. I'm not sure. I'm not sure. Notice daylight savings. Change and March. So. Can affect when people join this call. Cube, Conny, you. And one of the things. That'll be new is a co-located event. I called native. It'll be there. With. Conny, you. CFPs are open. I'd love to see some submissions there. And if anyone is interested in sponsoring. I think the info should be on the main page. Otherwise. Reach out. And if you have questions about it, let me know. Open source summit and. You and. N a are both open right now. If folks want to submit to this. Controls go away. High floating meeting controls. All right. Has there been any progress on. The air gaps. Let's see. This is back in November. On Kai. Some more questions. All right. So. I think. We should start seeing more of Jeffrey. Over the next few weeks. And then maybe this one will get done. So I'm just going to go on. If you all haven't seen this. You're on the call and you haven't seen it. Check out this. It's a set of. User stories. Related to. Air gap environments. That can give some context whenever we're talking about. Best practices and gotchas and other issues that. Could run into. Cloud native. Methodologies and. Kubernetes environment. So let's see. We have the. This one. I don't know if the ends on the call. You're on the call. So this one is about. When. You have an exception on the ability to follow a best practice. And. Ensuring that you communicate to everybody concerned. Why you're not able to follow it. Any type of work arounds or something. So let's say it's a security type of best practice. Maybe. Not running. Processes as the root user or. Having a privileged pod. Something such as that. Remounding proc from the host file system, whatever it may be. Where there's a best practice. Security best practice. Related to it. Running things with the least amount of privileges. And you may have a very valid reason. For example, for example, if you're in consumer service providers, the ops team running it may agree with. The idea here is to communicate that. So there's some. Information in this one about. Communicating it and some thoughts around. Around that. And talking about the motivation here and everything else. I think this one should be a good one. Because we're essentially talking about what do you do when. You're not going to follow a best practice. I think this one should be pretty. Agreeable. I think to most folks. We need to have exceptions and we should document them so that everybody's aware. Right now I'm not seeing. Any. Comments. Any thoughts and we can add them right now. If you want to discuss this. Or you can review it and please add. Go ahead. I just have a question because I saw the title. Working in progress. So that means that. It is complete and we can start reviewing it. Or at least can you remove the. Working progress. It's not complete. But I think. We can add some feedback from folks to keep moving it forward. Okay. I'm going to. This is John Fulman. How are you, sir? Hi, how are you doing? Hi, I haven't been reactive in this community. I've been so busy with client work. I apologize, but I joined today and one of the reasons why I wanted to speak up at this point is I'm part of the. I'm part of the category office working group. Within the C.C.F. We launched a Q con North America. Last year and the team. I'm sorry, what group again? Can you repeat? I'm sorry. Cut car office. Okay. And so it's about maturity for C.C.F. models. Security. People with technology. And I think all the kind of talks about. Where you would just section over here. And then we're going to talk about the. The best practices. Part of what we deal with in the group. And we try to bring this to the C.C.F. And right now we're trying to talk to other texts as well. And how we can incorporate kind of graph. With other texts as well. And this may be one where. We may be able to do some kind of, you know, join such together on this. On this topic as well. If that makes sense. Yeah, that, that sounds great. John. I'd love to. Collaborate. Yeah. As a matter of fact, maybe we can give you a presentation on one of your meetups. When we can talk about kind of graphics and how we can help. You know, draw these kinds of conversations, especially when it comes down to the compliance. And those kinds of things as well. Sure. Why don't you. Do you have my email still? Why don't you, can you. If you just text to me or I'll capture right now. And I'll send you an email. Yeah. And we can maybe set something up and talk and then figure out a format. On where, where and how long and all the other things. That'd be great too. Again, I apologize. I just been. I've wanted to be active. If it's so long and. And I follow everything. I just haven't been joined the other beat the meetups, but thank you. I'll continue you soon. Thank you. Sounds great. All right. Any other comments or thoughts on this one before I move on to the next. Okay. Oliver. Do you want to. I can stop sharing my screen for a moment. Maybe you. Go through this one. Do you like me too? What do you think? Well, the only thing is unfortunately I've got to drop in 10 minutes. I'm not sure if I'm going to make it through it. We did go through this and I'm happy to do it again. Okay. I'll let you have your nine minutes or however long that's left. And then I can step in as soon as you have to go. Yeah. I mean, I guess maybe for the interest of everyone's time, I mean, I'm happy to do that, but. I know I recognize some faces on the call now. So I don't want to bore people to death. Is there anybody here who has not seen this? I guess maybe just like, I don't know if just throw something in the chat or something. If you don't want to otherwise just verbally. I'm not wasting people's time. Otherwise, I'm happy to give you kind of a quick tour through this. I guess what is remaining before we get some approvals? The only thing I'm saying is there were some. Comments from Pankai. Regarding it versus NF. So maybe adding something that was more specific and you had some responses to that. I think I don't know if I had commented in the past. I think it's very important for us to. Keep in mind that whatever the domain is. It's possible to learn and apply it in some way into the networking and telecom domain. And so we, we don't always have to go specific, but of course providing some context so that people can relate to the domain that they care about can be helpful. For sure. And I think, I think, you know, I mean, not to debate it here since he's not, he's not here, but you know, I would actually encourage, I think, you know, and in fact, for anyone for the, it sounds like everybody has heard this before. You know, when I, when I put the user story use, you know, use case slash user stories, I mean, they were very much from the perspective of, you know, what you would call, you know, online charging, what I call convergent charging today, because it's really, you know, as if you look at sort of 5G, this is a, you know, a portion of this is part of the 5G core. So, you know, as far as I'm concerned, there's not a question that it's, there's networking involved here. But, you know, I did try to, you know, just open the, you know, the scenarios up a little bit to give others, you know, an opportunity to say, oh, wait a minute, it's kind of a similar in other areas or other aspects or other functions, I see some of the same kind of challenges and be able to expand on that. So I think Kankai, you know, he, he recognizes, well, there are some other areas where, and that's, that's perfect, that's great. I think, you know, I would encourage just to add those, propose adding those to the, to the list because persistent data is, is necessary. And I think that, you know, would be beneficial for us to have some outlines, some best practices for this as we're, as we are marching along here in cloud native, best practices. So I don't know what's holding us back, Taylor. I mean, people are, I have encouraged people to add, but I don't have yet to see anyone saying, well, that's not a use case or that's not a, you know, that's not, that's not true. All right. I'd like to get this, this one specifically pushed through. I think that would be happy for Pankai to contribute some things around these topics out of this networking paper from us next or contribute them to a new document, wherever they happen to fit. Now, we, as you know, that all of this is supplemental content, these use cases, user stories, this is something to help with best practices that we then want to see how we can apply them. That's what this is about. And any additional content that gives us context helps us to see where things can be applied, should be applied or should not. It was great. All right. I'm going to open this again, like this. So we have quite a few people on the call. I'm going to just ask, has, have folks on the call, who's been able to look at this? I've gone through this, I went through them. Of course, several times with you, Oliver. So has anyone else looked through this? Other than when Oliver went through it with everybody? I haven't read it, so I can't thank you yet. All right. Now I have another chance. I felt that this is not my turf, but I'm really glad I can go over it. I only partially heard you, Ben. I thought that this was not really my turf, but you know, I'm happy to go over it. Oh, well, I think the use cases and use user stories. May have areas where security can be applied since security is pretty much everywhere. Probably the same cigar with yourself. Have you looked at it? Okay, I should take a, you know, next few days I will go over it. Okay. Thanks, man. Hey, Taylor. Yeah, I have to go through this. I'll go through this and let you know. All right. All right. So while the idea here was to try to get enough context to start talking about best practices for handling state in cloud and a cloud native way in Kubernetes environments, I think these user stories are going to be able to pull out a lot of other things as well. You could see networking, of course, there's availability stuff which ties into resilience and availability. I didn't hear from Ildico. If you've seen them, but I know you have a lot of familiarity with data handling on the open sector world. So you might be able to provide some feedback here. Or more context as well. Yeah, I haven't had the chance to check this one out yet, but I'll do my best. Okay. I'm sorry. Busy start of the year. I understand it's, it's for everybody. So I've tagged you. In the, as a reviewer. So you can check that out. So. To save Oliver from doing it again. I know you have to leave. Just a quick view here. This is. Somewhat a mix of use cases and user stories. So looking at it from the CSP perspective and persistence of data. And then we have some user stories talking about from the subscriber. Perspective going all the way through and what needs to happen. These. How to deal with low latency. Updates whenever you're needing to ensure that the data, this specific one has been driven from. You could say like. Could tie into financial and accounting and other things, but there's other reasons to deal with. Low latency. Stateful. Type actions besides that. I think other people could see. This one's kind of related. Acid compliance. So this could be related to potential requirements. Or it could be where they're actually saying they need. Acid compliance. Or it may be that the actual. What, what comes about. You know, you know, underlying things, these type of things may end up being, we actually care about consistency and durability. The isolation is not a priority. It's not always, you know, people aren't going to normally try to break these apart, but if you can get down to that, the specific reason it can be applied in other areas as well. Availability. There's a lot of stuff around cloud native practices for how to be more available, which in a lot of ways is quite a bit different from how things have been done in the telcom world and how it was done in other domains actually in the past. There's been a major shift to try to, how do you handle this? How do you do availability in these type of dynamic environments where you expect failure? That's one of the big things. Anyways, and how to recover. This would really have to deal with how do we make sure that the services and data and everything are always available. But how do you do that in a cloud native way? Of course, one of the ways in the past, if you're like a Oracle fan or anyone else, you may have seen massive systems replicated with big sand storage and everything else. And that's not how you would approach it from a cloud native way. So how do we do that? So there you go. Quick overview. Please come check those out and give some feedback. If it looks good, what we're trying to do is just get us some user stories that we think provide enough context to be useful whenever we're writing up other things, best practices and other documents. That's the main thing. And we can always iterate. We can modify. We can do other pull requests to add, update, clarify. We do want to get these through. So once we have four or five thumbs up, then we can merge. And I think that's it. Let's see. Tom, did you ever get the assessment ready? Or do you just want to share your screen? You can do. I've given you access and all of that because I've got the requests through. Which, which link? The first one. If that doesn't work, I'll try and copy it over to a number. It worked. Is it just for me? Or can anyone access it? I think that version is, I think. If we copy it out into something else. I think looking, looking back in our Slack chat history, you were going to put it in the tug. Google drive. Oh, that's right. And I don't know. I may have actually put it over there. I'll. Just put that on the today. Cool. Yeah, I haven't reviewed that for probably at least 12 months or so. So I will do that. And I'll think about whether other things as it should be. All right. Do you want to. Chat about it real quick or? Yeah, yeah, sure. So. I mean, this was, this was pretty good. Do you mind if I just let you share your screen? And that way you scroll through it? Yeah, that's fine. All right. Go ahead. Okay, got that. So yeah, this was put together in the kind of early days of. The, what was before the CNF working group. I don't know what it was called. But we will, we were thinking about. How can we, what questions can we ask to understand. The cloud nativeness of something. From the point of view of the platform. So we're not, we're not trying to assess the, the cloud nativeness inside the application, which I know. I know that the kind of CNF tests we use, looked at some of those. So these cloud native principles, I think you'll probably be familiar with those. I think the ones that this group and others have been through a number of times and obviously missed specs. And so it was, it was, I kind of phrased it in my head as a kind of bunch of questions that we'd ask. And understand whether, you know, whether something was cloud native or not. So, you know, it's obviously not perfect because nothing's as binary as that. But we started to use this in, in Vodafone to sort of just do as a really simple. Set of questions to get people used to answer, asking themselves when they were looking at stuff. As to, you know, what input the operator has to have, you know, how tight is it to specific project hardware, et cetera, et cetera. So this, in this current form is not currently used in Vodafone. But certainly the characteristics and the questions are in different formats. So it'd be interesting to understand, you know, I need to go through it again, because I haven't looked at it in a couple of years or a year or so. Yeah, last edit summer 2020. So it'd be interesting to get people's thoughts on, on what's being asked, how useful is it? You know, there's likely to be loads of questions, comments and debate around the yes and no part. Yeah, that was the, that was the idea of it was to guide people down. Is it cloud native or not? I think it would be nice to have an assessment like this for application focus. So when you're building an application, we're thinking about, I mean, this, I guess this kind of covers managing deploying as well, but getting that other viewpoint. Yes. Adjusting the questions for a copy and making something similar. Yeah. I don't think that should be too difficult. I'm happy to start work on that. That'd be great. And I'd, I'd be glad to work with you on that too. We'll put together draft and share it with me. Yeah, sure. Does anyone have any questions or comments about that or. Right, anything else? Not for me. Thanks. I'm going to need to drop in a couple of minutes. Sorry. Take me kids for me. All right. Thanks, Tom. Thank you. Thank you. Any questions? Thanks to everyone. Y'all, um, I guess we'll end it here and we will see you again next week. Same time. Thanks. Thanks to everyone. Okay. Thank you.