Age | Commit message (Collapse) | Author | Files | Lines |
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: I0554d0a211392902207ba9ceccf0b98dc3c2cdf1
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Change-Id: Id557b5ef4d686da041b8097e390c7e5b563a0c3c
JIRA:-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Ibbba1d9864e788fb6c81cc00c503e9f69e885651
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Ifa2555336098e68d0fad8045e2f759aed587ad92
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Test case yaml and .rst file for ipv6
Change-Id: Ib9a554dc05445023687efb0ac608c7cbd0da4c21
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
run unixbench to get the score of processing performance
This patch includes the .yaml for the test case and the .rst for test case description.
JIRA:YARDSTICK-116
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: Ic75119d1db19dacc57edfa4dce607e0e29ae8db4
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Iabde8fa63f346cf1e4a02691f22d1761de79a239
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
running Parser Yang-to-Tosca module as a tool, validating output against expected outcome.
this patch is about task yaml and rst for test case description.
JIRA:YARDSTICK-224
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: Id254c5cf45de33b023bef889a58044a21ed0db43
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Change-Id: I299eb5a94afb8a29dee89938ff1d7b1bb7f43f3b
JIRA:-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
JIRA: YARDSTICK-93
Change-Id: I74adef0e6bae52a7080479d7054a92342f7324a7
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
JIRA: YARDSTICK-122
Change-Id: I8144215059a9abea08314a4c1e6a733dcdf0df53
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
1) add "attacker_baremetal.py" for fault injection
2) modify the monitor to excute on remote node after ssh connection
3) move all shell scripts together
JIRA: YARDSTICK-182
Change-Id: Ibb9dc908224ddb8b99a0140b75c1a046503f6dfb
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
idea: refact the Monitor class in old file "monitor.py" with the base
class and sub-class.
detail:
1) the BaseMonitor is the base class of other monitor
2) each monitor run in independent process
3) there are two monitor("openstack-cmd" and "process") for the first test case
4) MonitorMgr class used to manager monitor process
JIRA: YARDSTICK-149
Change-Id: I2eede94481f740812212e6cb673d175b5f543c15
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
with jnon and fatih's help, new docker image has been uploaded
so this part is about parser verify
validating output against expected outcome.
Change-Id: If50d241a5338888f14fd11a752dc72678e0c569b
JIRA:YARDSTICK-224
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
JIRA: YARDSTICK-213
Change-Id: I55ff36b02a0d0e0334505d68d361b8a14d36063c
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
JIRA:YARDSTICK-187
Change-Id: I1cecd400b4449a09d22d43f4a42e889f00dd4fe7
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
JIRA: YARDSTICK-214
Change-Id: I3a2358e8c36755a684f09524bd6fc8af9bf43f60
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
JIRA: YARDSTICK-213
Change-Id: I3f1f521da6a824c96cbc8712a098c61ff6b0540d
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
- add runner_id tag
- add test case name tag
- add task_id tag
JIRA: YARDSTICK-212
Change-Id: I75c27e23942a6e2189019e94bfe8026a5fd67621
Signed-off-by: QiLiang <liangqi1@huawei.com>
Conflicts:
yardstick/dispatcher/influxdb.py
|
|
Supports:
- Basic influxDB write with timestamp
- Add general result format func
- Add UT
TODO:
- refine database schema (e.g. add more tags) plan in another patch
JIRA: YARDSTICK-212
Change-Id: I1526568bbd850f1343135420ec59ed1b833bb99f
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
opnfv-jump-1: apex stable/brahmaputra branch
intel-pod5: joid stable/brahmaputra branch
intel-pod2: apex master branch
intel-pod6: joid master branch
intel-pod8: compass master branch
Change-Id: Ia659e10525863ee11854a266df58449c625c7f7c
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: yardstick-210
Change-Id: Ib888b654e742761a8be1b263f643950ea02380f8
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Dummy Context Usage:
- if no context specified in the task file then automatically use
Dummy Context
- or specify the context with type Dummy in the task file, like
context:
type: Dummy
Note: context without type name default use Heat Context.
(e.g. samples/fio.yaml)
JIRA: -
Change-Id: I7f798a7260bdd6ac24902e2c835a3b121319fd8c
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
JIRA:YARDSTICK-184
Change-Id: Iedd4a3708e08305b1c8fa7a8e1766ceef03ab8bb
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Add test case description for Memory Latency (TC010) and test case
.yaml task file.
JIRA: YARDSTICK-94
Change-Id: If7fb120868c9901fe097f310aa249e1fbc8a94ee
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
Change-Id: Ic0f7261dc07eb38d014a8790ac13e5310ec4ef8a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Similar to Yardstick TC001. Main difference is that each packet size
is run 10 times before next packet size.
JIRA: YARDSTICK-87
Change-Id: If0f59590dff9c8e5b86760667f01a373afe8aff0
|
|
New test case using pktgen tool. Based on TC001, but with additional
packet sizes and more repetitions of each test combination,
respectively. Test case takes approx.3 hours to complete.
Change-Id: Iba2de5efa33d6e2c960772fa5345595f6d7ab4e6
JIRA: YARDSTICK-80
|
|
refactor the attacker implement.
1) BaseAttacker is added
2) a simple attacker named "kill-process" inherit the BaseAttacker
3) serviceha.py selects an attacker through the BaseAttacker by attacker name
JIRA: YARDSTICK-149
Change-Id: Ib718d5edc6b5e14bc3ea0592e0146468ff70b43e
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
Change-Id: I39d589bfc0652d51b7e6d9e139b83160bf7f3692
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
This change adds the possibility to run scenarios as "background
tasks".
Background scenarios/tasks:
- are started before all "normal scenarios"
- runs in parallel with "normal scenarios"
- terminates when all "normal scenarios" have completed
their tasks
They are intended as a way to perform background tasks, e.g. collect
data such as cpuload etc, in parallel with the execution of normal
benchmarking scenarios.
Note that we already have the 'run_in_parallel' attribute but
this attribute has a couple of issues and do not solve all the
uses cases.
Change-Id: I9c5230bfdbbb66030f57b658ce1db87ff2c2d62b
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Add test case description for Memory Bandwidth (TC012) and test case
.yaml task file.
JIRA: YARDSTICK-113
Change-Id: I6f2b0bb8c920f3ece3a41bac744cc1ec1fd35cbc
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
This commit contains almost all of Jira #79. Misses still to collect
all results in one single .json file, now everything is written to
/tmp/yardstick.out. However, this may not be needed at all once the
database for test result collection is in place.
Change-Id: I210a477c3b5a110e97a6220e68d3ddc31ccce93a
JIRA: YARDSTICK-79
|
|
JIRA:YARDSTICK-
Change-Id: I6e43383c1eafa13314ab7678d0e1d42ed063c57f
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
|
|
Defining the 'nodes' attribute which can include more node
not only 'host' and 'target'
Design etherpad link:
https://etherpad.opnfv.org/p/yardstick_framework
JIRA:-
Change-Id: Ida18ebcda1c73c88d208aa11a10696d1063134ef
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
Change-Id: Ic4ee5d21f09fd324583f8a2c55e99684fbddd70b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
- 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>
|
|
This scenario reads processor and system load statistics
and does not run any benchmark tests.
The scenario is intended to be run in parallell with
other scenarios in order to collect processor and system
load statistics.
System load is read from /proc/loadavg.
Processor usage stats is read using the 'mpstat' utility if
it has been installed on the host.
If 'mpstat' is not installed on the host processor usage stats
is read from /proc/stats.
Change-Id: I7156e0c941100023571db750de7540786a4fedb8
JIRA: YARDSTICK-181
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
1)stop an openstack service
2)then monitor the corresponding api and check the availability of it
3)recovery the openstack service
JIRA: YARDSTICK-149
Change-Id: Id7b77d2f5c71844729c04f37442c8cfaa270ab12
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
Initial NodeContext implementation to support BareMetal,
Controller, Compute scenarios.
Usage:
0) install yardstick
1) mkdir -p /etc/yardstick/nodes
2) cp <yardstick_repo>/etc/yardstick/nodes/pod.yaml.sample \
/etc/yardstick/nodes/pod.yaml
3) edit /etc/yardstick/nodes/pod.yaml (make show ip, username,
ssh key are configured correctly)
4) yardstick -d task start \
<yardstick_repo>/samples/ping-node-context.yaml
5) cat /tmp/yardstick.out
Design etherpad link:
https://etherpad.opnfv.org/p/yardstick_framework
JIRA: YARDSTICK-169
Change-Id: I3f6ade8243e68d88326f23ed213edb32c638ed32
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
Lmbench scenario has now two scripts and will choose between them,
based on whether the intention is to run memory latency or bandwidth
tests. Added also unit test file for this scenario.
JIRA: YARDSTICK-113
Change-Id: I2ba4dbef31f3cafbdb3c583ece5ed9512a906896
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
Heat context code refactor to cater for the evolution of the
Yardstick framework.
Refactor runner_cfg host/target info handle, as specified at
https://etherpad.opnfv.org/p/yardstick_framework
step 4. Get general Context info (use Context.get).
Before this refactor host and target vm must have the same user name
and ssh key, that is not general enough for later extension.
test_case.yaml do NOT need to change.
JIRA: YARDSTICK-168
Change-Id: I5cfe868f3c6f633214ef550bc9676fe1de0709db
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
This patch modify the question that SLA check result is not complete.
JIRA: YARDSTICK-172
Change-Id: I10438390baee92caf00dbfcdbdb833823ff8ce31
Signed-off-by: houjingwen <houjingwen@huawei.com>
|
|
Heat context code refactor to cater for the evolution of the
Yardstick framework.
At test_case.yaml context segment add "type" to indicate the
context type, see samples/ping-heat-context.yaml for an example.
And the default context type is Heat, so the existing yaml file
do not need to change.
JIRA: YARDSTICK-168
Change-Id: Ida0ce12c17cd9b88d7acfb4c9eb1ac6986394b38
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
Support measuring operating system's high resolution by using Cyclictest.
JIRA: YARDSTICK-122
Change-Id: I2e00ce117e263deaaf52cd2d663b845bd5b65432
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
As agreed in the IRC meeting, use iperf for YARDSTICK-112;
support for netperf shall also be included in the framework (Yardstick-121).
bulk data test and req/rsp test are supportted by netperf
JIRA:YARDSTICK-121
Change-Id: I0e934dc067802c2792d751a19a187cd00ad8741b
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
|
|
This patch proposes a more permanent solution to replace the already
existing one (YARDSTICK-106).
A test suite is a .yaml file which consists of multiple task files which
are meant to run as a one set. Each test case in the test suite has to
specify the location of the test .yaml task file and can specify additional
task arguments or a task arguments file.
It is possible to specify the directory where the task files are located
in the suite file. If it is left unspecified then it defaults to
tests/opnfv/test_cases according to https://etherpad.opnfv.org/p/yardstick_folders
A Command line argument --suite is added to the task command. This
argument indicates that the intention is to run a test suite.
JIRA: YARDSTICK-107
Change-Id: I69508b3b536dd592b6240a2a32dd5d665e0ac4b4
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|