 Hello, everyone. Welcome to Zoom project update. I'm the speaker Jiwei. And this is our other speaker Lu Hongbin. We will show, first of all, we will show you a brief introduction about Zoom. And then we will say something about that the future we have already finished and we are going to do in the STEM. After that, we will show you a demo so that you can see how to use Zoom. First of all, what is Zoom? In simple terms, Zoom is an open-stake container service. It's armed to provide the API service for running application containers without the need to manage service and characters. And also in the grad smart open-stake service, the innovation of integrating open-stake service is that you can extend the container function by using the extending open-stake service. And you can see the open-stake service that we request for the best protection. Neutron, Keystone, and Query Libre network. Neutron provides the network service for Zoom. So when you use Neutron, WIMS Neutron function, such as security group, can also be used in Zoom container. And Keystone, we can use it as like NOAA. And the Query Libre network is a plug-in that can connect container network and Neutron. So we can also use other open-stake service for extension function that you can see Cinder and Glance. In actually business, sometimes we need to sell data for a long time. So the way we support it is to use Cinder. Zoom use Cinder, we can create a container. The user can choose to mount the Cinder volume to the container. Cinder volume can be an extending volume or a new creative volume. Each volume will be bound to a path in the container of the system. And the data stone under the patch will be persist. And we also can use Glance. Glance is used to stone dock images. Of course, if you don't want to use Glance, you can also use Dock Hooper. So why we choose Zoom? In fact, this part of PPDI will say something about the difference between other options for in orbiting, over-stake, and the doctor. Currently, there are some options for in orbiting, over-stake, and the doctor. For example, NOAA doctor. When we use NOAA doctor, the container is can be upright like a VIM. For example, you can start, stop, and so on. But the disadvantage of NOAA doctor is that there are still some difference between VIM and the doctor. The option of doctor by VIM-like model will still may cause a few functions that are available to achieve, like port mapping and so on. And we also have the mechanism. The mechanism is over-stake project of the container, of the container customer department function in over-stake. In fact, in fact, actually, the mechanism is most focused on the customer department of the container. And Zoom manages the containers as over-stake resources. And users don't need to carry about the service and the customer. So where can we use Zoom? For example, CICD, patch work-land, application hosting, and VCP. I will say something about the VCP. So development of VCP has a higher requirement on the ISO land of the containers and need to be able to cope with the farewell upgrade at personal. Zoom already supports container technologies. So we can achieve the S-land between containers. At the same time, the implementation of container-rebuilt foundation can also achieve the proposal for farewell version upgrade. We will take a later. So you can see is the fashion that we have already done. So we have the container-rebuilt and single-volume multi-touch and easy and container healthy check. So far, Zoom already supports container container. And the Zoom quota, this VCP is is the implement for this VCP implement quota managing for over-stake resources. So far, the resources can be managed is the number of the containers, CPU disk and memory. And container-rebuilt, we can also rebuild a container with different images to achieve the proposal of the upgrading containers. And single-volume multi-touch. So far, this VCP allows the same thing, allows the same thing the world to mount two or more containers. So this is the future that we are going to do. They are Kubernetes integration, Placement API, and also Kata container in Capsule. And we are going to make Zoom to support the VGPU. And so let's see our demo. Okay, hi. Hi, everyone. So as a brief recap of what is saying is, Zoom is a project that allows you to create containers without creating any VMs. So what you need to do is run a command and specify an image in the Dockerhugged and click the command and the Zoom will pull down the image from Dockerhugged and run the container based on this image. And so in here, I'm going to show the demo. And the first part of the demo is going to show you a very basic scenarios that you have a container image and I want to run the VMs on OpenSec. So this is the horizon dashboard. And there's a container tab that is provided by a plugin that is developed by our teams. And so in here, we can create containers. We specify the name of the image, which is in the Dockerhugged. And there's a few parameters you can set. For example, you can set CPUs and you can set the memories. And there's a few other parameters that you can set to configure these containers. And then you click create and we wait for the container to be up and running. And it will take a few seconds. So now the container is running. And we go inside the containers. We can see the detailed information of these containers. And there's a console tab that will drop into the shell of these containers. And in the shell, you can enter a few commands and see the output. And the network of this container is provided by the Neutron so that you can see the interface is getting the IP address for the Neutron. And you can pin the external IP address inside the containers. So when we finish using this container, we can delete the containers. So this is the first part of the demo. And so we show you how to use a drone to run and delete the containers, which is the most basic scenarios of running containers in OpenStack. And the second part of the demo I'm going to show is how to use the heat, the OpenStack objet storage service to create an application that's based on the containers. And the application we are going to create is going to be more advanced and sophisticated. And it requires to objet storage a few containers with other containers. And the third part of the demo is how to use the OpenStack objet storage such as front IPs and how to go back. Yeah, so I just pass the videos and right now I try to resume the videos. So here we create a stack that is in the heat. And we go into the stack, we can see the topology of these applications. It contains a few containers in the stack. And we have a front IP address that is from the Neutron. And here we can see the list of resources in this stack. And there's a few containers and there's a front IP. And this is the heat template we are using to create this stack. And there's a container that is host the icicle database. And there's another container that is host the applications. And in this container we have reset an environment variables that is pawned to the IP address of the database. And the IP address is getting from another containers. And we have a front IP that is associated with the container that is host the applications. And to associate the front IP we pull, we retrieve the part, the Neutron part of the containers and set it as a target to associate the front IPs. And here we have the URL of the applications. And we open the browsers, enter the URL, we can see the application is up and running. Yeah, we can see the application is running. And it's based on the containers. So this finished the demo. So that's all. So how to join us? This is our channel. We will get a meeting at every Tuesday. We are host a meeting in IRC channel. And there's a grouping, there's a block checker. There's standard in open stack. And there's a documentation. Yeah, I think it's finished. Yeah, any questions? So in the NOAA, the NOAA API is designed for the VMs. And the container they have some, the API of the container have some set of OLAP functionality with the VMs, but there's other part of the functionality that is not fit into the VM APIs. So we decide, actually the previous project, that is MATLAB, that is decided we're going to create a dedicated project there for the containers. And the MATLAB is created and eventually it's become a project that is for provisionally-accompanied clusters. And doing this is separate from the MATLABs and become the project to run the containers. Yeah, we are planning to use the placements. So we are going to report the host resource to the placements and we have the scheduler to find the candidate to schedule the containers. But this work is going on and we hopefully we can finish the features within this cycle. The direct answer is no, because the drone is don't want to become another optimizer, but we are doing a feature that is integrated with the Kubernetes and what we are going to do is to implement the virtual Kubernetes which is a process that is like the Kubernetes, but it's virtual and so the Kubernetes is scheduled apart to the virtual and the virtual Kubernetes is called the API of the drone to provision the part in the drone and eventually this is going to integrate and you can use the Kubernetes observation to observe the container in the drone. And this is a plan to adjust the use case. Yeah. Yes, so the container, right now we are using the docker, we are using the docker APIs and the container is not a replacement of the docker, it's a runtime in the docker. So in the drone you can say I create a container and you specify a runtime that is kata and so damn you can create a kata containers. Is that spring your questions? Yeah. Right now we have no plan to integrate with NOAA and if somebody requests this video, I'm going to ask the use case sorry. But right now we are just directly use the container in the compute host and if the people want the isolations, they can use the kata, choose the kata as a runtime, so I'm not sure if this still makes sense to run the container in the VMs and I need to learn more about the use case. So is there any other questions? Thank you.