summaryrefslogtreecommitdiffstats
path: root/tests/ci
AgeCommit message (Collapse)AuthorFilesLines
2017-09-11Bugfix: cleanup command not foundchenjiankun1-1/+3
JIRA: YARDSTICK-808 This bug is from CI, see log: https://build.opnfv.org/ci/view/yardstick/job/yardstick-joid-baremetal-daily-master/1560/consoleFull The reason is we don not have cleanup function in the script. It is in another script clean_image.sh. so I remove it, and call clean_image.sh when in openstack scenario. Change-Id: I844cd9e8f0b6e1e8ff7a6094be37789d35a2c345 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-08-31Introduced default values and remove unnecessary ones from ansible code ↵Maciej Skrocki1-5/+0
image build code. Change-Id: Id711d6fdacaddeafb8550290503d6cb6c814ea70 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-08-28Kubernetes context adoption when run in CIchenjiankun1-31/+37
JIRA: YARDSTICK-801 We need kubernetes test case run in CI. We have one scenario k8-nosdb-lb-noha for kubernetes. But for now, we need to do some adoption in CI script. Also I move check OS_AUTH_URL in heat.py. Change-Id: Iff86caf77fd74e70469ad2dc43f2238097ce0001 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-08-20remove apexlake-verifyRoss Brattain1-29/+0
Change-Id: I5ac8e5d573c390460e2472c7b3b4649cc78dd295 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-11Merge "yardstick setup ansible, including load_images"Ross Brattain2-0/+56
2017-08-10Merge "pip_license: quick hack script to add license info to requirements.txt"Ross Brattain1-0/+80
2017-08-08yardstick setup ansible, including load_imagesMalanik Jan2-0/+56
also update to cirros 0.3.5 added PROX compilation add create_node_pod_yaml role JIRA: YARDSTICK-639 Change-Id: If5999841287a54c7e5c64a7cc487c6394df90424 Signed-off-by: Malanik Jan <janx.malanik@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-08NSB updateDeepak S2-26/+91
Refactored main NSB VNF classes accroding to class diagram https://wiki.opnfv.org/display/yardstick/NSB+class+diagram All the SampleVNFs have been separated and placed under the SampleVNF class. Added AutoConnectSSH to automatically create SSH conneciton on demand. Added VnfdHelper class to wrap the VNFD dictionary in prepartion for class-based modeling. Extracted DpdkVnfSetupEnvHelper for DPDK based VNF setup. Extracted Stats and other client config to ResourceHelper Had to replace dict_key_flatten with deepgetitem due to Python 2.7 Jinja2 infinite recursion. Change-Id: Ia8840e9c44cdbdf39aab6b02e6d2176b31937dc9 Signed-off-by: Deepak S <deepak.s@linux.intel.com> Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-07pip_license: quick hack script to add license info to requirements.txtRoss Brattain1-0/+80
Change-Id: Ic41772cb32cd53d405b16880bd43cf89307b4716 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31cover.sh: delete .testrepository before running coverageRoss Brattain1-4/+4
When running py27 and py3 test ran into problems with .testrepository already exists, but testr thinking it was corrupt running testr No repository found in /home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master. Create one by running "testr init". error: testr failed (3) The fix seems to be to delete .testrepository before running testr coverage Change-Id: Ib8cd3ab9d3384935380ac29ce365439c6464adc3 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31cover: another 'db type could not be determined' workaroundRoss Brattain1-0/+3
Change-Id: Ib94ff2dfc86725e5367908296b5160f9565442b8 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31cover.sh: workaround 'db type could not be determined' bugRoss Brattain1-0/+3
https://bugs.launchpad.net/testrepository/+bug/1229445 rm -f .testrepository/times.dbm remove that file before running testr Change-Id: I178efefebe600a65d1a28beb9b01f7dfecaa4d00 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-26Merge "Bugfix: supoort insecure mode in checking openstack environment"Jing Lu1-1/+6
2017-07-26Bugfix: supoort insecure mode in checking openstack environmentJingLu51-1/+6
Change-Id: I18346aa177689bc995eb7d4883f4a66383e827ba Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-25update storperf installation in YardstickJingLu52-13/+15
Storper has updated its installaion step. The former used "nginx.conf" is not required any more. Change-Id: I9edd57ae7cffd3a95990844e6b775616d09132f1 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-17Open storperf testcase to huawei-pod2JingLu53-9/+24
JIRA: YARDSTICK-712 Change-Id: If91c936a3a59580a987cb6762db5d063edf6c9d7 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-10Change storperf target IPJingLu51-3/+3
As compass in master use OpenStack Ansible, the former IP "192.168.200.1" for Huawei pod-1 has been deprecated. Change-Id: Ia60885b36abec3455db2aa2939afbe2ef8bd79f5 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-10Merge "Yardstick install storperf update"Jing Lu2-1/+5
2017-07-07Yardstick install storperf updateJingLu52-1/+5
JIRA: YARDSTICK-702 Sicnce StorPerf has switched to use docker-compose to start container suite. The way Yardstick install storperf should also be updated. Change-Id: Idee05703b8ae5cd03bc214f598f56c8ac05ca755 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-05Merge "Use "OS_INSECURE" variable as the insecure mode indicator"Kubi2-2/+2
2017-07-03Yardstick: Aarch64 jenkins slave supportAlexandru Nemes2-4/+12
Change-Id: I2d58c38d75fc1fe036769340e9fb02932f543510 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
2017-06-30Use "OS_INSECURE" variable as the insecure mode indicatorJingLu52-2/+2
Now we use "OS_CACERT" as the insecure mode indicator, it is better to use "OS_INSECURE". Change-Id: I1406193e27510390b4b8fd8f4751d8361560172f Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-06-27Set TEST_DB_URL for storperfJingLu51-0/+1
JIRA: YARDSTICK-692 add the URL for the test results DB to the storperd_admin-rc TEST_DB_URL=http://testresults.opnfv.org/test/api/v1 Also, add metadata JSON to the POST to /job API when creating the job: Change-Id: Ib950f759d80e707bc49d9015bc120d985051f131 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-06-26Bugfix: remove double quote around SECURE variableJingLu52-17/+17
JIRA: YARDSTICK-689 This patch remove the double quote around the SECURE varibale as it may cause the fowllowing error: $ openstack "${SECURE}" image list openstack: ' image list' is not an openstack command. See 'openstack --help'. Did you mean one of these? access token create address scope create address scope delete address scope list address scope set address scope show aggregate add host aggregate create ... Change-Id: Ibb22e85b3dd89b0e3b62821bd5ebe4f155886ffc Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-06-22Merge "HA testcase improvement"Kubi2-17/+29
2017-06-22Merge "bugfix: storperf timeout in ci"Kubi1-0/+2
2017-06-22HA testcase improvementJingLu52-17/+29
This patch improve HA test case in the following aspects: 1. the "GeneralHA" type now will check if the target service process in the controller node. 2. support ignore server certificate 3. add debug log for recovering service failed 4. improve method to kill keystone process Change-Id: I9ae7ab54391fe41d5d7f3e4951a7ac2e3ba75968 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-06-22bugfix: storperf timeout in cirexlee87761-0/+2
JIRA: YARDSTICK-680 Change-Id: Ie405187b8ab085a9e4f40a7e7e7e661c94e83630 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-06-20Configure 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>
2017-06-07Bugfix: load_image will move image file if image already exist in ↵chenjiankun1-6/+0
/home/opnfv/images JIRA: YARDSTICK-678 Currently if yardstick-image exist in /home/opnfv/images, load_image.sh script will not build image, but this script will remove it. We should not remove the image file which user offer. Change-Id: I74ff6717606ff1dd9eacde4142e62d3923394baa Signed-off-by: chenjiankun <chenjiankun1@huawei.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 TC074JingLu52-2/+2
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-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-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-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 Polenchuk2-4/+4
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.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 "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-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-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-20Merge "Bugfix: load_images cleanup, shellcheck fixes"Kubi1-26/+28
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-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>