 Okay. So let's start. Good evening, all of you. Myself, Dharmankuswa and we are here for Tacker Project Update session. So first thing is, what is Tacker? Tacker is an OpenStack service for the orchestration with general VNF manager and for deploy and operate virtual network functions and network services. It is based on ETSI Mano architecture framework and as in ETSI Mano architecture, you can see that this red area is under the scope of Tacker Project. So we are as a VNF orchestrator and VNF manager. So this is the Rocky contribution from Tacker team. We ranked 37 in the review as per Stakeltics and ranked 53 in the commits and there are around more than 75 field bugs and we resolved around 52 among all of them and we did so many other contributions and the main contributions for the key contribution of this Rocky cycle is these are like VNFFZ support in NST for in-to-in network service deployment, symmetrical as a property of forwarding path, shared beam for Tacker conductor and placement policy support. So we will go for one by one. So first is VNFFZ support in NST for in-to-in network service deployment. To instantiate a network service from NST, NBEO plugin will extract VNFFZ data and it will generate Mr. workflow and execute them. So with the VNF forwarding graph that is created with network service, they can be shown in the list command like VNFZ listing that is OpenStake VNF graph list and we can update the VNFZ created via NST using NSUpdate command that is OpenStake NSUpdate. We can give you a NST template and then we can update that. The next one is placement policy support. This feature added placement policy support in Tacker operator can specify these placement policies in addition to affinity to videos like affinity, anti-affinity, soft affinity and soft anti-affinity. In this template, we can mention the policy like affinity and the type like it's strict as true or false to set its soft and strict affinity or anti-affinity policy. Through this feature, we can control the placement of video stance on node. The next one is symmetrical as a property of forwarding graph, forwarding path. A network service can have multiple VNF forwarding graph and each forwarding graph can have more than one, each forwarding graph can have different symmetrical values. So a user can set symmetrical value to true or false to change the symmetrical value of forward chain in networking SFC. If property is not set symmetrical, then it can be specified as a hyphen hyphen symmetrical in the CLI and to create VNFZ through command line. If it is not provided, here we can see that we mentioned it symmetrical as a true, but if it is not provided in template and not in the CLI, then the default value will be false. The next is shared VIM for Tacker conductor. Like some VNF LCM operation or not go through Tacker API such as policy execution or if you are executing through a Mistal workflow internally, then it will not go through the API. In that case, we don't have the keystone token to access the public and secret. In that case, we provide this feature as a shared VIM for Tacker conductor because internally sometimes we need to access the VIM, which are not created tenant. So in that case, we added this feature as a shared VIM feature because we have some ongoing activities which needs shared VIM operations. So we added this support. These are the ongoing activities in a stain cycle like Mistal workflow for VNF monitoring. In this feature, we are refactoring the current existing monitoring framework and we are introducing Mistal workflow to monitor VNF and another one is enabling video auto healing. So in the current scenario, when a VNF have more than one instance, so if any failure occurred in a single video, then we need to re-instantiate or take action on the whole VNF. So in that case, with this feature, we can execute action on a single video so that we can avoid the auto healing of the whole VNF. So it will help to provide high availability on VNFs. The next is force delete resources. Sometimes we need to clean the resources which are stuck in some abnormal state. So with this feature, we can delete them forcefully. We are also working on the CSR package support and some other like REST API for VNF based on ETSI and as well as specification and latest TOSCA profile support. These features are under discussion and these are started, but yes, we are looking for more contributors to help to implement on that. And some others are like code stability to maximize code coverage. We are adding for that. We are adding the more test cases and we are introducing some other additional test cases and refactoring the existing one. Another one is resource reservation for VNF resources. In this, we are integrating Bellegger with Tacker project. So these are the ongoing activities in Stein cycle. Beyond Stein, we are working, we have planned to introduce like more towards ETSI, MANO framework and micro service architecture. We have to more focus on the stability of the Tacker project, focus on the user scenario and support different VNFs. We need some help from other users who can help on identifying the scenarios where we can implement those cases and those VNF supported and support in Tacker project. Cross project work, we are working with OPNB, Doctor project also. For this, we already provided support of Tacker driver in the Congress because in the OPNB framework, we have some POCs and in that, we did, in our POCs, we used Congress as a inspector and Monaska as a monitor driver and Tacker as a VNF manager. So we already helped on the other projects to aid support for like in the Congress, the Tacker driver is already supported. I think it was under ongoing activity and I hope it is already supported now. So you can give feedback on, for feedback, you can join IRC channel, Tacker project IRC channel and we can also join the weekly meetings and the meeting times timing is Tuesday at UTC time. So you can contribute at the same, you can help on the other, so many areas in the Tacker and the contribution process is same like other OPNB projects and if you are interested to work and contribute more, so you can contribute in the terms of code review, in terms of bug traces, in terms of filing more bugs and testing the current Tacker codes and you can also give your ideas and inputs on Launchpad. So that's all. Thank you.