kloudbuster/doc/source/installation.rst
Yichen Wang d7d9575dda Cleanup logic enhancements, document enhancements
1. Enhance the cleanup logic;
2. Add the missing keypair into the resource logger;
3. Document enhancements on installation and contribution;
4. Fix the bug when parsing the image version string in DIB;
5. Fix the typo in Rest API specification;

Change-Id: Ibf4a1c7828ee4522938b4b55f9a8af5e6c6a133b
2015-09-02 22:59:28 -07:00

8.9 KiB

Installation

There are two ways to install and run KloudBuster tool. Users of KloudBuster should use regular PyPI based installation, while developers of KloudBuster should use GitHub/OpenStack Repository based installation. Normally, PyPI based installation will satisfy most of use cases, and it is the recommended way for running KloudBuster under production environments, or through an automated or scheduled job. A git repository based installation gives more flexibility, and it is a must for developers of KloudBuster.

Note

Installation from PyPI will only have the latest stable version.

PyPI based Installation

This is the recommended way to install KloudBuster for non-development use, and KloudBuster is available in the Python Package Index (PyPI): KloudBuster PyPI

Step 1

You will need to have python 2.7, pip, and some dependencies installed before installing KloudBuster, run the command based on your distro.

Ubuntu/Debian based:

$ sudo apt-get install python-dev python-pip python-virtualenv
$ sudo apt-get install libxml2-dev libxslt-dev libffi-dev libz-dev libyaml-dev libssl-dev

RHEL/Fedora/CentOS based:

$ sudo yum install python-devel python-pip python-virtualenv
$ sudo yum install libxml2-devel libxslt-devel libffi-devel libyaml-devel openssl-devel

MacOSX:

$ # Download the XCode command line tools from Apple App Store
$ xcode-select --install
$ sudo easy_install pip
$ sudo pip install virtualenv

Step 2

Create a virtual environment for Python, and install KloudBuster:

$ virtualenv vkb
$ source vkb/bin/activate
$ pip install kloudbuster

Alternatively, if you have virtualenvwrapper installed:

$ mkvirtualenv kloudbuster
$ pip install kloudbuster

Note

"A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them." It is optional but recommended. We could use:

$ sudo pip install kloudbuster

instead if isolation among multiple Python projects is not needed.

To verify kloudbuster is installed, just type:

kloudbuster --help

GitHub/OpenStack Repository based Installation

It is recommended to run KloudBuster inside a virtual environment. However, it can be skipped if installed in a dedicated VM.

Super quick installation on Ubuntu/Debian

$ sudo apt-get install python-dev python-virtualenv git git-review qemu-utils
$ sudo apt-get install libxml2-dev libxslt-dev libffi-dev libz-dev libyaml-dev libssl-dev
$ # create a virtual environment
$ virtualenv ./vkb
$ source ./vkb/bin/activate
$ git clone https://github.com/openstack/kloudbuster.git
$ cd kloudbuster
$ pip install -r requirements-dev.txt

Super quick installation on RHEL/Fedora/CentOS

$ sudo yum install python-devel python-virtualenv git qemu-img
$ sudo yum install libxml2-devel libxslt-devel libffi-devel libyaml-devel openssl-devel
$ # create a virtual environment
$ virtualenv ./vkb
$ source ./vkb/bin/activate
$ git clone https://github.com/openstack/kloudbuster.git
$ cd kloudbuster
$ pip install -r requirements-dev.txt

Super quick installation on MacOSX

KloudBuster can run natively on MacOSX. These instructions have been verified to work on MacOSX 10.10 (Yosemite).

First, download XCode from App Store, then execute below commands:

$ # Download the XCode command line tools
$ xcode-select --install
$ # Install pip
$ sudo easy_install pip
$ # Install python virtualenv
$ sudo pip install virtualenv
$ # create a virtual environment
$ virtualenv ./vkb
$ source ./vkb/bin/activate
$ git clone https://github.com/openstack/kloudbuster.git
$ cd kloudbuster
$ pip install -r requirements-dev.txt

Verify installation

To verify kloudbuster is installed, just type:

$ python kloudbuster/kloudbuster.py --help

Upload VM Image

Note

If your OpenStack Glance can access the Internet, you can skip this section and you are done with the installation.

KloudBuster needs one "universal" test VM image (referred to as "KloudBuster image") that contains the necessary test software. The KloudBuster image is then instantiated in potentially large number of VMs by the KloudBuster application using the appropriate role (HTTP server, HTTP traffic generator...).

Pre-built images are available for download from the OpenStack App Catalog (preferred method). For whatever reason the pre-built version doesn't work for you, the image can be re-built from MacOSX using Vagrant or from any Linux server. See below section <build_vm_image> for more details.

Manual upload of the KloudBuster VM image

If Glance does not have access to http://storage.apps.openstack.org on the Internet, the KloudBuster VM image must be downloaded from the OpenStack App Catalog to an intermediate location then uploaded to Glance using either a Glance CLI command or via Horizon dashboard.

The KloudBuster VM image can be downloaded from http://apps.openstack.org/#tab=glance-images. Look for an image named with the "kloudbuster_v" prefix and download the one that has the latest version.

KloudBuster VM images are qcow2 images named "kloudbuster_v<version>.qcow2" (e.g. "kloudbuster_v3.qcow2"). The name of the image in Glance must match exactly the image name in the App Catalog (without the .qcow2 extension), for example to upload the image from a local copy of that image:

$ glance image-create --file kloudbuster_v3.qcow2 --disk-format qcow2 --container-format bare --is-public True --name kloudbuster_v3

Build VM image

The official pre-built image from OpenStack App Catalog should satisfy most of use cases. This option is just for development purposes, and for whatever reason the pre-built version does not work for you.

Build on MacOSX

You need to install first:

And build the image with below commands:

$ # Clone the kloudbuster repository if you have not done so
$ git clone https://github.com/openstack/kloudbuster.git
$ # Go to the dib directory
$ cd kloudbuster/kb_dib
$ # Run vagrant and start building the image
$ vagrant up

After a few minutes (depending on virtualbox overhead), the qcow2 image will be built and available in the same directory. You can then upload it to OpenStack using the glance CLI, destroy the vagrant VM ("vagrant destroy") and dispose of the kloudbuster directory (if no longer needed).

Build on Linux

A generally faster build method than with MacOSX/Vagrant. Your Linux server must have python, git and qemu utilities installed. You can skip the package installation if you've installed KloudBuster using the GitHub/OpenStack repository based installation.

Ubuntu/Debian based:

$ sudo apt-get install python-dev git qemu-utils
$ # Source the virtual environment if you have one
$ pip install PyYAML

Redhat/Fedora/CentOS based:

$ sudo yum install python-devel git qemu-img
$ # Source the virtual environment if you have one
$ pip install PyYAML

Build the image with below commands:

$ # Clone the kloudbuster repository if you have not done so
$ git clone https://github.com/openstack/kloudbuster.git
$ # Go to the dib directory
$ cd kloudbuster/kb_dib
$ # Run the build image script, which will install DIB and start the build
$ ./build-image.sh

After a few minutes, the qcow2 image will be built and available in the same directory. You can then upload it to OpenStack using the glance CLI.

Trouble-shooting

If you get an error message saying that import yaml fails (seems to happen only on Ubuntu):

dib-run-parts Thu Jul 2 09:27:50 PDT 2015 Running /tmp/image.ewtpa5DW/hooks/extra-data.d/99-squash-package-install

"/tmp/image.ewtpa5DW/hooks/extra-data.d/../bin/package-installs-squash",
line 26, in <module>
     import yaml
ImportError: No module named yaml

You need to comment out the secure_path option in your /etc/sudoers file (use "sudo visudo" to edit that file):

#Defaults   secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"