summaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2016-12-05Merge "import new _put_file_shell method from upstream rally"Rex Lee1-2/+58
2016-12-05Merge "Bugfix: debug should be default off"Jing Lu1-1/+1
2016-12-01Merge "vsperf: Enhanced vswitchperf configuration"Rex Lee1-5/+5
2016-12-01Merge "ssh.py: add flag to keep stdin open"Rex Lee1-0/+19
2016-11-30import new _put_file_shell method from upstream rallyRoss Brattain1-2/+58
upstream openstack rally added new _put_file_* methods we should use these https://github.com/openstack/rally/blob/0.7.0/rally/common/sshutils.py#L270 Updates: imported rally test__put_file_shell unittests quote to prevent word split use -- guard only chmod on cat success Change-Id: I357d1a66b5beddad8042958f4e55d67fc68929f6 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2016-11-30vsperf: Enhanced vswitchperf configurationMartin Klozik1-5/+5
Original implementation of vsperf specific class was changed to relfect recent vsperf changes. It is now possible to modify any of vsperf's configuration parameters via --test-param CLI argument. It means, that it is possible to write a yardstick TC, which will define all required vsperf configuration inside the YAML TC definition. Vsperf documentation related to yardstick usage and sample TC files are located inside vsperf repository and they were updated by a separate patch. JIRA: VSPERF-422 Change-Id: I978d1c85ffeb3c90d9d47a20c6c0e0f68b437123 Signed-off-by: Martin Klozik <martinx.klozik@intel.com> Reviewed-by: <sunshine.wang@huawei.com> Reviewed-by: <lvjing5@huawei.com> Reviewed-by: <jean.gaoliang@huawei.com> Reviewed-by: <david.j.chou@intel.com>
2016-11-30Bugfix: debug should be default offrexlee87761-1/+1
JIRA: YARDSTICK-398 Change-Id: I8b2f776a9cf6d577150633999354db762fcb93ae Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-11-30Use flask jsonify method to return json resultchenjiankun6-232/+0
JIRA: YARDSTICK-433 Python json lib is very hard to parse when transport via network. Flask jsonfiy is more easier to use. Change-Id: I2afd5238d65bc474170c57d2f9307dc881ea4990 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-30Merge "Create API and command to create a influxDB container"Jing Lu4-0/+124
2016-11-30Merge "Decoupling prepare_env.sh and load_images.sh"Rex Lee2-10/+12
2016-11-30Create API and command to create a influxDB containerchenjiankun4-0/+124
JIRA: YARDSTICK-425 This API is used to create a influxDB Container Add command line to create a influxDB Container, too Change-Id: If9c2d04b779924d492a5d5ea91f7968fa959570e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-29Merge "Move requirement.txt from tests/ci/ to project root path"Rex Lee1-79/+0
2016-11-29Decoupling prepare_env.sh and load_images.shJingLu52-10/+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-28Merge "Create API to get test case result"Rex Lee6-2/+126
2016-11-24Create API to get test case resultchenjiankun6-2/+126
JIRA: YARDSTICK-416 Change-Id: I722566bb0e5bc5288cd6302559e56a3f92ebbeca Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-24Fix the conflict in yardstick.conf between API and CIchenjiankun1-1/+1
JIRA: YARDSTICK-421 In the Docker image, the default dispatcher value in yardstick.conf is local influxDB. But the CI will set another. It will cause a conflict. So I '>' to cover yardstick.conf file. Change-Id: I7088682e952ee7bb84f6872a49a24296d676a9cb Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-24Merge "Upgrade yardstick VM image from Ubuntu 14.04 to 16.04"Jing Lu16-20/+20
2016-11-21ssh.py: add flag to keep stdin openRoss Brattain1-0/+19
For some VNFs we may want to send periodic commands, for example to print statistics, but otherwise not write anything for long periods of time. Currently when we can no longer read from stdin we close it. A workaround is to constantly spam stdin with newlines to keep forcing stdin open. We don't want to have to do this, so add an enable flag to keep stdin open. If the caller wants to close stdin at some point it can. Change-Id: I9496022295dfd19804572e484fe4f170ca7d4ac3 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2016-11-21Create API to run test caseschenjiankun5-0/+193
JIRA: YARDSTICK-413 Change-Id: Ibf58b50b568fae3f2eea985b25ee33be0a3666b7 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-17Move requirement.txt from tests/ci/ to project root pathchenjiankun1-79/+0
JIRA: YARDSTICK-414 Change-Id: I63e4fe1f8cb11ce3d7d94ba999aa3d0597a7c28e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-16Merge "Add os-odl_l2-fdio-ha scenario support"Kubi1-0/+30
2016-11-16Merge "convert networkcapacity to LF"Kubi1-56/+56
2016-11-14Merge "Create a constants.py to manage constant variable consistently"Kubi2-0/+29
2016-11-10convert networkcapacity to LFRoss Brattain1-56/+56
JIRA: YARDSTICK-408 Change-Id: Iec9ce9ac991ee80f9396827c7caf9c7026e11e3f Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2016-11-09Upgrade yardstick VM image from Ubuntu 14.04 to 16.04JingLu516-20/+20
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-11-09bugfix: ipv6 should log in controller node to setuprexlee87761-0/+17
JIRA: YARDSTICK-363 Change-Id: Ic1f2ab98425512014d746a997b7356d3490c6b33 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-11-08Create a constants.py to manage constant variable consistentlychenjiankun2-0/+29
JIRA: YARDSTICK-378 Change-Id: I527d4f60f2a2081730118bdbbea6c19fc093672f Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-04bugfix: tc027 results in tc037 time outrexlee87761-10/+10
JIRA: YARDSTICK-363 Change-Id: Ic0186cd0678277b0b1b04a57a322f6193c1cf52e Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-11-01Add os-odl_l2-fdio-ha scenario supportchenjiankun1-0/+30
JIRA: YARDSTICK-373 Change-Id: Ia06ec788c50098cec0c22c6fb1eec97d7a4c9031 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-10-26Adapt blacklist for Colorado 2.0chenjiankun1-13/+0
JIRA: YARDSTICK-377 Change-Id: Ia8f3c760c0c7e99ce8262c7076a187c45ac0efac Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-10-14influxdb_line_protocol.py should move to 3rd party dirchenjiankun1-1/+1
JIRA: YARDSTICK-369 Change-Id: I286e883d88a47d2befa4bb523ad9384937e079b3 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-10-14Merge "run ipv6 test case on more pods"liang gao1-1/+3
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-11run ipv6 test case on more podsrexlee87761-1/+3
JIRA: YARDSTICK-363 Change-Id: I5f1c8b1f0038619102aa6e446853988093172d9c Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-10-11Provide yardstick-trusty-server.tar.gz for lxd scenarioJingLu55-69/+53
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-10-08Merge "Add raw image support for lxd scenario"liang gao2-0/+49
2016-10-08Add raw image support for lxd scenarioJingLu52-0/+49
JIRA: YARDSTICK-325 This patch adds a ping_lxd_test TC. ping_lxd_test is a dedicated ping test case for lxd scenarios. It uses Cirros LXC 0.3 image to test the image requirement of lxd. Change-Id: I11dce7ee884cfb0f151d3a60daf7ac82226956a3 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-10-08Merge "Decoupling yardstick_verify.sh"liang gao3-203/+238
2016-10-04Merge "ipv6 testcase to support fuel"liang gao2-7/+12
2016-09-29Propose common directory for Docker related filesjose.lausuch3-157/+0
Proposal 3 from this wiki: https://wiki.opnfv.org/display/INF/Docker+handling+in+CI#DockerhandlinginCI-3Dockerfilelocation Do not merge before this: https://gerrit.opnfv.org/gerrit/#/c/22565/ JIRA: RELENG-148 Change-Id: I6fc236688389879fd7f62788eaf77d75dc4730cd Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-29ipv6 testcase to support fuelrexlee87762-7/+12
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-28ipv6 test case to de-coupling to fuel/compassrexlee87761-5/+5
JIRA: YARDSTICK-358 1. plan to support fuel first 2. apex/joid situation will be taken care of in another patch Change-Id: Ia9293a2e925d874cc6182e975f563d92fb91a2c7 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-09-26Decoupling yardstick_verify.shxudan3-203/+238
JIRA: YARDSTICK-360 Change-Id: I9f0b44041a50d3538ffa7fb2941d847808b220ff Signed-off-by: xudan <xudan16@huawei.com>
2016-09-20Merge "compute capacity description adjustment and HT check added"liang gao2-3/+9
2016-09-20Merge "Create reporting config file"liang gao1-0/+20
2016-09-20Merge "Added opnfv_os-odl_l2-fdio-noha_daily.yaml and ↵liang gao3-0/+83
opnfv_os-nosdn-fdio-noha_daily.yaml scenarios along with support for hugepages which is needed for these scenarios"
2016-09-20Create reporting config filechenjiankun1-0/+20
JIRA: YARDSTICK-352 Change-Id: I55c5a584f4d964b4ba1dba12bf6c3a95413020b7 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-09-19Added opnfv_os-odl_l2-fdio-noha_daily.yaml and ↵juraj.linkes3-0/+83
opnfv_os-nosdn-fdio-noha_daily.yaml scenarios along with support for hugepages which is needed for these scenarios JIRA: YARDSTICK-347 Change-Id: Ie4840b328393488fb8e118c3f2cd610d61fdc283 Signed-off-by: juraj.linkes <jlinkes@cisco.com>
2016-09-17compute capacity description adjustment and HT check addedMatthewLi2-3/+9
JIRA: YARDSTICK-270 1)description info amended according to really tested 2)hyper-thread status check added Change-Id: I813a41ff1e55c2d816fa55b773cf6c4bdd2af2bd Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-09-14Modify comment in first line in all test suitechenjiankun24-24/+24
JIRA: YARDSTICK-348 Change-Id: I42751980bb33782da3fa33a9d4f110da153737dc Signed-off-by: chenjiankun <chenjiankun1@huawei.com>