commit | 3320c55d10b65d370f1b91bde1bcbd4d78a6a5ca | [log] [tgz] |
---|---|---|
author | Dean Troyer <dtroyer@gmail.com> | Wed Nov 23 23:19:10 2011 -0600 |
committer | Dean Troyer <dtroyer@gmail.com> | Fri Jan 06 16:39:46 2012 -0600 |
tree | e2dee62b889931bb7f7ff7d62c2c47592a5ad41b | |
parent | f4497d5eb9b1d1457593515ff7a9f23d433ccba0 [diff] |
Set up downloaded images for testing Change-Id: Ia08d314e26fcf4a443b567432d0c36202d151c9f
Devstack is a set of scripts and utilities to quickly deploy an OpenStack cloud.
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.
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
./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
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.