Age | Commit message (Collapse) | Author | Files | Lines |
|
update the pod name and scenario name, and extend the duration of graph
JIRA:-
Change-Id: Ic611dc8d49e666433c2191c4098d56d95d40f1af
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
|
|
|
|
1. update fuel plugin builder
2. change install directory in yardstick plugin
Change-Id: Ice560955bb659ca86476b9dd02b3028b853ac01c
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Because there were some change with community pod name.
We need to change it with new pod name so that all the result
could be shown in the grafana
JIRA:-
Change-Id: I584294a5ead4337160c1ce2fcca8a53901f03a07
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Since TC027 depends on specific pod configure,
so it only should be run at huawei-pod1
JIRA:-
Change-Id: Ib85daae64ce97cad907dbaa8309c80cf4f0153b5
Signed-off-by: kubi <jean.gaoliang@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-291
Change-Id: I85081c075fb795ee7839009952e49ad13b9cf2bf
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
JIRA: YARDSTICK-276
Change-Id: I63c4f2c36108e95f5d3b7da42e66cb8c9b16c817
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
JIRA:yardstick-290
Change-Id: I2537f6561221226cf8961a2f8221f039cecf7fe0
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: Ifdfe75c8168f7d5b9d5ec90880237864200ed4cf
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
This file is used for verifing yardstick in fuel integration.
Change-Id: Ied9f714763f974af5a3abd953f66c966f196c4ec
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: I93ffe038ee128976db001e4f2ece79366aa3826c
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
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>
|
|
|
|
JIRA:yardstick-14
Change-Id: I9ff76265db4677298bf60358a5259f3fb48f24a0
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
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: I333122dae5c00da3ad9fa495e0ca9e8f5d23ae4f
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Change-Id: Ib014d1e86fbe4e789d9a803b0f4cf03e40fa988f
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.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>
|
|
1. fuel can deploy yardstick
2. todo: fuel run yardstick
Change-Id: If1a4b178187d78bdc2d4c3b6469faff78dc51ead
Signed-off-by: Chou, David J <david.j.chou@intel.com>
Signed-off-by: Hinman, John <john.hinman@intel.com>
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Change-Id: Ifcbb93f517063d3144f3ea4d7772071d62826e9c
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
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-176
Change-Id: I16ae136700334e95a1edcda6a46208ca21c19951
Signed-off-by: kbbrodz <konrad.b.brodzik@intel.com>
|
|
JIRA: YARDSTICK-279
Change-Id: I70accc9a79b59447c907057c386f14f6a4f38346
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I694fbce4470a14893310334a39e15b61fbe8905a
Signed-off-by: Akos Farago <akos.farago@ericsson.com>
|