summaryrefslogtreecommitdiffstats
path: root/tests/ci/prepare_env.sh
AgeCommit message (Collapse)AuthorFilesLines
2017-09-29Get node IPs and IDs according to envCatalina Focsa1-15/+11
Extract node IPs and IDs for each node having a controller or compute role (name starting with the "cmp" or "ctl" prefix) and add them into the $pod_yaml file, analogous to the previous implementation. Since node IDs are expected to be unique and integers (condition that does not match the salt node ID format), they are substituted with an incremented index for each controller/compute node in the environment. Change-Id: Id90626edc3f098bd96343336b2be179721dee5a1 Signed-off-by: Catalina Focsa <catalina.focsa@enea.com> (cherry picked from commit 6892687967d2d5ac8db37dd67b3e52d9f775eda6)
2017-07-17Open storperf testcase to huawei-pod2JingLu51-4/+4
JIRA: YARDSTICK-712 Change-Id: If91c936a3a59580a987cb6762db5d063edf6c9d7 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-07Yardstick install storperf updateJingLu51-1/+1
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-03-28yardstick offline supportchenjiankun1-22/+28
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>
2016-11-29Decoupling prepare_env.sh and load_images.shJingLu51-10/+0
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-09-29ipv6 testcase to support fuelrexlee87761-5/+9
JIRA: YARDSTICK-363 1. fuel pod.yaml node id update according to the real environment 2. add constaints to run ipv6 on one fuel physical pod(lf-pod2) Change-Id: I5b91f1bea84f2c79e0b9c3195028e38ddad55363 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-09-09Bugfix: Fix a bug that cause yardstick-trusty-server image build failJingLu51-7/+4
JIRA: YARDSTICK-340 Change-Id: If305308acb76178d5a9a4af9a058e467a1f65a70 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-09-07Bugfix: Fix a bug that cause yardstick-trusty-server image build failJingLu51-1/+4
JIRA: YARDSTICK-340 Change-Id: I0e754df3a6f0869241ae2bdd5d0090182ebcce6b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-09-01Merge "ARM64: Add support for aarch64 architecture"liang gao1-0/+9
2016-09-01Bugfix: correct the path of pod.yamlwu.zhihui1-1/+1
According to https://build.opnfv.org/ci/job/yardstick-fuel-zte-pod2-daily-master/12/console, correct the path of pod.yaml. Change-Id: Ie364e1485b4a26c225062e8817a7d413d8c419fc Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-08-31ARM64: Add support for aarch64 architecturePaul Vaduva1-0/+9
Added support for arm64 architecture so that yardstick framework can be ran on arm-pod1 the armband CI pod. The modifications include testing for presence of arm64 architecture nodes in the pod and running arm64 specific code (building yardstick server image on arm64 version of ubuntu cloud. Openstack doesn't boot 3.13 kernel(arm64) so it was replaced with 3.19 kernel(also arm64), available for vivid cloud image of ubuntu. The Dockerfile for building the ci image was also mofied to add necessary tools for cross-building an arm64 image on amd64 host (the jumpserver) The jira case for this commit is ARMBAND-40. Change-Id: I906d4adbcf2ec2c0f1d695d9916ede42f4151080 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-08-30Change executed test cases for bgpvpn scenariosjose.lausuch1-1/+25
Due to lacking support for floating IPs in ODL VPNService, the default test cases fail. The replaced test cases are: opnfv_yardstick_tc043.yaml(Node ping test) opnfv_yardstick_tc019.yaml(Node HA test) Change-Id: Ib829430e00488697dc7543ea7143026dc68ff834 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-08-21bugfix: storperf not use expectrexlee87761-1/+1
Change-Id: I64af691ef25e61aeaa106e6662152dc46326c3f0 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-08-19BugFix: add scp constraintJingLu51-1/+3
Change-Id: Ide4203cba5b8d62dcb4006c227c850f7ef186ec5 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-08-18BugFix: fix storperf_admin-rc problemJingLu51-0/+3
Change-Id: I187e3e00d38745288f6fccd58ee6bd3d3aea06c9 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-07-30bug_fix tc045 ssh error caused by no id_rsa key filerexlee87761-0/+25
this patch fetch id_rsa when prepare the env JIRA: YARDSTICK-312 Change-Id: I9f172c4ec87a47143a63607dcb4725b86016605a Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-07-22StorPerf integration into Yardstick as a pulgin.Yaoguang Wang1-0/+3
This task will install *StorPerf* on the Jump Host. StorPerf will run in docker container on the Jump Host. JIRA: YARDSTICK-303 Change-Id: Ia592522a169f021adecc7d89d70079980be69665 Signed-off-by: Yaoguang Wang <sunshine.wang@huawei.com>
2016-05-23move /ci into /tests directoryMatthewLi1-0/+54
JIRA: YARDSTICK-269 Change-Id: I2b552aded888fa9d8f8ddd8d902b3d7f6d31a607 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>