freezer/tests/scenario
eldar nugaev f66f4ada4e Pluggable storages
Implements blueprint: preparation-pluggable-storages

Change-Id: I044c533102ba31f1acd2c89ed2d0a70578d1b991
2015-06-26 15:08:08 +01:00
..
vagrant-scripts Incremental LVM functional test 2015-05-20 19:45:37 +00:00
README.txt Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
Vagrantfile Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
__init__.py Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
backup_scenario.py Pluggable storages 2015-06-26 15:08:08 +01:00
prepare-vagrant.sh Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
run-local.py Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
run-remote.sh Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00
swiftrc Windows support for freezer 2015-04-13 10:06:46 +01:00
swiftrc.sample Functional tests and Vagrant environment 2015-03-30 14:35:35 +01:00

README.txt

Freezer Scenario Functional Testing
====================================

The most straight forward way to set up the Freezer functional testing
environment is by utilizing VAGRANT. There is initial Vagrant file that
by default is setup to work with Virtualbox and Ubuntu 14.04 as virtual
machine OS.

In order to prepare your Vagrant + VirtualBox/KVM environment there is:

  $ ./prepare-vagrant.sh

The script is tested to work on Ubuntu and will automatically download
and deploy Vagrant, VirtualBox, KVM and libvrt as well as mutate Vagrant
plugins. It will also download a base Ubuntu 14.04 64bit Vagrant box and
use mutate plugin to deoplu a libvrt version for KVM use.

Before running 'vagrant up' for the first time make sure you have replaced
the 'P-R-O-X-Y' string (Vagrant file) with the correct HTTP proxy URL and
port if behind one e.g. P-R-O-X-Y => http://proxy.test.company.com:3344

To start the process of MV deployment run:

  $ vagrant destroy -f #This will delete any previosly deployed instances
  $ vagrant up #This kick starts the Devstack Swift VM that tests use

When process is done normalyy it take 10 - 20 min depends on your network.
You should have a fully configured Swift object storage VM that is
accessible on a host only IP e.g 10.199.199.199

Copy file swiftrc.sample to swiftrc and edited properly should you need to.

Next you need to decide weather you want to perform the integration tests
locally on your station or into the Vagrant VM. There are two scripts to
do just that:

   $ ./run-local.py
   $ ./run-remote.sh

The first of them will setup loopback LVM disk that your Freezer scenario
tests will need and mount it in /mnt.
The second will create the LVM disk in the Vagrant virtual machine and will
synchronize all Freezer files to the VM as well where it is going to trigger
the integration test.

Successful test run should look something similar to this:

............
test_lvm_level0 (backup_scenario.BackupScenarioFS) ... ok
test_no_lvm_level0 (backup_scenario.BackupScenarioFS) ... ok
test_utils_methods (backup_scenario.BackupScenarioFS) ... ok

----------------------------------------------------------------------
Ran 3 tests in 2.696s

OK