summaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2018-07-01Yardstick Fraser Release notes - 6.2.1rexlee87761-0/+17
JIRA: YARDSTICK-1278 Change-Id: I96d54b06f0ef794c9c0ec26d78eb54ebcc6462ed Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-06-29Merge "Update PROX_NSB_DEVGUIDE for F Release"Rodolfo Alonso Hernandez10-25/+119
2018-06-29Update PROX_NSB_DEVGUIDE for F ReleaseDanielMartinBuckley10-25/+119
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>
2018-06-29Yardstick Fraser Release notes - 6.2.0rexlee87761-5/+98
JIRA: YARDSTICK-1261 Change-Id: I61adeaea8a727605481ffce9dae9646f160bf401 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-06-27Corrected scale-up command line argumentsChornyi, TarasX1-1/+1
Change-Id: If308fde797dcb01e58f37ad81bb116fde542366a Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
2018-06-21Merge "Add scale out TCs with availability zone support"Rodolfo Alonso Hernandez1-1/+111
2018-06-21Merge "Document for Fraser test case results"Jing Lu26-17/+1962
2018-06-18Update pmd/lcore mask for OVS-DPDK contextStepan Andrushko1-0/+36
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>
2018-05-25Merge "[release] Yardstick release note 6.1.0"Ross Brattain1-6/+35
2018-05-25Add scale out TCs with availability zone supportMytnyk, Volodymyr1-1/+111
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>
2018-05-23Test case spec for SDN controller resilience in HA configGeorg Kunz2-0/+197
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>
2018-05-23[release] Yardstick release note 6.1.0rexlee87761-6/+35
JIRA: YARDSTICK-1182 Change-Id: I3baca52e9bc0360b43f2ce61ea2f166a70e8c90a Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-05-20Merge "Test case spec for SDN Virtual Switch resilience."Emma Foley2-0/+185
2018-05-17Document for Fraser test case resultsJingLu526-17/+1962
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>
2018-05-16Merge "Test case description and configuration file for yardstick_tc088"Jing Lu1-0/+129
2018-05-16Merge "Test case description and configuration file for yardstick_tc089"Jing Lu1-0/+129
2018-05-15Merge "Document for Euphrates test case results"Jing Lu36-2886/+2086
2018-05-11[docs] Add info on gerrit groups to the devguide.Emma Foley1-1/+2
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>
2018-05-07Test case spec for SDN Virtual Switch resilience.Dimitrios Markou2-0/+185
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>
2018-05-04Add IxNetwork API Python Binding packageRodolfo Alonso Hernandez2-75/+41
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>
2018-04-26[release] Yardstick Fraser 6.0.0 Release notesrexlee87761-305/+209
JIRA: YARDSTICK-1129 Change-Id: I5adb2e9547c58b90d3eafb0e2b90015ce5472cfa Signed-off-by: rexlee8776 <limingjiang@huawei.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-24Document for Euphrates test case resultsJingLu536-2886/+2086
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>
2018-04-23Merge "[docs] Updated baremetal instalation instructions"Rodolfo Alonso Hernandez1-0/+9
2018-04-13Bugfix: interface down HA tc050 attack and monitor logistic wrongrexlee87761-27/+25
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>
2018-04-06[docs] Updated baremetal instalation instructionsChornyi, TarasX1-0/+9
JIRA: YARDSTICK-1111 Change-Id: Iefab24f74c87a0855c2d70090ac34256ffa9200c Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
2018-04-03[userguide] Use literalinclude directive in 05-operationEmma Foley1-75/+9
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>
2018-04-03[docs] update the user guide for "yardstick-operation"Emma Foley3-0/+366
* 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>
2018-04-03[docs] Move user guide chapters to make room for new chapter.Emma Foley14-551/+400
* 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>
2018-03-24Merge "Test case spec for SDN controller resilience in non-HA config"Ross Brattain2-0/+183
2018-03-23Merge "Test case description and configuration file for ↵Ross Brattain1-0/+151
yardstick_tc090:Control Node Openstack Service High Availability - Database Instances"
2018-03-22Added scale-up documentationChornyi, TarasX1-9/+45
Change-Id: I65770a4a879d890c75a2e5774579794fb9b591f6 Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
2018-03-22Merge "Test case description and configuration file for ↵Rex Lee1-0/+138
yardstick_tc091:Control Node Openstack Service High Availability - Heat Api"
2018-03-19Bugfix: sutie -> suite in documentationchenjiankun1-1/+1
Change-Id: Ia898a7a6d95e74b16cfc754b615cccfd9c5380ad Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-03-16NSB userguide: run TC in heat context & sriov portsMytnyk, Volodymyr5-4/+486
Add section that describeds steps to be able to run sample vFW TC in heat context with sriov ports confiured in the OpenStack. JIRA: YARDSTICK-1022 Change-Id: I764933e26ca7cb10aa1094901ec3304156054333 Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
2018-03-16Merge "Update API documentation"Jack Chan1-71/+156
2018-03-16Merge "testcase start service script fail on centos env"Jing Lu10-19/+72
2018-03-16Test case description and configuration file for yardstick_tc090:Controltjuyinkanglin1-0/+151
Node Openstack Service High Availability - Database Instances JIRA: YARDSTICK-960 Change-Id: Ibe47a9b4d1f095971857fcbaee57a3c7f64f9911 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2018-03-16Test case description and configuration file for yardstick_tc091:Controltjuyinkanglin1-0/+138
Node Openstack Service High Availability - Heat Api JIRA: YARDSTICK-961 Change-Id: I49fc2b2d8fc4fa090a74f1838f5ac386e39eaf49 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2018-03-15Update API documentationchenjiankun1-71/+156
JIRA: YARDSTICK-1070 Our current API documentation is out-of-date. We need to update it. Change-Id: If5133c0350a91affb8d3f856d23b23a9903c8620 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-03-13Test case spec for SDN controller resilience in non-HA configGeorg Kunz2-0/+183
This is the test case specification for verifying the HA capabilities of a SDN controller running in a non-HA configuration. JIRA: HA-31 JIRA: YARDSTICK-955 Change-Id: I10f9ce4a2888092c033d2c02bf9a5a950b8b12dc Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-03-09Do NOT hardcode interface speed for PROX testsDanielMartinBuckley1-1/+9
JIRA: YARDSTICK-1035 Do not hardcode NIC/interface speed in PROX test. Test assumes NIC used is 10Gbps. This is incorrect. It could support 1Gbps, 10Gbps, 25Gbps, 40Gbps or something else. This is used to calculate pps (Packets Per Second) In Baremetal the NIC speed could be extracted. however when run on a virtual machine this is not possible. Solution: Add in options section of test file. eg. Options: interface_speed_gbps: 10 Where 10 refers to a 10Gbps. In a setup where multiple interfaces are used. This will refer to the speed of the slowest connection. Change-Id: I89ab16479a2cdd1d79e52cbcc5a972762c60d057 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2018-03-08Test case description and configuration file for yardstick_tc088tjuyinkanglin1-0/+129
JIRA: YARDSTICK-958 Change-Id: I4b9633deca5b88c836aaeea02454495381fe5843 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2018-03-07Fix numbering and html (generated) alignmentDino Madarang1-3/+5
Fix numbering from 3,5,6 to 3,4,5 and alignment of the numbered list in HTML output. Trim lines to 79 chars or less. Change-Id: Icf233ef6bbf99ac0dcd8a9fc2599aee9dc1a46fd Signed-off-by: Dino Simeon Madarang <dinox.madarang@intel.com> Reviewed-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com> Reviewed-by: Emma Foley <emma.l.foley@intel.com> Reviewed-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-07Test case description and configuration file for yardstick_tc089tjuyinkanglin1-0/+129
JIRA: YARDSTICK-959 Change-Id: Ib2f99c9c00f4549a8a721cb06324d5b3356bdda7 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2018-03-06testcase start service script fail on centos envJingLu510-21/+74
JIRA: YARDSTICK-676 In the HA test cases, script 'start_serice.bash' is used to restart the OpenStack service to recover killed process. It uses 'lsb_release' command to determine the host linux distribution and the target Openstack service name. In some environments, the 'lsb_release' is not installed hence will cause process-recovery failure. This patch states the software precondions in the HA test case descriptions. Change-Id: Ie3f503b8185deec13eebbcacbeac57c0a018cb73 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2018-03-02Layout fixes to test case descriptionsMika Rautakumpu3-11/+16
Change-Id: I9658b023e4f3db7e22d67c71dfbba61511d981c6 Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>
2018-02-28Deprecate authentication variable OS_TENANT_NAMERodolfo Alonso Hernandez3-9/+5
OS_TENANT_NAME was deprecated as authentication variable in Keystone when moved from v2 to v3, in Icehouse (2014). Because this project doesn't support oldest versions, by default the only identification API version supported is v3. JIRA: YARDSTICK-902 Change-Id: I273fb0151ba583f7c8a5a809e5e8864e92c27d31 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-02-27Addition of NSB Prox developer guide.DanielMartinBuckley16-0/+1226
JIRA: YARDSTICK-840 This provides a developer guide to enable the reader to add NSB PROX tests based on existing PROX functionality. This allows the user to configure, run and debug NSB Prox tests for Baremetal and Openstack (both 2 and 4 ports) Change-Id: I2cb9eb6064e501dd9abe0d2cc4ed8ce4b369f174 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2018-02-12Fixed document for Grafana Port usageAbhijit Sinha1-3/+3
JIRA: YARDSTICK-992 The Grafana port has been changed to 1948 from 3000, as the port 3000 may be not free in some environments. The document still says it uses port 3000, which leads to confusion. Proposed Solution: The document needs to be updated with correct Grafana port number "http://host_ip:1948" Change-Id: I9078783849aec14602585f4d1b3bc293214ae737 Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
2018-02-06Merge "Adding three missing test case descriptions"Rodolfo Alonso Hernandez2-1/+4