Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: BOTTLENECK-117
This patch change the docker-compose file.
because of yardstick dockerfile.
so bottlenecks also need to change the style of docker-compose.
Change-Id: Idb82120c5b00ef8595a993886fa3fc0d6b6c4c32
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-115
This patch change an error that last patch haven't covered.
so i need to correct it.
Change-Id: I1ab1fbe4e60463482728ec3ab58ec71c4e1d7049
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-116
This patch fix the bug that bottlenecks project can't establish
dashboard, error message is elasticsearch is not install.
after install elasticsearch, the error message is can't get ip.
to fix this bug, change file requriment.txt and dashboard file.
Change-Id: Ibad0dc46ab44d500b799bbf67e169d76c59e7199
Signed-off-by: liyin <liyin11@huawei.com>
|
|
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-112
this patch change the yardstick and bottlenecks dockerfile
from stable to latest
Change-Id: I095957dc6aba25d76bb8e60be97c171c4a59ce57
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-108
Releng has updated the parameter input method. So the Docker file
need BRANCH argument to specify the docker image source.
Change-Id: I6c8eee3aaf7729964f0b810c209ccdcf9b75a233
Signed-off-by: yuyang <Gabriel.yuyang@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-65
Add installation of VIRTUALENV and deletion of it.
Change-Id: I4a339e8e87775fc2ea1e12d8fbf473850076bbd3
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
|
|
JIRA: BOTTLENECK-65
Adding cli framwork for Bottlenecks.
Usage:
bottlenecks testcase run <testcase>
Currently only the cli framwork and testcase command group is added.
run, list, etc., commands and openstack command group
will added afterwards.
Two setup entries are added. One is within the top directory and the
other is within the cli directory.
Change-Id: I304f6f2e9b29b9f582953c2739806c1fb3e87fed
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-105
there are files which be need to support docker-compose.
some files are docker configure file.
some files are used to build docker image.
kibana docker is bottlenecks project dashboard.
elasticsearch docker is bottlenecks project database.
influxdb docker is yardstick project database.
yardstick docker is used to run test case.
Change-Id: I7f0927c940a400f9f66ac77174f06236a1f4f265
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-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-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 election result for Yang throuth email:
https://lists.opnfv.org/pipermail/opnfv-tsc/2016-October/003088.html
Achievements/Conbributions include:
https://gerrit.opnfv.org/gerrit/#/q/owner:Gabriel.yuyang%2540huawei.com+project:bottlenecks
1. Adding POSCA test suite in Bottlenecks
a) POSCA testing framework
i. https://jira.opnfv.org/browse/BOTTLENECK-92
ii. https://gerrit.opnfv.org/gerrit/#/c/20837/
b) Adding Factor Test case System_Bandwidth
i. https://jira.opnfv.org/browse/BOTTLENECK-94
ii. https://gerrit.opnfv.org/gerrit/#/c/21351/
c) Adding Factor Test case CPU_Burden
i. https://jira.opnfv.org/browse/BOTTLENECK-95
ii. https://gerrit.opnfv.org/gerrit/#/c/21355/
d) Adding Factor Test case TX PKT Size
i. https://jira.opnfv.org/browse/BOTTLENECK-99
ii. https://gerrit.opnfv.org/gerrit/#/c/21563/
e) Adding Factor Test case RX_PKT_Size
i. https://jira.opnfv.org/browse/BOTTLENECK-97
ii. https://gerrit.opnfv.org/gerrit/#/c/21401/
f) Adding Factor Test case TX_Cache_Size
i. https://jira.opnfv.org/browse/BOTTLENECK-98
ii. https://gerrit.opnfv.org/gerrit/#/c/21561/
g) Adding Factor Test case RX_Cache_Size
i. https://jira.opnfv.org/browse/BOTTLENECK-96
ii. https://gerrit.opnfv.org/gerrit/#/c/21379/
2. Refactoring Bottlenecks documentations
a) Correcting table format error in userguide docs
i. https://jira.opnfv.org/browse/BOTTLENECK-88
ii. https://gerrit.opnfv.org/gerrit/#/c/19043/
b) Adding framework illustration in Bottlenecks docs
i. https://jira.opnfv.org/browse/BOTTLENECK-88
ii. https://gerrit.opnfv.org/gerrit/#/c/19131/
c) Adding Release Notes Doc Framework
i. https://jira.opnfv.org/browse/BOTTLENECK-88
ii. https://gerrit.opnfv.org/gerrit/#/c/22309/
3. Flake8 fix for Bottlenecks project
a) https://jira.opnfv.org/browse/BOTTLENECK-101
b) https://gerrit.opnfv.org/gerrit/#/c/22593/
4. Organizing the Bottlenecks weekly meeting and maintaining WIKI
a) Meeting minutes and meterial
i. https://wiki.opnfv.org/pages/viewpage.action?pageId=6828202
ii. https://wiki.opnfv.org/download/attachments/2926187/Proposals%20in%20Bottlenecks.pdf?version=7&modificationDate=1472176386000&api=v2
b) Release Planning WIKI pages
5. Design and sharing the POSCA test suite
a) POSCA test suite in Bottlenecks D release
i. https://wiki.opnfv.org/download/attachments/2926187/POSCA%20in%20Bottlenecks%20D%20Release.pptx?version=1&modificationDate=1475983276813&api=v2
b) Sharing POSCA in Bottlenecks weekly meeting
i. https://wiki.opnfv.org/download/attachments/2926187/2016-09-22%20Sharing%20POSCA%20in%20Bottlenecks.mp4?version=1&modificationDate=1475993554550&api=v2
Change-Id: I59980f6e8ff378e845af1297cf294e058be56880
Signed-off-by: yuyang <Gabriel.yuyang@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>
|
|
Proposal 3 from this wiki:
https://wiki.opnfv.org/display/INF/Docker+handling+in+CI#DockerhandlinginCI-3Dockerfilelocation
Do not merge before this:
https://gerrit.opnfv.org/gerrit/#/c/22565/
JIRA: RELENG-148
Change-Id: I07e1418ae06c59e6c4d495c8c87d28addbb98d03
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.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-88
Required by release meeting to add RN for Colorado 1.0.
A framework of RN is updated and more details will be filled in
Colorado 2.0.
Change-Id: I386240d9b8c6d9cf30e68a12e3e84f1e09833d2a
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
Change-Id: Ibb53a25d912fd96c93b25e39ee8da8b0977cf071
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: If16ac8f2e8d0114d8b7121d551ac5ac9a15bf76e
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I6d8e4e1d007bdcce037cf1ae93324de8080640ec
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-87
Change-Id: I67786b0481d734d09422fe5b757380cdd94d762d
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-88
changes:
1. add framework image in platformoveriew/introduction.rst to make
the Bottlenecks docs more user friendly
2. image name in platformoveriew/introduction.rst is not correctly
writed, correct it as Framework_Setup.png
3. correct the image width error
4. correct image path
5. change the illustration to Rubbos introduction section as commented
6. move the illustration in top-level directory as suggested
7. add brief decription of the illustration
Change-Id: Id86b813fa6e0a68349de60bb294b1cef43484a9a
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-87
Change-Id: Ifa3da0e5c4e67c65a61567af1b75d629959d076f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: BOTTLENECK-88
A right side line of the table is not aligned with others which causes
compling error.
Change-Id: I5391ef566573ec88b2e94ed36a3f628f8c8ddb8e
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-88
Change-Id: I963502bb494bfb8773b312f038e9a1ea9902e56e
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|