 Thank you. Greetings, colleagues. I'm glad to be with you today and I want to introduce you with our product, with our pristine machine. Pristine Machine is a startup company in a stealth mode. We already have a first client and it is our potential customer and he wants us to make them first in the first unknowns and to combine our marketing activities. That's why we cannot share all details of our products and even our main goals and business cases. But we can share some details which are related to OpenStack and that's why we are here. Our Android experiments are by product of our OpenStack-based development. We already are a very grateful community for a huge base of sources and for your documentation, for your products, it is really large stuff and it really helps us. We're excited to launch out of our products as soon as possible and we believe that it will make OpenStack more reliable and I guess more enterprise-ready. Let's see what we can show. Our first real challenge was to install OpenStack Compute Note into Android operating system. That was our first complicated task and it is the most complicated task. It was the first most complicated task for us. Other tasks are less complicated. This was our first K-point. Let me show how it works. It is an architecture of our presentation environment. I will show you a video because deployment takes too much time and we have only a few minuses. So we have our first video. It is an over-cloud environment based on Instack. There are already, here is a problem, sorry, guys. Here is an over-cloud environment based on Instack. We have already some set of images. All of them are default except this one. This image which we will show is an Android image which contains OpenStack Compute Note on it. As you can see, the build is Android. This is a Linux build but it is an Android operating system, a complete Android operating system. We saw some variables to work with under-cloud, to work with Instack virtual machine and to deploy our over-cloud system. Our over-cloud will contain only two nodes. We need only two nodes. The first is OpenStackControllerNode and the second one is OpenStackComputeNode, which is based on Android. So now deployment is running. It is waiting for readiness, but we will switch to another one video. Hope, yes! And wow! So, we have waited for the readiness of OpenStack. Over-cloud, two nodes are ready. Running and we will check them. We need at least their RP addresses to work with them. Both of them are running. We can see it with our build manager. They are using CPU and at the first time we will go to the OpenStackComputeNode because we need to set up it and to launch a command for over-cloud. We need to verify that over-cloud is working, that over-cloud is ready. So we again source details to work with over-cloud. We are switching to over-cloud compute node and are checking our nodes and images. As you can see, we don't have any nodes. We don't have any instances for the current moment, but we have two images. The first image is our friend, it's a zero-image, which we are all using for our testing. So we will make an instance with this default zero-image and it is run, it is launched. It will also take some time. We will check that the instance is created and later we will check that this instance is really running into our compute node. Start. So now our instance is running. We know how to access them. It has an IP address. To access it, we will go to the compute node and we open a VNC station. Also, for the current moment, we need to check that all processes are running. Required processes, for example, open the switch, client query process and other virtualization processes. So we will go to the VNC interface of this compute node and it must show us our default instance, which is running first. And we see that our zero-image is booting up. It makes some stuff, but it is completely functional, it has the name and later we can use it as our destination operating system. So why we do such things? It's a real good question, I guess. We're doing such things to learn, to learn how to build OpenStack from sources, how to work with it like it is our product. In such a way, we can build OpenStack and deploy it on any operating system we may need. Also, we can deploy it on different cross-multiple platforms. We can deploy it on different devices and different processor architectures. An example is that Android operating system, which is running in overcloud. It was really not easy to do, but we have done it. Everybody who works with Android knows that it is not easy to work with it and it is very limited in resources and you must do a lot of things to make usual Linux programs running as they are running, for example, on Ubuntu. But we have done it and now we have OpenStack Compute Note and then running on Android and as I said, it is extremely light operating system and it is really portable and this will help us in future. So as we can see, applying of standards and a bit of C++ makes everything possible. And we have some future goals, some current goals. There are several of them and they do not look very easy and very simple, but we already know that they are achievable for us. And we believe that OpenStack can become more reliable and more faster. And that's why we are here. That's why we want to participate in this process and to work with you guys to share our experience and to know what is better for the world. Thanks for your attention, for your time. And if you have any questions, I would gladly answer all questions. So thank you for your time. See you the next time.