aboutsummaryrefslogtreecommitdiffstats
path: root/tests/ci/load_images.sh
AgeCommit message (Collapse)AuthorFilesLines
2017-10-08Update load_images.sh to MCP@aarch64Cristina Pauna1-33/+9
The load_images.sh script still contained old functionality. The changes are: - don't use TestVM anymore, MCP does not load that by default like Fuel did upload the cirros image instead - don't upload the kernel separately for aarch64, one part image works now - add the needed extra-properties accordingly to each image The script was tested on arm, the test are running now without errors JIRA: ARMBAND-285 Change-Id: Iee8ce6cde43bebceb2edbb1310ea81c665876aff Signed-off-by: Cristina Pauna <cristina.pauna@enea.com> (cherry picked from commit af71c468fe83a5149e0e18cdb233e059302209e3)
2017-10-02load_images.sh: Add missing ssh_optionsAlexandru Avadanii1-0/+1
Empty ssh_options led to ssh login failure, which stopped the whole script. Change-Id: I8374a30a02b14d04eb0f623a0c58d7ebed77a589 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit 77c7d358bc6a61e2a5c24c6056cc3e40561f27c7)
2017-09-30Adapt getting the image architecture to mcpCristina Pauna1-4/+7
The part which gets the image architecture still uses the old fuel command. Adapted the script to use the mcp command. JIRA: ARMBAND-285 Change-Id: Iddce77c3a856ea11f9994861151db89a402e735e Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-07-05Merge "Use "OS_INSECURE" variable as the insecure mode indicator"Kubi1-1/+1
2017-07-03Yardstick: Aarch64 jenkins slave supportAlexandru Nemes1-3/+11
Change-Id: I2d58c38d75fc1fe036769340e9fb02932f543510 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
2017-06-30Use "OS_INSECURE" variable as the insecure mode indicatorJingLu51-1/+1
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-26Bugfix: remove double quote around SECURE variableJingLu51-12/+12
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-22HA testcase improvementJingLu51-12/+18
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-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 ApexJingLu51-2/+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 TC074JingLu51-1/+1
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 Lu1-14/+25
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 supportchenjiankun1-14/+25
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 Lu1-1/+8
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 TC074JingLu51-1/+8
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 Polenchuk1-3/+3
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-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-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>
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-02-14load_images: update flavor for _ovs_ scenariosMaryam Tahhan1-1/+1
Update the nova flavor used for the following scenarios: * os-nosdn-kvm_ovs_dpdk_bar-ha * os-nosdn-kvm_ovs_dpdk-ha without interfering with older scenario os-nosdn-ovs-noha. Change-Id: Id641e57a5f41413a891d4335ce2d119a5e8088e9 Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
2016-12-20Replace heat, keystone and nova command with openstack commandJingLu51-22/+25
JIRA: YARDSTICK-486 In future Openstack release, 'heat', 'keystone', 'nova' command will be deprecated. So we need to use 'openstack' command instead. Change-Id: I7070f8aaf0d235705b65e0760c845f843ad79719 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-11-29Decoupling prepare_env.sh and load_images.shJingLu51-0/+12
JIRA: YARDSTICK-430 The "prepare_env.sh" and “load_images.sh” have serious dependency. The “load_images.sh” uses the "YARD_IMG_ARCH" variable which is defined in the "prepare_env.sh" to choose the base ubuntu image version. We want to decoupling these two scripts, so they can be invoked separately. Change-Id: I30c1b4a65f73b1550fa5eb96366fe8b1d59251d7 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-11-09Upgrade yardstick VM image from Ubuntu 14.04 to 16.04JingLu51-4/+4
JIRA: YARDSTICK-365 This patch upgrades the base Ubuntu version of Yardstick VM image from trusty(14.04) to xenial(16.04). If you still want to use Ubuntu 14.04 to build Yardstick custom image you can use command: sudo ./tools/yardstick-img-modify tools/ubuntu-server-cloudimg-modify.sh trusty And now the "yardstick-trusty-server" is rename as "yardstick-image". Change-Id: I0765f3aee2d17eea1ad2257d0f576cdb9ef2b18d Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-10-14Bugfix: fix a bug in lxd scenarioJingLu51-2/+2
JIRA: YARDSTICK-325 Change-Id: I6e3aaeb3070c97ab306848b0e7fdc568a486663e Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-10-11Provide yardstick-trusty-server.tar.gz for lxd scenarioJingLu51-20/+40
JIRA: YARDSTICK-325 This patch removes ping_lxd_test.yaml and changes vm image used for lxd senarios. In the *-lxd-* scenariois, Cirros LXC 0.3 image will be used for Ping test case. For yardstick generic test, a dedicated yardstick vm image will be used. Change-Id: I5f9e7a92e3e5dded0014baec77085d80cc904b52 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-09-26Decoupling yardstick_verify.shxudan1-0/+205
JIRA: YARDSTICK-360 Change-Id: I9f0b44041a50d3538ffa7fb2941d847808b220ff Signed-off-by: xudan <xudan16@huawei.com>