Age | Commit message (Collapse) | Author | Files | Lines |
|
Changes small things required for the integration of ApexLake with Yardstick
JIRA: YARDSTICK-35
Change-Id: I6f92d738cb80e34108b76f900382e9c05ecabe70
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Inludes the last files required by ApexLake for a complete execution.
JIRA: YARDSTICK-35
Change-Id: I4315b8081554c8fad98c8fa72f9e2796ecb9360b
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
JIRA:YARDSTICK-184
Change-Id: Iedd4a3708e08305b1c8fa7a8e1766ceef03ab8bb
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Include some other tests to reach the required coverage
JIRA: YARDSTICK-35
Change-Id: Ie47b0ca9451d4dcc0f5e31ba98f8c38923689475
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Includes benchmarking unit to run benchmarks in ApexLake
Also includes tests.
JIRA: YARDSTICK-35
Change-Id: I67c62efd6cbe0883963e8c4ddc86d003b1d355ac
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Includes the deployment unit module used for deployment by Apexlake
Also includes tests
JIRA: YARDSTICK-35
Change-Id: Ia5c89f3cd03d53b1fc4e418215955fd91aff9d03
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Add python module providing API for Yardstick to configure and execute
ApexLake and the test cases for the virtual Traffic Classifier.
Includes documentation.
JIRA: YARDSTICK-215
Change-Id: I87af59c715d789ac78c836123e9ed3d8e0036eec
Signed-off-by: Vincenzo Riccobene <vincenzo.m.riccobene@intel.com>
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Stop size parameter's type should be float to allow for performing
measurements on only L1 and L2 cache if needed.
JIRA: -
Change-Id: Ibc4d052c343e9dcccf6101c6c949172bb5a0f9e1
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
Two runners, Arithemic and Sequence, broke running tests
even if SLA "monitor" was set. Changed these two runners
to work in similar fashion as the other two, i.e. that only
None can break. "assert" still asserts, and "monitor"
just logs but then continues.
Change-Id: Ic441761cad8747e5ecfcd0babe719c1aa23981e7
JIRA: -
|
|
|
|
The Arithmetic runner is modified to accept several named
parameters to iterate over in each scenario. Possible to chose
either to iterate through them in a nested-for-loop fashion
(default) or in a tupled loop fashion (combine i:th element
of each input). Still possible to only provide one parameter
to step/iterate over, as before.
All existing yaml files with Arithmetic types have been modified
to run the tests as before, and to provide same results as before
this change. The only change is in sample file pktgen.yaml to
provide a valid example of how to use this modification.
It is also possible to step backwards, i.e. start > stop, with
a negative step parameter value.
(Noticed that tests are terminated when there is SLA error
problems in "monitor" mode. Should be fixed in another commit)
Change-Id: Ib2ebd24b71dd55d6817cee8e67026a0dd13a9e17
JIRA: -
|
|
Add utility tools and related tests to ApexLake
Fix also small things in all tests
JIRA: YARDSTICK-35
Change-Id: I76ab79b3b7ba3b48633517477b262f5bcdc743f0
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
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>
|
|
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 supporto to ApexLake for the test case to validate the vTC instantiation on OpenStack
JIRA: YARDSTICK-146
Change-Id: Ib154bac19ec1c32a508682235478a3c7fc530299
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Add support to ApexLake to the test case that validates the instantiation of the virtual Traffic Classifier within OpenStack
JIRA: YARDSTICK-145
Change-Id: I533712de36de4e40fdec15b2be2348fbb8c29dfc
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Add support to ApexLake for the calculation of the throughput of the vTC in case of
noisy neighbors deployment, through the DPDK pktgen.
JIRA: YARDSTICK-36
Change-Id: I00950f967cac1f12f733a05af8166c757dc02e0a
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Add to ApexLake the support to the calculation of the throughput for the vTC using DPDK pktgen.
JIRA: YARDSTICK-35
Change-Id: I2ead9522648d6955f64fd18c543dabf7f26e2490
Signed-off-by: Vincenzo Riccobene <vincenzo.m.riccobene@intel.com>
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
JIRA: YARDSTICK-35
Change-Id: I8cb5c05a0d33aac2bc90aa037843db67d2ab0e36
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Inlcude a LUA script that generates constant rate traffic for DPDK pktgen
Also include PCAP files of requested size (64, 128, 256, 512, 1024, 1280, 1518)
JIRA: YARDSTICK-35
Change-Id: I25c1a6a8763bd14fdf25450619a5e5bbd8e978db
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.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>
|
|
Add packet generator base class (to support extensions of packet generators
Add the DPDK packet gen python wrapper and tests
JIRA: YARDSTICK-35
Change-Id: I2072801bcf077586b6abb45c5d452a346e2efe70
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Adds to ApexLake a module that manages the connection with OpenStack Heat to trigger instantiation and termination of stacks.
Also Moves tests and bin directory in the right place.
JIRA: YARDSTICK-35
Change-Id: I0ea407a3129625a238fb4187896c65a2bcd02700
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
Fix for the validation error on port.properties.network
when deploying using OS Kilo or later.
Change-Id: I761cc958573d6eb8c909a08f186486f3ac93e816
JIRA: -
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>
|
|
Adds to ApexLake the script to run the tests for the python modules of the project (they will be added later on).
It also adds the tests for heat template generation
JIRA: YARDSTICK-35
Change-Id: I3c7fcfe044b33130dd6a5d1285f3d6522eac58c6
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
|
|
|
|
Adds to ApexLake the support to the generation of the all the possible configurations and related heat templates.
Files containing constants have been added as well to support the module. They will also be useful for other modules of the framework.
JIRA: YARDSTICK-35
Change-Id: I9d33d5b11c586d40dbff199c21e428113bf3cdeb
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.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>
|
|
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>
|
|
|
|
In ping.py:
If ping a ip address timeout, the return value "stdout"
is null. And the code "rtt=float(stdout)" raises a
ValueError exception. The better handle is to avoid the
exception and log a ping timeout.
Change-Id: Ia2a3ff44c35dda1a700a5109f8e642a636e89bc6
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
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>
|
|
total time and one task time both will be put into console
JIRA:YARDSTICK-166
Change-Id: I1422355c5ca0228c11e6334c13bb13554bdca4af
Signed-off-by: kubi <jean.gaoliang@huawei.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>
|
|
First commit for ApexLake: the vTC Characterization Framework
The included file is a lua script for the calculation of the throughput for dpdk_pktgen
JIRA: YARDSTICK-35
Change-Id: I02d015cee5f6b0593d668498439893f9091f5a8b
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.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>
|
|
Execute a sample task file from Yardstick, push the test results
to MongodB provided by Releng using the common result api
provided by Functest.
Usage:
0) install yardstick
1) config yardstick
mkdir /etc/yardstick
cat << EOF >> /etc/yardstick/yardstick.conf
[DEFAULT]
debug = True
dispatcher = http
[dispatcher_http]
timeout = 5
target = http://213.77.62.197/results
EOF
2) run test
yardstick task start sample/fio.yaml
3) fetch result from remote result_collection_api
curl "http://213.77.62.197/results?case=Fio&installer=compass"
JIRA: YARDSTICK-132
Change-Id: I0996c6487c1900704380feb895555057a3f184e9
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
JIRA:YARDSTICK-100
Change-Id: I1986b5e443abf186ef9c0235b66ada26c8574af1
Signed-off-by: wym_libra <yimin.wang@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>
|
|
|
|
Use openstack library oslo_config for parsing configuration options
from the command line and configuration files.
Refer http://docs.openstack.org/developer/oslo.config/ or rally
source code for more info on oslo_config library usage.
This patch is initially for test result dispatcher configuration,
but it is very general to use.
Usage:
0) install yardstick
1) mkdir /etc/yardstick
2) cp <repo_root_dir>/etc/yardstick/yardstick.conf.sample \
/etc/yardstick/yardstick.conf
3) edit /etc/yardstick/yardstick.conf
4) run `yardstick task start xxx` cmd
JIRA: YARDSTICK-61
Change-Id: I01677ef6e9ab7c1975aa193799195e850da73478
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>
|
|
JIRA: YARDSTICK-34
Change-Id: I782ba5845f8bd54a19bad078fe7be546400f7524
Signed-off-by: houjingwen <houjingwen@huawei.com>
|
|
JIRA:YARDSTICK-160
Change-Id: I2cfe91b30d0c906417234d5bf7787fb5dc568921
Signed-off-by: jean.gaoliang@huawei.com <jean.gaoliang@huawei.com>
|