 Hi everybody, it's Laios. So actually, I tried to collect a few interesting things from the Yoga Cycle, what I think should be really good to hear. So we have done a lot of things. I don't see I and then there are everything, but just a few features which should be interesting for everybody. So one is the Node Local Virtual IP address. That's actually a really cool stuff. And you can have virtual IPs for your VMs which can share it and can access only on the same physical node or pod. So it's really useful for load balancing between services or similar. Another big and really interesting feature is the off-pads smart link DPU with OVN. So actually, it was a really multi-project effort because it was not neutron, but it was also involved with NOVA. But even it was a project in OVN and that's outside of OpenStack. So it was really a cross-project feature and effort. So with this now, you can manage smart mix which has their own operating system and OVS running on them. And you can manage them from neutron and you can schedule your VMs to use those with the help of NOVA. Next slide, please. Another OVN feature that actually we already have in the previous release is the router gateway QoS. But now you can use that feature and API with OVN also. So we have a list of gaps between OVN and OVS deployment, for example. And it was in the gap list and now we have a few things which we removed from this gap list. And you can use OVN for more use cases. And this was one of those features. There was another feature in this cycle which is actually for the quality of service. And it was again a cross-project activity between NOVA and neutron. So like in the previous cycles, we were done to have quality of service and scheduling available for VMs which use minimum bandwidth. Now you can define quality of service with minimum packet per second. And you can schedule your VMs to hosts which has enough bandwidth in packet per second for that VM. So it's really cool stuff. So with this now you can have even more granularity to schedule your VMs only to hosts where you have enough capacity and bandwidth. Yeah, actually that's it for the coolest stuff for the yoga and what we have done for yoga. I would like to mention a few things what we plan or what we see on the horizon for the Z cycle. So there are a few things which we can't finish during the previous cycle. One is again a QS feature. So the previous one was the minimum guaranteed packet per second but there is another that is the packet rate limit. So if we can say it's an analog for the bandwidth limit QS rule type but it's for packet per second. And actually the previous feature which I mentioned for yoga that was a scheduling feature but this one the packet rate limit this is a data plane enforcement feature. So there will be no scheduling guarantee but actually on the data plane the packet will be limited. There is plan to work on the distributed metadata feature that is actually will help to avoid the many agents which we have for neutron. So if we finish that there will be no need for the metadata agent because OVS agent will be responsible for handling the metadata traffic between your VM and the no metadata service. So it will perhaps make easier the scheduling and then the deployment of your OpenStack. Actually it's more like the next thing is more like a project internal thing but it can be really interesting for people who use not just core neutron features but other networking things like firewalls as a service. So firewalls as a service was retired a few cycles ago because there was nobody to maintain it and I am really happy to announce that we have a team now who started to work on firewalls as a service they started to maintain it they started to fix CI jobs and actually they would like to have new features like it seems that there will be OVM compatibility so we will use firewalls as a service with OVM as well. So it's really interesting to see that there are new contributors to OpenStack and to neutron so it's really good to see. And actually another QoS quality of service thing so it's a really hot topic in the latest few cycles and then that is to make the previously mentioned guaranteed minimum bandwidth feature work with OVM because actually it works now only with the OVS and the CRIOV backends. So with that we will have again one less gap in the OVM gap list so it's really good to see that we will have more backends which provide the full feature list of neutron.