commit | 782f24ee39a1c9cc201956b726c95140cb73dc83 | [log] [tgz] |
---|---|---|
author | Chmouel Boudjnah <chmouel@chmouel.com> | Wed Feb 29 13:42:44 2012 +0000 |
committer | Chmouel Boudjnah <chmouel@chmouel.com> | Wed Feb 29 13:44:38 2012 +0000 |
tree | 6c81fe425443ef14074688110926ac562ca94280 | |
parent | b32c876ed5e66c8971c8126432c1ae957301eb08 [diff] |
Add small note about Swift. Change-Id: Id1c014e6fcdf8e52a5e01e7bacf01a567d25e70a
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.
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.