commit | ce043c4dbf38a4947274cbfcbee79bd8e6283a6c | [log] [tgz] |
---|---|---|
author | Dean Troyer <dtroyer@gmail.com> | Fri Feb 03 22:56:38 2012 -0600 |
committer | Dean Troyer <dtroyer@gmail.com> | Thu Feb 23 22:21:49 2012 -0600 |
tree | 41bcc588ba452d48108a872a95b547c96f22b95d | |
parent | 8d87ca05330d050561611fcc43cfa941a340d13a [diff] |
README updates Change-Id: I0732a26a50b736e89d35b03a9ff79fa068804677
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/[release]. For example, you can do the following to create a diablo OpenStack cloud:
git checkout stable/diablo ./stack.sh
Milestone builds are also available in this manner:
git checkout essex-3 ./stack.sh
Installing in a dedicated disposable vm is safer than installing on your dev machine! To start a dev cloud:
./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.