oneiric powered development environment for openstack
Shell Other
Latest commit 6b8a115 Dec 3, 2016 OpenStack Proposal Bot Updated from generate-devstack-plugins-list
Change-Id: I21c31b0778486971719f1281428c7a089f583656
Permalink
Failed to load latest commit information.
data Fix comment in plugin-registry header Aug 31, 2016
doc/source Updated from generate-devstack-plugins-list Dec 3, 2016
exercises Neutron: use "OSC show -f value -c id" instead of "OSC list + grep" Nov 18, 2016
extras.d Merge "Ensure testing configuration can run as late as possible" Nov 30, 2016
files Merge "Add keystone VirtualHost for port 443 when USE_SSL is True" Dec 2, 2016
gate Mostly docs cleanups Mar 28, 2015
inc meta-config: Fix consecutive same sections Nov 25, 2016
lib Merge "Always setup cells v2" Dec 2, 2016
pkg Update ElasticSearch version default to 1.7.5 May 5, 2016
samples Update local.sh sample file to use OSC Nov 11, 2016
tests meta-config: Fix consecutive same sections Nov 25, 2016
tools Merge "Move default Keystone API version to v3" Dec 1, 2016
.gitignore Add files/*.deb and files/*.deb.* to gitignore Aug 25, 2016
.gitreview Add .gitreview config file for gerrit. Nov 16, 2011
.mailmap Remove AUTHORS Aug 14, 2014
FUTURE.rst Document where we are going Feb 5, 2015
HACKING.rst Fixes language: "following allowing" -> "allowing" Aug 23, 2016
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.md Update stable branch example Nov 3, 2016
clean.sh Merge "Remove all *.pyc files in $DEST when executing clean.sh" Nov 28, 2016
exercise.sh Remove EC2 API from devstack Mar 15, 2016
exerciserc Remove EC2 API from devstack Mar 15, 2016
functions Enable bridge firewalling if iptables are used Sep 29, 2016
functions-common Merge "If plugin is enabled multiple times fail" Nov 29, 2016
openrc Move default Keystone API version to v3 Nov 2, 2016
run_tests.sh Remove old comment in run_tests.sh Apr 17, 2015
setup.cfg Replace the devstack.org with devstack docs url Sep 26, 2015
setup.py Convert all HTML doc to RST Oct 22, 2014
stack.sh Merge "Always setup cells v2" Dec 2, 2016
stackrc Merge "Move default Keystone API version to v3" Dec 1, 2016
tox.ini Update to bashate 0.5.1 Apr 26, 2016
unstack.sh Remove call to undefined teardown_neutron_debug Nov 12, 2016

README.md

DevStack is a set of scripts and utilities to quickly deploy an OpenStack cloud.

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 http://docs.openstack.org/developer/devstack

IMPORTANT: Be sure to carefully read stack.sh 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 stack.sh 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 Newton OpenStack cloud:

git checkout stable/newton
./stack.sh

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=git://git.openstack.org/openstack/glance.git
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):

./stack.sh

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

  • Horizon: http://myhost/
  • Keystone: http://myhost:5000/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
nova 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...

stack.sh 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. stack.sh specifically does not run if started as root.

DevStack will not automatically create the user, but provides a helper script in tools/create-stack-user.sh. 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.