 Okay. Okay. Okay. Let's begin. Hello everyone. Hello, Berlin. What's up? I'm very glad to bring you this sharing. Yeah, I'm Xiao Yang and this is my colleague, Zhou Xin. Hello, everyone. Well, from EasyStack. EasyStack is a leading provider of open source cloud computing solution. We are established in February 2014 by the early school OpenStack R&D team from IBM, China. We have more than 100 equal partners. And you can look at our leadership, innovation, research and deployment details. EasyStack joins the top three OpenStack vendor in 2018. Look at EasyStack is number two. Yeah. This is our four product lines. We have EMI, EasyStack multi-cloud service, EKS, Enterprise Production Ready Kubernetes service, and ECS stack. A cloud-ready HCI product and ECS, Enterprise OpenStack product. Why choose EasyStack OpenStack product? I think EasyStack OpenStack product has the following comparabilities. One click rolling upgrade on microservice architecture. What you like the results? Extraction to application center. And we have high performance storage and simple maintenance and monitoring to automation service. We have three design concepts. Software and hardware integration design. Best product, optimization to open source and enterprise experience. Design for failure. The value to customer is sustainable evolution capability. This is our innovative distributed microservice HA architecture. We have distributed microservice components. Converge deployment control, computing, storage and networking service. Also have a modular parental expansion. Based on our microservice architecture, we have achieved to ability of rolling upgrade and evolutionary capability. We can use our ECS, US, ECM, ECAS and ESCL upgrade packages to rolling upgrade our cloud environment. This is our product software architecture overview. You can see ECMS provides monitoring for all software and ECAS provides automation center. You can use ECS stack cloud automation service to deployment, expansion maintenance and upgrading our cloud environment. This is our monitoring service. It has a comprehensive monitoring of hardware services and performance. And you can use our virtualized full resources or orchestration to directly orchestrate a published application topology. And orchestration application center images. It will let you be a cloud application architect because it can be virtualized for open stack cloud resources like instance volume, LB, firewall and so on. We also have enterprise production ready disaster recovery capability. Many to many replication. It's designed for cloud, for open stack cloud. Cloud resources and trick protection. And next, welcome my colleague Zhou Xin bringing us a live demo. Okay, thanks Xiao Yang for sharing us the powerful product. So today we will do the demo by using our two data center region from Beijing, China. So let's begin. The first coming up is ECS automation service. This is ECS measurement page. So it can manage the left circle of cluster. It includes nodes management, license management and configuration measurement and also have cluster expansion and upgrade. And also it integrated monitor system ECMS and the cloud service console. So today we'll demo adding a new feature into the cluster by upgrade. We take the enable disaster recovery as an example. So before this, we go to the cloud service check if this disaster recovery has been added. So we go to the ECS cloud service console. We find the eye size manager. And there are instance volume and network nodes found the disaster recovery in here. So we come back to ECS and make an upgrade. We click the cloud environment upgrade. In the page, there are three steps you should do. First, import upgrade package and select target version and finally click the start. Because we have already imported the upgrade package before, so we just select target version and click the start. During the upgrade, there are no effects with the cloud service because it will take several minutes. So we do the nest demo. The nest demo is orchestrated the application in the APC center by visualized orchestration. So we go to the nest. Go to the ECS switch to console navigation. Go to collect the APB marketplace means APC center. And browsing all those applications, there are two applications. So we choose the Berlin APP, Customized APP. So check the detail. It has only one version, 0.1. So we remember this. So the nest will edit it by visual orchestration. So we turn to the left side and find orchestration. Click stack and click create template. Select the last create from APC center. Great. Oh, we're loading the Berlin APP. Okay. Now select a version because it's only one version. So select and click. Addisable commerce coming out. So we can see that the application is not an LB application. So we make some change to make it to be an LB application. So we just use the left side resource and the drag and then release. Let's do it. First, we drag one instance and fill some information. And choose one key pair and see the server is ready. And we drag load balance and release so it matched. We fill the listener. Set a port and set LB port. Select the upstream server one by one. Set the port. Select the last server. Set port and save it. In this commerce, we also need a floating IP. So we just drag. We can see that it's perceptive. So we should place to the load balance and save. So I finish the template and save. The network is very slow. Maybe should patient fill a template name. And we select the last option, import to APB market. And there are two options. The first option is create a new application. And the two is a new version application. So we select a new version. And we should fill some description for the new version application. First fill a version and some description and import. The new version application has been imported to the APB market. So we check it. Browse in the other application, select the Berlin app. We see there are two versions. The 0.2 is what we have finished. So we finish the second demo. So in this time, we come back to the ECS and check our upgrade. In the ECS page, the upgrade shows 100%. So we made it. During the process, it also proves that it's a smooth and seamless upgrade. So we go to the cloud service console and check the disaster recovery has been added. We select both navigation. Collect the assets. Maybe just refresh. That's loading. Oh, we found the disaster recovery service. It's named DR resource. So our upgrade is finished. The first demo is finished. So we do the last demo. The last demo is to show you how to backup an open stack resource by using disaster recovery. We have two data center cluster named demo one and demo two. And as following, there are two steps you should do. The first is a DR service. And the second is a DR group. To save time, we have created the data connection by DR service. It is used to keep the data sinker. And now we just create a DR group and put your open stack resource into it. So now we wait to demo the sinker. We go to our backup cluster to check the DR group has existed. This is our backup demo two backup cluster. So you will see that DR group is empty. So we just come back demo one primary cluster to do the backup service console and create DR group. And set name for in DR 1002. And set pure item ID. I will fill project ID. It means open stack project ID. I will get it from a backup cluster. It means which project you want to place in the backup cluster. So we go to the backup cluster and go to the UUID and fill it. So we also created the DR group. And then we go to the backup to see. It also have a DR group. So the group is sinker. We come back demo one. We created the group and add your own stack resource. Let's select a demo as an example. And fill the project authorization. Now the resource has been added. So you can see the status is changed from init to restoring. Finally it will change to map. So it will take one minute. In this moment we will come back to the backup cluster to see if they have the same resource refresh. The restoring is working. Now in the time we can see our ECS more details. Like this nodes management. This is a nodes list and check the detail. You can see the hardware, hardware and the NIC configuration and the desktop configuration. Now we should return back to check the backup. So I think we need a better minute. Oh, it's okay. It's mappered. The result has been added. Go to the backup and check. Oh, it also has a sinker. So the resource should be maybe added. We check the computer resource and check the instance. The name gf. We go to back demo one. The name is gf. So our open stack resource has been sinked. So the second demo is finished. Oh, thanks for choosing. Yeah, I think it's amazing demo. Okay, finished? Finally, okay. I want to say these stack missions is a world-class cloud computing enterprise based on the open source ecosystem. And welcome to visit our booth at 8. Yeah, 8. Thank you. That's all. Thank you.