 Hello, everyone. Thank you for arranging the time slot. And thank you for giving us the time for this presentation. And we'd like to quickly introduce our recent activities to solve this problem that we described in this title. How can we revoke the legacy telecom infrastructure for cloud native? And let me introduce briefly ourselves. We are the biggest telecommunication company in Japan. And we are mainly focusing on using OSSS to solve this kind of problem. And today, what we want to talk today is already described here. And we want to explain our solution that solved this problem. And the very solution for us is making a adapter between the cloud native projects and telecommunication infrastructures, like a model, as you may know. And we are working on making that adapter called attacker in an open stack. So let me introduce it briefly. So Yasugumi-san, please. Hi. My name is Yasugumi Oyawa. So I'd like to introduce our background first. So we have several challenges for migrating legacy telecom infrastructure on mixed environment on VM and cloud native architecture. The diagram showed a simple use case. So there are containers or VMs around there. And it's managed from an open stack over Kubernetes as a virtualization inference manager. And it's also controlled from VNFM features for virtual native function manager. And this is just a typical challenge for us, for example, how to sift VMs for legacy applications just crawling into containers or how to introduce a web structure management plan for both VNFM and CNF. And definitely, generic VNFM in the key feature. So for realizing such requirements, we have contributed OpenStackTec which is one of the major project in OpenStack and its own features for controlling VNFs. And so orchestrating virtual telecom infrastructure is, for example, managing physical virtual machines and the containers or virtualized network and applications ranging from co-op to VLAN. So we have several use cases trying to adapt TACA for them. And this is one of them. It's VLAN on Kubernetes cluster with TACA. So there are many components managed from TACA. It's VDU or VCU. VDU is for a virtualized distributed unit. And VCU is a virtualized control unit. So TACA manages all of these features as a centric control plane. And the definition of such a managed platform is given as packages called as VNF package via auto interface. It's included, for example, HelmChart or Manifest or Management Driver of TACA. And also, TACA team has contributed to ORAN to life cycle management VDU and VCU. And ORAN is an alliance joining several telecom providers or vendors around the world to realize such a VNF world. And yeah. So this slide is just showing one of our recent challenges in ORAN community. It's managing the starting X from TACA. OK. Thank you, Smith. We're going to show a quick demo to describe how TACA control the old Kubernetes resources. As Yosemite said, there are many cloud-native projects. And we can use that directly. But there is no common interface to use that. So we want to make adapter to abstract those different cloud-native projects. That is TACA. And we'll show the TACA make those old components with HNF-based turned-out compliant interfaces. This is the initial state. There are no clusters. And the first, TACA make Kubernetes cluster on edge site. So this demo shows the TACA make two-site edge and cloud. And they're now TACA making their edge site Kubernetes cluster with a cluster API. And the cluster is created. And their authorization configuration is sent to client side. And their TACA has a custom driver to achieve this kind of provisioning like sending a Kubernetes config or something like that. And now, TACA scale out the edge site cluster with cluster API. Now the worker nodes is scaled out from one to two. Then in our TACA, now we show the TACA upgrade the Kubernetes version on the cloud site. And the version is upgraded. So there are two clusters already set up. And we deploy the application on that cluster. And we use a machine learning application called the salesman as an example here. And we can see the edge can access to the cloud application. So TACA control all of those things with the common interface. And then terminate all things. And like I said, we can do this with our Kubernetes projects like a cluster API, Kubernetes itself, and Helm. But there is no common interface which is suitable for the telecommunication company. So we make a target as an adapter, like I said, over and over again. So that's all for us. Thank you very much.