 Good morning all. This is Anil Panala. I'm the Senior Technical Program Manager at Microsoft. My colleague, Ying Shi, actually is a Principal Software Engineer Manager. Unfortunately, he couldn't join us today. I'm sure he's listening to us today remotely and he's been contributing in this presentation as well. So we both was thinking what to share in this forum. I'm sure most of you know about the Sonic and you've been very closely collaborating with us. So we just wanted to give a little glimpse on the insights of how the Sonic qualification is done when there is a change request comes in and how we actually look at it and why the Sonic quality is important. We wanted to give little insights to the community here and what kind of help or support we are looking towards from the community as well. So in the quick agenda here, so we'll do the quick introduction on Sonic. I'm sure most of you, we are in the Sonic summit, so we don't really have to explicitly mention, but I'm sure we wanted to give you a little insights on the Sonic introduction as well. And we wanted to give you why Sonic quality is very important at the stage we are in. We did a lot of enhancements in the Sonic and why it is very important at this point. And followed by some of the control process, it's been following right now for any of the image validations and what's working currently well and what support needed from the community. So let's dive in. So I'm sure this is one of the classic slide. I'm sure you might be knowing it. So Sonic software open source for networking in the cloud. It's open source by Microsoft and its partners and then joined Linux Foundation. There are many benefits of Sonic and some of the key benefits we wanted to highlight here is it's basically disaggregates the hardware network hardware and the software, which is very, very important at the industry level we are at. We don't have to lock in the hardware and the software together. So that's the benefit of the of the Sonic and the container solution actually offers consistent, you know, operational maintenance as we just heard from the Dell. They also were able to bring up a new solution Lexus EQ. We can do a lot of enhancements on top of Sonic and even in the security level also we can have a lot of features and functionalities through applications. We can keep adding them. And the beautiful benefit here is when we when we have a bigger scale organizations and we have a lot of physical switches and either multi running in a multiple network operating systems instead of that with Sonic we can actually replace with as a one network operating system. So that's it'll be easy for the management and operations as well. So what is Sonic, right? So again, going to the basics of it. Sonic is a Debian Linux based network operating support system which support supported by many physical switching platforms and it also has all major assets on the right side. I'm sure this is one of the classic diagram you might have seen from from many time. So all the physical layer actually we have a psi which is like a switch abstraction interface which acts as a hypervisor for the whole solution. And it actually helps in communicating the SDK communication back to the north side of it. So the Sonic is consist of a lot of components and most of all the components are containerized using dockers which enable to build whatever the calls you want are based on scenario which needs to be pulled out or the call we can do on the component level as well. On the top, since it's all containerized, you can use any kind of containerized management tools like Kubernetes or anything like that on top of it and keep adding more more applications for configuration and management tools as well. And we just wanted to say thank you to all the community members. I think it's been growing pretty well. I've seen a lot every year over a year we have seen new new community members has been added and thank you for everyone for contributing into this and making together as one of the best networks operating system in the world. So it's just a glimpse of how the Sonic is powering Azure cloud basically. If you see there are multiple layers in the network. We have a tier zero which is like a top of rack. We have a tier one which is actually leaf. We have tier two which is spine and we have one and above on top of it. The blue one indicates where actually currently we already enable the Sonic. So most of the tier zero and tier one we already enable the Sonic. Tier two we are actually currently in progress. We've been working on that. It's Sonic for Chassis. It's coming in in the tier two layer and it's going to go above that and even the van and everything. We have plans for that as well. On the management side. We also have M zeroes which are enabled by Sonic already and we are working on the C zeroes as well. So this is a kind of a high level of how how the adaptation rate not just how the adaptation rate within Azure itself how we are trying to do and and we've been going towards it. All right. So why Sonic is important, right? Why Sonic quality is very important? So we became a way of journey, right? So we did a lot of things. The features has been improved, increased a lot. The functionalities has been increased a lot and the complexity of the whole Sonic itself. We've been improving and there are a lot of new skills have been entering into this Sonic supporting the Sonic and a lot of combinations with T zeroes, T ones and T twos has been there and the adaptation rate has been increasing. The footprint in all the things is increasing. So it's actually we started with a small and we are in the very big stage at this point and everything what we doing is a quality. It's makes very, very important and and also the shifting left the quality, right? So finding the early bucks, which actually going to save a lot of time and also the cost for the for the organizations as well. So and and we are trying to see how the community can also help us to find the early bucks before we start getting into the into the production networks. So we would like to share some of the process we follow currently. So any anything in the community or anything we see, right? So there are a couple of ways we do it, right? One is the any of the feature requests. We have it or the issue reporting. So any feature request will go through the high level design review and the test plan review and which it concludes as a PR creation or any issue being remoted within the reporter within the community. We do the issue triaging and we find the solution and we create as a as a pull request as a new change request into the into the system. So and this is one of the key slide of this and what we do with respect to the process, right? So any of any any pull request, anything, any change request has been created. So before it's merged with the code, there is series of unit tests being done in the in the in the environment and that's very, very important and every every change has to go through a PR and and because we need to do the protect the image integrity and we we run, we make sure all the unit test is actually passed and before we merge the code and that's the first stage of it. So this is a stage process. So once we once we go through that cycle, so it will go as an image build and then it goes to the image qualification. So image qualification has more more advanced qualification, more testing is in is done across in the in the stage where we have integration testing, we do the data and the control plane testing and we also make sure that it's been tested across the multiple physical appliances before and we make sure that it's it's completely tested to 100 to 100 percent before we call it as a ready to deployment and that's where this is the stages are very important and we will any any any mechanism anything we feedback goes back any of the stages. For example, we find issues in the image qualification side or even even in the pilot or production whatever issues we observe, we try to get back as a feature request or the bug fixes and we try to make the changes again with the same process. So in this in this also we we wanted community to help us any anything we find issues ahead of time. We wanted your support to look into it and help us, you know, build it more faster solutions on that. All right, so what what's currently working right this we have full support from community and and we have a lot of comprehensive quality gatekeepers. So as I mentioned, we do unit testing, integration testing, control plane testing for building images, we make sure before we merging the code itself, we do a lot of checks and it's very important and every feature and change request has to go through a PR process and and the control process in place before we merge it and we've been growing the number of test cases right so every year by year we've been improving and keep adding all the test cases and this is where we need help from you as well to increase and support and help in building more test cases into that and for all different combinations and layers within the within the network. And as I said, community has been has been helping us with the unit testing and repo management as well. And these are the things which been going well for any of the qualifications so far. What we actually need, I mean, and we need we need support from you guys to share and any of the extreme test cases you've been running across your organizations. And we are okay and we are we are we are open to listen some of the test methodologies you've been using. And we want to see them evaluate them and add them you know if there are any any new things you've been innovated from your site. Any any any test case reporting tools you've been working on we wanted to hear from you and if you can share across that. And we as I mentioned earlier we wanted you to help contribute in growing the control plane and and all the test cases for the son if qualification and also not just the sonic itself right so we also wanted your help or contribution towards the site test and infrastructure on testing on that as well. So yeah so thank you for listening and and we wanted you guys to help us in all the ways you've been helping already but we request you to look into this and see how how you can add or contribute contribute to the sonic qualification. Thank you. Any any questions? You're saying the one specific skew which is not working or is it normally I think when we when we there is two different streams we do it so when we do the publicly available any images we have a generic images specifically which can be deployed into any of the skews you have and if if we work on any of the specific skews we also give a different images for that specific too. If if you don't have a specific on that list I think you can come back to us or come back to the community and share that whatever the issues you've been observing with the specific images with the specific skews and we can do a triaging on that why this is not working and we can definitely look into it but the the cycle of the image processing we wanted to continue every six months and and we want to see if these issues can be identified ahead of the time or you can we can still maintain or support the older versions if you are still running that if you have issues in the newer versions but it's it's we are ready to listen them and as a community we can try to resolve them but yeah if you have any specific ones we can as Shin mentioned right you can bring it up in the in the triage meetings we can definitely take a look and yeah absolutely sure sure I think the question was a security patches right and which is not part of the any of the upcoming releases I think he has a concern that what is the road map for that feature and all that is it is it this question you're asking right I think Shin already shared what what we're planning for the 2022 2023 or five release we have a road map for every six months on that and and I'm sure if it's not there on the list and we will definitely so on the question of security release right so I think the security patch is not something that always go with the release right this vulnerability are getting uncovered at any random time so it may or may not go well with any release planning and they also in reality there's a lot of consideration that a security patch issue have to follow the common industry like a CVE process right so you you cannot just open up a security issue to everybody overnight because a lot of people are actually running on this in the infrastructure so this is something that in the in the sonic tsc we have started the discussion of how do we want to manage the disclosure right there's a certainly upstream disclosure of stuff like you mentioned on FR on news and maybe some cv is from debian itself and maybe some cv in whatever SSL right so there's a certain stuff upstream and the sonic team is more a community is more on the receiving end of things right how do we react to it and then there are certainly going to be things that it's actually part of a course on it right maybe someone made a sonic change that is having a security issue so i don't think the we have a valid kind of ready step yet the tsc is discovering discussing of how do we want to handle that collectively because we have a lot of operators that is probably need some time to clean up the fleet right in the infrastructure and then we have vendors who need to kind of prepare that for the operators so that they can roll out right so yeah yeah so yeah you you will see some analysis on the specific fr since coming soon there's some there's actually some discussion in the tsc community on that front on the fr vulnerabilities on whether that's a real one that's impacting sonic or not we will have those kind of analysis coming thank you liao that was a good question any other questions i think most of them automated and yes yes yes the final these are more of a platform you know specific on that kind of thing yeah any questions all right thank you so much