| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- Renamed docker image 'opnfv/yardstick-ci' -> 'opnfv/yardstick'
as recommended by project.
- Added cirros image and releng repo to docker image in order to
make it more usable in offline mode.
- Renamed run_benchmarks to run_tests.sh
- Moved some environment setups to a new file prepare_env.sh
- Added daily test suites file for ericsson and LF pods.
Docker image is now built and pushed by releng script:
https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/opnfv/opnfv-docker.sh
The ci/docker/Makefile file is not used by releng to build yardstick
image but the makefile can still be used to build and test docker
images locally.
Change-Id: If9d6740b39e91d145c587d8d5e2bd372d09a46a9
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Added test suit selection and an option to use
the HTTP Result API.
Part 1: https://gerrit.opnfv.org/gerrit/#/c/2201/
Change-Id: I1c25d07e46cd44e25f448706ff2dfc3b31cd7208
JIRA:-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
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>
|
Jo¶rgen Karlsson