 Hello everyone. Thank you for joining me on this session. My name is Titus Kurek. I'm a product manager at Townally Cow. And today I'm going to talk about Microstack. So Microstack is an open stack on rails solution that allows you to install Microstack very quickly in the most straightforward available way. This session is going to be followed by a quick demo during which I will demonstrate how to install and use Microstack on my workstation. And hopefully there will be time for some questions and answers. So once we wrap up the session, we'll open the panel for questions. So at the beginning, I'm going to talk about two phases of OpenStack. So the first phase of OpenStack is that OpenStack is awesome. And we all know that like we are here because we believe that OpenStack is awesome. It combines market-sized worldwide. It's around a billion of dollars, which is very impressive. It's much higher compared to the market share of the containers market. OpenStack is one of the three biggest open source projects. And only three open source projects achieve this number of involvement from various companies, from various organizations, from various developers. And this is OpenStack, Linux Kernel, and Chromium. What we observe at Canonical and based on the data that are provided by various independent research institutions is that its adoption is constantly growing. If you have a look on the chart below, various proprietary solutions for private cloud implementation. Their adoption is declining while the adoption of OpenStack continues to grow, which is great. And finally, it is very major project. This year, OpenStack has been celebrating its 10 years anniversary. It's been available for 10 years. It's being supported by various companies and independent organizations. It achieves a level when it is really major. And its directions moving forward are going to focus on providing even more stability. So OpenStack is awesome and we all know about that. But unfortunately, OpenStack has second state. This is that it is complex and huge. It is a giant beast. If you have a look at the number of services that are currently available there for OpenStack, there are 32 services plus a number of supporting tools. Obviously, you don't need all of them, right? If you're about to run OpenStack in a data center, in a production environment, you're still probably going to struggle with at least 10 of those primary services, right? Now, each of those services, using a number of configuration files, each configuration file consists of a number of parameters. How are you going to absorb all of that knowledge? Will you be able to configure OpenStack to your desired ultimate state manually? Of course, no. And it is a known fact that OpenStack deployment used to be painful. In fact, there are various commercial OpenStack distributions available around which help you to at least abstract this complexity during the deployment phase so that you don't have to bother about all of the services, all of the processes running, all of the configuration files, every single line in a configuration file. But this is just one portion of the problem. The other problem is that OpenStack operations used to be even more painful. The successful deployment of a cloud is usually just the beginning of the journey. The entire cloud has to be operated effectively for deployment. So OpenStack operations used to be even more painful. And finally, back to this point that it is a huge beast. A typical production deployment consists of at least 12 nodes. So if you're about to set up a lab environment where you just want to experiment with OpenStack or if you were looking for OpenStack as a solution for your edge, it's OpenStack really unanswerable because with all of these overheads, it may turn out that you actually won't be able to successfully use it either on your workstation or in your development environment or on your edge. So this is the second phase of OpenStack. What if you don't need all of this complexity? What if you just need OpenStack? What if you need basic OpenStack services? If you don't need all of those container, per-metal, short-fire system services, just the basic goodness of OpenStack, which is typically Keystone, Glance, Nova, Neutron, and Cinder. What if you don't really care about various extensions, about various configuration options in its configuration files? What if you can just go with the default map? And finally, what if you don't need this cluster consisting of 12 nodes and all you need is just a lightweight OpenStack on Rails solution? Well, if you're looking for something like that, then I hope I have an answer for you. So at the end of the day, we may ask ourselves the question, why not just a single package? Why shouldn't we package all of OpenStack components together with all of their dependencies so that you would be able to install it in a single command and just start using it without struggling with all of this complexity behind its deployment and post-deployment operations? So if you're looking for a solution like that, then I hope I have an answer for you. And this answer is Microstack. So Microstack is an OpenStack in a snap, which means that all of its services with all of their dependencies are packaged together in a single error type that can be just installed by running a snub install command. There's another command to initiate it after the installation, but this is all you need. There are just two commands to set up an OpenStack class. If I'm going to present all of that during my demo part of this presentation, but if you would be looking to try OpenStack on your workstation, then I would encourage you to visit the following website, Microstack.run, or ubuntu.com slash OpenStack slash install, where you will find detailed information about how to install Microstack in just these two steps. So let's not have a look at what's behind Microstack, what's behind this OpenStack on Rails solution. So there are just basic services that are available in Microstack, but as mentioned before, they give you all of the goodness, all of the traditional goodness of OpenStack that you usually need to start your journey. You will find keystone there, you will find the horizon dashboard, glance for images, nova for compute, cinder for storage, neutron for networking, neutron comes with OVM by default, OVM is open source SVM platform that runs on the top of OVM, and what's also worth calling out is that clustering is also available in Microstack. So you can have, if you're looking for a solution where you would be running more than one server, then you can clustered Microstack so that you would be able to use multiple servers at the same time. With regards to minimal requirements, it's a multi-core processor and 16 gigabytes of RAM, so if you're running a typical developer laptop, you should be able to install it on your workstation. So as stated before, Microstack is an OpenStack for testing and development, you can get it up and running on your workstation, but it's also OpenStack for the edge. So if you have a look at what the trends are with the edge computing nowadays is that obviously the data center is going to remain as the key technology powering the infrastructure of organization. And we see OpenStack being deployed in the data center. This can be any type of an OpenStack, this can be Chound OpenStack, it can be AirShift, it can be Ansible powered OpenStack. And then on the edge, we see a bunch of satellite clouds, micro clouds, which typically run either on a single server or just a very small number of the servers like kind of a mini rack with three or five servers. And for this kind of a micro cloud approach, Microstack is the most straightforward way to go. But if you're looking for an OpenStack for the data center, that Microstack fits there as well. So the quick answer is yes, of course, you can use Microstack in the data center as well, like it provides clustering, so as stated before, you can get it up and running across a number of bare metal machines. But one thing you have to remember is that it's an OpenStack on Rails solution, right? It is a snap-based install that the most straightforward way to get OpenStack up and running is very light-based, but it's also opinionated. What does it mean? It means that it's not really configurable. So you only get those basic services and they come with the default value in the configuration file. So if you're looking for a more decent solution for the data center for an OpenStack in the data center, then my recommendation would be to have a look at Charm OpenStack, which is another distribution for OpenStack addressing all of its complexity, but in a different venue, providing a model-driven approach towards its deployment and operations. It's Charm-based, it's composable, configurable, provides lifecycle management capabilities, and it works at any scale. So when you go with your journey with Microstack, it's about making a decision that at some point you need a more powerful solution. So you've got the case, then you can switch to using Charm's OpenStack. But let's get back to Microstack and also analyze the differences between Microstack and solutions like DevStack or PackStack that also provide this kind of an OpenStack on Rails solution. So if you have a look at the differences listed here, the main benefit of Microstack is that all services are available in a single package, which is not the case with Azure Desktop or PackStack. It is a zero open stack because SNAPs receive automatic updates. There is a commercial support available from Chemical for Microstack, while DevStack and PackStack are just kind of a development and testing solutions. It provides the most straightforward deployment with a single command to install it and just another command to initiate it, which is again not the case with DevStack or PackStack. And obviously the disadvantage of Microstack compared to DevStack or PackStack is that it's not configurable. So again, it's an opinionated, SNAP-based OpenStack on Rails solution coming with basic set of services and default values in the configuration file. And now I'm going to move to the demo part of this presentation. So I'm going to switch to my terminal window where I have Microstack already installed because all of this process takes up to 20 minutes. So I ran this command before. We start with Microstack installation using some flags. Then it's just a matter of how quickly can it be downloaded on your local network. And then you run the Microstack init command that takes care of the initial services configuration. And while it's complete, we can start interacting with Microstack using the standard OpenStack client. So I can run something like OpenStack Capital List to display all of the services that are running here and start interacting with all of those APIs. But I can also go to the web GUI. It takes a while. One thing you have to remember is that it's still fully functional OpenStack. And I'm just running Dell Inspiron with limited resources. So it takes some time. But here we go. It's coming. I'm going to use the default username and password that's set during the Microstack installation. And I get the regular OpenStack dashboard. It's 100% upstream, so there's no customization here. It's just like a typical OpenStack that it gets up and running when installed on the O1. And now we can start navigating. We can check images. So there's a serious image downloaded by default. And now what I'm going to do in the next step is to instantiate the testing stones on my Microstack cloud. So obviously I can use, oh, sorry, obviously I can use typical OpenStack client commands as well as server create. But there's just a shorter command available with Microstack that you can use to spin up your test instance. We can move to the instances in the GUI to see whether it's coming. It is not coming yet, but as I stated, it takes some time. So we're about to wait and try to refresh. Here we go. It's building. So it's going to be available in a second. Now it's active. And a server test to launch. The instance has been successfully built. And we can install it. Sorry, we can access it by using a command that's provided here. So we're now inside of the instance on Microstack. We can run some basic commands. For example, let's check the uptime. And that's basically it. So again, what we get as a result is a single node OpenStack running on my workstation. It's 100% upstream. And it can be clustered. So if I would be running, if I was about to run OpenStack across a number of physical nodes, this is also available. And you can refer to those installation instructions that I provided at the beginning of this presentation to get Microstack up and running in a cluster mode. So that's basically it as for the demo and as for this presentation. I hope you enjoyed it. I would encourage you to give Microstack a shot. It's really just 20 minutes to get it up and running on your workstation. One thing that's worth calling out is that if you install it and you just want to remove it because it's consuming some resources on your side, there's only a single command to again uninstall it from your workstation. So that's all with regards to the presentation and the demo. I will be glad to answer any questions that you may have. Thank you very much.