summaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2017-04-24Merge "standardize ssh auth"Rex Lee39-335/+391
2017-04-23Merge "Add SRIOV support"Kubi5-2/+92
2017-04-18Add SRIOV supportJing Zhang5-2/+92
A generic provider network solution is introduced. To identify whether a network specified in the test case is a provider network new attributes are introduced in the test case network section: networks: test-net: cidr: '192.168.1.0/24' provider: "sriov" physical_network: 'physnet1' If the "provider" attribute is present, the network is an existing provider network. If the value is "sriov", binding:vnic_type=direct is added to the interface in the heat deployment template. In orchestrator/heat.py, the interface creating functions are given a new parameter that tells if the network in use is a provider network. The benchmark/contexts/model.py is changed to store the value of the provider attribute from the test case and function calls to port creation is updated with the provider parameter. The same change is made in contexts/heat.py as well. Also calls for creating a new tenant network is replaced for creating a new provider network if the provider attribute is present. Update-1: Change test_model.py Update-2: Per comment, change comment style to """" Update-3: Change test_heat.py Update-4: Add unit test cases to pass coverage test Update-5: Add SRIOV provider network example in opnfv_yardstick_tc008.yaml Update-6: Per comment, remove empty line in orchestrator/test_heat.py Update-7: Per comment, change comment lines in orchestrator/test_heat.py Update-8: Add more unit test cases to pass coverage test Update-9: Change to create SRIOV provider network on the fly so as to support co-current test runs Update-10: Per comment, init physical_network to 'physnet1' Change-Id: I76004c4fcc9bffcfd8ed021fd647e0cecb346ef4 JIRA: YARDSTICK-612 Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
2017-04-11standardize ssh authRoss Brattain39-335/+391
we need to be following defautl paramiko rules, first use pkey, then key_filenames (autodetecting ~/.ssh/ keys), then password We have too much boilerplate redudant code everywhere, we need to standardize on a factory function that takes a node dict. Using Python3 ChainMap we can layer overrides and defaults. VNF descriptors have to default key_filename, password to Python None. The only way to do this is to omit key values if the variable is not defined, this way the dict will not have the value and it will default to Python None Add python2 chainmap backport Updated unittest mocking to use ssh.SSH.from_node Change-Id: I80b0cb606e593b33e317c9e5e8ed0b74da591514 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-04-06pip install yardstick failed in ApexJingLu52-17/+0
JIRA: YARDSTICK-625 In Apex, yardstick uninstall and install via pip failed. This bug blocks yardstick CI jobs. This patch enables pip install yardstick in editable mode. So the install_yardstick() in yardstick_verify is unnecessary. Change-Id: If290dac5fee5584601064ae9753ae2340643d3ca Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-06Bugfix: fix ubuntu image name typoJingLu51-1/+1
Change-Id: I8722f2ddd096bc784f45d4bcf58ea6a84d319fb2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-05Bugfix: fix query job status in TC074JingLu54-5/+5
JIRA: YARDSTICK-621 The storperf job status query in TC074 didn' work properly. The cause is the "type: status" is not passed in the URL. This patch also update storperf VM image to xenial. Change-Id: Idd9f501416b24612f6045a57ba2a95e2ed3a9572 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-05Merge "Add opnfv_os-ovn-nofeature-noha_daily test suite"Jing Lu1-0/+62
2017-04-05Merge "Yardstick virtualenv support"Jing Lu1-12/+9
2017-04-05Add opnfv_os-ovn-nofeature-noha_daily test suiteJingLu51-0/+62
JIRA: YARDSTICK-624 Change-Id: Ia783bec53e4d889736db7e510d28c32377d4f9b2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-01Merge "yardstick offline support"Jing Lu2-36/+53
2017-04-01Bugfix: take test case modification into effect in load_images.shJingLu51-0/+2
JIRA: YARDSTICK-622 Bug log: https://build.opnfv.org/ci/view/armband/job/yardstick-fuel-armband-baremetal-daily-danube/24/console This error is because the file changes done in the load_images.sh is not updated. After file modification, pip install -U . is required to tack changes into effect. Change-Id: I8be3ffc963e3d5cec861b68a33efc2fa5bdabbd2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-01Yardstick virtualenv supportchenjiankun1-12/+9
JIRA: YARDSTICK-620 Currently we recommend using docker to run yardstick. And it is hard to use virtualenv to install yardstick. So I modify install.sh in yardstick root path. It will support using virtualenv to install yardstick(including API) in linux. In this patch, I make yardstick support read yardstick configuration have priority over constants. Change-Id: I9ea1241b228532a6497451e6c8f232173ddb783e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-31Merge "Store packetsize in influxdb"Rex Lee1-3/+3
2017-03-31Store packetsize in influxdbJing Zhang1-3/+3
This allows calculating throughput in Gbps. Add: test_pktgen.py Change-Id: I7e2132ec71985c14570ef18b952b2264ebf7abbc JIRA: YARKSTICK-611 Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
2017-03-30Bugfix: Add test suite for opnfv_os-odl_l3-ovs-ha_daily scenarioJingLu51-0/+62
JIRA: YARDSTICK-617 Apex has a new scenario 'opnfv_os-odl_l3-ovs-ha_daily' in CI. This patch add yardstick test suite for this scenario. Change-Id: I50eb84fb506e7cf87cbd6bcb67f3df6d185d8b6b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-28yardstick offline supportchenjiankun2-36/+53
JIRA: YARDSTICK-597 Currently yardstick can not run offline. In some case this will block the process, causing yardstick job failed The reason is yardstick will pull the latest code when run in CI. Actually we need not pull the latest code because the code in yardstick is already the latest code. So I remove them. Also I check the environment variable and yardstick-image when fetch openrc file and load images. Change-Id: I797da272932ab5292aa40585c82c119aa71b8849 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-28Merge "Bugfix: Error validating value 'cirros-0.3.5'"Jing Lu1-21/+25
2017-03-28Merge "Bugfix:add storperf flavor for TC074"Jing Lu3-5/+17
2017-03-28Bugfix: Error validating value 'cirros-0.3.5'JingLu51-21/+25
JIRA: YARDSTICK-607 some scenarios come with a Cirros-0.3.5 image, Yardstick's load_images.sh will load a second cirros-0.3.5 image, causing the following error: 2017-03-27 07:42:58,317 yardstick.orchestrator.heat heat.py:449 INFO Creating stack 'demo-2ada98f3' error: failed to deploy stack: 'ERROR: Property error: : resources.ares.demo-2ada98f3.properties.image: : Error validating value 'cirros-0.3.5': No images unique match found for {'name': u'cirros-0.3.5'} This patch fixs this error by skipping load cirros image if there already exist one in the glance. Change-Id: I4d43d82d331f6575efd4560be9b6be175e03cd1b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-27Merge "model: pylint fixes"Rex Lee1-1/+1
2017-03-27Merge "Bugfix:HA test cases rely on dynamic ip addresses in fuel pods"Jing Lu10-10/+30
2017-03-25Bugfix:HA test cases rely on dynamic ip addresses in fuel podsJingLu510-10/+30
JIRA: YARDSTICK-602 change HA test cases to rely on dynamical generated pod.yaml in fuel pods Change-Id: I0efb01489eb2dd94babf1a45bff2fbf6adef5f6e Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-25Bugfix:add storperf flavor for TC074JingLu53-5/+17
JIRA: YARDSTICK-604 the storperf container now uses a flavor called "storperf", if this flavor is absent, stack creating process will fail. also the openstack variables that passed to the storperf container also needs a update Change-Id: Iab4be6491cc9b24526948e5571f0476ec885a93d Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-24Update cirros image to latest versionMichael Polenchuk3-5/+5
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-03-23model: pylint fixesRoss Brattain1-1/+1
remove redundnant parens replace type with isinstance fix import order Change-Id: I0407cbbf6993290f392f17c398827603b5bc1ebd Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-03-23Bugfix: TC002 image error in fuel-arm pod scenariosJingLu51-2/+2
JIRA: YARDSTICK-601 This error is cause because the TC 002 configuration file has been modified in image section, the old sed command in load_images.sh "sed -i 's/image: cirros-0.3.3/image: TestVM/g' tests/opnfv/test_cases/opnfv_yardstick_tc002.yaml samples/ping.yaml" didn't work properly. Change-Id: Ie897213622d05bb267f94b466eb2529e797d484e Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-22Merge "Yardstick: User interface for Yardstick."Jing Lu1-0/+72
2017-03-22Merge "aarch64: Improve arch detection snippet"Jing Lu1-7/+8
2017-03-21Merge "update lxd image disk format for openstack CLI"Jing Lu1-1/+1
2017-03-21Merge "Bugfix: remove vivid as it is EOL"Jing Lu1-1/+1
2017-03-21Merge "add missing test suite files for new scenarios"Jing Lu2-0/+76
2017-03-20aarch64: Improve arch detection snippetMatei Valeanu1-7/+8
Get the arch from a compute node Also move code that depends on YARD_IMG_ARCH, after YARD_IMG_ARCH gets set JIRA: YARDSTICK-591 Change-Id: I5ed3ef9cfa92e5bf9e6ada21396d18643cf1a55c Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
2017-03-20Merge "Add CPU pinning support for node context"Jing Lu1-12/+8
2017-03-20Bugfix: remove vivid as it is EOLRoss Brattain1-1/+1
Vivid is end of life, and thus not supported. Change-Id: Ia293fcd6fd2a3279a642a6dbbb7ad1811334c3e1 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-03-20update lxd image disk format for openstack CLIJingLu51-1/+1
JIRA: YARDSTICK-598 As we have replaced 'glance image-create' command with 'openstack image create' command, we also need to update the disk-format for openstack CLI. the 'root-tar' is no longer a valid choice. (choose from 'ami', 'ari', 'aki', 'vhd', 'vmdk', 'raw', 'qcow2', 'vhdx', 'vdi', 'iso', 'ploop') Change-Id: I53f839f658c5a6f216f5bb942b1c4f4dcdbf9814 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-20add missing test suite files for new scenariosJingLu52-0/+76
JIRA: YARDSTICK-589 Change-Id: I1690d4e2bd741fe1514c8496ee6ff10b72158859 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-20Merge "Bugfix: load_images cleanup, shellcheck fixes"Kubi1-26/+28
2017-03-17Yardstick: User interface for Yardstick.rajesh_4k1-0/+72
Currently Yardstick doesnt have any UI which gives detail analysis of the test-results. This commit generates a HTML page after the execution of a command "yardstick report generate <task-ID> <TC-name>" which intern can be executed after the execution of test-case. Used: Highcharts.js for the graphs. JIRA: YARDSTICK-280 Change-Id: Ic98cc348719f3922bff178f52e7944a4a931763a Signed-off-by: Rajesh K <4k.rajesh@gmail.com>
2017-03-17add missing test suite files for new scenariosJingLu52-0/+178
JIRA: YARDSTICK-589 Some new scenarios, e.g, opnfv_k8-nosdn-nofeature-noha_daily, have been added in the Danube release, test suite files for these scenarios should be added. Change-Id: If3f4ef233b7b1516e182ed28f15feece1728e6d9 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-13Add CPU pinning support for node contextJingLu51-12/+8
JIRA: YARDSTICK-573 Since the yardstick framework now has supported an improved node type context, this patch adds support for VM vcpu pinning ability in the node type context. It provides several scripts that can be used to configurate the controller and compute nodes. Change-Id: If2c6e7b1b85ff78b9d2a5997bf03bdc6877aaf74 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-09Merge "Bugfix: Failed executing command: 'free -s 1 -c 10'"Rex Lee2-15/+36
2017-03-08Bugfix: load_images missing space before =Ross Brattain1-1/+1
load_images.sh arm64 change had issue with shell load_images.sh: line 34: [: amd64=: unary operator expected https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/894/console Change-Id: I14f0b8628db7ac90a4966f85e9e7e27a0e0fae02 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-03-09Bugfix: Failed executing command: 'free -s 1 -c 10'chenjiankun2-15/+36
JIRA: YARDSTICK-585 In CI when run tc070, there is a error: Failed executing command: 'free -s 1 -c 10' Here it is the log: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/runners/duration.py", line 69, in _worker_process method(data) File "/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py", line 126, in run result.update(self._get_mem_usage()) File "/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py", line 116, in _get_mem_usage result = self._execute_command(cmd) File "/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py", line 70, in _execute_command cmd, stderr) RuntimeError: ('Failed executing command: ', 'free -s 1 -c 10',u"free: seconds argument `1' failed\n") And it is a bug of free. the -c option should in front of -s, so change the position will solve this problem. Also it has another bug: 'KeyError', there no 'cached' keyword, so I change it to 'buff/cache'. Change-Id: I0ca16e8d8cc11c6a3b2f364cadbdb3ea367eee53 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-08Bugfix: load_images cleanup, shellcheck fixesRoss Brattain1-26/+28
We should have run shellcheck on this. This is why we don't use the shell, too many obscure gotchas. shellcheck: load_images.sh:25:75: warning: sudo doesn't affect redirects. Use .. | sudo tee -a file [SC2024] sudo echo foo >> /etc/foo won't work, the >> will be run in the current shell, replace with: echo foo | sudo tee -a /etc/foo shellcheck: load_images.sh:47:15: warning: Declare and assign separately to avoid masking return values. [SC2155] replace local cmd='a' with two line version shellcheck: load_images.sh:141:32: error: [ .. ] can't match globs. Use [[ .. ]] or grep. [SC2081] use [[ ]] Change-Id: I14d9768612ea147eaf139603f7eb8753e979ba2c Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-03-08Bugfix: yardstick will create stacks with the same name when run using API ↵chenjiankun1-6/+8
in parallel JIRA: YARDSTICK-575 Currently yardstick will create stacks with the same name when run using API in parallel. The reason is there is a global variable in context base and the core will always deploy the first context in Context.list. When run in parallel, it will run in the one process. So yardstick will deploy stacks with the same name. The solution is do not use Context.list in yardstick core. And using a local variable instead. BTW, if we use API to call yardstick core, we can not config the output way. So I parse yardstick.conf when task start. And I think we can include scenario_cfg, context_cfg, yardstick_cfg in one config object later so that we can get all config in one object. Change-Id: I1ada4ef486bd252e78c3a2e49c6a39b3f8f16a7c Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-08Merge "Add uefi image support for yardstick"Rex Lee1-17/+27
2017-03-03Add uefi image support for yardstickCatalina Focsa1-17/+27
Add support for downloading and building an uefi single part image. Keep three part image support if needed. Keep modifications required for arm64, when using vivid. Install and use parted required for GPT partitioning. Change-Id: I1a9a20701e2fe1f6f644f2c687c5da2e09b69d89 Signed-off-by: Catalina Focsa <catalina.focsa@enea.com>
2017-03-03Merge "Split reporting_target from http_target in yardstick_verify"Rex Lee1-2/+7
2017-03-01Merge "Re-enable floating IP tests for bgpvpn"Rex Lee2-0/+8