Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: YARDSTICK-363
Change-Id: Ic1f2ab98425512014d746a997b7356d3490c6b33
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-378
Change-Id: I527d4f60f2a2081730118bdbbea6c19fc093672f
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-369
Change-Id: I286e883d88a47d2befa4bb523ad9384937e079b3
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
JIRA: YARDSTICK-270
1)description info amended according to really tested
2)hyper-thread status check added
Change-Id: I813a41ff1e55c2d816fa55b773cf6c4bdd2af2bd
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: YARDSTICK-315
1) make packetsize workable
2) add ping_count parameter
Change-Id: Ice2235fc5744b94df6a3f981c23159ca8280d876
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: YARDSTICK-319
Change-Id: I25ee9a2582c751024b30e91eabf77aebb14a02f7
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
VM A runs pktgen-dpdk as a traffic generator and is connected
back-to-back with VM B running testpmd for forwarding packets.
1. use linux expect to fetch the latency statics data.
2. fetch 10 samples of latency and calculate avg_latency.
3. use screen to keep test scripts running in the background.
4. add a function send_command() for screen in ssh.py
JIRA:YARDSTICK-233
Change-Id: I90ae64b3d198c79f159275ae35715eb284f05080
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
grafana dashboard
Change-Id: I255586efb0d1e25d7505838693d90a40282249b4
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
two metrics:Number of Connection, Number of Frame
JIRA:YARDSTICK-283
Change-Id: I71f1de25667437bbeac7c06749ff8fb38f41a791
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
It measures disk size, block size and disk utilization.
JIRA: YARDSTICK-284
Change-Id: I61b3fb8a35da41c77450c157f843fb853d77dddd
Signed-off-by: wangyaoguang <sunshine.wang@huawei.com>
|
|
Change-Id: I34a44111078efe50b1dbbaddda72474d25aafe43
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
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>
|
|
|