 Good morning. Hello Taylor. Good morning. So it is five after eight. So I don't know, should we start or wait a little bit more. But you guys. Go ahead and start. Let's just take a look at stuff I'm working on some of the issues right now. Okay, I will share the screen but okay. I think that you can see my screen right. Yes. Okay, well in terms of announcements that we have something for the next or something coming. I don't know. Well, let's see. There is one this week. Well not some announcement but this week is a Telecom TV event on Thursday. Yeah, the great talk a debate one second. I can get back to the right on there. There we go. Yeah, there's the agenda. One of them that looks interesting open ran and closed ranks. Different people working on different sides. Jennifer Dell. Someone that executive director of tip. Telecom and for project is going to be on that one. And all of these are free that anyone can watch them or anything. I think so right. Ticket. Discount ticket price. I can't tell. I'm trying to look at it. Watch all the key moments live and free on telecom TV. At least it seems like it based on the. Oh yeah, here we go registration. It's interesting the registration says. Which ones are you interested in but doesn't mention. Oh yeah it does it's just telling you others that are coming up later in the. 2023. So all right. Open ran summit telcos and public cloud summit and stuff but those are all 2023. I guess we could add those. Other ones. Okay. I will try to register and. I can wait and. Yeah. Here. I found like, and this week is the open source. Summit in Japan. There is one single topic. Which are related with telcos. I don't know if it's meant to be Japanese or. And I didn't register because I'm. The ticket for this one is 25. Dollars per. For the virtual event. I didn't consider like just paying 25 or. So single topic, which I don't know if it's going to be. In English or Japanese or. Probably. Later. We can access to the recording and see what, what happened. Right. Sounds good. All of these three are part of the. One or our separate things. Are different things, right. Yeah, those are all different events. And they have options to your chest. Virtually or all of them are important. Probably virtually most of the telecom TV has virtual. Okay. I'm just spitting them in here because I think we should at least take a look and see if there's any items that. I think are important. Any, any other event. Probably. I mean, there's MWC. But. I don't, I don't, you know, that's a big event. I'll say. There's some encouragement at one summit. And the elephant developer forum to. Get engaged with the tip staff. So maybe we should look towards some meetings. With them and what would be, you know, areas to collaborate. Did you take a look of the. Silver or the name. Silver project. Yeah, I have been some. Watson, especially has been looking into it, but. Ideally, we can find a way to collaborate and have. Contributions both ways. If they're going to be utilizing tools and. Existing documentation and other stuff. It would be good to contribute upstream from Silva and then. For folks to be engaged with them to incorporate directly and, and think about, you know, the direction they're going. Yeah. Have it listed right there. Look at that. CNF tests would be the test suite. I'm guessing, you know, just Kubernetes in general, but I think they're actually. Gonna. At least have. Some part of the. Kubernetes ED test or Kube ref or something, which will. Be related to the. Kubernetes conformance or I'll say the. Ensuring that. It's compatible. Yeah, from my understanding, it's like, let's be taking the. I don't get. Right. To, or. To just focusing in this particular area, like, I mean, they're, they're not trying to cover. They're, they're a one or. So. Yeah. Just read the documents and from a lot of good things and so in. So the issues that she. They. Find like that. Same rail. Okay. So what else? Have you ever watched the. The. All right. The recordings of the one time it. No, I haven't. Is there some good ones on there to. Yeah, well, I was probably one of. I like it was. From Santa. I guess she, she. She has that. Good presentation talking about the. The problems with the telcos like the direction that they are taking. And. They wise are. Or the reason that they are, they having to, to start working with Matthew and. But Matthew's proposing. So I guess she summarized very well, like. The main goals and. The reason behind that. Probably. For now is one of the. Great. They want one. Not a great one, but just. Offering like a different point of view things. Probably this, this could be. Yeah. Yeah. Yeah. Can you just add a note here? No. Drop the title or whatever. Yeah. The rest of them are. Are you there? But. Not too much. We have been trying to do. I don't know. Different perspectives. Things. The other one was fairly with that. The. A few words store shop. So. They provide like. The sort of code. Yeah. Sort of things. But I don't know if you have a chance to attend it or. No. Yeah. Or Matthew. I guess. The source code. The use for. I was watching and slack when they were doing the updates, but I didn't get back to it. By the time they did a demo, I saw they were doing up to the last minute changes. You find it interesting. Well, I like the way that. John. Explained certain concepts and things. So. One of the terms, which is so confused for me is package. In terms like a nephew, I guess it's more like. Like a kind of a home chart. But more like open and. Has an option to. The way to treat things from upstream and combined with the. The downstream. So. Yeah, he has. All these concepts defined there and try to clarify all these things. For the workshop. Yeah, I have a lot of things. I mean, it's not easy to reproduce because. Definitely. You need like a virtual machine in. In GCP and. Have. You to. Ripple. Associated with that PM and things like that. And that's relation is based on. The whole name. But. But yeah, just reading the documentation. It's very valuable in terms like. At least clarify a few things. From my point of view. So could the starting point. Right. Sounds good. I'll check that out too. And. I definitely would like to watch that video. Been trying to get her engaged. Some she's. Okay. Open source summit in Vancouver. Before. Things officially really got started. Like some of the initiatives and. It was just a small. Gathering to communicate what was going on. She had spoken back then about. Like adoption of stuff like that wasn't happening. Like CICD practices and things. So. It would be. It'd be good to get her involved. See how we can get engaged with her. Yeah. Absolutely. We had to. To have like a PR open or like that. Yeah. I put a title on for this. I mean, that's straight forward. Just say do it. Yeah. For me. I'm okay. So do we have to wait for. Come to. Thumbs up or anyone else? I guess. Well, yeah, we can wait for. Does it look good to you. That title. I was trying to add. Some other people just want to get it. Closed out. I don't think when it's five for this. Would be more important as. Adding. Adding more content to that. Best practice. Thanks. Lucina. Or. Creating. Other best practices. Like there's some other content. Yeah. I mean, it says user stories and stuff, but I guess it's valid for everything. There's maybe enough. And we just need to. If you go open the actual. Go ahead and merge it. I think with listening on your. As long as nobody. Objects. It's a title. It's minimal. We've already accepted the best practice. Yeah. Delete it. And then go open that. Best practice. From. Okay, it's an exception. Yeah. Oh, can you go to the top. Did that. Title. Was this supposed to delete some stars or something? Are we supposed to have this? I don't think maybe I was supposed to delete them. Yeah, because I went. You have it. Just edit it and do a direct. Just edit it. Just edit it. Just edit it. Just edit it. Just edit it. Just edit it and do a direct. Command. Treated it like it was going to make it bold. Didn't. Just before that, let me take a look out. Because I thought some. There you are. We're hiding here. Just. He's not in send out command. All right. Down sections. Oh, it's the same, right? That basically, yeah. Yeah, only one. Yeah, it's an emphasis and we had spaces around between the asterisks. What are all these release sign-up, it's not the same case? There's no spaces. So I guess, you know, I don't know that it matters. When you're using the pound sign at the start, it's already going to do something. Okay. Just, yeah, you can just call it fixing errors or whatever. Mark dinners. Linting errors, yep. That's good. All right, so if you scroll, so we have all these sections proposal work, workload context. And just scroll through and you'll see what do we actually have in this document. Proposal. Well, I was just saying, yeah, what is all of it, if you look above, it's really the only content we have. So that, I mean, that's fine. I think that's enough to kind of communicate what is this best practice. What's actually relevant and make sense. We haven't been doing those check marks. I think we should probably start doing that. This all seems completed enough. But do we need to delete some of the stuff that's lower down. Like, like, like the workload context. Yeah. So I mean, it says user stories optional, but do we just leave it like that? Or delete it. You know, it's kind of a template kind of seems like we should just clean it up once we're done. I'm not sure. Because I don't know, probably eventually we can add more things here or or if we move, if we modify template, we have today all its places as well. Well, I'm not saying modify the template. I'm saying literally just modify this one best practice and delete the extra stuff that's not necessary. So it's clean at the end. We can add them back if it makes sense, but user stories for this particular best practice don't really. Don't seem to matter unless you're going to write your own right here. I guess we could write a user story that says here's an example of someone having a best best practice that they're going to ignore. They're not going to follow a best practice. So then they document. If we want to give a real example, like when should you not when an example of not using or not following the no root processes and containers. So maybe a side car that. That's using it and it has an exception. But then we literally have to come up with. I mean, it's fine if we want to give real, a real example. So maybe it's okay to leave this and prompt us, but we should put something in there. What we have done in the other documents. What we have information for them right like that. Yeah. References would probably be. Something easier to add in. To that, to that one. Anyways, it's fine. The ticket open was only for title. It would be good to add more content, but. We can also work on other best practices. I at least want to close out what we had an issue for. The references. And I guess we could open issues. But I think. Mark them as. When they're. We had some input from. There's a way to say, Hey, we're open to anyone collaborating. They're adding two things. Help on it, like the tags. There's a. I think it's like. First contribution or whatever you tag in it. People are starting to click through tags and just help on any project. So. If there's anybody that's looking to contribute. You know, we've had people drop in on this call before. So we could add a, I guess that ticket add title to exception. So that would have been straightforward for. Pretty much anybody to go in and read and go, okay. Here's what the summary and motivation. Let me come up with a title. It's. Document your exceptions. We could create new tickets, like add, add references to. That best practice. And for that particular one, I think someone could go through and add a reference. So here's an example of documenting your compliance. There's. There's a lot of. Examples out there for different, any project. It doesn't really matter. This isn't specific to cloud native or tell comments. Communicating. If you're following standards. Community standards, best practices, whatever. Can you close. Ticket. 227. All right. Yeah. Completed. Anyways, I think we should. We could add tickets. For any of them. Some motivation. Requirements for multi interface. What do we have left today? Eight minutes. Well. When I just started the. The draft. But when I created draft, I didn't know about. These. Discussion in the community about that. Modifying the API is what they're trying to do in the. To support. Multiple interfaces. So, so that's why it's like a hold. Because. I don't know. We don't have to. Like a best practice for that. Mostly we're going to have or for what. The community is going to propose. So. That the current state, like, I mean. Definitely we have the draft here. But yeah, this is not something related with what. The community is doing. I mean, does, is it not aligned with what they're doing? Annotations. No, I don't know. No, from my understanding that they want to. Modify the current API. Definition. So that's the. That's my understanding. It's like. In your ball definition, you will have. The capabilities to that. The different. Interfaces. Implementation on multiple is going to. That new API definition. So. So I still don't know how they are going to implement that. But. Probably, yeah, probably the thing that I should. Refer here is like to all the discussions that are hot. In the community. The way we can. Correlate things. Yeah. Yeah, because they have a lot of documents and. Discussions in the community, which are not affected here. But yeah, I guess. In regard in these draft. I think it's. For now it's. Better to keep it as it is like a draft. See what. It's happening in the community. I mean, if, if we can write it where it's aligned. Then we can move forward. If it's already aligned, then I think we can move forward now. Aside from that, I think it'd be good to get an update from. I don't know what's going on with the discussions. The current discussions will signal work. Do you have you been keeping up with those. The last time that I attended was. Before the one summit. But yeah, they were discussing the. The things that they discussed before in the keep calm. I mean, they didn't. Too much progress on that topic. I'm trying to find the actual. I don't even can't find the. The meetings. Like when do they may. Not in a slack. That's good. SIG network, multi-network. Oh yeah, they have a specific channel. That's right. Community think was on November 2nd. So what's the next. They had. They didn't announce it in slack, but they had a November. That's right. All right. Rank requirements. Oh, this is a follow-up meeting. This one. There's a. Each network fighter manages their end points and end point slices. Topic. I guess this was. Recorded. Maybe. Let's see. Okay. I'm going to ask. Google may. Very interesting doctrine. This. Talks about the different use cases. And they discuss. Why, why they are doing these. Multi-network performance. Which one. Yeah, the requirements. Yeah. So take what they use during the. Contributors on me. And they were checking. They were checking that. So what I'm going to do is. These two. Documents. Here, right? Like, at least. Like a reference. But the community is doing right. Sounds good. So the annotation. Document. The best practice. To me seems still relevant. Annotating whether. Telling people that they need to do annotations for. How they're. Setting up their network is. Is moving people towards. Called me to practices, even if the community hasn't cited on. Where that could be. You can still. Compliment. The, some of the core concepts for doing. Doing these things. The configuration declaring your. Declaring. Your intentions and what you're wanting. Even if you're doing it. In. Vendor specific. Annotation types. I mean. It's still moving towards that versus saying, oh, we're going to statically generate. What we need with a shell script that. Generates, you know, the things on the fly by talking to some external database. And you have no idea what's going on because it's statically configured by a network admin. Ahead of time. Like that wouldn't be cloud native. But if you said that you're. Defining stuff and then the. In home templates, even if it's Dan M or. Multis or whatever, but you're leaving it up. Like device configuration or whatever else. If you're trying to make it where that stuff is dynamically determined. It's at least moving towards it. And then if we have a more generic way of doing things, then that configuration that someone is already using. With multis and Dan M or whatever, like you've done it. That works with all of them, like just adding all of the different ones. And then. Determining based on. The CNI that's there, you can do it. Well, if you've already done that, now you can simplify your code because you're in my mind, you should be able to simplify it. You're moving it all to one standard. Configuration. So I think this document doing the annotation is still. Valid moving it forward. Yeah, and also the other thing that I was thinking right now is. It's also applicable for, for example, controllers. So let's say that. There are certain annotations which applies only for engine X or. Check proxy. So. And also you can apply the same, same approach, right? So. So you can specify all. All the major ones or like. All the different notations. And doesn't matter. Like, I mean, at the end of the day. Your part or your deployment are going to take just the annotations, which are relevant to. The particular. It's a controller, right? No matter if you have for once those other ones are going to be northern. So basically the main idea is not restrict the number of annotations that you can put it in your. About definition. It's like. Put whatever, like. Don't be scared. Yeah. So. So what do you suggest? Like. To continue doing the. Discussion in the draft. So, or starting. Moving the draft from. From there into the. Into a PR or. Taylor. I'm trying to, I'm thinking like, if we get it out, ideally we're going to get. I'd like to get some more people engaged on it. And. I wonder if. What's been written if it would be worthwhile to. Have something written up. Maybe just taking what's currently there. And then go talk with. The sig. Multi network group. Add it to their agenda. It's an open agenda. Get it on. You know. Maybe we go talk with. Hop on like a. A multis call. I think they were talking on the plumbers working group, but that one might not be as good. But. Community getting. Feedback from. Other folks would be good. So whether it's written up in a pull request happens, that would be fine. And then say, hey, we want feedback on this. I mean, I'm almost up for tagging people. In the GitHub. If a pull request is there. Say, just start tagging people in other groups. Yeah, that's a good idea. To prove. This, this idea and see. Yeah. I mean it. The way it's written is a little bit more general to where it might be helpful for the sig multi network. Or if they're doing and how they're wanting to apply it. Probably would have been good to. Show them that. At the. Cube con meeting, but. If we could get it on a future one, that would be good. Yeah, also if I did some of the functions or like. Something is missing there. Be free to add it like. Probably. Very good. Don't comment on anything. I'm up for. Working with you to try to. Get something ready and maybe pull in some other info. I'm. Silva, you know, if we can get on and talk with them and say, here's an area where we're trying to do, I, I seems like they're trying to move forward on implementation. And it would relate to. RA to RC to stuff with the etiquette. So. Maybe reaching out to. Silva and. Are you involved on the etiquette side? Currently, do you think this would be good? I. Barely. I mean. Yeah. Just. I didn't attend all the meetings. Just. But yeah, I can. I think again. And she. Can propose that. I'd like to see if we can talk with the silver folks. And then the other part would be. Testing. Like what. Think. I mean, thinking forward, of course, if. If something moves forward in sig multi network, then there's. Going to end up being. E to E test around that. Eventually. That'll go into Kubernetes conformance. But it. The. So once it's in Kubernetes, then there's going to be different things that could be tested like in the CNF test suite and everything. If you have a CNF coming up and it's using multiple interfaces, is it using this new. Multi network. Thing that whatever comes out of that. But that's far future. So is there anything that we can do now that. Would be. Beneficial as a tool in the community to. Say. Are you doing. Declared of network configuration or not. Yeah. Because. There's teams. I'll be. The thing is like. NSM. They. In NSM. In the. They. Did a complete refactoring of source code. So basically the. The way to define things and. To use all the API. They. Moffitt complete everything. So. The source code that I used to. Have for NSM. Is not working with the. Latest. Release that they have. So I don't know. Why they decided to do that. Probably they had their own think of reasons to do that, but. Yeah, I need to. Check with. I don't know. He prepped can help me. To. Fixing those things because I. I couldn't make. To work for. For the current release that NSM. I try to. So basically what I'm trying to say. I tried to date. The source code that I have for. Making sure that. She's still. I'm valid, but. Have some issues with that. NSM. Daman seems to be. Deprecated. No one. Is. Updating the source code. Anyway. I. I tested. I'm still working with. Still. Newest. Multitudes still working as expected. So. So. Yeah. It's. My only concern is. With NSM. NSM proposed. A new. Different approach. Compared with. And then. You know, what does you have to pre-define the networks and you. Say, well, I have all these. Different networks and. My thoughts are going to attach to those. Of course, during the. Per request. In NSM. The approach is different. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. In NSM. The approach is different. Like. You don't define anything. So don't you know. Find it. Your deployment. And. NSM. Is going to start. Connecting. Or creating the networks. Doing the execution or the creation time. So it's more like an on demand. Solution. So. This, this source code seems to be working before. And I have the end to end testing and checking all these things. And try to split in different pieces. For example, it's just. It's just focusing the structure. It's fine. The things I said for, for the infrastructure. So I. And I. Have. Different things like. For example, this component can be. Replaced with. A similar solution. I haven't tested. But yeah. The mayor concern is this one. Which was. A huge problem because they. And they don't have. Good documentation. How. How can you use your. They're dedicated. To consume those services. So this, they used to be. The initial approach. Which was. A fine for my. Proposal. Now is. I don't know. So. Yeah. It should be nice. If. Fred can take. Some eyes on this and help me. Just. Yeah. We're putting forward. The idea of. The best practice. Before there's. A community consensus on how to do things. I think. Something like this would. Would be instead of saying. Here is how to do it. It would. It would be. In an area that says, here's an example of what could be done. And then it would be okay. Since things are going to continue changing in. Network service mesh. And other. You know, whatever comes out of. SIG multi-network. Then our best practice needs to make sure that any implementation specific stuff is. It's apparent that it's not. The standard, but instead just. An example of what could be done. Okay, that's right. Yeah. As far as tests. Testing goes. I guess it can be a. What we had referred to as carrot. I guess it's a carrot test or it's a test that indicates that you could be doing something cloud native, but we don't know if you're not like, you may be doing something we're not aware of. So if we looked and said, hey, we're looking for this type of annotation. This network service mesh annotation. And they have it, then we go, oh, this is good. They're doing something positive. So we want to let. End users of the CNF know that they're doing something positive. But if we don't find it, it doesn't mean that they're not doing something we didn't recognize since there's not a single standard yet. But if there is something that we can show, here's what's currently happening. A valid, like you think it's a valid use of network service mesh that's still applicable. Like whatever they're currently doing. And we can write up, here's an annotation test. If we look at it, that seems like a valid thing. And if there's anything that we can say, here's a valid example. In multis and Dan M of doing annotations. That's like a community standard. If you see anybody doing something. Then I think that could be a valid test. So then we're looking at ideally multiple ways that people can do annotations until there's a, you know, a single way, then we need to try to cover and look for others. Probably right now, as far as the CNF test suite, it would be a bonus type of test where we're going. If you see this, then it's indicating positive. Cloud native behavior by this CNF. It's not, we're not saying, yes, they're absolutely cloud native in the way they do this, since there's not, but it's an indicator, which is okay. I mean, communicating to someone that it appears they're doing something good is fine. And that same sort of example that could be looked at for testing could go into the actual best practice right up. So we're keeping the best practice general. And we're giving examples. And then it, you know, if. Both signal to network makes progress and they came out with like an alpha release, we could just include that. And we do an update to the same best practice. Anyways, that's kind of what I'm thinking. Yeah, no, that makes sense. So is there to propose something and. Eventually. Fine or foolish all these things. Based on the feedback from the community and sort of like. No, mentioning anything. Yeah, we're about time, aren't we? Really? Okay. Well, that was the, I guess the only. I don't know if we still have the next. Yeah. I don't know if we have to start preparing for the holidays and. If you want to. Have the meetings or. Yes. Let's see if I. Real quick before we move on to that. Looking at your screen right there for the open issues. I would the link between non-route best practice. And run right in test suite. That one's pretty straightforward. Tom, I want to get that one knocked out. I'm just kind of looking at the titles real quick. So that one seems okay. We have, we just need to update it in the docs. That seems pretty straightforward to try to clear. Some of these out and have momentum. I want to add that to my to-do list. Would you assign me on that? Okay. Maybe Lucina too. Let's get multiple people on this. This one is straight forward enough. Let's get it completed. All right. Go ahead and go back to the list of issues. And. The 228 skip that one's harder organization. As multi network. We did that. The do not run containers with privileges. So that's another best practice. And. We have all the content. In the list of issues. Google doc. And there's also a test. Test or multiple versions. Of tests. In the. Inside of the. Test suite. There's one in the certification enabled, but the test suite actually has multiple types. So I think that one should be one that we. Put together sooner than later, since we already have content. And having more best practices. I think will motivate people. To get involved. And it's good to document. One thing that. I remember in Lucina. So I'm just trying to think of like what are some things that we can put in place and. Move forward on. Lucina. I mentioned. Previously to. That we could start using that best CNF dev. Document. We had held held off because we didn't have. Any best. Enough best, maybe no best practices when Robbie created it. But I think we could start linking them in there. Like the non root. And that would be one of the best practices. Like how do people find these? Well, you can go and get a hub and look at that CBB. CBP folder. But. I think it'd be better to just send people here. Now this may need, you know, some updates, or maybe we just start putting them in. I just realized, scroll it up. Under configuration life cycle. Best CNF dev applications configured via standard way. I guess those are just examples. What is number two application now? Some membership of the tier to its peers. Interesting. Those are not. Those are going to be fake. I think so. They just got put in there. I was trying to see if they're actual best practices that we should write out. Yeah, that didn't go anywhere. Yeah, those are just examples. But adding the ones that we have in here might be a good thing. I don't know if we want to update. The. Categories. Before doing that, or just put them in. Because we're trying to, we want to be able to get more people engaged since, you know, in 2023. Get this going again. We had a higher number of folks that were. Involved for a while and it's kind of fallen off. But we're towards end of year. So. Thinking like 2023 and. Getting people engaged. And contributing. If we say, here's what we're trying to do. We're trying to help. The developers and the, and the end users of those developers with. Having CNS that are following best practices that everybody understands. So here it is. The best practice for CNS developers. We're contributing right here. And starting with this document. When we're talking to people. It's probably better than go to get a page and. Clicking and. What is. BBP PPP stand for, you know. Just. You know. Yes. Confused. The other content. Or maybe one of the. We can add it here in the cities could be sustained. Maybe. Some practice. Best practice for sustainability. Or environment. Care. What do you think. I didn't catch the last part. Can you say that again? No. Yeah. I was thinking like maybe. Providing like. 11. The number 11 like sustainability. Like. Or things that impact. Yeah, that's great. That's great. Yeah. Sustainability. I don't know if it's just environmental sustainability might be the category. If there's any other sustainability. Yeah, I don't know if we have some best practices in that term, but at least like raising the topic there and. Could be something. Interesting to explore. I like it. Environmental sustainability or just sustainability. I don't know if there's any other sustainability. I don't know if it's just environmental sustainability might be the category. If there's any other sustainability. Yeah, I don't know if we have some best practices in that term, but. I don't know if there's any other sustainability that a CNF would care about, but. Yeah, what Lucina just put in there. Can we add this comments to the, if it hadn't already happened to the. The meeting that's please. This is a good idea. I really like that. Thanks. Thanks. You're awesome. All right. Yes, for that, adding that category. And then what do you think as far as adding best practices into the. Best CNF dev doc. No, that's also. Yeah, that way we can give it more visibility. Right. Since we're running out of time before break. Let's see. Let's just mark that I'll come back to what I was going to say. December 26. Let's just cancel that one. I'm a no on that. Let's. Are you going to. Do you want to run one on. On the six vector. No. All right. Let's cancel. And. And this one as well, right? Cancel on the second sounds good. But what is the 19th? Nothing. 19. That's not, that seems all right. Let's keep the 19th. All right. Okay. Yeah, looks good. All right. So. Are you available this week. For maybe some working sessions to get through some of this. Yes. I have some time. So one that I don't want to do, but I think should be done. If we're going to do this. Add practices to that document is update the categories. From 10 to seven. Take it. Two to eight. That's something that's. A little tedious and annoying, but if we get the categories updated. Or decide if we're going to update them and then do it. Yes or no. We'll make it better if we're adding tickets. Adding new best practices. Sorry. So ticket two to eight. Which is going to. If we match this best practices for CNF developers. Set of categories. And looking at. Matching them to the CNF test suite. Or a set of categories. I think it'll be easier to find stuff. So I'm going to. Show. I think that like the rationale document has content. Like that's base content for best practices that we could potentially write up. Any. What's that. Are you going to share something. I'm sure I can share. So this is just this rationale, which is just a short, these are just short write up of different things, you know, microservices, reasonable startup time. If they're not responding to readiness checks. And this is after downloads. So this, this test. Waits for the CNF. The image to be available and actually. Initiate container startup. On the host machine. So if, if it's not. Having any response at all, then. And it's indicative of a monolithic application. So that's the idea. And. Having something around a best practice. You know, if it takes. 20 minutes for an application to actually respond to availability. When something's going on. Even if it's saying, I don't want to accept new services. Don't, don't. Have the proxy or whatever. Put me in service yet. Because it's waiting on multiple other things to come up. There should be some type of responsiveness and say, I'm waiting. You know, if I'm thinking like restful applications. You can still respond and then have applications that are intelligent because of the response. That's not the best choice, but it'd be better than nothing. Like no response. Anyways, the point is. If we go to categories that match, then I think it's going to be. A little bit easier, but we need to look and see if it's makes sense for what we've been writing over there. So compatibility and solubility, upgradability. That one. Let me. Bring this. And then this. Not found. Not found. Doc. So installation. Upgrade configuration life cycle. Those were merged. Installability and life cycle management. I'm saying there's no space here. You'll mind a thing. All right. So this is. Merging two categories. Which there was overlap and which one does it go in? Is it going to go in. To configuration or is it going to go into. Configures life cycle or is this part of the initial installation? Well, upgrades and installation. I mean, there's configuration items that you could say, well, it's important to do this so that you can do deployments. But then you go, well, isn't that part of the life cycle? So that whole. Discussion around where it should go. It seemed like it was better to. Have something like this. So that was the decision there. Microservices, I think still. Split. I need to move these. Each other. So we still have microservices hardware compatibility. I think. Hardware support got merged in. Believe. But I'm going to go over to the test categories. I guess that's the idea. We don't have to do it now, but I think we should. Look at this and then decide. Are we going to. Keep them separate. Or they're not in sync or do we merge them? Okay. Just realized we had this configuration tests here and we have. Compatibility, I guess it is split. All right. So we need to look that over in my mind and then. That kind of influences how we think about best practices and. When we're communicating. When we're in the middle of it, you know, Victor, you may go, I know this is applicable in multiple areas, but when we're trying to get other people engaged and they go, I don't. I don't know what that is. All I do is help over here. And we'll go, yeah, it's applicable. But more less categories is probably easier. So this would be seven right now and eight. If we had the sustainability rather than 11 total. And you think that it's going to be a bit more confusing to have less or everything. In a single. Um, it's been. Less confusing when people are saying a best practice. Is applicable in two different categories. And those categories are similar enough. So then you just go, here's the set. They're all applicable. In the context of a specific best practice, it may say this is for. More applicable for the install on day one. And another may be well upgrades are applicable. They're not related to the day one, but they're also part of life cycle management. Those are real. They're kind of all related tests. They're close enough in relation. And depending on how you. How your workflow is and the opera, you know, operations workflow and everything. You may split those out or eat and have like a. A special dev and then salt team or. Or not, but it's all related. Whenever they come in. Let's take a look or if you want to look ahead of time, but I'll reach out to you maybe with some time and we can look at that and then look at adding best practices. And then some working sessions to maybe work on. The new best practices like the network stuff and how we present that to that, to different groups. But that's good. Right. Thanks, Victor. Thanks for listening. Have a good day. Thank you.