OpenStack Single-Node (MicroStack)

I have been using OpenStack single-node installation at home for the last couple of years. With a personal cloud at home, I could deploy apps used at home (i.e. media server, file storage…) and run labs.

I like OpenStack but have to say that it is a hard nut to crack. Installation is probably the most painful area. I have tried different approaches like manual install, devstack and packstack but always had to spend a lot of time fixing things.

Recently I came across another method: MicroStack. While Devstack uses Puppet to deploy Openstack, Microstack does the same job using a single snap package.

A full OpenStack in a single snap package. MicroStack is an upstream multi-node OpenStack deployment which can run directly on your workstation.

At the time of writing, the supported OpenStack services are Glance (Image service), Horizon (Dashboard), Keystone (Security), Neutron (Network) and Nova (Compute).

The only issue I’ve faced with MicroStack is the connectivity between VMs and physical network. It seems to be a feature that is not implemented yet.

Unfortunately, the Microstack documentation is limited at this point in time. Therefore, I had to do some research and came up with a “workaround” that is detailed in the Physical Network section.

MicroStack Requirements

According to the official documentation, these are the minimum requirements to run Microstack in OpenStack Single-Node mode:

  • Hardware: 2 CPUs, 8 GiB of memory and 100 GiB of disk.
  • Operating System: Ubuntu 18.04 LTS or Ubuntu 20.04 LTS.

I am using my old HP ProLiant ML 350 G6, which I kindly call “Death Star”. It doesn’t have the power to destroy planets, but comes with 2 Xeon Quad Core and 96Gb RAM.

My HP ProLiant ML350 G6 (a.k.a. Death Star)

OpenStack Single-Node Design

The diagram below presents an example of a personal cloud for home lab.

OpenStack Single-Node Design

The following sections use this design as a reference to implement MicroStack and a workaround to enable the connectivity from a physical network.

MicroStack (OpenStack Single-Node) Setup

The best thing about MicroStack is the easy setup. With literally two lines of command, you have OpenStack up and running.

First install using snap:

sudo snap install microstack --devmode --beta

Then run the automatic OpenStack configuration:

sudo microstack init --auto --control

It will take about 10 to 15 minutes to finish depending on your machine.

When the installation finishes, you will access the dashboard using the host IP address or hostname. If everything went well, you will see the login screen.

Horizon Dashboard

The admin password can be obtained by using the following command:

sudo snap get microstack config.credentials.keystone-password

You will notice that we need the prefix “microstack” when using any of the OpenStack components’ CLIs. We can remove the prefix by creating an alias, like this:

sudo snap alias microstack.openstack openstack

As we will use Open vSwitch CLI in the next section, please create an alias for it:

sudo snap alias microstack.ovs-vsctl ovs-vsctl

Single-Node Physical Network

This is where the fun starts! The default configuration does not allow you to connect VMs directly to your physical network. Unfortunately, the MicroStack’s documentation is limited at this point in time, so I had to do some research to find a solution.

I had a quick look at the source code, and it looks like IP addresses are hardcoded. Therefore, I used a “workaround” instead of a proper fix. As I couldn’t replace the default external network CIDR (, I replaced it with a new one to work with my physical network.

Delete Existing Networks

In order to replace the default external network, we first need to delete it. We will also delete the test network, as it will no longer be required.

The default configuration has a router attached to the networks. Therefore, we need to remove it before deleting the networks. Find the “test-router” under Admin > Network > Routers and delete it.

Remove Router

Now go to Admin > Network > Networks and delete the existing networks.

Remove existing networks

Physical Network Configuration

The new physical network will enable internal networks to communicate with the external world. Therefore, we will name it “public”. Go to Admin > Networks > Network and click on the “Create Network” button. Use the same information as picture below.

Public Network

Note: The default neutron physical network name for MicroStack is ‘physnet1’. Use the command below if you want to double-check this configuration.

sudo ovs-vsctl get open . external_ids:ovn-bridge-mappings | awk -F: '{gsub("\"","");; print $1}'

For the subnet configuration, please replace the Network Address and respective Gateway IP for your physical network configuration.

Public Subnet Configuration

Disable the DHCP and add the IP range from your LAN that will be reserved for OpenStack.

Public Subnet Details

Important! Remember to check if your DHCP server’s if the IP address range do not conflict with the ones allocated for OpenStack.

If you are here just for the physical network configuration, the next steps are optional. Otherwise, follow the steps until the end to test your configuration.

The “Workaround”

Until now, we have done nothing different from the usual OpenStack network configuration. Although I don’t consider the configuration below as a proper fix for my problem, it did the trick for now.

First, we need to add the Physical Ethernet (enp3s4 in my case) as a port of our external bridge. As described in the Open vSwitch Common Configuration Issues, adding the port without removing the IP address from the Physical Ethernet is indeed a common mistake. Therefore, the following commands add the port, remove the IP address from Physical Ethernet, and add the server’s external IP address to the bridge.

ovs-vsctl add-port br-ex enp3s4
ip addr flush dev enp3s4
ip addr add dev br-ex
ip link set br-ex up

Note: If you are remotely accessing your server, I would recommend running all commands above as a single command line.

Persist Changes through reboot

This section presents an approach to ensure that it will apply the right configuration after rebooting the machine.

As far as I understand, MicroStack uses a ‘oneshot’ service on systemd for network configuration. Therefore, I created another service to complete my network configuration.

First, we need to create the following script with the network configuration. Name it ‘microstack-br-workaround’ and save it under ‘/usr/local/bin’ folder.

# Workaround to enable physical network access to MicroStack
# Adds the server physical ip address to br-ex.


# Add IP address to br-ex
ip address add $physicalcidr dev br-ex || :
ip link set br-ex up || :

Now create the file ‘microstack-br-workaround.service’ in the ‘/etc/systemd/system’ folder.

Description=Service for adding physical ip to microstack bridge



Enable the service, so it can run during the next boot.

systemctl daemon-reload
systemctl enable microstack-br-workaround.service

Now you can reboot to check the network.

Home Lab Network

Here I describe how my home lab network was configured. Change some parameters if you know what you are doing.

First go to Admin > Networks > Network, click on ‘Create Network’ and use the settings from picture below.

Home Lab Network

Now give a name to the subnet and define the respective CIDR block.

Home Lab Subnet

Leave the DHCP checked and click on the ‘Create’ button.

Home Lab Subnet Details

Now we need to connect our home lab network to the public network. Go to Admin > Network > Routers and click on ‘Create Router’. Use the information from the picture.

If you go to Project > Network > Network Topology, the router appears connected to the public network. Let’s connect it to the home lab network by clicking on the router and then on ‘Add Interface’ button.

Choose ‘home-lab-network’ from the drop-down list and click ‘Submit’.

The resulting network topology should look something like this.

Final Network Topology

Test Virtual Machine and Security Group

Now we need to check if our configuration works. Following the diagram from the previous section, we will create the VM and respective security group.

Floating IP

First allocate a floating (public) IP that the VM will to access the physical network. Go to Project > Network > Floating IPs and click on ‘Allocate IP to Project’. Leave the default configuration and click ‘Allocate IP’.

You should be able to see the allocated floating IP in the list.

Security Group

We also need to create the security group before the VM. Go to Project > Network > Security Groups and click ‘Create Security Group’. Then name it ‘test-sg’ and click ‘Create Security Group’.

After creating the security group, you will be redirected to the rules management page. Otherwise, go to Project > Network > Security Groups and click on the ‘Manage Rules’ button for the ‘test-sg’ group.

We are going to add couple rules for our test. One to allow us to ping the VM and another to connect via SSH. Click on the ‘Add Rule’ button and choose ‘All ICMP’ from the rule drop down list as shown in the picture below.

Click on the ‘Add’ button and repeat the same process for the ‘SSH’ rule.

Virtual Machine

Finally, it’s time to create our VM. Go to Project > Compute > Instances and click on ‘Launch Instance’ and then use the following information to create your instance:

  • Instance Name: test-instance
  • Select Boot Source: Image
  • Create New Volume: No
  • Allocated Image: select the cirros image in the ‘Available’ section by clicking on the up arrow.
  • Flavor: select ‘m1.tiny’ from the ‘Available’ list by clicking in the respective up arrow.
  • Allocated Network: select ‘home-lab-network’ in the ‘Available’ list by clicking in the respective up arrow.
  • Security Groups: remove the ‘default’ group by clicking on the respective down arrow and then select ‘home-lab-network’ in the ‘Available’ list by clicking in the respective up arrow.

We need to associate a Floating (public) IP to the VM, so it can connect to the physical network. From the Actions’ drop down list, select ‘Associate Floating IP’.

Then assign the floating IP.

Testing Your OpenStack Single-Node

We can now test the network connectivity. Start with a simple ping test.


Then connect to the VM via SSH. The default password for the cirros user is “gocubsgo”.

ssh cirros@

You can use the following command to test the internet connectivity from your VM:

curl -I

Consider the VM’s internet connection successful if you received the HTTP/1.1 200 OK response.


I expect that by now you have your own OpenStack Single-Node up and running. I have been thinking about looking at the source code and see if I can find a more definitive solution. Although, I may not have much time for it and the MicroStack guys may include this feature in near future.

4 comments / Add your comment below

  1. hello Sir,
    do you have some guides to deploy openstack on an ubuntu server in a production environment?

  2. Rodrigão, muito bom o post! Era o que eu precisava para começar com openstack 🙂 Abração!

  3. What if we are using Microstack Multinode and we have the Public IP block ?
    e.g eth01 –
    And we have another block of Ips e.g how would we set VM’s to access Public network?
    Please help we are working on this issue for a week, and Openstack is new to us? Any solution to this workaround?

Leave a Reply

Your email address will not be published. Required fields are marked *