| commit | df0972c1ee4d8dbb5b7a053198d8772a39fbdf86 | [log] [tgz] |
|---|---|---|
| author | Dean Troyer <dtroyer@gmail.com> | Wed Mar 07 17:31:03 2012 -0600 |
| committer | Dean Troyer <dtroyer@gmail.com> | Tue Mar 13 15:17:58 2012 -0500 |
| tree | 55d39eab32507c527b80d9fcd6271fa3a9e3a6a3 | |
| parent | 8ebe0308e314878b85cd51913d2c826ef07cd8a0 [diff] |
Spring cleaning in docs This is nearly all about spiffing up stack.sh to improve comment content and readability. Shocco has been fixed so the comments and code line up properly again in http://devstack.org/stack.sh.html so the comments are being cleaned up and updated. Change-Id: I2add0351106fb832fbf6e236cbd90630df97dec3
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.
If you would like to use Xenserver as the hypervisor, please refer to the instructions in ./tools/xen/README.md.
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
If the EC2 API is your cup-o-tea, you can create credentials and use euca2ools:
# source eucarc to generate EC2 credentials and set up the environment . eucarc # 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.
Swift is not installed by default, you need to add the swift keyword in the ENABLED_SERVICES variable to get it installed.
If you have keystone enabled, Swift will authenticate against it, make sure to use the keystone URL to auth against.
At this time Swift is not started in a screen session but as daemon you need to use the swift-init CLI to manage the swift daemons.
By default Swift will configure 3 replicas (and one spare) which could be IO intensive on a small vm, if you only want to do some quick testing of the API you can choose to only have one replica by customizing the variable SWIFT_REPLICAS in your localrc.