diff options
author | Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com> | 2015-10-02 10:18:17 +0200 |
---|---|---|
committer | Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com> | 2015-10-14 16:19:20 +0200 |
commit | d03858bbac357b6d705c7137d2d20d5c8e34ecc6 (patch) | |
tree | 729aa5b9665120c4c836557b2eb67d4d48229031 /ci/run_tasks.sh | |
parent | 882af7878ab8119fede93a215c9e402023f817be (diff) |
Docker container for Yardstick CI
The Docker container is intended to be run by the CI pipeline but it
may also be used stand alone.
Building the docker image:
$ cd yardstick/ci/docker
$ make clean && make
Pushing image to docker hub:
$ docker login ... (credentials needed)
$ docker push opnfv/yardstick-ci (need to connect your account to opnfv)
The docker image must be manually built and pushed to the docker Hub.
This will probably be handled by gerrit triggers in the
future (including revision handling and tagging of images).
Example invocation:
docker run \
--privileged=true \
-t \
-e "INSTALLER_TYPE=fuel" \
-e "INSTALLER_IP=10.20.0.2" \
-e YARDSTICK_BRANCH="refs/changes/01/2201/7" \
-e RELENG_BRANCH="master" \
opnfv/yardstick-ci \
run_benchmarks
Basic steps performed by the container:
1. clone yardstick and releng repos
2 setup OS credentials (releng scripts)
3. install yardstick and dependencies
4. build yardstick cloud image and upload it to glance
5. upload cirros-0.3.3 cloud image to glance
6. run yardstick test scenarios
If anything goes wrong in any of the steps above a non-zero exit
status is returned.
Some limitations:
Scenario results (yardstick.out) are currently discarded. A future
patch will take care of dumping the result to a database.
Currently the container only runs the ping sample scenario. Testsuite
execution (and selection) will be added in a future patch.
The container has only been tested against fuel installations.
Change-Id: I0bd29035082d3e283429c7392de8fc11b9fd777f
JIRA: YARDSTICK-136
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
Diffstat (limited to 'ci/run_tasks.sh')
-rw-r--r-- | ci/run_tasks.sh | 43 |
1 files changed, 0 insertions, 43 deletions
diff --git a/ci/run_tasks.sh b/ci/run_tasks.sh deleted file mode 100644 index 27ccb3a3c..000000000 --- a/ci/run_tasks.sh +++ /dev/null @@ -1,43 +0,0 @@ -#!/bin/bash - -############################################################################## -# Copyright (c) 2015 Ericsson AB and others. -# -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Apache License, Version 2.0 -# which accompanies this distribution, and is available at -# http://www.apache.org/licenses/LICENSE-2.0 -############################################################################## - -# Run yardstick tasks back-to-back -# This script is called from yardstick-{pod} job and decides which tasks -# are executed as part of that job. - - -# verify that virtual environment is activated -# assumes the virtual environment has been created as described in README.rst -if [[ ! $(which python | grep venv) ]]; then - echo "Unable to activate venv...Exiting" - exit 1 -fi - -EXIT_CODE=0 - -# Define tasks to be run -TASK_FILE_NAMES[0]='samples/ping.yaml' -TASK_FILE_NAMES[1]='samples/iperf3.yaml' -TASK_FILE_NAMES[2]='samples/pktgen.yaml' -TASK_FILE_NAMES[3]='samples/fio.yaml' - -# Execute tasks -for TASK_FILE in ${TASK_FILE_NAMES[@]} -do - echo "Executing task from file: $TASK_FILE" - yardstick -d task start $TASK_FILE - - if [ $? -ne 0 ]; then - EXIT_CODE=1 - fi -done - -exit $EXIT_CODE
\ No newline at end of file |