 Hi, my name is Kanagraj and I'm going to talk about the Stelco Agile Orchestrator in decision. In OneApp CLA project, there is a platform called Open Command Platform. It is introduced to orchestrate or automate the different accents involved in the OneApp. So it enables to model the given accent as the normal as well as we can capture the execution details in the normal. That's we can call this cordless. Also, we can associate the accent with the actual implementation of that. It could be a scripting language or programming language. It allows to onboard and manage those actions and while executing, we can troubleshoot those accents for prints. It also allows to model the environment using the normal, which is called an Mormon profile. At the same time, it enables to orchestrate across the different domains or the tools. It's called as a plugin profile. So Open Command Platform is built with a specification called Open Command Specifications is currently used in this platform. This specification helps to model the accent with what are the required inputs, what are the required outputs and how the execution is performed. So all those related informations are captured in this normal and that normal is completely processed and then converted into an action or a command by this model engine. It enables a GRPC and the command console or the Linux shell. So through which we can onboard the actions we can manage the action can execute the actions. So all these operations can be performed. So for the programmatic integration, we can use a GRPC while scripting integration, we can use the cell command. On the other side, it enables to come up with different profiles for supporting different environment or protocol specific things like STTP or SNMP, or we can even integrate the robot, which is currently we are trying as part of the wheeling release. So on one side it enables to integrate in the programmatic or scripting approach. On the other side, it enables to integrate with a different environment to throw the profile. So the environment can be a specific product like one app or it can be orchestrator like on a bespoke or like open stack heat. So all those things can be integrated seamlessly into this platform. So on one side, it allows to integrate with a different environment. On the other side, it enables to access them seamlessly. So it's built on top of the domain model. So it has a product under the product. Usually a product will have service, service will have these top features. So the feature is model as like a command which require input and output. Under the environment is model with the profile. Profile basically captures all the environment details like it could be the connection details or the credentials, which are the information required in order to operate those environment from this platform. And another is artifact. It helps to store the required artifacts like the scripting or the configurations, etc. Even the environment variables and then it can be used during the execution. So the execution is model using the runtime model. So in which there are three models execution, execution takes the command, the instance and then the user will give the input as the parameter. And with that parameter, the execution will happens and then finally it's produced. The result is nothing but the instance of the output. So when execution, the user can also provide the profile, which is nothing but the environment details on the artifact, which is required for executing the given actions. So using this platform, we have already completed one use case in the one up all OVP VNF test platform in which we have done the end to end service automations. So what we have done, we have taken all the one up actions as the command and then expose like the CLS and the same commands or consume like the test cases in the VTP. So one side the action is seen, seen like a command from the DevOps point of view. On other side, the same action is seen as the test case from the testing or the certification point of view. So it's like a develop the action once and then you seek across the DevOps, CACD or other real production environment. So it says the developer involved in multiple places. Otherwise, which is the common practice today. So when we're looking at this, the picture, the VNF lifecycle validation is made up of this complex, the workflow shown here. So the complete workflow is orchestrated through this platform. So it acts like a twin one for the tester, it fills the user role in the options of the user. And for the user, it costs from the bugs as because it's already tested from the testing point of view. So, so in summary, it basically helps to model any actions as the YAML and onboard into the OCOM. So from that point of view, it will be seamlessly seen like one action with that given on your PC or the CLI or the test case. So the same action is seen with a different interface, but end of the day, it is going to be the same actions. So more details about this, the automation, what we had done the end to end things we have given in this week. Please refer this week for more information. So that's all about this other orchestrated. Thank you for seeing this, watching this session. Thank you. We have now activated the phone bridge. Unfortunately, our speaker is online but unable to access the audio. So if you have any questions, feel free to enter them in the Q&A with speakers Eric Chat, and he will respond to you in that chat. We have a few minutes left. If there's any questions that don't get answered, then we will refer you to a Slack channel where you continue the conversation.