Name Mode Size
data 040000
doc 040000
extras.d 040000
files 040000
gate 040000
inc 040000
lib 040000
playbooks 040000
roles 040000
samples 040000
tests 040000
tools 040000
.gitignore 100644 0 kb
.gitreview 100644 0 kb
.mailmap 100644 0 kb
.zuul.yaml 100644 23 kb
FUTURE.rst 100644 4 kb
HACKING.rst 100644 12 kb
LICENSE 100644 10 kb
MAINTAINERS.rst 100644 1 kb
Makefile 100644 2 kb
README.rst 100644 4 kb 100755 4 kb
functions 100644 31 kb
functions-common 100644 72 kb
openrc 100644 4 kb 100755 1 kb
setup.cfg 100644 0 kb 100755 1 kb 100755 45 kb
stackrc 100644 37 kb
tox.ini 100644 2 kb 100755 4 kb
DevStack is a set of scripts and utilities to quickly deploy an OpenStack cloud from git source trees. Goals ===== * 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 Read more at 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. Versions ======== 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:: GLANCE_REPO= GLANCE_BRANCH=milestone-proposed 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: * Horizon: http://myhost/ * Keystone: http://myhost/identity/v2.0/ 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). Customizing =========== 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.