| commit | 2eb9a13cce822251fd8e3115bf71ee62b777c265 | [log] [tgz] |
|---|---|---|
| author | Rohit Karajgi <rohit.karajgi@nttdata.com> | Wed Aug 08 02:34:51 2012 -0700 |
| committer | Rohit Karajgi <rohit.karajgi@nttdata.com> | Wed Aug 08 07:01:00 2012 -0700 |
| tree | 14facf58934ebaa491e9e335478134d9a53c7c38 | |
| parent | 0416f332fdbb55a2dbeb68810fa165bdb1e0f4a4 [diff] |
Splits out build config params in Tempest. The build parameters for instances and volumes should be configured separately. This patch adds the following Tempest vars: COMPUTE_BUILD_INTERVAL COMPUTE_BUILD_TIMEOUT VOLUME_BUILD_INTERVAL VOLUME_BUILD_TIMEOUT Change-Id: Ia5357114f8e4248a8de4bd0327e08323c487e897
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] in the DevStack repo. For example, you can do the following to create a diablo OpenStack cloud:
git checkout stable/diablo ./stack.sh
You can also pick specific OpenStack project releases by setting the appropriate *_BRANCH variables in localrc (look in stackrc for the default set). Usually just before a release there will be milestone-proposed branches that need to be tested::
GLANCE_REPO=https://github.com/openstack/glance.git GLANCE_BRANCH=milestone-proposed
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 can enable easily by adding this to your localrc:
enable_service swift
If you want a minimal Swift install with only Swift and Keystone you can have this instead in your localrc:
disable_all_services enable_service key mysql swift
If you use Swift with Keystone, Swift will authenticate against it. You will need to make sure to use the Keystone URL to auth against.
If you are enabling swift3 in ENABLED_SERVICES devstack will install the swift3 middleware emulation. Swift will be configured to act as a S3 endpoint for Keystone so effectively replacing the nova-objectstore.
Only Swift proxy server is launched in the screen session all other services are started in background and managed by swift-init tool.
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.