summaryrefslogtreecommitdiffstats
path: root/testsuites/posca
AgeCommit message (Collapse)AuthorFilesLines
2017-02-21quota limit for posca_stress_pingliyin2-3/+9
JIRA:BOTTLENECK-140 Those code will update an action of quota. Before out test begin we will make quota no limit. so we could do stress test. Those quota limit will change openstack forever. maybe will create damage for openstack. Change-Id: I0a6a06c6c303589881cb2ab7b754213ecf1a845f Signed-off-by: liyin <liyin11@huawei.com>
2017-02-20stress_test_dashboard_codeliyin7-3/+217
JIRA:BOTTLENECK-138 Those codes will create dashboard for stress test. And we have fixed a bug, that we will increace env prepare in this patch besides: we also add some code of how to yardstick api. Change-Id: I64bb249ee0df9fe37e998a784ba346719bf25197 Signed-off-by: liyin <liyin11@huawei.com>
2017-02-17stress test of ping testcaseliyin4-5/+123
JIRA:BOTTLENECK-136 those code will add a new testcase: posca_stress_ping This will use docker python client to realize the fountion of calling yardstick to test. And yardstick will create several VM pairs to test. Because of the limites of quotas, we now create 2,5,10 VM pairs. Change-Id: I096250c547cd598c7c632a884b31d81c2be125f8 Signed-off-by: liyin <liyin11@huawei.com>
2017-02-14Dashboard and output file code reconstructionliyin4-108/+143
JIRA:BOTTLENECK-134 Those code will change the way to create dashboard. And dashboard as a spare function to show data. And we add log system to dashboard creation. The output file is created anyway. Change-Id: Ia3c4d5a8ada27005702e3eed08757f61610da22f Signed-off-by: liyin <liyin11@huawei.com>
2017-02-13Merge "Bug fix: yardstick result return no content"Yu Yang (Gabriel)1-1/+5
2017-02-09Bug fix: yardstick result return no contentliyin1-1/+5
JIRA:BOTTLENECK-130 this patch will fix this bug: we try to expect this error, And we try to run it again. if failed, then yardstick RestAPI or have some error. Change-Id: I9fa63da637456a16c151f4fe7c566b3f5ff0e01d Signed-off-by: liyin <liyin11@huawei.com>
2017-02-09Add POSCA jenkins job supportyuyang2-5/+6
JIRA: BOTTLENECK-128 This patch is to make the POSCA testsuite could be built automatically for OPNFV CI job. Change-Id: I21d7fd553ce3591aea3391a33fe0a7b8579b57d4 Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
2017-02-09Log_dir bug fix&Add function of test_ip initliyin3-21/+8
JIRA:BOTTLENECK-129 This patch fix the error of log_dir can't be found. And change several thing: 1.Add if config don't have test_ip, it will use local:8888 as test ip. 2.Fix the bug in setup.py. 3.Add parser init to logger file. Change-Id: I808c69e2b2ff3c04f271cc7f3e14e1ab406a4d1b Signed-off-by: liyin <liyin11@huawei.com>
2017-02-07Bottlenecks stack config parser.liyin3-0/+27
JIRA:BOTTLENECK-126 realize the function of parsering stack config. include the function all the jira mationed. it's important for stack creating. this patch also include manager.py. This file modify some file such like template intial. Change-Id: Iaa6fdbde6bf9cb1ff9875d47268440dfe70ecc49 Signed-off-by: liyin <liyin11@huawei.com>
2017-02-07Bottlenecks POSCA testing code reconstructionliyin3-146/+120
JIRA:BOTTLENECK-103 This is the foundation of adding stack samples. This code change a lot code. but it's a basic. Those code will be changed in the furture. Change-Id: I8d5bbb9cc401b1aaac54ec4dffc4c005a42d17ac Signed-off-by: liyin <liyin11@huawei.com>
2016-12-27bugfix: remove timeField for Kibana index-patternyuyang1-1/+0
JIRA: BOTTLENECK-121 Remove timeField item in index-pattern which causes kibana no reading test results. Change-Id: I855dba186cc0e0db8e5c9dbd7aa21df80722d70e Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
2016-12-21Add flake8 style config and for POSCAyuyang15-155/+197
JIRA: BOTTLENECK-100 Adding flake8 configuration and fix for POSCA Change-Id: Ib822d5abde535263a4473d67c15cc17995f1417b Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
2016-12-07cpu_burden script&configureliyin2-86/+82
JIRA: BOTTLENECK-118 This patch add a new function cpu_burden. there are two things: 1.add configure file of cpu_burden, this default file could run test case 2.add script of cpu_burden, this script use the configure file could use yardstick restful api call date. Change-Id: Icd88b317fb97d8f12d81279eaffc2d3effc8ab65 Signed-off-by: liyin <liyin11@huawei.com>
2016-12-02dashboard log info checkliyin1-1/+6
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>
2016-12-02dashboard bug: can't deploy dashboardliyin2-8/+33
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>
2016-12-02add more debug infoliyin2-7/+9
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>
2016-12-02bug fix patchliyin1-0/+2
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>
2016-12-01bug fix patchliyin2-3/+4
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>
2016-12-01posca test suite urls changeliyin2-13/+15
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>
2016-11-30posca test suite support influxDB containerliyin2-0/+10
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>
2016-11-30posca system bandwidth dashboardliyin2-0/+103
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>
2016-11-30POSCA test case completeliyin3-95/+213
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>
2016-10-25Modify POSCA code into PEP8 styleliyin7-299/+450
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>
2016-10-08Merge "Add Factor Testcase CPU_Burden"Jun Li2-0/+132
2016-10-08Merge "Add Factor Testcase RX_Cache_Size"Jun Li2-0/+128
2016-10-08Merge "Add Factor Testcase RX_PKT_Size"Jun Li2-0/+134
2016-10-08Merge "Add Factor Testcase System_Bandwidth"Jun Li1-0/+123
2016-10-08Merge "Add Factor Testcase TX_Cache_Size"Jun Li2-0/+128
2016-09-22Add Factor Testcase TX PKT Sizeyuyang2-0/+134
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>
2016-09-22Add Factor Testcase TX_Cache_Sizeyuyang2-0/+128
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>
2016-09-22Add Factor Testcase System_Bandwidthyuyang1-0/+123
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>
2016-09-22Add Factor Testcase RX_PKT_Sizeyuyang2-0/+134
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>
2016-09-22Add Factor Testcase RX_Cache_Sizeyuyang2-0/+128
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>
2016-09-22Add Factor Testcase CPU_Burdenyuyang2-0/+132
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>
2016-09-22Adding Posca Testsuite in Bottlenecksyuyang4-0/+59
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>