Can you install OpenStack on RaspberryPi's?

asked 2013-06-12 11:09:36 -0500

anonymous user


updated 2013-06-12 13:45:26 -0500

smaffulli gravatar image


I was looking at this link:

It's essentially a 33 RPi cluster. I was wondering if installing and setting up OpenStack on this was even remotely possible? Of course, instance types would be incredibly small - but just as a test and proof of concept for distributed computing?


edit retag flag offensive close merge delete

6 answers

Sort by ยป oldest newest most voted

answered 2013-06-12 22:03:29 -0500

matt joyce gravatar image

The Raspberry Pi does not have an ARM mcu with virtualization interrupts. It would be a poor target for virtualization. Also it's lack of disk space and memory resources would make it a poor target as well.

However one could consider an LXC target. It could make for an acceptable build target on ARM if you were doing some sort of arm build testing in a CI environment or something.

Having a few ARM units rigged into an existing openstack environment as an availability zone for ARM testing could in fact be quite useful. Depending on your needs.

edit flag offensive delete link more

answered 2013-06-12 13:46:44 -0500

smaffulli gravatar image

As a toy to play with, maybe. John Dickinson wrote about installing swift on the Pi.

edit flag offensive delete link more

answered 2013-12-10 09:00:26 -0500

ewindisch gravatar image

I've run OpenStack Compute (nova) on a single raspberry Pi using a modified version of Devstack and the Grizzly release.

As others mentioned, I used LXC as this was the only 'virt' target that could have worked. I also chose to use the ZeroMQ messaging driver. That choice was predicated on the fact that it limited the complexity of the installation and the memory footprint on the Pi. Plus, as the author of that driver, I wanted to see it working on ARM.

Ultimately, I discovered that LXC just didn't work on my single-Pi-OpenStack board. It might have been as "simple" as memory, or it might have been the version, or even overall ARM support. I decided not to dig into it further. I knew that to proceed, I'd need to create a cluster of Raspberry Pis as while I could get all of the essential Nova services to run, the machine was swapping too heavily and had no free memory to run containers.

I'd suggest you need a minimum of two Raspberry PI boards to run OpenStack Compute using a bare-minimum number of services. That would exclude support for VNC, Spice, nova-cert, EC2, etc. One machine could run all of your core services, the other dedicated to nova-compute.

This repository is quite old and it may be that it no longer works due to external dependencies, but you're welcome to take a look. The big changes here are my configuration settings for localrc and masking the installation of dependencies that aren't available for installation in Raspbian (but not actually required for Nova):

If you want to run OpenStack services besides Compute, you'll need additional Raspberry Pis.

edit flag offensive delete link more


Hello, I need your help. I am trying to deploy openstack on Raspberry Pi 3. I already built LXC on thta. But when I am trying to build Openstack on that its showing some error: (see below) + die 413 'Unable to determine DISTRO, can not continue. + local exitcode=1 set +o xtrace ./

Humayun Kabir gravatar imageHumayun Kabir ( 2017-07-03 09:39:29 -0500 )edit

answered 2013-06-12 21:56:23 -0500

fifieldt gravatar image

updated 2013-06-12 21:58:16 -0500

edit flag offensive delete link more

answered 2013-06-12 22:22:56 -0500

vkmc gravatar image

updated 2013-06-12 22:23:15 -0500

If it's just for fun... yeah, it's possible. If not, Pi's specs are not enough for a decent OpenStack cloud deployment.

I tried it a few months ago with the most basic deployment over Raspbian.

It would nice to see how it behaves in a cluster though :)

edit flag offensive delete link more

answered 2013-06-13 06:48:34 -0500

badiane gravatar image

updated 2013-06-13 06:57:14 -0500

"The Raspberry Pi does not have an ARM mcu with virtualization interrupts."

If you are using container based virtualization it shouldn't matter, but I don't know if libvirt, which I think is used to manage LXC, has that as a pre-requisite.

But were libvirt not make that a requirement, it should be possible to use LXC where ever the kernel makes it possible.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-06-12 11:09:36 -0500

Seen: 29,813 times

Last updated: Dec 10 '13