Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Icfbed0433cb9cfb6f8f479fc69699d08ad49602b
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
- reduce progress verbosity when downloading with wget
- added some debug printouts for trouble shooting
mount issues
Change-Id: Ic608f847b0fe74df231ce3d7d419dcf6c19807ed
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Add more debug output and clear devmap table in order to
solve build problems in YARDSTICK-226.
Change-Id: Idfdbb925501c8debb67406f2dd316e1d4bfbaaa8
JIRA: YARDSTICK-226
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Fixes a problem with loopback devices not
beeing detached when the image build fails.
Change-Id: I3e422be4fb0157289a032c14700e184f58d544d9
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Fixes two issues in the chrooted environment:
- /proc must be mounted when installing certain packages.
- prevent services from starting when installing or updating
packages.
JIRA :-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
Change-Id: Ia7180c190bf93c173ea93207ed323ca96662c029
|
|
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>
|
|
This is a workaround for building on CentOS.
CentOS don't have nbd so guestfstool is used to mount the
ubuntu image.
The http sources has been changed to ftp as the apt-get
tool inside the Ubuntu image dont work well with http
sources when running on CentOS.
Change-Id: I23679ff034ea76782dcc73d3283cb70ebace5ee8
JIRA: YARDSTICK-136
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Two scripts are added. One that will be installed in user's PATH
and one that is an example of how to modify an image from within.
See README for example and script for more info
Change-Id: Iab743f6e9105d5ba872ffba0512ffee954c6d830
JIRA: YARDSTICK-28
Signed-off-by: Hans Feldt <hans.feldt@ericsson.com>
|