aboutsummaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2018-05-25[release] Yardstick release note 6.1.0rexlee87761-6/+35
JIRA: YARDSTICK-1182 Change-Id: I3baca52e9bc0360b43f2ce61ea2f166a70e8c90a Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 23d911a604f5686ade4fbbf80e0e046a2160dc8c)
2018-05-24Test 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-20Test 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> (cherry picked from commit 4cc2882c73a64e243f98c0448ca2d1f9a677953c)
2018-05-15Document 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> (cherry picked from commit 4c20fb57684bc21e7ae0461341088100e518307d)
2018-04-26[release] Yardstick Fraser 6.0.0 Release notesopnfv-6.0.0rexlee87761-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> (cherry picked from commit a324c1b922ae2598dbe25e9b2885620ef09f4901)
2018-04-23[docs] Updated baremetal instalation instructionsChornyi, TarasX1-0/+9
JIRA: YARDSTICK-1111 Change-Id: Iefab24f74c87a0855c2d70090ac34256ffa9200c Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> (cherry picked from commit 1c4a5e82aec771aba616879a9a351bade6d6d8d0)
2018-04-18Merge "[userguide] Use literalinclude directive in 05-operation" into ↵Emma Foley1-75/+9
stable/fraser
2018-04-17Merge "Bugfix: interface down HA tc050 attack and monitor logistic wrong" ↵Jack Chan1-27/+25
into stable/fraser
2018-04-16[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> (cherry picked from commit ee9995c42368ee04ba06cd101b086c57dbbb3bba)
2018-04-16Bugfix: 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> (cherry picked from commit af7f0bea3a0d24bdf084622acc9932ccd261e42e)
2018-04-10[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: I630e701136b9d573539fe69ea0a42018a67d040f Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 5b4cee9606f26f4c208fcd1aec544ddd436b8162)
2018-04-10[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: I9dbf4a3d33c2b38f7567bc3493466e72a59e1a0c Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 3248682fcc789f95ff8246a8d1f208a6a3abd46d)
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-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-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
2018-02-02Removed zero from tc numberMika Rautakumpu1-1/+1
Originally tc number was TC0042, after fix TC042. Change-Id: I3c36e39a141ec8eb74f9f00d7218bd511a56fbc9 Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>
2018-02-01Adding three missing test case descriptionsMika Rautakumpu2-1/+4
HA tests TC056, TC057 and TC058 are missing from Yardstick test case list. Missing white space added to tc056.rst. Change-Id: Id56a22ad96af8c3d05d95fb58259e9683ce9fab0 Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>
2018-01-20Merge "update docs for procedure after host reboot"Ross Brattain1-6/+10
2018-01-15update docs for procedure after host rebootJohn O Loughlin1-6/+10
Added instructions to restart nginx and uwsgi after the host is rebooted. Added instructions to start yardstick container if the host is rebooted. Removed section on virtual python environment as it is not needed. JIRA: YARDSTICK-919 Change-Id: I6e8bd1d52954c2aa138ce7879211b91b3644ecb2 Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-01-15bugfix:Incorrect title for testcase 081JingLu51-2/+2
JIRA: YARDSTICK-915 fix the wrongly numbered testcase title Change-Id: I61f94b66e3f9dac655b5c71646524b19bae7307c Signed-off-by: JingLu5 <lvjing5@huawei.com>
2018-01-09Testcase 084 documentationJingLu51-0/+140
JIRA: YARDSTICK-906 TC084 is to evaluate the IaaS compute performance by using SPEC CPU 2006 benchmark Change-Id: I628edf1d73e12d9f18eaf9609fa862ca456a1c71 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-12-22Merge "Bugfix:proxy env, ansible multinode support"Ross Brattain1-4/+44
2017-12-22Merge "Remove "flake8" and "pep8" from test-requirements"Ross Brattain1-1/+1
2017-12-21Add doc about installing YardStick on OpenSUSErossella1-0/+85
Add guide to install YardStick on OpenSUSE and modify the README to state that OpenSUSE is supported. Change-Id: Id107b24e0ec1ab441426bb150d9e863986d20fc1 Signed-off-by: Rossella Sblendido <rsblendido@suse.com>
2017-12-16update release notes for Euphrates 5.1.0Ross Brattain1-24/+61
Change-Id: I11b248882dd314baebd3ab4e7e676a1f3e0b50cd Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-12-16Merge "Addition of NSB Prox test documentation of vPE and LW-AFTR test cases"Ross Brattain3-0/+217
2017-12-14Bugfix:proxy env, ansible multinode supportMalanik Jan1-4/+44
JIRA: YARDSTICK-893 - hosts and plays in ansible/nsb_setup.yml refactored Fixed proxy configuration from env or /etc/environment in nsb_setup.sh Fixed ansible parameter 'environment: "{{ proxy_env }}"' in: - roles for components download. - roles for components dependencies install. Now, you can use ansible to modify all yardstick-standalone hosts at once. 1) Configure http[s]_proxy in - /etc/environment or - env variables 2) Modify ansible/yardstick-install-inventory.ini: [jumphost] localhost ansible_connection=local [yardstick-standalone] yardstick-standalone-node ansible_host=192.168.1.2 yardstick-standalone-node-2 ansible_host=192.168.1.3 [all:vars] ansible_user=root ansible_pass=root 3) start: ./nsb_setup.sh # for baremetal/sriov ./nsb_setup.sh <path to admin-openrc.sh> #for openstack heat Change-Id: I167db8bae8303210f21e8ae6f3870ef054bbedce Signed-off-by: Malanik Jan <janx.malanik@intel.com>
2017-12-14Merge "Refactor userguide "Yardstick Installation""Ross Brattain1-320/+392
2017-12-14Change testcases 'cirros' image to 'yardstick-image'Rodolfo Alonso Hernandez1-2/+2
The default OpenStack 'cirros-0.3.5' image doesn't exist anymore. The image included by default in any testing OpenStack deployment is now called 'cirros-0.3.5-x86_64-disk', but this name can change. Because Yardstick, during the installation, deploys a customized image, 'yardstick-image', it makes sense to use it as the default image. JIRA: YARDSTICK-873 Change-Id: I8fd7cbc01d4fa52e9107f2fac7d2d9ff5d1091c7 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2017-12-13Remove "flake8" and "pep8" from test-requirementsRodolfo Alonso Hernandez1-1/+1
Removed "flake8" and "pep8" from test-requirements. Since 44070670c798d2cde2824f3150b2b11bf35c6319, "pylint" is the code style checker, instead of "flake8" or "pep8". JIRA: YARDSTICK-832 Change-Id: Iee598b0b1793d71dc74be36fa1875387b17d1e25 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2017-11-22Addition of NSB Prox test documentation of vPE and LW-AFTR test casesDanielMartinBuckley3-0/+217
YARDSTICK-840 NSB Prox test documentation of vPE and LW-AFTR test cases documenation. Change-Id: Ic6da6546faf0494fdee71962a515083e6e10a410 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2017-11-17Tox: add a pep8 targetEmma Foley1-1/+1
Adds a pep8, pep8-full targets to tox: * pep8 target: runs pylint on the changed files * pep8-full target: runs pylint on whole repo Adds scripts to run pylint: * stored in tools/ Documentation: changeed the command for running tests (run_tests.sh -> tox). This runs the same set of tests as before. JIRA: YARDSTICK-832 Change-Id: I652da87723682d958f3fcbc2eb4cd88422636a3b Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2017-11-13Refactor userguide "Yardstick Installation"Rodolfo Alonso Hernandez1-320/+392
[1] must be refactored in order to: * Include proxy options. * Use OpenStack client, instead of project CLI. * Use sudo in some commands. * Adapt the document to rst coding style. * Fix minor errors. JIRA: YARDSTICK-828 [1] https://github.com/opnfv/yardstick/blob/923aa1738cbf5a8053e77e00937fc26f2142f6a3/docs/testing/user/userguide/04-installation.rst Change-Id: Ice63f344a8a87221bdf4daa6153b9ccac321e5b7 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>