openstack/devstack
Code Issues Proposed changes
System for quickly installing an OpenStack cloud from upstream git for testing and development.
1,131 Commits 11 Branches 13 Tags 124 MiB
Shell 92.9%
Python 6.7%
Makefile 0.3%
Jinja 0.1%
5836b1533a
Go to file
Russell Bryant 5836b1533a Wait for VM to stop before deleting security group. 
Related to bug 938853.

The patch for this bug prevents deleting security groups through the
OpenStack API if they are still in use.  This patch for devstack updates
the floating_ips exercise script to wait until the VM has stopped before
deleting the security group.

Change-Id: If42f85934c2b92d4d001c419cabb09e2e3dc1aae
2012-02-24 10:23:33 -05:00
exercises Wait for VM to stop before deleting security group. 2012-02-24 10:23:33 -05:00
files Add nova-volume endpoint to service catalog 2012-02-24 02:10:22 +00:00
tools Fix troubles with git cloning https 2012-02-14 15:30:34 -08:00
.gitignore Update gitignore to ignore log files and localrc 2011-11-01 13:15:09 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-11-16 11:24:49 -08:00
AUTHORS Preserve swift tenant_id variable when writing into keystone catalog. 2012-02-23 17:01:40 -08:00
exercise.sh Source stackrc in exercises. 2011-11-10 15:11:28 -08:00
functions Extract common functions into a separate file 2012-01-31 12:18:16 -06:00
openrc Wait for instance termination to complete. 2012-02-22 11:19:32 -05:00
README.md Update README.md to let users know how to access stable/[milestone] versions of devstack. Other text cleanup as well. 2011-11-23 12:52:31 -08:00
rejoin-stack.sh Restart openstack services after running stack.sh 2012-02-23 12:08:43 -06:00
stack.sh Enable nova-volume by default 2012-02-24 02:01:57 +00:00
stackrc Use keystone master branch by default 2012-02-16 16:34:16 -06:00

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 oneiric 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

Read more at http://devstack.org (built from the gh-pages branch)

IMPORTANT: Be sure to carefully read stack.sh and any other scripts you execute before you run them, as they install software and may 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/[mil estone]. For example, you can do the following to create a diablo OpenStack cloud:

git checkout stable/diablo
./stack.sh

To start a dev cloud (Installing in a dedicated, disposable vm is safer than installing on your dev machine!):

./stack.sh

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 osapi and ec2 creds
. openrc
# list instances
nova list
# list instances using ec2 api
euca-describe-instances

Customizing

You can override environment variables used in stack.sh by creating file name 'localrc'. It is likely that you will need to do this to tweak your networking configuration should you need to access your cloud from a different host.