A brief history of MicroStack

OpenStack is no doubt a wonderful and successful piece of software. It allows you to create your own cloud infrastructure, and thanks to its open-source nature, it’s free to use for everyone. But as with many giant software projects, all that power comes with a challenge: it is reasonably complex to install and configure. A number of OpenStack distributions do exist that intend to make engineers’ life a lot easier, but those also tend to be more complex than a non-experienced user would like them to be.

To solve this problem once and for all, Canonical created a simplified and easy-to-install distribution of OpenStack called MicroStack.

About MicroStack

Canonical MicroStack is an open source project that enables you to easily deploy a fully-functional OpenStack environment on your workstation or even a virtual machine (VM) in minutes. Even though it was originally designed with testing and development use cases in mind, eliminating the need for dedicated hardware, it is now heading towards its first stable release. This means that it will soon be suitable for production use cases too.

The first version of MicroStack was distributed as one big snap package with all OpenStack components in it, running natively on the host where installed. It included core OpenStack components only. This was a good solution, although not so customisable. A beta version has been available for some time and has gained significant community adoption with more than 2,500 active installations. It has never moved towards its first stable release, however. Instead, Canonical has been working on an even more flexible and yet more powerful solution that is both customisable and easy to use.

This is how the K8s-native MicroStack edition was born. It is basically a fresh start for the project. A big part of it was rewritten, and a new architecture was used. This new solution has been in development since 2021, and we released a beta version around October 2022. The first release aimed at a single-node installation, which is already useful for many use cases, such as CI/CD environments. The following versions will expand on that so you can install multi-node clusters.

Many things are different in this new version. Juju is at the heart of the deployment, using Charmed Operators to deploy each OpenStack component as a separate unit. Kubernetes is the substrate for all control plane services. Most OpenStack components become separate pods in K8s. Even the Juju controller itself is hosted there. It leverages the native and natural resilience of the K8s model to deal with OpenStack’s high availability (HA). This eliminates the need for using traditional HA technologies, such as Corosync, Pacemaker, HAProxy and Keepalived. Finally, Juju is driven by Terraform and its new Juju backend provider, making it a nice and easy ramp-up into the Juju world.

Of course, some parts of OpenStack are not a good fit for running inside a container. Services like nova-compute (that drives QEMU/KVM), ovn-chassis (that plugs into the network cards), ceph-osd (that needs access to physical hard drives) work better when run natively on bare metal. This is why those are distributed in a separate package to be installed on hypervisor/storage nodes.

Everything comes packaged as snaps, making OpenStack fully decoupled from the underlying operating system (OS). MicroK8s is used to bootstrap the Kubernetes substrate. MicroStack itself was already available in the snap format, providing cloud management and governance services, with a new snap package for the data plane functions.

You can test it now

As mentioned above, a beta release of the K8s-native edition is already out, and you can test it right now. The current version of the tool uses Yoga OpenStack and is limited to installing the cloud in a single-node mode, but this is already suitable for many cases like developing, education, training, test environments, PoCs, personal cloud, edge computing, labs, CI pipelines, integration and API tests, and much more.

To test it, first, you need a bare metal machine or a VM with enough resources and running Ubuntu 22.04 LTS. If you use a VM, make sure to enable nested virtualisation; otherwise, you will not be able to spawn cloud instances. The following steps are very high level, and they assume you already have some knowledge about OpenStack. Please refer to our official introduction guide for more information about OpenStack, its architecture and services.

Installing K8s-native MicroStack

There are two approaches for installing K8s-native MicroStack. For a simple and streamlined installation, you can run a script that will do most of the installation for you. In this blog, we’re going to use this method. You can also refer to my YT video for the more advanced scenario.

For the easy way, run the following commands:

sudo snap install microstack --channel sunbeam/beta 
microstack install-script | bash -x

The installation script takes a while to finish. Once it completes, Openstack is already installed, and you can access the dashboard (Horizon) on your local web browser. To find out what the URL for the dashboard is, take a look at the status for the dashboard charm:

juju status -m openstack horizon

Alternatively, you can source the RC file to use the command line:

source demo_openrc

If you want to go with a more detailed approach where you manually execute each step, check what you are doing and learn more in the process, I encourage you to watch my video and read the official tutorial on our discourse page.

Conclusion

OpenStack adoption has been greatly facilitated with on-rails solutions like MicroStack. MicroStack K8s-native edition is a new and revamped tool that builds on top of what MicroStack used to provide in the past. It is a new project, already in beta, but very promising and definitely worth keeping your eyes on for the next few months. How about having some fun trying it out?