Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Change-Id: I38455fd42afaa965612edfaa46e385c7934ff7e7
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-272
Change-Id: Icf41642fe0c31584f92c68cc9f97fa3f1e90b66e
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
|
|
suite.yaml has constraint and task_args parameter, so
each task_case can be able to add constaints (currently
support pod_name and installer), also support parameters
to be replace for special test case like tc043.
JIRA: YARDSTICK-299
Change-Id: I2b2c8f9858893da03aaa8bcac20a474a2d434509
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
This scenario reads network interface utilization stats and data sent/receive
rate using "sar -n".
Change-Id: I9c69f03c017bc2f8a5d87a4de286af147e8a086a
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
Adjust target node key name.
Signed-off-by: JingLu5 <lvjing5@huawei.com>
Change-Id: I5daee8c2579aa1f14aac076c49803eb8b5029a97
|
|
JIRA: YARDSTICK-272
Change-Id: Id2f1b3d1beff8843700cdfcaaa1e8f496f445ed9
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
|
|
There was a bug in how the mock was created and a new unit test is added
in order to cover the "else" of the if conditions
Change-Id: I3c8dfcd81240cb93ecdec1f63f7974f5342947c0
Signed-off-by: Manuel Buil <manuel.buil@ericsson.com>
|
|
1. first need to change in yardstick
2. then change in releng to modify the input parameter
JIRA: YARDSTICK-299
Change-Id: I3d707721acbc1d63be34da4e98138f845dc93466
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-256
Change-Id: I48d66081dcfabf4462ef1ff15c9a3ad28132aaf9
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Add a new scenario type 'ScenarioGeneral' that support orchestrating general HA test scenarios.
Director, ActionPlayer and RollbackPlayer are uesed to execute the test scenario (or test flow).
JIRA: YARDSTICK-288
Change-Id: Ied2ccd4712f3c3efde6771bfa4538c1e9e137c11
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
|
|
|
|
|
|
Enhence CPUload to measure maximum, minimum and average CPU usage.
Change-Id: I22d5e56a120ef6bb6ab93094bb053d9999173b32
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-276
Change-Id: I63c4f2c36108e95f5d3b7da42e66cb8c9b16c817
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
|
|
Operation class is used to do some work on the target system such as creating a VM instance.
JIRA: YARDSTICK-275
Change-Id: Ib62846824b74dcdae51f143bc59fba385cc7d84c
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
|
|
Modifications of the SFC Yardstick test
The test creates two chains. One chain blocks HTTP the other one blocks SSH.
We doublecheck that HTTP works in one but not in the other and the same for
SSH.
There are some things that must be modified manually as ODL is not yet ready
for ovs 2.5.90. Here are the instructions:
https://wiki.opnfv.org/display/sfc/Yardstick
Change-Id: Ide6588a682f3491ab58c47ee7335205868c109fc
Signed-off-by: Manuel Buil <manuel.buil@ericsson.com>
|
|
|
|
Verify and add support for multiple target VMs.
This is related to further work with SDNVPN project.
In the task configration file, use 'target' for specifying one target VM and use 'targets' for specifying multiple target VMs.
Change-Id: I682188ef4c2c2c012d5ab00417b69f5b31b87137
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
New scenario class allows to execute vsperf installed inside VM.
Vsperf is executed in trafficgen mode. It means, it will only
configure and execute traffic by external HW traffic generator
based on custom configuration file. After traffic generator stops,
then test results will be converted from vsperf CSV format into
JSON and passed to yardstick for further processing.
Currently, traffic is passed only through external bridge. In
the future, test scenarios will launch VNFs and traffic will
be properly routed to them. Proper routing can be ensured
by OVS flows configuration via setup-script executed during
setup phase.
Testcase definition yaml files inside vsperf/ directory won't be
pushed to the yardstick, but they will be stored inside vsperf
repository. They are part of the draft review only to show
how it is done.
JIRA: VSPERF-288
Change-Id: I13a519ed39091fe89d1a43cc522738044fb3c609
Signed-off-by: Martin Klozik <martinx.klozik@intel.com>
Reviewed-by: <sunshine.wang@huawei.com>
Reviewed-by: <lvjing5@huawei.com>
Reviewed-by: <jean.gaoliang@huawei.com>
Reviewed-by: <david.j.chou@intel.com>
|
|
JIRA: YARDSTICK-274
Change-Id: Iac8c525b36b2778767177b17e6107866cc514e40
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
|
|
Change-Id: I8976ddf3dd43813ee38051dc4b0030265b85c3ef
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-273
Change-Id: Id81b554b559d14ced440a1fa004d14d791fd2306
Signed-off-by: qiujuan <juan_qiu@tongji.edu.cn>
|
|
JIRA: YARDSTICK-271
This scenario reads hardware specification, including number of cpus, number of
cores, number of threads, available memory size and total cache size of a host.
Change-Id: Icb6c2e103f63fdd61be2461d25c1cf1f4115f161
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Unify tool install location
Change-Id: I45fc76a0631187136a2602d1a9c26f3df94ce9dd
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-267
This scenario reads system cache hit/miss ratio and other statistics using cachestat tool.
Change-Id: I601cb7e64d234571c0a0fd65a5e32604b3a617ec
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
JIRA: YARDSTICK-259
This scenario reads memory usage statistics on a Linux host.
memory usage statistics are read using the utility 'free'.
Signed-off-by: JingLu5 <lvjing5@huawei.com>
Change-Id: I677aa65ca264dc77a963bf8b6913a729fbf031be
|
|
JIRA: YARDSTICK-255
add RAMspeed scenario for measuring memory bandwidth.
Change-Id: Iba740d7fdb394d96f32ee824925bbbf8fb689614
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Using LMBench to measure latency of cache.
two parameter can be configured (repetition and warmup)
Change-Id: I5e4ecca0f9dd9c9ce2cecce3623dd8347ab2b5b1
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
"yardstick testcase show" will show the details of specific test case
yardstick testcase show <case-name> (e.g. yardstick testcase show opnfv_yardstick_tc001)
JIRA:-
Change-Id: Ibb91625dc3e6802855f28160ee0aa8c7e386cf7a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
"yardstick testcase list" will list test cases info(Name, Description)
in tests/OPNFV/test_cases/
Change-Id: Icf2e6a803d90d33012f009519e47e750bfd57489
JIRA:-
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
as we discussed yersterday, for daily jenkins task,
i have a new idea, i add a precondition check and a key parameter in test case,
if environment info(eg. "DEPLOY_SCENARIO") meet the preconditon which was defined in test case ,
this test case will run, if not meet, this test case will skip.
and default is allow all test case to run, so this patch will not influence existing test case.
any comments are welcomed
Change-Id: I4300ac58994d51c0ddb4dd6d58b7191f796ddcee
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Change-Id: Id4c8b1bc05e768bdb2b8f17798f13f4d83dcd9d6
Signed-off-by: Ricardo Noriega <ricardo.noriega.de.soto@ericsson.com>
|
|
JIRA:YARDSTICK-187
Change-Id: Ia15d17afdef145f7b230a8a4d25a61eed5cdfd76
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
In Heat Liberty release OS::Nova::Server will always use the user
pre-configured in the image (e.g. "fedora" for stock Fedora cloud
images, "ubuntu" for stock Ubuntu cloud images, "cloud-user" for
stock CentOS cloud images etc)
Change all ec2-user -> ubuntu
Add admin-user in Heat model for backwards compatibility.
Refer below links for detalis:
https://etherpad.opnfv.org/p/yardstick_release_b_troubleshooting
https://github.com/openstack/heat/commit/e423bec7f10b0f5d07f05d195b3b7860f6bceb00
http://blog.scottlowe.org/2015/04/23/ubuntu-openstack-heat-cloud-init/
JIRA: -
Change-Id: I6b8b2b21daf113a3a86aee1126b0c3e74737ef4f
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|