aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/Yardstick-TC012-1456495966540
diff options
context:
space:
mode:
authorMartin Klozik <martinx.klozik@intel.com>2016-06-28 12:46:04 +0100
committerMartin Klozik <martinx.klozik@intel.com>2016-07-01 11:33:57 +0100
commit415af13357318f6c3328ea13953a0369fb27a147 (patch)
tree7bb7ddc9a7d46a54f242434b84f9c87fb5f850bb /dashboard/Yardstick-TC012-1456495966540
parent8a4f8df64b8897bf38e77399099099f92266048b (diff)
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>
Diffstat (limited to 'dashboard/Yardstick-TC012-1456495966540')
0 files changed, 0 insertions, 0 deletions