No description
Find a file
Jesse Andrews 1a52a02f10 support gerrit style refs/changes/... for branch names
To use a gerrit "branch" with devstack I would find the repo/remote and
set it for the specific project.

Example: https://review.openstack.org/2059

Would mean I update my localrc with the following settings:

KEYSTONE_REPO=https://review.openstack.org/p/openstack/keystone
KEYSTONE_BRANCH=refs/changes/59/2059/2

Change-Id: I0793415fb03cc08d1eb1a3faf1b8ec3e723beb31
2011-12-05 15:03:49 -08:00
exercises initial devstack + essex 2011-11-23 11:26:39 -08:00
files Merge "Fix glance config" 2011-12-01 18:54:38 +00:00
tools Rename openstack-integration-tests to tempest 2011-12-01 10:23:32 -06: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 revive working with subset of services 2011-11-20 09:55:44 -08:00
exercise.sh Source stackrc in exercises. 2011-11-10 15:11:28 -08:00
openrc revive working with subset of services 2011-11-20 09:55:44 -08: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
stack.sh support gerrit style refs/changes/... for branch names 2011-12-05 15:03:49 -08:00
stackrc Rename openstack-integration-tests to tempest 2011-12-01 10:23:32 -06:00

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.