summaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2017-06-22bugfix: storperf timeout in cirexlee87761-0/+2
JIRA: YARDSTICK-680 Change-Id: Ie405187b8ab085a9e4f40a7e7e7e661c94e83630 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 6552d3b7b08c3b9dcaa8f44adc31d5028c00e863)
2017-06-21Configure Yardstick flavor to give more RAM to ARM instancesAlexandru Nemes1-1/+1
Yardstick TC005 fails with errors that indicate low memory conditions: "fio: error while loading shared libraries: librbd.so.1: cannot map zero-fill pages" Changing the yardstick flavor to give 1024MB of RAM instead of 512MB made this test case work. JIRA: ARMBAND-275 Change-Id: I2193802082c28edb20004964d2df3780eb5eccb7 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com> (cherry picked from commit 5c8e38667e17059db1c62dd21f868966a6b2a519)
2017-06-20Fix configuration error in TC025tjuyinkanglin1-1/+8
JIRA: YARDSTICK-647 Change-Id: Idc2a87d20a631c37f151cc945de155ef8855e9c3 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn> (cherry picked from commit c076c8372f32a88059783fbc993ab2ebb8967e2e)
2017-06-01Imporve monitor_process pass criteriaJingLu56-17/+17
JIRA: YARDSTICK-660 The monitor func()'s criteria in the monitor_process.py now is whether at least one process of the specific controller node service is recovered. But in reality is more resonable to use whether processes have been recoverd to it's original amount. This patch is aiming at improving the isssue Change-Id: I950ce2a89555801b96092735b0d670e892049927 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit 37921fcd232cd2fbba9f45ef9fa5d8c912f54af6)
2017-06-01fix multi-monitor unitest hangRoss Brattain1-8/+8
need to mock SSH.from_node().execute.return_value because we switch most SSH calls to use from_node() factory function Change-Id: Ibea525c2fcc243d41de8ccbcd40bc98532d69006 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com> (cherry picked from commit 5271e612d427b29c2da84f8417f4192427ae3977)
2017-06-01Merge "increase monitor number in cases." into stable/danubeJing Lu12-0/+32
2017-06-01Merge "Add a new monitor type: MultiMonitor that can run any number of other ↵Jing Lu1-0/+61
monitors at the same time." into stable/danube
2017-06-01Add a new monitor type: MultiMonitor that can run any number of other ↵LiHuan1-0/+61
monitors at the same time. JIRA: YARDSTICK-397 Change-Id: Ic5cb79f0820029e306373abead1ea43fac9abee2 Signed-off-by: LiHuan <lihuanwk@126.com> (cherry picked from commit 747a3260fef52fb5f7da337bc149ec202a05be6e)
2017-06-01Bugfix: change monitor command in tc019JingLu51-1/+1
JIRA: YARDSTICK-655 The original openstack command used for monitoring high availability openstack nova-api service in tc019 is "nova image-list", the "openstack image list" command used in tc019 now may not correctly show the nova-api service status. This is patch swtich the monitor command to "openstack server list". Change-Id: I8810f28b4328ceb4d911a3041a24774ae9cae8f0 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit a5e13df9381c531716b1e41e7a9dedb130fc6e35)
2017-06-01increase monitor number in cases.HuanLi12-0/+32
change cases to multi-monitor mode and improve monitor accuracy. JIRA: YARDSTICK-397 Change-Id: I6840423dd83899b769df76fbee808f9bf5dc4cfd Signed-off-by: HuanLi <lihuansse@tongji.edu.cn> (cherry picked from commit ab7292a8e3060bf6feaa830b156089fa70854664)
2017-05-06Bugfix: Support HA test cases in TripleOJingLu51-1/+1
Change-Id: Ib1f6f45677e66ca88fb546ea0662f52588e9d336 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit 67da8f2ddb5cbf14bbf0df48b10240ba6ebadbe9)
2017-05-04Bugfix: Local Openstack Operation in HA test frameworksdanube.2.RC1danube.2.0tjuyinkanglin2-2/+32
JIRA: YARDSTICK-635 Change-Id: Ic27517714db9325e7a3b1ef623c49af61c36b2b5 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn> (cherry picked from commit 2fb95fbb9380ea7ce92dcb32cd2f0789b9f91bdc)
2017-05-04standardize 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> (cherry picked from commit 99abbb424007da2e01762f3c040a39c0157cbe1f)
2017-05-04Store 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> (cherry picked from commit 639450d91ab409f70b6f119291197da40b1d5f0b)
2017-05-04Modify HA test cases and HA test script to support other installerstjuyinkanglin2-12/+20
JIRA: YARDSTICK-633 Change-Id: I65fd1ba11504dc61485f83c3bcc93bec4d41883b Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn> (cherry picked from commit 27cc0643cf93f4b44c12fbdfcc3e0841d46214c4)
2017-05-04Merge "fix ha issue when run tc050~tc054 in ci" into stable/danubeJing Lu1-3/+3
2017-05-04fix ha issue when run tc050~tc054 in cirexlee87761-3/+3
JIRA: YARDSTICK-634 Change-Id: I46681c7e8afe391eef9c5309470028167e911950 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 71bbbdb18b5f8621b8b4ed9aa0e4fcc1e8882085)
2017-05-04run ha test case in compass podrexlee87761-4/+28
JIRA: YARDSTICK-634 Change-Id: I586d5177598efeda8ac3937d1eb04cd5b97b6ec6 Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 5c4b29189bd69912c9bc356a15a46db764045537)
2017-05-04bugfix: fix HA testcasesJingLu51-1/+1
Change-Id: Ib38e94610a108ff7195cefdfaf048e0f4fd894e8 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit 6604cb5f2d6e3c819cb8488f1ad3468184822cf9)
2017-04-25Bugfix: Make tc019 abd tc025 accept --task-args options to change pod.yamlxudan2-2/+6
JIRA: YARDSTICK-628 Change-Id: I7d1b84232a7477a2854ef1625cc63521999eff65 Signed-off-by: xudan <xudan16@huawei.com> (cherry picked from commit 3f7829f0f28ce4d517ea8654122ee0d686fddf3e)
2017-04-06Merge "Bugfix: fix ubuntu image name typo" into stable/danubeJing Lu1-1/+1
2017-04-06Bugfix: fix ubuntu image name typoJingLu51-1/+1
Change-Id: I8722f2ddd096bc784f45d4bcf58ea6a84d319fb2 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit 571ee6afca03120c393def421eb35a466f9a940b)
2017-04-06Bugfix: 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> (cherry picked from commit b2fb23ca8ccc1acedaa9156552af4ba347f24103)
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> (cherry picked from commit d2cb7ce7331d8da4c3b5b70b09dac49cf65d1710)
2017-04-06Merge "Yardstick virtualenv support" into stable/danubeJing Lu1-12/+9
2017-04-06Yardstick 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> (cherry picked from commit b74d875134b988a26441d559a9e700aaa68d6a0c)
2017-04-06yardstick 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> (cherry picked from commit 38df788fc4a683717a6e7cbd498fad1e7cbe7209)
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> (cherry picked from commit da47f4de9d57f40ecc7cedeac18c0d061bd21c84)
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-03-30Bugfix: 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> (cherry picked from commit 3f70095d15afb86567f885cbfbd89183d857f671)
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> (cherry picked from commit 0e930373273dc76db929e8e885beb97e04636ad2)
2017-03-30Yardstick: 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> (cherry picked from commit 25b21add71fcf7c2c795bd950b5117d69fac68fb)
2017-03-30Update cirros image to latest versionMichael Polenchuk3-5/+5
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com> (cherry picked from commit 043727feabaf7cabb719dbd3d52274bcd0dbea66)
2017-03-28Bugfix: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> (cherry picked from commit 0691766d310e00d7f1cec763427db271076b5633)
2017-03-27Bugfix: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> (cherry picked from commit 6c414e6f46861f71aa68db43ffabcad2305f3f32)
2017-03-25Merge "Add CPU pinning support for node context" into stable/danubeJing Lu1-12/+8
2017-03-23Merge "Bugfix: TC002 image error in fuel-arm pod scenarios" into stable/danubeJing Lu1-2/+2
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> (cherry picked from commit 2fb078e21a3cd0dc69732f33b5a6ecc422eb577d)
2017-03-23aarch64: 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> (cherry picked from commit 13d68ab65475ec556383480a17dbaf63e3ab140c)
2017-03-23Bugfix: 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> (cherry picked from commit 892d2e536e46a6e6427c061931c58f80b542589d)
2017-03-22Bugfix: 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> (cherry picked from commit 14172bb39e8e30f37ec5bb80be6b187ab6858e88)
2017-03-21update 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> (cherry picked from commit d64fbf2f276a98a7cc37d92c57f5b7f3517286b8)
2017-03-21add missing test suite files for new scenariosJingLu52-0/+76
JIRA: YARDSTICK-589 Change-Id: I1690d4e2bd741fe1514c8496ee6ff10b72158859 Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit f7371c36ff26ae9a8f526d0b76d13020a2239a23)
2017-03-20Add 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> (cherry picked from commit f138b480ea4c9954d107555d7a46ec3d4375653f)
2017-03-18add 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> (cherry picked from commit 94d0c6200c8f39988911eedffea703f8b4737fcf)
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: 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