aboutsummaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2018-04-19disable DPDK images for ARMRoss Brattain1-1/+3
We are trying to compile DPDK for the os-nosdn-ovs-ha scenario because we added TC042  "Measure network latency using testpmd and pktgen-dpdk". However it looks like TC042 is only enabled for compass in opnfv_os-nosdn-kvm_ovs_dpdk-ha https://gerrit.opnfv.org/gerrit/#/c/54659/1/tests/opnfv/test_suites/opnfv_os-nosdn-kvm_ovs_dpdk-ha_daily.yaml - file_name: opnfv_yardstick_tc042.yaml constraint: installer: compass pod: huawei-pod1 We don't actually need TC042 and DPDK or os-nosdn-ovs-ha. But in order to run TC042 we have to know beforehand that we are going to use DPDK, so we have a conditional in the load_images.sh script that tries to guess when we will need a DPDK image. The conditional only checks for *[_-]ovs[_-]* if [[ $DEPLOY_SCENARIO == *[_-]ovs[_-]* ]]; then ansible-playbook \ -e img_property="nsb" \ -e YARD_IMG_ARCH=${YARD_IMG_ARCH} \ -vvv -i inventory.ini build_yardstick_image.yml if [ ! -f "${QCOW_NSB_IMAGE}" ]; then echo "Failed building QCOW NSB image" exit 1 fi fi For this release we won't be able to get DPDK images to compile on ARM, we should fix this conditional and not try to compile. Also change the shell glob to match *[_-]ovs_dpdk[_-]* to only enable DPDK images for ovs_dpdk scenarios JIRA: YARDSTICK-1124 Change-Id: I03142e6b8aa00dc9cdf9b446868fb723cd10198b Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-17remove apex lake tc007 from test suitesRoss Brattain4-52/+0
fixes opnfv_os-nosdn-fdio-noha_daily.yaml failures due to missing testcase Change-Id: I5f050d72334da46b94de5fa3662047bf694f7e3e Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-13Bugfix: interface down HA tc050 attack and monitor logistic wrongrexlee87761-64/+17
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-03Bugfix: k8 scenario fixrexlee87762-45/+19
JIRA: YARDSTICK-1109 Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-31ADD tc042 into CIliyin3-0/+31
JIRA: YARDSTICK-1108 We add this test case in ovs_dpdk-ha and ovs_dpdk-noha testsuites also add image build into load_images script Change-Id: I2b0c6b106dd98c3693df18dba46259ff8ef0a76e Signed-off-by: liyin <liyin11@huawei.com>
2018-03-28add new Fraser scenariosRoss Brattain10-0/+304
New scenarios from wiki: https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Statu Change-Id: Ifd6e45e73be2bbb99743aa3f4981d22899aab92a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-23Merge "TC042 bug fix"Ross Brattain1-2/+9
2018-03-23Merge "Test case description and configuration file for ↵Ross Brattain1-0/+78
yardstick_tc090:Control Node Openstack Service High Availability - Database Instances"
2018-03-22Merge "Make Sample VNF hugepages size configurable"Ross Brattain1-2/+20
2018-03-22Merge "update ci pod in the test suite according to Fraser"Rex Lee1-28/+36
2018-03-22Add k8-nosdn-stor4nfv-ha/noha scenariochenjiankun2-0/+0
JIRA: YARDSTICK-1090 We have k8-nosdn-stor4nfv-ha/noha scenario in compass, so we need to add this files to trigger it. Change-Id: I79709c53b8542434f7324ad907fa95b4855839d3 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-03-22update ci pod in the test suite according to Fraserrexlee87761-28/+36
Change-Id: I999b44cc4e0ec1029c6efca224e691298a007689 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-22Merge "fix Dummy test context name"Jing Lu2-1/+2
2018-03-22Merge "Test case description and configuration file for ↵Rex Lee1-0/+59
yardstick_tc091:Control Node Openstack Service High Availability - Heat Api"
2018-03-22fix Dummy test context namerexlee87762-1/+2
more dummy test fix base on I0ccb7e9fabdf6bc2890d2e4763f53baee06c87b2 Since I1447fb5ed447691eaeb0a97f928c0b3333799d07, the context name is a mandatory parameter for every context. JIRA: YARDSTICK-886 Change-Id: I10ee6bcc0507fa90b6e99261a98a96655fc66947 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-22Merge "Add k8-nosdn-stor4nfv-ha/noha scenario"Jack Chan2-0/+36
2018-03-21TC042 bug fixliyin1-2/+9
JIRA:YARDSTICK-786 yardstick DPDK image have problems to build. We will fix this by using nsb image the pktgen DPDK testcase will use sampleVNF image Change-Id: I24b7b6a9acfe21ec956fa9c4ee7ebe7ae1787dbb Signed-off-by: liyin <liyin11@huawei.com>
2018-03-21Add k8-nosdn-stor4nfv-ha/noha scenariochenjiankun2-0/+36
JIRA: YARDSTICK-1090 We have k8-nosdn-stor4nfv-ha/noha scenario in compass, so we need to add this files to trigger it. Change-Id: Iefa3a83407bff7d3c1de1959f35b6d8e5eecd145 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-03-21Bugfix: update test case base on node parameters in cirexlee877644-125/+125
JIRA: YARDSTICK-1082 Change-Id: I00080d0317a54b73a6cd571198e9446962c11b5a Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-20Merge "Add "YARDSTICK_REPO_DIR" into tests path"Ross Brattain1-1/+1
2018-03-20Add "YARDSTICK_REPO_DIR" into tests pathting wu1-1/+1
In the CI flow, script "load_images.sh", variable ${YARDSTICK_REPO_DIR} needs to be added in front of tests path to avoid the error: sed: can't read tests/opnfv/test_cases/*: No such file or directory This fix is specific to arm64 JIRA: YARDSTICK-1086 Change-Id: If19b295233bb7313226dae70df016ad236bed2ac Signed-off-by: ting wu <ting.wu@enea.com>
2018-03-20update scenario test cases according to gating releaserexlee87761-67/+75
JIRA: YARDSTICK-1046 Change-Id: I12223876d1cf1f3e45152f6b7996b75a66b16fe6 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-19Bugfix: storperf fails on ci when install pluginrexlee87761-2/+2
JIRA: YARDSTICK-1060 Change-Id: I6356bf16c547a1bd15f83f3ff6390822b7980f28 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-16Merge "Add ODL noHA testcase"Ross Brattain2-0/+285
2018-03-16Merge "Replace assert statements in tests"Abhijit Sinha1-1/+1
2018-03-16Test case description and configuration file for yardstick_tc090:Controltjuyinkanglin1-0/+78
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/+59
Node Openstack Service High Availability - Heat Api JIRA: YARDSTICK-961 Change-Id: I49fc2b2d8fc4fa090a74f1838f5ac386e39eaf49 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2018-03-14Add "YARD_IMG_ARCH" input variable to "build_yardstick_image.yml"Rodolfo Alonso Hernandez1-0/+1
"YARD_IMG_ARCH" variable is added as input parameter to "build_yardstick_image.yml" ansible script, in order to generate the correct image for the running architecture. JIRA: YARDSTICK-1058 Change-Id: I33954c236695478eaae34fcfca2e9d5b40791bbf Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-12Merge "Update the fuel pod.yaml"Ross Brattain1-1/+9
2018-03-09Do NOT hardcode interface speed for PROX testsDanielMartinBuckley1-11/+19
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-09Make Sample VNF hugepages size configurableRodolfo Alonso Hernandez1-2/+20
The amount of hugepages claimed for a Sample VNF is always 16GB. This value is excesive for most of the Sample VNF applications (except for vPE). Making this parameter configurable we allow to spawn smaller VMs by using less hugepages (in case of StandAlone and OpenStack deployments). Because this parameter depends on the Scenario and the type of VNF executed, the parameter is located in: scenarios: {options: hugepages_gb} # number of GB of hugepages claimed PENDING: document this new parameter. A new userguide section should be created to document all "scenario" sections and parameters. JIRA: YARDSTICK-1061 Change-Id: I6f082e105289bd01781be18f2fecbe0ba2fdfdee Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.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-08Update the fuel pod.yamlDimitrios Markou1-1/+9
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-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-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-06Replace assert statements in testsEmma Foley1-1/+1
JIRA: YARDSTICK-966 Change-Id: Ic98711fa1a31d27fcb60bd96b1b3e22b5cca86b3 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
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-02Merge "VNF interfaces are sorted by "vpci" address before being populated"Ross Brattain1-4/+17
2018-03-02VNF interfaces are sorted by "vpci" address before being populatedRodolfo Alonso Hernandez1-4/+17
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 Foley28-69/+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 Sinha14-62/+52
2018-03-02Merge "Make files pep8 compliant before replacing assertEqual(None, xx)"Abhijit Sinha2-265/+199
2018-03-02Merge "remove releng from Dockerfile and elsewhere"Emma Foley1-25/+3
2018-03-02Replace assertEqual(None, xx) with assertIsNone(xx)Emma Foley14-62/+52
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 Foley2-265/+199
* 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-01NSB: move interface probe to VNF, and attempt driver-only probe firstRoss Brattain4-33/+417
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>
2018-03-01remove releng from Dockerfile and elsewhereRoss Brattain1-25/+3
Current CI does openrc fetching before starting the Docker container and then passes openrc via Docker mount JIRA: YARDSTICK-691 Change-Id: Id0649130f48db5a5586149b237c5252b953e57be Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-01vFW scale-up template.Mytnyk, Volodymyr1-1/+16
Added topology and traffic profile templates Added support for using JinJa2 templates in topology definition Added support for static pipeline configs for SampleVNFs JIRA: YARDSTICK-1043 Change-Id: Iab99fd5b5ad69ca32ee70b9fe47779387ad27e7f Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
2018-03-01Add arguments to the traffic profile renderRodolfo Alonso Hernandez2-62/+6
In order to render configurable traffic profiles in NSB test cases, a new variable is introduced: "extra_arg". The content of this variable is added to the VNFD render data, under a key called "extra_args". This will allow the user to define Jinja templates for traffic profiles. E.g.: $ cat test_case_definition.yml scenarios: - type: NSPerf traffic_profile: traffic_profile.yml extra_args: vports: 10 $ cat traffic_profile.yml {% set vports = get(extra_args, 'vports', '0') or 4 %} {% for vport in range(vports|int) %} uplink_{{vport}}: data... {% endfor %} JIRA: YARDSTICK-946 Change-Id: Ib3c1f2d89efa012772edf2156e97d5f4742a6b80 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-01Import "traffic_profile" modules only onceRodolfo Alonso Hernandez7-55/+66
"traffic_profile" modules should be imported only once. Every time TrafficProfile.get is called, the modules under "yardstick.network_services.traffic_profiles" are loaded [1]. Instead of this, the modules should be registered only once the first time "yardstick.network_services.traffic_profiles.base" is loaded. This will reduce the execution time and will avoid unnecessary calls. [1] https://github.com/opnfv/yardstick/blob/d2c7cc4e9768ed003257a95c92cdb278d516761b/yardstick/network_services/traffic_profile/base.py#L36-L37 JIRA: YARDSTICK-951 Change-Id: Ia3565378ba3a1377fcb0aea8bda50ef8189414fd Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>