 Hello? Hello? Hello? Hello? OK. Hi, everyone. Thanks for coming to the VisualOps show. I hope I can take the 20 minutes to explain what we're doing here, and I hope that makes sense to you. So VisualOps, we are basically what you see is what you get, the experience for your cloud applications. That's a screenshot actually from our SaaS applications. First of all, a little about ourselves. First of all, my name is Peng, Peng Zhao. I'm actually the CEO and co-founder of VisualOps. My personal background is in the great computing, especially the computational grid, the scheduling stuff, like Globus, if you know that, back 10 years ago. And I actually tried to build as offering back to 2003 using ZAN and the great stuff like the cluster computing. VisualOps itself is a visual cloud management services like SaaS services for you to build your application in the cloud. So currently, we support OpenSec and we previously will support AWS, these two as well. The company is founded in 2012 and early 2003, and we are mostly rooted in Beijing and have a branch in San Francisco. We raised that wrong actually last year from Sequoia in 2003. So this is a horizon. People are actually using this standard web UI console you got in OpenSec. I'm not trying to say there's something wrong with it. Actually, I'm saying it works, it's clean, it's neat. But the thing about it is it's the only way to doing the UI console for your deployment. We think there's a better way to do it, not only better way, but another way. So that's our offering. It's actually a web-based console for you to drag and drop your applications, to build your infrastructure and applications. So this is how it looks. On the left side, it's actually the resource panel. You can drag and drop the instance, the different volumes, load balancers. And on the right side, you can configure each resource's properties. The cameras allow you to, it's basically the similar experience you got in the Microsoft Visio. So after you design this, you can actually deploy the application into the cloud, AWS OpenSec. After, so from this stage, it's quite similar to what happens you got in Juju or CloudFormation or Heat. But we don't use those things. We use our proprietary stuff. Primary reason is that we try to be multi-cloud. We try to be independent of different clouds. So we use our own format. And the other thing is we support more syntax, like a configure management syntax than these two. So we need to use our own stuff. And underneath, we're actually using Solstike to do the configure management. So our ideas actually bring what you see, what you get, experience back to the cloud. It's actually have the three major feature set for you. The first one is like you can drag and drop to build and design and deploy your application in the cloud. The second one is you can actually visualize your entire infrastructure into Vjobs. Like you can import your existing footprint to Vjobs and generate the diagram automatically for you. And also, we do the continuous detection of the configuration drift. So if there's something wrong with your infrastructure, we can detect it automatically and send email to notify you. The third one is we do the automatic drift fix to ensure the application is always running in the desired state. What I mean is like supposing you have a lamp stack running in the cloud. And then suddenly, the database is crushed. The whole instance is going crushed. And then we can replace the database instance and redeploy my circle in the instance and then reload the data and restart the database in that new instance. And then reconfigure the web servers to point to new database servers. So everything is happening automatically and no human intervention needed. So that's three major feature set we are going to do. And actually, this diagram shows you the whole complete idea of what you said and what you got. Two major part is visualize what you have. And ensure the application is always running as I design. The first one is like visualize what I have. It's actually useful if you want to collaborate with your colleagues. Say, my boss asked me for how my infrastructure looks like. I cannot show him a bunch of recipes. So here it is. You check it out. I need to give him a visual diagram of the infrastructure. And the problem with that diagram is like how do you keep that synchronized with your real production? And that's where we can help. We keep reloading the diagram if there's some changes. Next, you might my co-founder, CTO Xu, to do some real demo of results to you guys. Hello. Hello. Thank you. Now I will show you how the results works and how it works for OpenStack. We define a stack. Stack means a template. It can be deployed to the cloud to repeat your design. And when the server is there, when the design is running in the cloud, it's named as an app. First, we can create a stack. Our create stack, we can use all of the supported OpenStack resources, such as a router. So router, you can edit all the properties. In order to design, we'd like to expose all the properties the providers can provide you to you. And you can have the whole power of OpenStack. And here's the subnet and the network. You can also add other resources to the canvas. Your own, the system-provided image and your own image. And configure all the properties, such as flavors, and key pair, and so on. And also, you can put low balancers here, additional subnites to connect some nights with routers. And connect the low balancers. And if we do something wrong, here's another subnet. It is not connected with the router, with other subnites. If you do something wrong, you can connect the pool with the house. It can be here. Here's what it will show. There's an iris. You cannot do it. And after you've dragged the resources, you can also configure the software on it. We support Docker. You can just indicate which Docker image you want and how to run it. Then it can be run in the server. Also, we can use some simple state. Now we can add some simple one. I will design. You can just one click to launch them into the cloud. Just run. I just told you, if we have some misconfiguration, the ID will tell you something is wrong. Here, we have a low balancer connect to a server. That is, do not have the connectivity. So it will stop us. And prevent we do wrong things if we delete it. It can be run in the cloud. And we can select the keypad to run the stack. Then after we run the stack, it will be launched into the cloud. Also, we can have some more complex design. Such as this one, we can, in this design, we can set there is a load balancer and two web servers and DB servers. If you set up a little bit complex application, there may have the requirement that you'll have to write some configuration file that need to reference the other servers, IP address, or something that can only be determined in the runtime. Some traditional configuration management tools use the method to collect the information from running servers and then dispatch it to the running services. Now, as we can deploy the whole stack for you, so we can got the information just after we launch the server and give you the configuration directly, such as in this configuration. We can just point the IP address of another server and render it into the desired servers. And if there is some errors, it will propel you. Oh, there is something wrong. What can I do? Then it can be properly rollback. And you can fix the problem and launch it again. And this is another stack. And here's how you can launch other stacks. After we write it, it will become an app. When we launch an app in the cloud, it will report the results data from the cloud. If we change something from the cloud side, it will reflect in the app. Here, I will try to access our back end, try to connect our back end open stack management console and try to modify the server outside of our visual ops. The server is located in China, so there is a bit slot. Yeah, when we wait it, we can see we also have the AWS support. It can also import existing VCCs and create VCCs just like our open stack version. We are waiting the back end open stack to make the app to live. The current status is under building. And a minute later, it will become active. Do you have more work when we wait it to become lab? Probably, we can show you a more complex scenario of how to deploy Spark into the cloud. We also have our kind of marketplace, like AWS marketplace, but we preview the templates for visual ops. It's actually similar to a marketplace but dedicated for a digital application because what you find in the AWS marketplace is more a single image sandbox application. But here, you can find the Hadoop, Spark, Cassandra, all these production-ready and digital applications that try with Spark. Now, this is a preview template we made for the Spark. Actually, you can single click to launch it into the cloud. Actually, this one is for AWS still. We didn't import it for one stack yet. It's a bit of a slow. That's the stack. And in each instance, you can see the detail, the configuration, we call it state. It's actually a declaration of the states. After the configuration of that instance, you can see using YAM to install some package, download some archive from somewhere, and try to configure the supervisor D to launch the Spark process. And instead of the configuration file, you can open to see it clearly. And then you can click launch to deploy the application into the cloud. And we give you a cost dimension of how much cost monthly in AWS or in OpenStack. Sometimes it takes like seven minutes, depends on how complex the stack is to launch the application. But you got a general idea. So it will help you if you have a running application in the cloud, we will do the auto scaling and auto scaling of your components. Supposing you have a traffic burst to come in, then we do the auto scaling and configure the new instance and connect to the other dependent services for you. So back to the stack, back to the PDF center. So back to our slide. Actually, that's a whole life cycle of what we do for our application. We do design the stack and launch into our application. We also do the import to visualize your existing footprint into a app into VisualOps. And then you can actually update the running app if you want to do some changes. And we're keeping ensure your application always running in the desired state, also doing the model as well. So it's roughly a really complete life cycle management experience. To sum up, we actually automate an orchestration service for you. You can think of more as a YBox pass, compare with something like HeroQL or Cloud Foundry because people try to migrate off from those past players because they post too much constraint to your code. But when they migrate to the us layer, they found it's too much overhead to actually manage the infrastructure. So they want something like us to kill all this heavy lifting for them. So that's really kicking in. And we actually, I think there was some speaker, last speaker mentioned the infrastructure code. We are doing the same thing here, which give you the repeatable experience of deployment and consistency and the word and control of your infrastructure. And we also apply desired state. So it means you order the state, we cook it, auto-scaling, auto-healing. And we also do the log and the auditing for you. So you can say, at the end of each month, we'll send you a report of what happens in your, what kind of deployment you made with the kind of change you made into your instructor. So help to do the auditing. And also you can do the push to play deployment. Say you have a new Docker image. You can push it to the Docker hub. And we will fetch the latest word and reload the containers for you. So that's all. Any questions? All right, cool. Thanks.