Devstack is a script used primarily for upstream OpenStack development. This wiki page documents usage information for devstack on Fedora.
Getting Devstack for Fedora
Devstack has native support for Fedora in the master branch. The stable/essex and stable/diablo branches of devstack do not support Fedora.
Start by cloning the upstream devstack repo.
$ git clone git://github.com/openstack-dev/devstack.git
Devstack allows you to create a
localrc file with settings specific to your environment. Creating this file isn't strictly necessary, but it's likely you'll want to use it at some point. Here are some options commonly used that are worth noting:
By default, devstack puts your GIT checkout in /opt/stack instead of your home directory. To choose a more sensible location set
By default DevStack will spew 100000's of lines of shell script at your console while it works. This is less than helpful, because you can't understand what it is doing and if something goes wrong the important messages have probably scrolled off the screen. So turn off verbose output and instead save all shell output to log files. Also make each screen session log its output.
LOGFILE=$DATA_DIR/logs/stack.log SCREEN_LOGDIR=$DATA_DIR/logs VERBOSE=False
Set this if you would like to use Qpid instead of RabbitMQ. Qpid is set as the default in the Fedora OpenStack packages.
disable_service rabbit enable_service qpid
By default, devstack assumes your primary network interface is
eth0. Ethernet and other network device naming has changed in recent versions of Fedora. To see what your machine actually uses for a network device, run ifconfig and use the device that your machine uses to talk to the outside world. It is likely that this is
HOST_IP_IFACE=em1 PUBLIC_INTERFACE=em1 VLAN_INTERFACE=em1 FLAT_INTERFACE=em1
When creating the stack deployment for the first time, you are going to see prompts for multiple passwords. Your results will be stored in the localrc file. If you wish to bypass this, and provide the passwords up front, add in the following lines with your own password:
MYSQL_PASSWORD=badpassword SERVICE_TOKEN=badpassword SERVICE_PASSWORD=badpassword ADMIN_PASSWORD=badpassword
To have devstack automatically load custom images, set the
If you would like to load the Cirros images devstack uses by default, as well as the Fedora 16 image, use:
For a list of other variables that can be specified, including ones that allow you specify custom git repos and branches to use for testing, see the
To run devstack, you just run the
Using the environment
Once the stack is up and running, you can use it like you would any other OpenStack deployment. Devstack includes a couple of files that will populate your environment with the needed variables for various tools to work:
$ . ./openrc $ nova list
$ . ./eucarc $ euca-describe-instances
Running the devstack exercises
Devstack includes a set of exercise scripts to do some basic testing of the running stack. These tests are used by jenkins to gate commits to various OpenStack projects. To run them, run the
To see a list of tests:
$ ls exercises/ boot_from_volume.sh bundle.sh client-args.sh client-env.sh euca.sh floating_ips.sh swift.sh volumes.sh
To skip a set of exercises, specify a comma separated list of exercise names in the
$ SKIP_EXERCISES=swift,volumes $ ./exercise.sh