Age | Commit message (Collapse) | Author | Files | Lines |
|
Project: yardstick e6277570188829687b2ecf48adbd10bc3c9d46bd
Add test case description and task file for TC049
JIRA: YARDSTICK-295
Change-Id: I9c13bee1bb986f515f4bc41e4455176240e2f19d
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Project: yardstick 086bd65535027be14a23b4296539900b0220c1b6
Add test case description and task file for TC048
JIRA: YARDSTICK-294
Change-Id: Ie6a9271a4cbc81bce47f7f59e609b90a9de1e909
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Project: yardstick bd67f539aa7ad9a659b7d945942e1eeda96c45d7
Add test case description and task file for TC047
JIRA: YARDSTICK-293
Change-Id: I23a0e78a297cdc5742fa8d1234e6f271e076f359
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Project: yardstick 0f1b872b3bbff6e0f2c8d56f3037064206dd068d
Add test case description and task file for TC046
JIRA: YARDSTICK-292
Change-Id: I552c8357bd9378bea70a12872497d09711c91eef
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Project: yardstick e416cdd3339ca283216e7af9a162641534360e52
bugfix:fix all generic test cases in grafana
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>
|
|
Project: yardstick 55e2e867e9a3f01b39f619251253470948e250d4
Update README in fuel plugin
Change-Id: Ice5e394ebdd734b10833b90e84427601fec173ad
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Project: yardstick cd9d1296ab33b0193bfd37e77241291065d9a06b
Update fuel plugin
1. update fuel plugin builder
2. change install directory in yardstick plugin
Change-Id: Ice560955bb659ca86476b9dd02b3028b853ac01c
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
Project: yardstick 567694e4db2d0776db6c115b98f54a4737e52124
Creating Director and related codes.
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>
|
|
Project: yardstick de26decf97c64b4a9a624d0acbf3882af4916f39
Bug fix:change pod name and extend graph duration
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>
|
|
Project: yardstick f5acf5d40684080f1633a3c4eafebfe5e6ab69b1
bug fix for huawei-pod2
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>
|
|
Project: yardstick 55af4f473d60838b57b14670423717b7f2e901ea
Enhence CPUload scenario
Enhence CPUload to measure maximum, minimum and average CPU usage.
Change-Id: I22d5e56a120ef6bb6ab93094bb053d9999173b32
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Project: yardstick 65d32056b14f5f34c2aba186f7ccb3e34c67a9a5
Creating result checker classes
JIRA: YARDSTICK-276
Change-Id: I63c4f2c36108e95f5d3b7da42e66cb8c9b16c817
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
Project: yardstick 7b2923df78a0820df9e968ae1909d838c07ebd83
vsperf: Initial integration with VSPERF
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>
|
|
Project: yardstick 3cf1c2162d800e4f5a5596bdf54732ba906c95f6
Add Yardstick TC044 TEST CASE
JIRA:yardstick-290
Change-Id: I2537f6561221226cf8961a2f8221f039cecf7fe0
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Project: yardstick 609e6ea459afc1aff901ecb1cd38c403ef8f8c13
Add test case description and task file for TC045
JIRA: YARDSTICK-291
Change-Id: I85081c075fb795ee7839009952e49ad13b9cf2bf
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Project: yardstick 4d78a2c02653f4918b55e0becad9094518e1afc3
Add fuel test suite
This file is used for verifing yardstick in fuel integration.
Change-Id: Ied9f714763f974af5a3abd953f66c966f196c4ec
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Project: yardstick e112b517bdca5f685dd250b9b0a7f6a18f4fb6f8
Add zte-pod1 info in Yardstick test cases Grafana page.
Change-Id: Ifdfe75c8168f7d5b9d5ec90880237864200ed4cf
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Project: yardstick 991aaea442d2a36d43871224a7d96a7e7eea6910
fix the ssh bug when run tc043 in CI
Change-Id: I93ffe038ee128976db001e4f2ece79366aa3826c
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Project: yardstick eacef205efa9289bccbf38d82df07cdc63486d35
Creating a generic opertion
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>
|
|
Project: yardstick 51b902b9d9d7a641357dd615dcd5a5529bffc8bb
Add Yardstick TC004 TEST CASE
JIRA:yardstick-14
Change-Id: I9ff76265db4677298bf60358a5259f3fb48f24a0
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Project: yardstick 12f7ee47f39091be7b139f9bc083dbc675099937
SFC Yardstick test
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>
|
|
Project: yardstick 588631b53537b71330bd21e4f9aebb9de429b2a3
Creating a generic monitor
JIRA: YARDSTICK-274
Change-Id: Iac8c525b36b2778767177b17e6107866cc514e40
Signed-off-by: lihuan <lihuansse@tongji.edu.cn>
|
|
Project: yardstick d51cbf72b8fb2e5c6acc06248919b1401d09c853
Add support for multiple VMs
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>
|
|
Project: yardstick 14c7413448e4690fefd0ecad908ec86d6f774d6f
Add plugin Command
Change-Id: I8976ddf3dd43813ee38051dc4b0030265b85c3ef
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Project: yardstick bad1fedef56b1dc5f526c29a5bdc508f7bedf1f4
Add zte-pod1 in Yardstick-Main
Change-Id: Ib014d1e86fbe4e789d9a803b0f4cf03e40fa988f
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Project: yardstick d7aca2eadc53a1e1dbf7c7c29f2a83e7e5085b0c
fix ssh bug when running tc043 on huawei_pod1
Change-Id: I333122dae5c00da3ad9fa495e0ca9e8f5d23ae4f
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Project: yardstick 41dde94d0a4e575317c297e124ba0624e64c8552
Change floating ip association method
Change-Id: I694fbce4470a14893310334a39e15b61fbe8905a
Signed-off-by: Akos Farago <akos.farago@ericsson.com>
|
|
Fuel@OPNFV just added the Yardstick plugin.
This plugin is a little different, instead of breaking fuel plugin
code apart from the contents (i.e. fuel-plugin-yardstick separate
from yardstick itself), it holds both fuel plugin metadata and
actual yardstick code in the same repo.
So far, yardstick plugin code itself is arch-independant and should
not be touched.
TODO:
- add yardstick patches for arm64 until we can validate Yardstick;
- submit patches added locally in Armband to upstream
(Yardstick@OPNFV);
Change-Id: I24bc8858b92c9bdd529a64de833d7b98c06a6ade
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|