Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: BOTTLENECK-107
JIRA: BOTTLENECK-106
This patch has done the flowings:
1.Using the RESTful API form yardstick
2.Common function reuse.
3.If there is no test_ip it would use host ip and port as test_ip.
4.A little demo of dashboard. Now is can't work
Change-Id: I1063176c762c40238019c73f5359f23bc5aab19c
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-102
Modify all the code in the testcase POSCA into PEP8 style.
Using more standard way to realize our function.
Change-Id: Ic014678db454b8a36b36395c32b4769f6cf700be
Signed-off-by: liyin <liyin11@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
JIRA: BOTTLENECK-99
Add factor testcase to locate the bottleneck of tx pkt size.
A separated logic for determine if the tx pkt size is the system
bottleneck is provided.
Change-Id: I9ccbe19c88a72170b66fffd7f1bd7e5a45dbdc27
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-98
Add factor testcase for locating tx cache size bottleneck.
A separate logic for determine if the bottlenecks is tx cache
size is provided.
Change-Id: Ie3e8a79bf55d6b3223b45c52fb4fbc9b047d38cb
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-94
Add factor test to find the bottleneck of system bandwidth.
A separate logic is provided to determine what is throughput for
a deployed system.
Changes:
1. Add testcase script
2. Delete whitespaces
3. Logic fix
Change-Id: I37ab9d40d90c585191619d4753eca285fee64dd4
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-97
Add factor testcase to locate bottleneck for rx pkt size.
A separated logic for determine if the system bottleneck is
rx pkt size is provided.
Change-Id: I478b4cf94b07eeb56e87a4825ff0a62367c05175
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-96
Add factor testcase for locating bottleneck of rx cache size.
A separate logic is provided to deterine if it is the bottleneck
of rx cache size.
Change-Id: I52652f73c512a829a3dde85e4cb36073327773e8
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-95
Add cpu burden factor testcase to locate cpu bottlneck for system.
A separated logic is provided to determine if the bottleneck is the
CPU capability in the system.
Changes:
1. Add testcase script
2. Delete whitespaces
Change-Id: I37017d5a0378450b07286ba36f9976d92f504eeb
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-92
The POSCA (Parametric Bottlenecks Testing Catalogue) testsuite
classifies the bottlenecks test cases and results into 5 categories.
Then the results will be analyzed and decoupled bottlenecks will be
searched among these categories.
The POSCA testsuite aims to locate the bottlenecks in parmetric
manner and to decouple the bottlenecks regarding the deployment
requirements.
The POSCA testsuite provides an user friendly way to profile and
understand the E2E system behavior and deployment requirements.
Goals of the POSCA testsuite:
a) Automatically locate the bottlenecks in a iterative manner.
b) Automatically generate the testing report for bottlenecks in
different categories.
c) Implementing Automated Staging.
Scopes of the POSCA testsuite:
a) Modeling, Testing and Test Result analysis.
b) Parameters choosing and Algorithms
Test stories of the POSCA testsuite:
a) Factor test: base test cases that Feature test and Optimization
will be dependant on
b) Feature test: test cases for features/scenarios
c) Optimization test: test to tune the system parameter
For more details of the proposal, please refer to
https://jira.opnfv.org/secure/attachment/11479/
POSCA%20Testsuite%20Proposal%20in%20Bottlenecks.pdf
Changes:
1. Add Posca testsuite directories and files to Bottleneks,
leaving adding test cases for latter commits.
2. Fix file appd issue.
3. Delete the un-used packages in testsuites/posca/run_posca.py
4. Add testcase processing logic to run_posca.py
5. Add config dimensions
6. Add scripts directory
Change-Id: I54d9b51381a804b76a83680912227e058da3165e
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|