Skip to content
System for quickly installing an OpenStack cloud from upstream git for testing and development.
Shell Python Makefile
Branch: master
Clone or download

Latest commit

lyarwood tempest: Increase m1.nano and m1.micro RAM by 64MB to avoid tmpfs exh…

tmpfs exhaustion has long been suspected as the root issue behind
failures to load ssh keys and other metadata from local config drives as
documented in bug #1808010. This can also lead to failures fetching
metadata from n-metadata-api leaving Tempest unable to SSH into

This change increases the RAM of the m1.nano and m1.micro flavors by
64MB to hopefully avoid these errors going forward. This is also ahead
of our eventual upgrade to Cirros 0.5.0 where 128MB becomes a

Related-Bug: #1808010
Change-Id: I4b597579cf89939955d3c110c0bd58ca05de61f0
Latest commit 54edc7a May 22, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
data Fix comment in plugin-registry header Aug 31, 2016
doc Cleanup py27 support May 9, 2020
extras.d Merge "Ensure testing configuration can run as late as possible" Nov 30, 2016
files Remove bridge-utils/brctl usage Apr 30, 2020
gate Mostly docs cleanups Mar 28, 2015
inc Support extras in Glance Store install Mar 30, 2020
lib tempest: Increase m1.nano and m1.micro RAM by 64MB to avoid tmpfs exh… May 22, 2020
playbooks Drop DEVSTACK_GATE_FEATURE_MATRIX Mar 18, 2020
roles setup-devstack-source-dirs: add var for paths Apr 26, 2020
samples Fix default security group in samples/ Sep 5, 2019
tests Use python3 as default python command Feb 17, 2020
tools Fix pip distro package removal for focal May 12, 2020
.gitignore Ignore local.conf in root of repo Dec 18, 2018
.gitreview OpenDev Migration Patch Apr 19, 2019
.mailmap Remove AUTHORS Aug 14, 2014
.zuul.yaml Switch to new grenade job name May 4, 2020
CONTRIBUTING.rst [ussuri][goal] Update contributor documentation Apr 23, 2020
FUTURE.rst Document where we are going Feb 5, 2015
HACKING.rst Update docs building Aug 11, 2019
LICENSE Add Apache 2 LICENSE file Apr 18, 2012
MAINTAINERS.rst Move Sahara into in-tree plugin Jul 1, 2015
Makefile Suppressed echoing of the line. Apr 30, 2016
README.rst Update (git|review) links to opendev Jun 21, 2019 typo fixed Dec 20, 2018
functions Support upload of qcow2.xz image format Apr 22, 2020
functions-common Cleanup yum things Apr 30, 2020
openrc Merge "Export OS_CACERT after sourcing .stackenv file" Jun 11, 2018 Remove old comment in Apr 17, 2015
setup.cfg Cleanup py27 support May 9, 2020 Convert all HTML doc to RST Oct 22, 2014 Cleanup yum things Apr 30, 2020
stackrc Cleanup yum things Apr 30, 2020
tox.ini Cleanup py27 support May 9, 2020 Revert "Remove deprecated PostgreSQL database driver" Oct 17, 2019


DevStack is a set of scripts and utilities to quickly deploy an OpenStack cloud from git source trees.


  • To quickly build dev OpenStack environments in a clean Ubuntu or Fedora environment
  • To describe working configurations of OpenStack (which code branches work together? what do config files look like for those branches?)
  • To make it easier for developers to dive into OpenStack so that they can productively contribute without having to understand every part of the system at once
  • To make it easy to prototype cross-project features
  • To provide an environment for the OpenStack CI testing on every commit to the projects


IMPORTANT: Be sure to carefully read and any other scripts you execute before you run them, as they install software and will alter your networking configuration. We strongly recommend that you run in a clean and disposable vm when you are first getting started.


The DevStack master branch generally points to trunk versions of OpenStack components. For older, stable versions, look for branches named stable/[release] in the DevStack repo. For example, you can do the following to create a Pike OpenStack cloud:

git checkout stable/pike

You can also pick specific OpenStack project releases by setting the appropriate *_BRANCH variables in the localrc section of local.conf (look in stackrc for the default set). Usually just before a release there will be milestone-proposed branches that need to be tested:


Start A Dev Cloud

Installing in a dedicated disposable VM is safer than installing on your dev machine! Plus you can pick one of the supported Linux distros for your VM. To start a dev cloud run the following NOT AS ROOT (see DevStack Execution Environment below for more on user accounts):


When the script finishes executing, you should be able to access OpenStack endpoints, like so:

We also provide an environment file that you can use to interact with your cloud via CLI:

# source openrc file to load your environment with OpenStack CLI creds
. openrc
# list instances
openstack server list

DevStack Execution Environment

DevStack runs rampant over the system it runs on, installing things and uninstalling other things. Running this on a system you care about is a recipe for disappointment, or worse. Alas, we're all in the virtualization business here, so run it in a VM. And take advantage of the snapshot capabilities of your hypervisor of choice to reduce testing cycle times. You might even save enough time to write one more feature before the next feature freeze... needs to have root access for a lot of tasks, but uses sudo for all of those tasks. However, it needs to be not-root for most of its work and for all of the OpenStack services. specifically does not run if started as root.

DevStack will not automatically create the user, but provides a helper script in tools/ Run that (as root!) or just check it out to see what DevStack's expectations are for the account it runs under. Many people simply use their usual login (the default 'ubuntu' login on a UEC image for example).


DevStack can be extensively configured via the configuration file local.conf. It is likely that you will need to provide and modify this file if you want anything other than the most basic setup. Start by reading the configuration guide for details of the configuration file and the many available options.

You can’t perform that action at this time.