Age | Commit message (Collapse) | Author | Files | Lines |
|
Add documentation to review the changes to original vEPC infrastructure
files to configure NSB test run in a specific test setup.
Add initial steps to prepare NSB to use Spirent Landslide for vEPC tests.
JIRA: YARDSTICK-1459
Change-Id: I3b937b1a21d6ec6851a92946e46c679385fdff9c
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
JIRA: YARDSTICK-1349
The test case document will cover the following:
- test purpose
- test configuration
- pre-test conditions
- test sequence
- test verdict
Change-Id: I2841a7ff3d248bb3e4739579fad722dc02b5504f
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
|
|
All references to submodules must be removed for docs to
work going forward.
Can be tested once your project has a local tox file
Change-Id: Id74581cc584f70ae0b31e31c9dd91593c7be6615
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Added details how to install Yardstick using install.yaml.
Updated:
- 04-installation.rst
- 13-nsb-installation.rst
JIRA: YARDSTICK-1335
Change-Id: I526c328f1b197833a2cf496cfef15ba89c11fab1
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
|
|
|
|
Added details of conventions used when writing unit tests.
JIRA: YARDSTICK-1335
Change-Id: I7bb141126968c88c8a2d7e0dce4f33ed6f79cee4
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
A new section was added to the devguide, stating
expectations for code contributions.
* What to include in a change
* Code style guidelines
* How to run tests
JIRA: YARDSTICK-1335
Change-Id: Idfe7790042a3a3fe6cd8763374b10f2268bd63cd
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
Add some new terms (OpenStack, Docker, PROX).
JIRA: YARDSTICK-1335
Change-Id: I948957cf7b1540f7a027ab9da2d829e5e05c87c8
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
|
|
Docs builds have transitioned to using local
build jobs. This allows Yardstick docs to be
built and verified locally.
The time taken to build and verify docs in the
gate for new changes should be reduced, as the
docs for each project will be built separately.
This change also allow contributers to test
their docs builds locally, using tox::
tox -e docs
tox -e docs-linkcheck
TODO: Update the dev guide to include new tox
environment
Related: DOCS-191
JIRA: YARDSTICK-1415
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Change-Id: Ib8bab85475dcd5127a2c41a2d55dce8f8d9da574
|
|
Add option parameters to TC074 to allow the user to specify
volume type, volume count, availability zone, stack name,
and subnet cidr.
JIRA:YARDSTICK-1294
Change-Id: I161f44b5f2c7e70fcfb80a3b916efc34bd06824c
Signed-off-by: Ameed Ashour <Ameed.Ashour.Ext@nokia.com>
|
|
Added details about hosts configurations in order to run tests for
standalone context.
Changes made to '13-nsb-installation.rst'.
JIRA: YARDSTICK-1402
Change-Id: I4e3304065343014a80b85fc712cdde3ca62d8b2e
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
|
|
Removes the deprecated nowarm and nosdd parameters from the
call to StorPerf.
Adds a call to initialize the disk right after the stack
creation is complete so that the results from the
performance run are valid and not skewed by a disk that
is not operating at a consistent level of performance.
Adds the jobs API v2.0 when the custom parameter 'workloads'
is used instead of workload.
Improves documentation and adds more info about the
workload and workloads parameters.
Co-Authored-By: Ameed Ashour <Ameed.Ashour.Ext@nokia.com>
Change-Id: I17e96028f6a82e2c800c8f73c7be866e1cab6ad8
JIRA: YARDSTICK-1322
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
Other references to VTC have also been removed.
Change-Id: Ia5592e29ddca1bf05cefa5b1364e0757ac78bc79
JIRA: YARDSTICK-1335
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
Change-Id: I0b0fddf8dfdd68fa144b28dba911352e9a4974fd
JIRA: YARDSTICK-1253
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
JIRA: YARDSTICK-1278
Change-Id: I96d54b06f0ef794c9c0ec26d78eb54ebcc6462ed
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
Contains Updates :-
New Description of Grafana output
New Description of ProxDuration Runner
Update Description of Openstack Network
Change-Id: I861bb7eab4aeed207c0151be6766c48c5f10c6ef
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
* Change the notation used for heading levels and
add a key at the top of the file.
* Wrap lines at 80 characters.
* Highlight keywords
Change-Id: Ic6e7194270bbffb3ddaf688c774b632287b0c201
JIRA: YARDSTICK-1253
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
JIRA: YARDSTICK-1261
Change-Id: I61adeaea8a727605481ffce9dae9646f160bf401
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Change-Id: If308fde797dcb01e58f37ad81bb116fde542366a
Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
|
|
|
|
|
|
Added default values for pmd/lcore mask to the SampleVNF test case for
Trex TG.
lcore mask - specifies the CPU cores used for non-datapath OVS-DPDK
threads.
pmd mask - specifies the CPU cores used for data path packet processing.
Updated documentation for Standalone OVS-DPDK context.
JIRA: YARDSTICK-1246
Change-Id: I8d008a185c94d2047ffa4769d7974bc4d283fd7f
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
|
|
Add PROX and vFW scale out TCs with availability zone
configuration. To be able to specify the availability
zone for specific VNF or TG the following example of
command line option shoud be used:
yardstick -d task start --task-args='{
"num_vnfs": 2, "availability_zone":
{
"vnf_0": "az_0", "tg_0": "az_0",
"vnf_1": "az_1", "tg_1": "az_1",
... }}' <SCALE-OUT-TC-FILE>
The steps to run new scale-out TCs is documented in the
userguide.
JIRA: YARDSTICK-1203
Change-Id: Ib3878485c5483981fe9b48ab02995712bcc31ae5
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
This is the test case specification for verifying the HA capabilities
of a SDN controller running in a HA configuration.
JIRA: HA-33
JIRA: YARDSTICK-955
Change-Id: I016ec1ef7bb51b79f8c21440abf8f04c923ef9dc
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
JIRA: YARDSTICK-1182
Change-Id: I3baca52e9bc0360b43f2ce61ea2f166a70e8c90a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
JIRA: YARDSTICK-1132
In B and C releases, Yardstick provides an overview of the results of test cases developed by Yardstick, executed on OPNFV community labs.
This work has not been done for the D and E releases, although result analysis for Euphrates is available at (https://wiki.opnfv.org/display/yardstick/Euphrates+release+test+results+analysis). We plan to restart to provide a basic test case results analysis for Fraser and compare performance data with Euphrates.
This JIRA ticket will be resolved into 3 commits: 1. Document for E release test case data; 2. Document for F release test case data; 3. Document for results analysis.
Change-Id: I3c59851c8878ba37145e6ad6958272a62bad3f52
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
|
|
Added the yardstick-reviewers and yardstick-committers groups
as an alternative to adding individual developers to a code review.
Change-Id: I1ebba56ba27dac00f7e7af7858b3c599a0f1eae8
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
This is a test case for verifying the proper functionality of
SDN Vswitches which are located in the Compute nodes of an OpenStack
environment.
This test case is unaware of the configuration (non-HA,HA)
JIRA: HA-34
JIRA: YARDSTICK-955
Change-Id: I701bf1f9527b1a31b9cb52e102734e10c4162766
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Add IxNetwork python package to the requirements list.
This module is needed for the "NSPerf" scenarios using IXIA as traffic
generator, when IxNetwork is the program used to handle the IXIA
generator.
The latest version of this module is 8.40.1124.9 [1]. The license type
is MIT.
[1] https://pypi.python.org/pypi/ixnetwork
JIRA: YARDSTICK-1106
Change-Id: I279933c95994f5120930256a104c4192a0b9900d
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
JIRA: YARDSTICK-1129
Change-Id: I5adb2e9547c58b90d3eafb0e2b90015ce5472cfa
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-1132
In B and C releases, Yardstick provides an overview of the results of test cases
developed by Yardstick, executed on OPNFV community labs.
This work has not been done for the D and E releases, although result analysis
for Euphrates is available at (https://wiki.opnfv.org/display/yardstick/Euphrates+release+test+results+analysis).
We plan to restart to provide a basic test case results analysis for Fraser and compare performance data with Euphrates.
This JIRA ticket will be resolved into 3 commits: 1. Document for E release test case data; 2. Document for F release test case data;
3. Document for results analysis.
Change-Id: I372a60807ac3dfaab87e70cdb956c1059b019f7a
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
1. simplify the attack to be one interface
2. move monitor step before attack
3. update rst doc to match
JIRA: YARDSTICK-1120
Change-Id: Icfa21d58e7ccdbeaca8a9a1a3098cceb21c981c3
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-1111
Change-Id: Iefab24f74c87a0855c2d70090ac34256ffa9200c
Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
|
|
Uses literalinclude directive instead of having a copy of the file content in documentation.
This means that any update to this file is detected, and the most up-to-date content is used.
If a testcase is updated, the updates wil be picked up.
The examples used are ones that are tested reqularly.
JIRA: YARDSTICK-1066
Change-Id: I15d967eb04d1e6f4348683d8746fa9989dceda94
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Add a new chapter: operation which shows how to use Yardstick and
how to create test cases
* Include details on how to reuse and keep VNFs between testcases
JIRA: YARDSTICK-885
JIRA: YARDSTICK-886
Change-Id: I365152e8812427a3c54259adbc18d5ddb216d775
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Increment the numbering on chapters
* Fix some of the changes flagged by doc8
Change-Id: Ie03d165297671dfd50b9de339612cdc8bf00b988
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|