 Hello, everyone. Thank you for coming. I'm CeCe. I'm from China. The topic is the ability of application orchestration in OpenStack with Cloudify. If you work first on the business application as a pass, all you are the operation administrator, so you must hear about world orchestration. Yes, we all know some content orchestration, for example, Google's Kubernetes or the DCOS Marathon. But today, we will talk about the application orchestration in OpenStack with Cloudify. Okay. Okay. Let's look at the feature together. We all know the three layers, S, pass, and SAS. And Cloudify was designed as a tool for pass applications. Cloudify tagged customers who launched a pre-built application in cloud environments. And want to operate their own service quickly without dealing with the technical opinions. So we can use Cloudify to operate the cloud-native applications and the traditional monolastic application and the container applications. So next, I will introduce Cloudify from full accept. First, OpenStack native. The OpenStack can integrate with OpenStack component. For example, Noah, Neutron, Sina, Crystal, Height, and more. And so, Cloudify can run as a service of OpenStack. Second, Stand and Tosca. Cloudify DSL is based on the Tosca. DSL is domain-specific and language. Tosca is topology and orchestration specification for cloud applications. So you can describe an application with all the resources, from infrastructure to mid-ware and to application code, scrap, and logs. The third, application orchestration. We all know that Cloudify is a cloud orchestration framework. And we can model application and the service. And the main application, the entry-left circle. So we can perform ongoing operations such as scaling, hailing, and maintenance. The fourth, plugability. Cloudify provides reusable component abstraction for the system. And we can model application that you want it with describing language. For example, OpenStack results. And Cloudify includes a number of the official supported out of the books, plugins, and we can also build our OS if we need it. We can also Cloudify includes three items, application, topology, and workflow, and policy. But as a core of the Cloudify is Blueprint. Each Blueprint tells Cloudify the details, how to run an application. For example, what mid-ware service is needed to run, and what the dependence are between the service, and how to install the service. Where to fund the application and the service banner is. When to spend more distance on terminal exciting one, and even how to monitor each of the service. So the Blueprint make it super easy to get your application up and running on the OpenStack Cloud. The next is, it really takes six steps to run, to deploy and manage the application, provision, install, configure, and deploy, monitor, and scouts. And all the other steps can be described in Blueprint. The next is what we have done about the application orchestration in OpenStack. The first is how to install the Cloudify. We now support three ways to install the Cloudify. The first, we have built the Cloudify as a container image. So we can manage and schedule it by Kubernetes. And we also support the customer to create a Cloudify instance. And we also support Cloudify as a service in OpenStack. So the Cloudify can have been installed, but the OpenStack provides the results for the Cloudify. So the first one, the administrator of the OpenStack create all the results for the applications. And we can add the results to the Cloudify. And the results of support can be used by our plugins. The plugin is not supported on the open source. So the customer just took care about the business application, don't care about the OpenStack resource. This is an application orchestration example in OpenStack with Cloud. From this chat, we can know the simple example, the web server and the DB server. This is the node for Cloudify. So we can have the file nodes, web server and DB server, and the Node.js, and MongoDB, and the business application node seller. But the other results are provided by OpenStack. So the application orchestration includes resource management and orchestration. The results are meant by us, not by customers. Customers just to orchestrate their business application. For example, install the DB, install the web app. Out of the orchestration description in the blueprint, just reset that. In the blueprint, we just to tell the user, install DB, install web app and create DB on the database on DB. And the configuration, the web application connect to DB. And the configuration, the resource is from OpenStack. So the Cloudify can start the component in the red orders. We all know the application uses some resources. For example, application network subnet and the security group and the Filii IP, just provide the best OpenStack. Okay, that's all. Thank you.