 So, let's start. My name is Rongzhu, and I come from China, an IZT corporation. Today I will share the project update about Morano. So first, let's introduce what is Morano. Morano is an application catalog in OpenStack. Our mission is to provision an application catalog service so that the user can compose and deploy composite environments on an application abstract level where I manage the application lifecycle. This is a sneak about Morano, that's a sneak, and some project background from the latest service adoption number. There are about 14 percentage users are deployed Morano. Among them, 8% of the Morano users are usually in production environment, and 16% are in user data or QA environment. There are about 20% of the users are considering using Morano in the future. So, this is a picture of a snapshot from the service. So, let's talk about why we use Morano. Morano separates application developer and operators and the user. They can, to their developers and application developers and operators, they didn't, like a white box to the apper, they can define the application and some logic of the services. But to the end users, they just need to one click to deploy the app. There are third part about this. First, they can separate third part developers and apper operators and the end users. To their developers, they define the apper and life cycle action and push them to Morano package to the Git. To their operator, they can pull the Morano package from the Git and then they can modify some locally cloud and image and configurations. And then the operators push them to the Morano application catalog. So, to the end users, they can just browse the application catalog and then click the, from the dashboard or the COI, they can just click one click and to deploy the app. And this is about the Morano architectures, like most of the OpenStack projects, they have some components like Morano UI, Morano client and Morano API engine and the Morano agent. They interact with Kistone to abstraction and use it to abstraction the service. So, we introduce the Morano, the key features. The first one is application, Dominica UI. Application creators can define the, especially the form user feel to when application is provisioned. The form is defined as a YamaBasey file and describes the UI field levels and some valid rulers. When I use, when I use the one to deploy deployment application, they can just have some, you can have some fields in Horizon. Then the, these features are environment configurations and flavors, but a native OpenStack API, this is a scenario about the users want to not use Horizon UI, they can use the HTTP restore API service, create the environment and define them to, and then begin to deployment. Any third part, any third part service can use Morano to automatically deploy and Dominica to update the service on demand. The third one is users can provision apps with one click and after, after, after users select the service and configure the properties, just push a button and Morano automatically take care of the rest. And the rest is provision virtual machine and the network and the storage. Then install the VMs OS and then deploy the request service like WordPress or any other services. Make all request, request the configuration to make service available. So with one click, you can use a deployed app. Morano can also monitor deployment progress and logers by the Horizon UI. After your application are ready, use the logers to check environments, events from any deployment attempt for a particular environment. For example, if you host a web application firm, you can check node creation, web service installation, Dominic class creation, web application development and other details. Some details in the Horizon UI and some top knowledge and Morano can deploy workloads to multi-regions. Morano enable users and admin to access all workloads in cross-region. When deploying a package from the Morano catalog, simply select which regions you want to deploy to. Each regions can be configured separately and the application can have resources in multi-regions. Also, Morano have a tool to validate the application package. Developers can use a set of COI tools to quickly validate Morano PR and FIAT and the Morano package to enable fast application development and ease of resolution and improvement application support. Morano PR fires can be checked for common snack errors and typos. In other words, Morano PR statements, while Morano packaging structures can be valid for common package errors like some missesome classes or some invalid typos or some statements. So, next, this is the features we want to do in STEM cycle. First is the UI framework enhancement. We want to give the users more nice UI and some technological development, like fixed Morano dashboard function, this is due to the website is closed. So, let's break the original important Morano package workflow. So, we need to find a new way to import a Morano package workflow. And the next is we want to integration with Gailer as a Morano package backend. So, this is all. We need more people to contribute to Morano. This is now, this is too few. So, any contributor will welcome about code review, documentation, bug fix or some useful use case. Thank you. We have some questions. They are just a demo. So, this is a demo about to create a Morano package, Morano app. First of all, we can create a Morano environment. So, let's create a Sucasian app. This is a dynamic UI. Users can select the parameters for this application. This is Sucasian. Sucasian, they need a web and a DB backend. So, there are two realms. So, people can set the, this is a password validation. So, users can define this Sucasian. And the app is deployed successfully. You can just click the URL, the Sucasian URL. So, the app is deployed successfully. What is your home page to install Morano? You can do all that documentation in this. Does it work with virtual machines or a sort of container? If you want to work in a container, the container will be in the VM using Kubernetes. Yeah. How many people are still working on the project? There are many companies that use this, like AT&T, Oracle. They didn't communicate. So, I'm alone. If somebody is interested, please do some contributing. You can directly use the hit template or use the Morano package template. Okay. Are there any principles where you look? No. No. No. Not integration with any answerable playbooks. Just use hit. Deploy Morano service in OpenStack. You're using OpenStack answerable, yeah? Yes. No. Okay. So, thank everyone for joining us.