Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: BOTTLENECK-214
Bottlenecks VNF scale out testcase
Change-Id: I05c4dec483062dd59c4b062516c8a6c1bc83ad6e
Signed-off-by: Ace Lee <liyin11@huawei.com>
|
|
JIRA: BOTTLENECKS-212
Add moon feature tenant testcase to Bottlenecks
Change-Id: I3795470fa5fab1866da346ec376dbd8f00f8205b
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECKS-212
Add moon feature resource testcase to Bottlenecks
Change-Id: Ib9bddfcd980e38c40d4a76b6cfd48bb9a656c81e
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-205
This is the script of testpmd scale-up feature testcase.
we will debug the dashboard.
Change-Id: I4a6de0e7e1ea7c04639ece78a7b11b75128d8d2f
Signed-off-by: liyin <liyin11@huawei.com>
|
|
|
|
|
|
The purpose of this test is to increase the
number of VNFs being tested while monitoring
aggregate performance scaling.
requires https://gerrit.opnfv.org/gerrit/#/c/37993
Change-Id: I0015ef0326859512c7b9ab4c57ef9b5a710ca852
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
The purpose of this test is to increase the amount
of resources provided to the VNF and monitor the ablilty
of the VNF to scale
requires https://gerrit.opnfv.org/gerrit/#/c/37991/
Change-Id: I4e2384ef120dea2348a623acc1d439696d95e73b
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: BOTTLENECK-177
This patch will debug some error in system bandwidth testcase.
use the new docker way to test this testcase.
Bug fix about dashboard and test framework.
Change-Id: I7167ffd75efab9a7780407aa5b9a4337ebb9b4c7
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-175
After this patch,
Bottlenecks will try to find the stress of the openstack system.
we try to create 20 stacks one time.
And 20 stacks the other time.
we will try to find if openstack will pass threshhold twice.
This patch only affact latest version
Change-Id: I6146cf5c6fe0ac4968337cc36e07f715b64191d0
Signed-off-by: Ace Lee <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-171
Add support of Bottlenecks docker frame refact,
After this patch we will provide the ability of several installer.
Add Yardstick_TAG to adjust yardstick docker version
Change-Id: Ib431f8acf4a76b59f9d5e8783bcc7d2e5be208ae
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: BOTTLENECK-143
Add task selection to test suite entrance file
Change-Id: Ia21b3121d104a457a66e2c77e3caf091e102f388
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: BOTTLENECK-133
Some Yaml, XML and __init__.py file do not have liscense headers.
This patch is to add headers to those files or delete those are deprecated.
Change-Id: Ie059b1f1879eb420eec171f96985247510c74642
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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-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-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>
|