summaryrefslogtreecommitdiffstats
path: root/etc
AgeCommit message (Collapse)AuthorFilesLines
2017-04-06Yardstick virtualenv supportchenjiankun1-0/+33
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-02-17Update missing license headersDeepak S5-0/+40
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-01-19Adding sample yardstick.conf & pod files to help describe the topologyDeepak S2-0/+82
JIRA: YARDSTICK-487 Change-Id:I23dabcf6b4b7d49b8eb0f18778cddd50a1195a05 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2016-12-26Use ConfigParser to write yardstick.confchenjiankun1-13/+12
JIRA: YARDSTICK-474 Currently, I use file.write() method to write config in yardstick.conf. But it is not recommended. So I change to use ConfigParser to write config in yardstick.conf Change-Id: Ia789cf09296afd5d1507bcf99f165378bf87c591 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-10-10Bugfix: no pod.yaml file error when run test case not in the root pathchenjiankun1-0/+0
JIRA: YARDSTICK-364 Change-Id: I8c460064c058f77971140f69689ba638179f89d9 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-09-21get rid of private key in reporexlee87761-27/+0
JIRA: YARDSTICK-356 Change-Id: I1ef7c665f7baa15f61e2bca8c0f0d0e6d0f77248 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-09-05Bugfix: use key_file instead passwork to log onto node in fuel baremetal pod.JingLu51-5/+5
Change-Id: I03101df2aeeebfc7b5f65a8c21c0a462d819e57f Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-08-30Change executed test cases for bgpvpn scenariosjose.lausuch1-0/+43
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-07-29Add zte-pod1.yamlwu.zhihui1-0/+42
JIRA: Yardstick-313 Change-Id: I7dc908e55e9c3c891a525a3285c6ae42a1bcae48 Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-02-23Merge "ipv6-bug-fix: update physical pod yaml configure"qi liang1-4/+10
2016-02-23ipv6-bug-fix: update physical pod yaml configurekubi1-4/+10
due to the configure of huawei sc physical pod has been changed, ipv6 testing failed, so i update the pod.yaml in yardstick to make it run successfully again JIRA: YARDSTICK-186 Signed-off-by: kubi <jean.gaoliang@huawei.com>
2016-02-22Add missing license filesAna C1-0/+10
This change adds missing license information. Change-Id: I2ddc85e3fb7b92a86b8a0f054d4ee177af198c8f Signed-off-by: Ana C <ana.cunha@ericsson.com>
2016-01-26InfluxDB add authentication supportQiLiang1-0/+2
JIRA: YARDSTICK-212 Change-Id: I6b669800160268db70b5c9e43cbbc053576ec4b5 Signed-off-by: QiLiang <liangqi1@huawei.com>
2016-01-21fix some missing license filekubi2-0/+17
fix .coveragerc, etc/yardstick/nodes/pod.yaml.sample etc/yardstick/yardstick.conf.sample Change-Id: Iece74c80316202fb000dda0ea2b3f8fdb6fe5eb8 Signed-off-by: kubi <jean.gaoliang@huawei.com>
2016-01-16modify sc lab pod yaml as real configurekubi2-10/+46
Change-Id: I6587794b7206cb3d5f13b6c448670d1c97ecd596 Signed-off-by: kubi <jean.gaoliang@huawei.com>
2016-01-08support for ipv6kubi1-0/+42
JIRA:YARDSTICK-187 Change-Id: I1cecd400b4449a09d22d43f4a42e889f00dd4fe7 Signed-off-by: kubi <jean.gaoliang@huawei.com>
2016-01-07Initial InfluxDB dispatcherQiLiang1-0/+5
Supports: - Basic influxDB write with timestamp - Add general result format func - Add UT TODO: - refine database schema (e.g. add more tags) plan in another patch JIRA: YARDSTICK-212 Change-Id: I1526568bbd850f1343135420ec59ed1b833bb99f Signed-off-by: QiLiang <liangqi1@huawei.com>
2015-11-13A initial HA test casewym_libra2-0/+70
1)stop an openstack service 2)then monitor the corresponding api and check the availability of it 3)recovery the openstack service JIRA: YARDSTICK-149 Change-Id: Id7b77d2f5c71844729c04f37442c8cfaa270ab12 Signed-off-by: wym_libra <yimin.wang@huawei.com>
2015-11-01Support NodeContext typeQiLiang1-0/+24
Initial NodeContext implementation to support BareMetal, Controller, Compute scenarios. Usage: 0) install yardstick 1) mkdir -p /etc/yardstick/nodes 2) cp <yardstick_repo>/etc/yardstick/nodes/pod.yaml.sample \ /etc/yardstick/nodes/pod.yaml 3) edit /etc/yardstick/nodes/pod.yaml (make show ip, username, ssh key are configured correctly) 4) yardstick -d task start \ <yardstick_repo>/samples/ping-node-context.yaml 5) cat /tmp/yardstick.out Design etherpad link: https://etherpad.opnfv.org/p/yardstick_framework JIRA: YARDSTICK-169 Change-Id: I3f6ade8243e68d88326f23ed213edb32c638ed32 Signed-off-by: QiLiang <liangqi1@huawei.com>
2015-10-15Support general configuration fileQiLiang1-0/+13
Use openstack library oslo_config for parsing configuration options from the command line and configuration files. Refer http://docs.openstack.org/developer/oslo.config/ or rally source code for more info on oslo_config library usage. This patch is initially for test result dispatcher configuration, but it is very general to use. Usage: 0) install yardstick 1) mkdir /etc/yardstick 2) cp <repo_root_dir>/etc/yardstick/yardstick.conf.sample \ /etc/yardstick/yardstick.conf 3) edit /etc/yardstick/yardstick.conf 4) run `yardstick task start xxx` cmd JIRA: YARDSTICK-61 Change-Id: I01677ef6e9ab7c1975aa193799195e850da73478 Signed-off-by: QiLiang <liangqi1@huawei.com>