aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-03-08[bugfix] report generate command print errorrexlee87761-1/+1
JIRA: YARDSTICK-1056 Change-Id: I32ab9ae7482f6b81e00d6d3e7e858d980a2dd95f Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-08Add ODL noHA testcaseDimitrios Markou2-0/+285
This testcase confirms the resiliency of Opendaylight in a noHA deployment SPEC: https://gerrit.opnfv.org/gerrit/#/c/49245/ Change-Id: I810011c35c7bb6377f9295330cf7122d10cf74c3 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
2018-03-08Merge "Allow VMs to access internet"Rodolfo Alonso Hernandez7-4/+62
2018-03-08Update the fuel pod.yamlDimitrios Markou2-1/+22
Fuel except Controller and Compute nodes it deploys an ODL node in noHA and HA deployment and also a Gateway node in a noHA deployment. So it is essential to describe them in Fuel's pod. JIRA: YARDSTICK-1050 Change-Id: Iee6c25c5b2e2e4e661ceb0591bf2437f7f7fa7f8 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.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-07Merge "NFVi Test stops after one hour even if configured context duration is ↵Ross Brattain1-2/+4
longer"
2018-03-07bugfix: fix prepare_env.sh shell quoteRoss Brattain1-2/+2
JIRA: YARDSTICK-1051 Change-Id: If28bc0f2fe2e3cdec95882bb2abedf839e6ac2e0 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-07NFVi Test stops after one hour even if configured context duration is longerDanielMartinBuckley1-2/+4
JIRA: YARDSTICK-1021 If the Test is to take longer than the Default Duration timer use defined test time. If not use Default Duration time Change-Id: Idacc188e199ff031310b9826238b63ed3f2ea409 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2018-03-07Merge "ansible: fix urlsplit('hostname') in convert_openrc"Emma Foley1-1/+1
2018-03-07Merge "Add l2fwd module in Tgen mode"Jack Chan8-0/+1028
2018-03-07Merge "Add test case sample to enable mixed network"Jack Chan1-0/+65
2018-03-07Merge "add opnfv_k8-nosdn-lb_ceph-noha_daily.yaml"Ross Brattain1-0/+18
2018-03-07Merge "[bugfix]tc006 failed due to volume attached to different location ↵Rex Lee2-6/+26
"/dev/vdc""
2018-03-06Merge "Add start service operation"Ross Brattain1-0/+3
2018-03-06add opnfv_k8-nosdn-lb_ceph-noha_daily.yamlRoss Brattain1-0/+18
https://build.opnfv.org/ci/job/yardstick-joid-baremetal-daily-master/2206/console Change-Id: Ib5fc186caa285ef8f6a879fd1fd2f786b07a257a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-06Merge "Move SSH key generation from "init" to "deploy""Emma Foley2-37/+91
2018-03-06Move SSH key generation from "init" to "deploy"Rodolfo Alonso Hernandez2-37/+91
In [1], the Context SSH key generation was modified; the SSH now has a name matching the name context (which depends on the given name and the task ID). In a test suite, the task ID is the same for all test cases executed in the same batch. If the context name of different test cases is the same (there is no impediment, e.g.: "demo", "yardstick"), the SSH key filename will be the same. Currently the SSH key generation is done during the initialization process, at the begining of the test suite executing. If, by coincidence, two test cases have the same context name, the first one will remove the SSH key file during the "undeploy" process; then the second one will rise an exception because the SSH key file is deleted. This patch moves the SSH key file generation from the initialization process to the context deploy process: TEST SUITE: - init: parse all test cases - test case 1: - deploy (generate SSH keys) - run - undeploy (delete SSH keys) - test case 2: ... [1] Id175061d6cfe23a068bb3d12ce176c1f176e8236 JIRA: YARDSTICK-1045 Change-Id: I05dc46db20d2a0cba3092c415ce9b248513406fb Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-06Add start service operationDimitrios Markou1-0/+3
Support the capability to start a service through the operation perspective. JIRA: YARDSTICK-1041 Change-Id: If817f4a522546de2e4a826c1e85b3545e6f3efed Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
2018-03-06Replace assert statements in testsEmma Foley3-21/+21
JIRA: YARDSTICK-966 Change-Id: Ic98711fa1a31d27fcb60bd96b1b3e22b5cca86b3 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-06Allow VMs to access internetJohn O Loughlin7-4/+62
Add option to the config file for default network. Check to see if 1 default network is defined. Enable nat on all defined networks. Add default gateway to VM JIRA: YARDSTICK-1016 Change-Id: Ie943a7c7b4f1a9673774cf8fedaba0af352cd7f4 Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-03-06Merge "Enable heat context to support existing network"Jack Chan9-34/+205
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-05Merge "Bug fix ansible scripts"Ross Brattain1-1/+1
2018-03-05Merge "Error in string format in HeatTemplateError message"Ross Brattain1-1/+1
2018-03-05Error in string format in HeatTemplateError messageRodolfo Alonso Hernandez1-1/+1
There is a missing "s" in HeatTemplateError message [1]. [1]https://github.com/opnfv/yardstick/blob/8400c1895c49cb0c7802692f75d820fb5b8b7dc4/yardstick/common/exceptions.py#L70 JIRA: YARDSTICK-1047 Change-Id: Ieb6fbf0af35d624015dbf34f34de7c7cc9145dd5 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-05Merge "Fix report generation"Ross Brattain1-3/+5
2018-03-05assertTrue(mock.called) -> mock.assert_calledEmma Foley33-92/+92
When checking whether a mocked method has been called, mock.assert_called or mock.assert_called_once should be used, and not unittest.assertTrue(mock.called) This change does this update. It can be verified with: grep -irn "self.assertTrue(.*called)" --exclude-dir=.tox And the replacement was done with: sed -i 's/self.assertTrue(\(.*\).called)/\1.assert_called_once()/g' <list_of_files> Change-Id: I4f26e0c736bf33e0b2413c8e8c33dbdb91f090e2 JIRA: YARDSTICK-865 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-05Bug fix ansible scriptsJohn O Loughlin1-1/+1
For 'qemu-img version 2.10.1' unit 'MB' is not acceptable Changing to 'M' JIRA: YARDSTICK-1019 Change-Id: Ic9153e9e9c85d949d15b1d15cc8cddfad986b4a3 Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-03-05Fix report generationXavier Simonart1-3/+5
The command "yardstick report generate task_id yaml_name" was returning some errors and failing to generate a html report. With this fix an html report will be generated with all data from influx. JIRA: YARDSTICK-1023 Change-Id: If9aab4b85cfb2b5809f608568e1adb2ddeec8b78 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-03-05Merge "prepare_env.sh: fix some shellcheck warnings"Ross Brattain1-14/+15
2018-03-03prepare_env.sh: fix some shellcheck warningsRoss Brattain1-14/+15
prepare_env.sh:13:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:14:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:15:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:16:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:17:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:18:3: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:22:8: warning: Declare and assign separately to avoid masking return values. [SC2155] prepare_env.sh:28:1: warning: INSTALLERS appears unused. Verify it or export it. [SC2034] prepare_env.sh:36:5: warning: Can't follow non-constant source. Use a directive to specify location. [SC1090] prepare_env.sh:42:1: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:46:5: warning: Can't follow non-constant source. Use a directive to specify location. [SC1090] prepare_env.sh:46:12: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:53:5: warning: i appears unused. Verify it or export it. [SC2034] prepare_env.sh:54:27: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:68:25: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:73:19: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:73:49: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:76:27: note: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead. [SC2002] prepare_env.sh:77:24: note: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead. [SC2002] prepare_env.sh:80:46: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:83:46: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:86:46: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:89:43: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:92:43: note: Double quote to prevent globbing and word splitting. [SC2086] prepare_env.sh:96:71: note: Double quote to prevent globbing and word splitting. [SC2086] Change-Id: I96a1f591b825d21e3ba202f1d681449347d940a6 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-02heat: replace neutronclient with shadeRoss Brattain1-7/+6
neutronclient is deprecated and also has bunches of issues with SSL and such. JIRA: YARDSTICK-890 JIRA: YARDSTICK-1032 Change-Id: I41c9aac0ea69e1307560a001f7dc34178fcd7e71 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-02Merge "VNF interfaces are sorted by "vpci" address before being populated"Ross Brattain3-23/+32
2018-03-02Merge "Prohibit the importation of a list of libraries"Ross Brattain8-3/+127
2018-03-02Merge "Layout fixes to test case descriptions"Ross Brattain3-11/+16
2018-03-02Merge "Remove main() and __main__ from tests."Ross Brattain120-701/+1
2018-03-02Add yardstick.benchmark.contexts.heat.HeatContext._delete_key_file()Emma Foley2-7/+13
* Move logic for removing key file into its own method * Update the log message to be more useful JIRA: YARDSTICK-1026 Change-Id: I8c131720ed91c939698c41ad63d586396fcce1fe Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-02VNF interfaces are sorted by "vpci" address before being populatedRodolfo Alonso Hernandez3-23/+32
In [1], VNF interfaces in TG PROX are sorted by "vpci" address, before this value is populated in "vnfd_helper". "vpci_if_name_ascending" is only used in TP ProxPofile [2] to generate the stats. This patch delays this sorting process until the stats generation. [1]https://github.com/opnfv/yardstick/blob/a74ad5a1ec1a73389c5983440b2031b0bc72cea1/yardstick/network_services/vnf_generic/vnf/tg_prox.py#L62-L64 [2]https://github.com/opnfv/yardstick/blob/a74ad5a1ec1a73389c5983440b2031b0bc72cea1/yardstick/network_services/traffic_profile/prox_profile.py#L33 JIRA: YARDSTICK-1044 Change-Id: I988dc48f9a82baa1c64f728d9e6d54f2f4bae010 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-02Remove main() and __main__ from tests.Emma Foley120-701/+1
Removes the unnecessary main() functions from tests. Also removes shebang (#!) where it appears at the top of files. JIRA: YARDSTICK-861 Change-Id: I79180d1eb9c5bce640142dd62ce28c7437c1b210 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-02Merge "Replace assertEqual(None, xx) with assertIsNone(xx)"Abhijit Sinha20-71/+61
2018-03-02Merge "Make files pep8 compliant before replacing assertEqual(None, xx)"Abhijit Sinha3-266/+200
2018-03-02Merge "remove releng from Dockerfile and elsewhere"Emma Foley7-49/+3
2018-03-02Layout fixes to test case descriptionsMika Rautakumpu3-11/+16
Change-Id: I9658b023e4f3db7e22d67c71dfbba61511d981c6 Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>
2018-03-02Replace assertEqual(None, xx) with assertIsNone(xx)Emma Foley20-71/+61
Change-Id: Ie956d8064a8fbcbd3d56c5a79c4c613d35184af4 JIRA: YARDSTICK-942 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-02Make files pep8 compliant before replacing assertEqual(None, xx)Emma Foley3-266/+200
* tests/unit/network_services/helpers/test_samplevnf_helper.py * tests/unit/network_services/traffic_profile/test_rfc2544.py * yardstick/tests/unit/common/test_ansible_common.py JIRA: YARDSTICK-942 Signed-off-by: Emma Foley <emma.l.foley@intel.com> Change-Id: Ib3c71db5f5774d2bfb3a9cbd260b838eb5501448
2018-03-02Merge "Add "render-only" option to "task" command"Rodolfo Alonso Hernandez5-54/+235
2018-03-01Merge "Add ability to reuse existing OpenStack set-up"Ross Brattain4-4/+129
2018-03-01Add "render-only" option to "task" commandRodolfo Alonso Hernandez5-54/+235
This new option provides to the user the ability to output the rendered input files. This option could be useful in case the input files are Jinja2 templates, depending on input arguments. The user can preview the rendered input tasks files without executing them. JIRA: YARDSTICK-1020 Change-Id: Ib15ade7e1adcb29beae5e635fb5d02045c4432bb Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-01Add ability to reuse existing OpenStack set-upEmma Foley4-4/+129
This change adds two optional flags to the context configuration for heat: * no_setup -- to re-use an existing OpenStack deployment * no_teardown -- to skip undeploying the context, so it is available in other testcases In order to achieve this, resource naming had to be made more predictable. When no_setup or no_teardown are set: * Do not add a suffix to context name * When searching, try with and without a suffix to find a server by name All behaviors remain the same unless these values are set. NOTE: This feature doesn't work with the NSPerf scenario, because the interfaces in the VNFs are bound to DPDK after the first test, so the look-up for missing topology information fails in subsequent test runs, as the interfaces are not visable to the kernel. This can be addressed either by either unbinding the interfaces from DPDK at the end of each test, or modifying the look-up for the missing topology information to query DPDK as well. The change will be made in a future patch. JIRA: YARDSTICK-886 Change-Id: I6df5e86e419c283a2bee41917e4f62179aa9c31a Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-03-01NSB: move interface probe to VNF, and attempt driver-only probe firstRoss Brattain18-482/+1068
If no devices are present we can't detect MAC address so we can't match Heat ports to interfaces. If only the driver is missing we can try to probe the driver using lspci. We can use lspci to ask the kernel what driver it should use for the PCI device. If we can't probe at all because the device is already bound, we can use dpkd-devind to find all the PCI address we care about and create a map with PCI device and real kernel driver. Then we can dpdk force rebind to the kernel driver. Once we have rebound to the kernel driver we can detect MAC address and all the other attributes that are required. Fix VnfSshHelper to allow override of wait timeout And a bunch of other refactors that got swept up in this JIRA: YARDSTICK-835 Change-Id: I14cb657ed289a77941d048345d06ced5b5d5da52 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>