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-103
Add random key generation in fixed directory path.
Changes:
1. Add random key generation method
2. Add logic to cleanup the used key
Change-Id: I405d1d670422b9381879d0e58cb9c9fc1370f954
Signed-off-by: Yang (Gabriel) Yu <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>
|
|
Change-Id: Id91a4d743f7e94b962db4cc50b125700049e311a
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: Ic8731de1f9c62465a28225df4dd5b4b079cb6f49
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-71
Change-Id: Ie7ec366f4bf759b59431397e81f5bd2fb31bc0cf
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-47
the run_vstf.py file will be completed later which mainly focuses on instances creation
and vstf configuration info for each testcase, the configuration info for each testcase in define under
/vstf/testcase_cfg directory
Change-Id: I2dc5615e2f377202fadaf351ac9d31ec93d8598a
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I84483b323e17092b2025b8d0340e695207707600
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I452107e21294333c4d6624675232158ca4462aff
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: Ib9af1e9fbc09288f1eeb3800eef401490ff215d1
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I1215c6ecc9642bb2e4d433276fc3f6941e775e0b
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-46
Change-Id: I652460595e024877744f9ce7399a0a50a9fa75f7
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-46
1)add .py file for test suite running entrance and .yaml config files
2)adjust the project test running scripts to top directory
Change-Id: Iad9eedf704e85a8c7e974310938a7d652d008469
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-56
Change-Id: Ic9acad5eaa4917093bdb85a80960f796f5b4ba7f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|