System for quickly installing an OpenStack cloud from upstream git for testing and development.

Go to file

Derrick J. Wippler aaa0dbb2e7 Restart openstack services after running stack.sh * Added screen_rc function in stack.sh to save started services to stack-screenrc file * Added rejoin-stack.sh to rejoin the current screen session or start a new session Change-Id: I381a7832bc8a107bfbd51c5ecfbd2e9134cf0a0a blueprint: restart-services		2012-02-23 12:08:43 -06:00
exercises	Wait for instance termination to complete.	2012-02-22 11:19:32 -05:00
files	Adds quantum service and endpoint to keystone if quantum is enabled.	2012-02-21 13:50:00 -08: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	Delete security group after terminating instance.	2012-02-21 17:47:46 -05: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	Restart openstack services after running stack.sh	2012-02-23 12:08:43 -06: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:

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