aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-08-29Merge "Bugfix: openstack router list broken in Yardstick container - ↵Jing Lu2-2/+2
dovetail" into stable/fraser
2018-08-29Merge "ping bottlenecks failed when security group rule do not support ipv6 ↵Rex Lee1-0/+12
- dovetail" into stable/fraser
2018-08-29Merge "Make security group configurable - dovetail" into stable/fraserRex Lee5-58/+165
2018-08-28Bugfix: openstack router list broken in Yardstick container - dovetailrexlee87762-2/+2
Dependancy of python-openstackclient is not constrained. This patch specify openstacksdk and openstackclient's version according to [1]. This patch apply for bugfix and need to backported to fraser stable branch. Continual work need to be done in Gambia according to YARDSTICK-1398. [1] https://github.com/openstack/requirements/blob/stable/pike/upper-constraints.txt JIRA: DOVETAIL-728 Change-Id: I57c718e192699ac322150458d18508b06c93d22b Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 1e53af56c278921dad5671a5c4b8cafcdaa54ba9) Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-08-27Merge "Decrease Sampling interval - Invalid Port results" into stable/fraserAbhijit Sinha1-10/+17
2018-08-27ping bottlenecks failed when security group rule do not support ipv6 - dovetailrexlee87761-0/+12
JIRA: YARDSTICK-1380 Change-Id: I2163eeb9ab17e4f0216ddaed688e78acdf51a1ff Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 1c5d667f11d9d8a67a262eb6cc5ac53ff9d0cadd)
2018-08-27Make security group configurable - dovetailrexlee87765-58/+165
Make sercurity group can be configured via the context. The format would be: context: name: demo image: yardstick-image flavor: yardstick-flavor user: ubuntu security_group: rules: - remote_ip_prefix: "0.0.0.0/0" protocol: "tcp" port_range_min: 1 port_range_max: 65535 - remote_ip_prefix: "0.0.0.0/0" protocol: "udp" port_range_min: 1 port_range_max: 65535 - remote_ip_prefix: "0.0.0.0/0" protocol: "icmp" JIRA: YARDSTICK-1360 Change-Id: I00c45767ee2d70b790590e824599d5a4c274bced Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit cea576574ac0554c1320179bffe6965ac1333972)
2018-08-27Merge "the recovery action of "baremetal down" should be triggered ↵Jing Lu5-3/+59
mandatory" into stable/fraser
2018-08-27Merge "Bugfix: HA test case baremetal down ipmi power off failed - dovetail" ↵Jing Lu2-29/+5
into stable/fraser
2018-08-22Update docker image tag to 6.2.1Patrice Buriez1-1/+1
JIRA: YARDSTICK-1137 Change-Id: I5cb4a06a3c8f6582cdc8d0fa82a7413bc4f2e022 Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
2018-08-21Decrease Sampling interval - Invalid Port resultsPatrice Buriez1-10/+17
JIRA: YARDSTICK-1219 The computed in/fwd throughputs displayed on the L2FWD, L3FWD and VPE dashboards. The computed value is likely 4x the expected value. It is required to return sampling information form Generator AND VNF at least every 1 second. Change-Id: I4435fd05ba3116ead836843a4c2fce133b767a28 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 2d10b0bf7238f5417d46f89c76b856f7e345f738) Signed-off-by: Patrice Buriez <patrice.buriez@intel.com> (also picking from commit 68aaa8ce8b20ba39040aa2469b384f59709620a7)
2018-08-21the recovery action of "baremetal down" should be triggered mandatoryrexlee87765-4/+60
YARDSTICK-1222 has made attacker recover only when the sla not pass. But for baremetal down test case, the node need to power on even the sla pass. TODO: Make attacker can support mandatory recover in some situation. JIRA: YARDSTICK-1337 Change-Id: Ib567b9b9025e5ee421ea47140c468537ad16f090 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 5f11cb9f55aa0529fddfe916a2976a9aa5b4c08f)
2018-08-21Bugfix: HA test case baremetal down ipmi power off failed - dovetailrexlee87762-29/+5
Test case tc025 baremetal down failed to ipmi power off the node. This patch target to solve: ipmi_password is not correctly fetched JIRA: YARDSTICK-1326 Change-Id: Ia915cd07cba420643fa9a679975178328be55700 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit fb895253e4ceeff2df53043b5b994f63c740b1f6)
2018-07-19add support of dpdk for bottlenecks_pingYang (Gabriel) Yu1-0/+5
This patch is supposed to be coordinated with https://gerrit.opnfv.org/gerrit/59901 to support dpdk scenario for Bottlenecks JIRA: YARDSTICK-1332 Change-Id: I4ae3d05523d0624d689702cb8eb23be364830de1 Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com> (cherry picked from commit 60b2c02f3968d84df339b491d659b6549bfc3771)
2018-07-12Merge "Sample VNF version need to be updated to Fraser" into stable/fraserAbhijit Sinha1-1/+1
2018-07-12Change "monitor" to "assert" in SLADimitrios Markou3-9/+9
Change "monitor" to "assert" in SLA to make an Overall testcase to fail if a subtest Scenario fails JIRA: YARDSTICK-1305 Change-Id: I90f5c95f0ddace160d751a435d60ae09a42101f2 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit 2552e6fd05ef1432992a2ef538dc31c6a2247ea4)
2018-07-06[Bug fix] Execute teardown if SLA is set to "assert"Dimitrios Markou1-0/+1
In Duration runner if SLA is set to "assert" and a SLAValidationError happens then a teardown is needed to avoid garbages in the environment. JIRA: YARDSTICK-1291 Change-Id: I9056b0da3e7e496171ed42430ffc340b5c68f108 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit 30fc9f545d526fdbd69af483b0bad0ea781d648c)
2018-07-04Sample VNF version need to be updated to FraserRodolfo Alonso Hernandez1-1/+1
JIRA: YARDSTICK-1289 Change-Id: Ib150fafdfcc7a7aa09e4ed9c683fc3013676dac4 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com> (cherry-picked from commit 41777f75f551e6c448d21c9cf29d4e2967268f98)
2018-07-01Yardstick Fraser Release notes - 6.2.1opnfv-6.2.1rexlee87761-0/+17
JIRA: YARDSTICK-1278 Change-Id: I96d54b06f0ef794c9c0ec26d78eb54ebcc6462ed Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-07-01Bugfix: uwsgi config file yardstick.ini output errorrexlee87761-2/+2
JIRA: YARDSTICK-1280 Change-Id: I45b4b781cee21035897ba0c34dc740af6365e918 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 27858564cfaf4809808de52a843d2c60c13326e2)
2018-06-30Bugfix: docker build failedrexlee87761-1/+1
Due to no inventory.ini specified in Dockerfile, which resulsts in ansible-playbook run fail JIRA: YARDSTICK-1277 Change-Id: Iaf689b71b8c86b54b2451d8a8c480f7d94d53561 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit ce9a39a0e9e2747afa722f360ddc74dc697b3217)
2018-06-30Bug Fix: correct the file path to build docker fileting wu2-12/+11
To be able to build a docker file, the path to file "exec_tests.sh" should be modifed from .docker/exec_tests.sh to ./exec_tests.sh. JIRA: YARDSTICK-1157 Change-Id: I0f707ba579039d0efc8f2185b596e23b901c09df Signed-off-by: ting wu <ting.wu@enea.com> (cherry picked from commit e5c9c487105f0bbe6416e612da77f5c93b9b354c)
2018-06-30Fix ansible scripts for running in containerJohn O Loughlin2-6/+8
JIRA: YARDSTICK-1147 Change-Id: I52dae85a2d97192bc8a48c5aeea3173b3d4de003 Signed-off-by: John O Loughlin <john.oloughlin@intel.com> (cherry picked from commit 5db2f11d309d42cdf7cf177b86d31deb3fe58e37)
2018-06-29Yardstick Fraser Release notes - 6.2.0opnfv-6.2.0rexlee87761-5/+98
JIRA: YARDSTICK-1261 Change-Id: I61adeaea8a727605481ffce9dae9646f160bf401 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 1b9bca5b7b51d79bab432a10e16bdb0d69a80dfe)
2018-06-29Merge "Update docker image tag to 6.2.0" into stable/fraserRodolfo Alonso Hernandez1-1/+1
2018-06-29Update docker image tag to 6.2.0Emma Foley1-1/+1
Change-Id: Iec55c8f400d5413f173359d21cb1cc3b3d4f935f Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-06-29NFVI support for standalone, baremetal and heat contextsChornyi, TarasX26-280/+553
JIRA: YARDSTICK-1257 Change-Id: I6733bd49ac91985e8f3d7722e6990e8733bb430e Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> (cherry picked from commit 005358a39a87e42061dd5b344916c2ffe0475961)
2018-06-29Fix NSB NfVi support for 25 and 40GbpsXavier Simonart1-4/+27
When setting interface_speed option in the test case, NSB/PROX was still considering 100% as 10 Gbps. With this fix, when interface_speed is set to for instance 25 Gbps then NSB/PROX will start generate at 25 Gbps. Yardstick logging info printed on the screen will show performance result as percentage of interface_speed (e.g. 100% will be 25 Gbps). This is done by sending the command "speed 250" to PROX (PROX cannot know the underlying interface speed in all cases e.g. in virtio, and hence considers 100% as 10Gbps). JIRA: YARDSTICK-1217 Change-Id: I4989161b04a7afa5e347935ee7ccef7dfe5a504d Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 1d61af34eb7b35b912d124768ad26eb5f0cd03a8)
2018-06-29Merge "NSB Topology fix for Prox 4 port test case" into stable/fraserEmma Foley14-32/+329
2018-06-29Merge "NSB NFVi BNG test fails to run - stops after one step" into stable/fraserEmma Foley1-4/+16
2018-06-29Merge changes from topic 'prox-stable/fraser' into stable/fraserEmma Foley25-1283/+11008
* changes: NSB NFVi PROX BNG losing many packets NSB NFVi PROX VPE losing many packets Decrease Sampling interval Addition of Configurable Sampling and Configurable Confirmation Retry
2018-06-29Merge "Convert SLA asserts to raises" into stable/fraserEmma Foley46-156/+219
2018-06-28Merge "Extended Context class with get_physical_nodes functionality" into ↵Rodolfo Alonso Hernandez20-77/+473
stable/fraser
2018-06-28Merge "Add "os_cloud_config" as a new context flag parameter" into stable/fraserRodolfo Alonso Hernandez9-27/+101
2018-06-28Merge "Stop running tests from tests/unit" into stable/fraserRodolfo Alonso Hernandez6-56/+10
2018-06-28Extended Context class with get_physical_nodes functionalityChornyi, TarasX20-77/+473
JIRA: YARDSTICK-1255 Change-Id: I446d715dc6cf716a4fcbc1b809c1b1d6303071e0 Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> (cherry picked from commit 595212edf5ccd71af1bf7ef57a8d260fb1ec0c9e)
2018-06-28NSB Topology fix for Prox 4 port test caseAbhijit Sinha14-32/+329
The uplink and downlink interfaces for the 4 port test cases were inconsistent and fixed in this commit. This affects all the 4 port PROX test cases. Tested on: Heat L2fwd-4 and L3fwd-4 test case. JIRA: YARDSTICK-1185 Change-Id: Ia2ce7ed0dc395b812f84ede94e259b42dc833579 Signed-off-by:Abhijit Sinha <abhijit.sinha@intel.com> (cherry picked from commit 8ebd2d3fde473ffcd139090bd688882d4e5e0f44)
2018-06-28NSB NFVi BNG test fails to run - stops after one stepDanielMartinBuckley1-4/+16
JIRA: YARDSTICK-1244 When sending the start or stop command to PROX. We sould not send the same core. We should not send "start 1,1" instead we should send "start 1" Change-Id: Ie600dc3ed808fd00341e92f13bd52199e68dc51f Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit e219f22429ad2e6e6060c5c3440df72e014be273)
2018-06-28NSB NFVi PROX BNG losing many packetsDanielMartinBuckley9-23/+45
JIRA: YARDSTICK-1101 Problem was incorrect generator and changed the traffic profile to allow a tolerated loss of 5%. ARP packets are not managed (just passed thru the system) therefor the tolerated loss must be higehr than normal. Change-Id: I03bd62b397a66b50961e810d033c6894d0b3e9a6 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 48c9e48dcff498c8f51ec507d4107bc658b82d82)
2018-06-28NSB NFVi PROX VPE losing many packetsDanielMartinBuckley6-1169/+10165
JIRA: YARDSTICK-1105 Running a vPE test ends up with up to 25% drooped packets. This is due to tolerated loss being incorrectly configured, test duration was too short and test interval was too short. Note This is due to the fact that vPE use case have by default a tolerated loss of 100%, Now changed to 0.001, same as L2FWD Also: Grafan dashboard has been updated to show all SUT CPUS Utilization in 1 panel. And LINE rate MIN, MAX & TEST Rate have been added Change-Id: I7adae2199b3f656fe460705b6aeb3aa69c767d50 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 39b3d9ae8ff19a0d64bff0e874f05b6dbcc30b01)
2018-06-28Convert SLA asserts to raisesMiikka Koistinen46-156/+219
This commit converts Python assertions to a custom exception in all places where SLA validation is checked with an assertion. This commit also fixes all emerged pylint errors. JIRA: YARDSTICK-966 Change-Id: If771ed03b2cbc0a43a57fcfb9293f18740b3ff80 Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com> (cherry picked from 39f80e9b06395ae1515cfcf08508504ad4dd978a)
2018-06-28Decrease Sampling intervalDanielMartinBuckley4-40/+126
JIRA: YARDSTICK-1219 Currently NSB for NFVI using PROX returns sampling information every 13 seconds. This is too slow. It is required to return sampling information form Generator AND VNF at least every 1 second. This change is depandant on JIRA: YARDSTICK-1212 and YARDSTICK-1220 Change-Id: Ica7ab795a2919d191d8cd846d028e15739e33fb7 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit f8b45aca386ed5852d9568c531ba4595c68cc0e2)
2018-06-28Addition of Configurable Sampling and Configurable Confirmation RetryDanielMartinBuckley7-50/+671
JIRA: YARDSTICK-1221 In order to increase accuracy of result the following are done :- - Improve Measurement Accuracy (YARDSTICK-1212) - Improve Sampling Interval (YARDSTICK-1219) - Allow 4 PROX ports to be read simultaneously (YARDSTICK-1220) This change does the following :- - Stores LINE Rate statistics of Sample - Requires a confirmation retry before deciding to increase or decrease this is configurable. - Allows the user to disable Sampling or specify a sample interval - Added Code Coverage of ProxDurationRunner based on YARDSTICK-1199 Change-Id: I27242ac1849c9a2712866385b5fbc05977c71516 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com> (cherry picked from commit 2e447af9a5a54355aa20028813660d07d1bd2e18)
2018-06-28Add "os_cloud_config" as a new context flag parameterRodolfo Alonso Hernandez9-27/+101
This new parameter will contain the OpenStack cloud specific configuration used by Shade client. This new flag is used only in Heat context. By default, this new parameter (dict) will contain this content: 'os_cloud_config': {'verify': False} This field will be used by HeatStack [1] to create a Shade cloud. Shade retrieves, if not defined, the OpenStack configuration from "os_client_config". This configuration is used to generate the cloud configuration, which is the description of the OpenStackCloud returned. The default parameter defined, "verify", refers to the related bug. By default, in case of using SSL certificate it will not be verified. [1] https://github.com/opnfv/yardstick/blob/b338d3091bb0beb89d4ad9f7c144f43a31a19a74/yardstick/orchestrator/heat.py#L47 JIRA: YARDSTICK-1139 Change-Id: I875a7018401b84e51dab775b8194174645d27e06 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com> (cherry picked from commit 9ae331e1aa1081c3e821512d1940846dfb4063ec)
2018-06-28Merge "Bugfix: HA kill process recovery has a conflict" into stable/fraserJing Lu2-6/+31
2018-06-28Merge "Replace glance delete image with shade client." into stable/fraserRodolfo Alonso Hernandez5-44/+93
2018-06-28Merge "Replace glance create image with shade client." into stable/fraserRodolfo Alonso Hernandez5-78/+171
2018-06-28Merge "Replace cinder detach volume with shade client." into stable/fraserRodolfo Alonso Hernandez5-30/+109
2018-06-28Merge "Replace cinder delete volume with shade client." into stable/fraserRodolfo Alonso Hernandez5-44/+98
2018-06-28Merge "Replace cinder create volume with shade client." into stable/fraserRodolfo Alonso Hernandez5-119/+143