User Tools

Site Tools


functest_docker

This is an old revision of the document!


Functest within a Docker

This is the unofficial procedure to run Functest within a docker.


Prerequisite

Some of the Functest tools need to have access to the OpenStack management network of the controllers.

For more info: https://ask.openstack.org/en/question/68144/keystone-unable-to-use-the-public-endpoint/

For this reason and besides the public network, you need to configure an interface on the management network as well in your jumphost (or wherever you want to deploy the Functest docker to run the tests).

Example:

The OPNFV Fuel installation uses VLAN tagged 300 and subnet 192.168.1.0/24 as Openstack Management network.
Supposing that eth1 is the physical interface with access to that subnet: 
$ ip link add name eth1.300 link eth1 type vlan id 300
$ ip link set eth1.300 up
$ ip addr add 192.168.1.66/24 dev eth1.300

After doing this, try to ping one of the controllers and make sure it works, otherwise the Rally installation will fail.

Docker Installation

  • Install Docker on the server you want the tests from (example for Ubuntu):
$ curl -sSL https://get.docker.com/ | sh

Ubuntu: https://docs.docker.com/installation/ubuntulinux/

RHEL: https://docs.docker.com/installation/rhel/


  • Add your user to docker group to be able to run commands without sudo:
$ sudo usermod -aG docker <your_user>

Manual procedure

  • Pull the Functest Docker image from the hub:
$ docker pull opnfv/functest

  • Check that the image is available:
$ docker images

  • Run the docker container giving the environment variables
    • INSTALLER_TYPE. Possible values are "fuel" or "foreman".
    • INSTALLER_IP. Usually "10.20.0.2" for fuel and "172.30.10.73" foreman.
$ docker run -ti -e "INSTALLER_TYPE=fuel" -e "INSTALLER_IP=10.20.0.2" opnfv/functest

Now, you are inside the docker container.


  • Run the script to install functest environment and start the tests.
$ {repos_dir}/functest/docker/start.sh

NOTE: This will run ALL the tests we have for SR1:

  • vPing test case
  • ODL suite
  • Rally benchmark (this will take long) ←– need to change something to run only 1 set of tests and not all (see * below)
  • Tempest


* In order to run only 1 suite of Rally bench, you need to modify the call to rally within start.sh script:

$ vi {repos_dir}/functest/docker/start.sh
(go to line 126)
python ${FUNCTEST_REPO_DIR}/testcases/VIM/OpenStack/CI/libraries/run_rally.py --debug ${FUNCTEST_REPO_DIR}/ all
Change "all" to "keystone" for example:
python ${FUNCTEST_REPO_DIR}/testcases/VIM/OpenStack/CI/libraries/run_rally.py --debug ${FUNCTEST_REPO_DIR}/ glance
Other options are:
- ['authenticate', 'glance', 'cinder', 'heat', 'keystone', 'neutron', 'nova', 'quotas', 'requests', 'vm', 'tempest', 'all', 'smoke']

Automated procedure

# Remove any docker containers leftovers
$ docker ps | grep opnfv/functest | awk '{print $1}' | xargs docker stop &>/dev/null
$ docker ps -a | grep opnfv/functest | awk '{print $1}' | xargs docker rm &>/dev/null
$ docker images | grep opnfv/functest | awk '{print $3}' | xargs docker rmi &>/dev/null

# Pull and store fresh image from Dockerhub
$ docker pull opnfv/functest

# Run Functest (example for Fuel)
$ docker run -t -e "INSTALLER_TYPE=fuel" -e "INSTALLER_IP=10.20.0.2" opnfv/functest \
 "/home/opnfv/repos/functest/docker/start.sh"

NOTE: the output will be shown on the screen until you press ^C. To attach to the docker output again type:

$ docker ps
$ docker attach <ID_of_the_container>

Docker Demo summits

# Pull the demo image
$ docker pull jlausuch/functest-demo

# Run Functest using a specific script (not start.sh)
$ docker run -t -e "INSTALLER_TYPE=fuel" -e "INSTALLER_IP=10.20.0.2" opnfv/functest \
 "/home/opnfv/repos/functest/docker/demo.sh"
functest_docker.1444316621.txt.gz · Last modified: 2015/10/08 15:03 by Jose Lausuch