Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: BOTTLENECK-115
This patch add some debug info to screen.
so test situation will be displayed to every one.
And it's could be easier to understand
Change-Id: Iecf767eedf42825a13dae59235ab99d1767e744e
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-114
this patch fix a problem that docker can't run
because of lacking pyroute2.
the way to solve it is add return value judgement to avoid circle
return value error, is return relue when get into circle function
Change-Id: I3af9abdb417abc5cf04c0e4db7eed576222bb1ea
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-113
this patch fix a problem that docker can't run
because of lacking pyroute2.
the next is docker-compose file have some error that yardstick can't
pull inluxdb container.
the next is fix some bug incode.
Change-Id: I238b69b456d2810e84bae5c134e6b05a8fc5da63
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-111
This patch add two functions to bottlenecks project:
1.change yardstick urls and some return value.
2.bottlenecks project wait time change.
Change-Id: I1a7f98f69676cda8cb0dc62276704c2cfcf240d8
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-110
This patch support bottlenecks testsuites posca support use yardstick
rest api to pull InfluxDB container.
the yardstick use this container to store its test result.
Change-Id: I6ad6b5d7a9748c385787567b3d6d1dfe4cee167f
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-109
this patch provide a dashboard of system_bandwidth test case
when the test over this script would be run.
and you could login host:5601 to see the view of dashboard.
Change-Id: Ifb9717baa56a16fb2231a4e20d5688e34647d45b
Signed-off-by: liyin <liyin11@huawei.com>
|
|
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
The stack created judging logic in Rubbos testsuite is optimized
by replacing the wating method with judging from the stack created
return value.
Change-Id: Ie96476fbfb8baf995237f71b993cf9d381b94217
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-103
Fixing the bug when key generation within rubbos controller
Change-Id: Ib444b3a8fab14217bda75bee307ea18652e8b4e4
Signed-off-by: yuyang <Gabriel.yuyang@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>
|
|
|
|
|
|
|
|
|
|
|
|
'add_posca_test_suite_framework'
* changes:
Add Factor Testcase TX PKT Size
Adding Posca Testsuite in Bottlenecks
|
|
JIRA: BOTTLENECK-101
Using autopep8 to fix the python style scanned by flake8
Change-Id: I74bf28ed4d999dac3dd36e9101f099c9853a49b6
Signed-off-by: yuyang <Gabriel.yuyang@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>
|
|
JIRA: BOTTLENECK-87
Change-Id: I67786b0481d734d09422fe5b757380cdd94d762d
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-70
log is shown in https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-vstf-virtual-daily-master/9/console
and https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-vstf-virtual-daily-master/10/console
for image names, we use bottlenecks_<suite name>_<option>
for vstf_collector.py, it is used for transfer test result to community dashboard, it works for B release, for C release,
we should adapt it later, now we only fix its path error.
Change-Id: Iad2bf39837d02aa1e5ea8a323411d98082135882
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-70
Change-Id: I768be0a0b30df266f6f130bf616d6d808cf1849c
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I9777e84b9be905c484a7d86be2287cde27ae33fe
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I2a8ab6fbbeff407713eea71ebf504a2ce2dbb342
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
JIRA: BOTTLENECK-70
Change-Id: Iade7d7a97f3b0ba54be33b37cf80c1530c410b95
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-70
Change-Id: I21cf538b7984cbc5036fc6fe897d0c90eec19e55
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: Icd024d990635b5a52385f11e7b458e18a8f186f1
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-86
Change-Id: Ia76b833bdec7554468ce081d3d572e87cea2d9f7
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-86
Change-Id: I1603d8121d58ea36d6bd2aa241590fddd70c2e6f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-70
the instance creation process is added here, as for the config info parsing,
it will be added in next patches in prepare_env func in run_vstf.py.
the images used by vstf should be changed next time, temporarily, the rubbos image
is used.
Change-Id: I2ffe03dc64ec4f315e4383c59831cfbdfbebdcfb
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: I36b03085030284a951fc35c3b898ceeb245390a6
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: Ic73b953cc7b63e4629ba7ad9c673196528891c4f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: I996944eacb7c2f57784aec50df75047d9780a1dc
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: I47b471be9d74bce5cef35f1d4f447900e54b7210
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
JIRA: BOTTLENECK-84
Change-Id: I4de0971b6d4ba60f3a0261e303fa194495c033c4
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-83
Change-Id: I1d4d4b4f53cedc6aa987f7842016099725aad516
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
The resources for this test case is 1-4-0-1 configuration.
JIRA: BOTTLENECK-80
Change-Id: I1eb013bc6b3fd0e988c809fcb068aa999cd9a73e
Signed-off-by: wangyaoguang <sunshine.wang@huawei.com>
|
|
This is a fundamental test case with minimum resource for rubbos test.
The benefits are two-fold. One is as daily test case since its bring-up time is fastest.
Another is as a baseline.
JIRA: BOTTLENECK-79
Change-Id: Ia4ffa5f2631da69ca5c6fc52558d3cf063d1b893
Signed-off-by: wangyaoguang <sunshine.wang@huawei.com>
|
|
This test case takes 1-2-0-1 configuration in rubbos.
JIRA: BOTTLENECK-78
Change-Id: I0a3c551d44ce2fadb2c42fac25426d07fad8aa95
Signed-off-by: wangyaoguang <sunshine.wang@huawei.com>
|