aboutsummaryrefslogtreecommitdiffstats
path: root/etc
AgeCommit message (Collapse)AuthorFilesLines
2018-01-24Check RS for virtualized OpenStack/YardstickStepan Andrushko1-0/+34
Draft for env requirements reading and validation Script can be run from tools/virt_ci_rampup.sh. First requirement file is parsed/stored. This file must be created in ahead and named as 'infra_deploy.yaml'. Then separate ansible role is used to validate resources. Ansible-role fails if there is not enough resources on the host for cpu, ram, disk space. JIRA: YARDSTICK-945 Change-Id: I86cd4bdc963de3aa51392fc73a239cbd426bc64a Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
2018-01-04delete obsoleted zte pod infozhihui wu1-50/+0
Delete zte pod info in yardstick/etc/yardstick/nodes. Change-Id: Ie22fd9fa4b84529f0b2a7d113776d3559106e67a Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2017-10-18Adding sample trex exampleDeepak S1-0/+38
Change-Id: I3b79d33dba5cc559634122a135ff469f054214fc Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-17Merge "fix invalid chracters in ansible scripts"Ross Brattain1-9/+9
2017-10-15Adding sample multi-port ansible scriptDeepak S1-0/+37
- trex - ixia - ixia correlated Change-Id: I7d1414227c27c2bb03454eac94592e07c434f070 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-15fix invalid chracters in ansible scriptsDeepak S1-9/+9
Change-Id: I3d1a491e4c0f0554a861d9bb24fbd0ac94835759 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-12collectd: set intel_pmu events path and OVS socket pathRoss Brattain1-2/+6
switch from hardcoded path to dynamic path based on bin_path also enable proxy for install_collectd add barometer settings for virt and ovs_stats Change-Id: Id138aef548332a3e3fcb3963b746e7c9f10c0948 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-10-05Merge "Adding scale out templates for ovs_dpdk/sriov using 2 node setup"Ross Brattain2-0/+44
2017-10-05Merge "Adding 2 node ixia generic scale-out test case generation"Ross Brattain1-0/+54
2017-10-05Merge "Adding auto generate scale-out support for correlated traffic"Ross Brattain1-0/+77
2017-10-03Adding sample testcases to run on standalone contextDeepak S6-0/+165
- vFW - vCGNAPT - vACL - UDP Replay - vPE (Only OVS supported) Change-Id: Idbc4d1d6bc1283e40d2fcb9457a871a9198ad147 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding auto generate scale-out support for correlated trafficDeepak S1-0/+77
Change-Id: I2755b596068545c1a3a672ceff47d814a44ae050 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding 2 node ixia generic scale-out test case generationDeepak S1-0/+54
Change-Id: I7da2d5bcd7c58c669e28a7271e4c6848c003e84a Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding scale out templates for ovs_dpdk/sriov using 2 node setupDeepak S2-0/+44
2 - node setup: - Traffic generator starts new stream on both uplink and downlink This patch addes amsible scripts to enable scale_out testcases - vfw Change-Id: I0340636bce3e74cd6175f728b9e7e014a4eb2fd5 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-02add collectd resource node capabilityRoss Brattain1-0/+25
allow manually adding collectd nodes using Node context. if a node is present with a collectd config dict then we can create a ResourceProfile object for it and connect to collectd. example nodes: - name: compute_0 role: Compute ip: 1.1.1.1 user: root password: r00t collectd: interval: 5 plugins: ovs_stats: {} Change-Id: Ie0c00fdb58373206071daa1fb13faf175c4313e0 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-29bugfix: tc054 default value is wrongrexlee87761-0/+22
management route ip is not common in most SUTs, so it should be removed. also huawei pod1 ipmi info should updated so this test case can be added into ci later Change-Id: I3a29c59c473ee7087d4d61753ffc955b061571fb Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-08-24Standardized TRex client library pathMaciej Skrocki1-0/+1
- path should be defined via TREX_CLIENT_LIB environmental variable e.g. TREX_CLIENT_LIB=/opt/trex_client/stl - refactored unit tests Change-Id: I18767e48daf774432c010f1b88d18a4f0ee4e156 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-12Move the comment above the config parameter line to avoid the expectionDeepak S1-1/+2
Traceback (most recent call last): File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/cmd/commands/task.py", line 54, in do_start result = Task().start(param, **kwargs) File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/core/task.py", line 148, in start self._do_output(output_config, result) File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/core/task.py", line 227, in _do_output dispatchers = DispatcherBase.get(output_config) File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/dispatcher/base.py", line 46, in get for out_type in config['DEFAULT']['dispatcher']] File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/dispatcher/base.py", line 38, in get_cls raise RuntimeError("No such dispatcher_type %s" % dispatcher_type) RuntimeError: No such dispatcher_type Http # setup multiple dipatcher with comma deperted e.g. file Change-Id: I497d0d9ce7fdb7ea2913af6ebeb4bb9008344fed Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-08-08IXIA traffic generatorDeepak S1-0/+90
Change-Id: I09bcb3f2c4b945283070d442589d3bf00468abbc 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-07-28Merge "Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migration"Rex Lee1-0/+5
2017-07-27Adding support for multi-dispatcherDeepak S1-1/+1
JIRA: YARDSTICK-684 This patch adds the support to enable multi-dispatcher of result. e.g. [DEFAULT] debug = False dispatcher = file, http Change-Id: Id0e1a1bba14edd899fcf5b275be1f0a091b6db77 Signed-off-by: Deepak S <deepak.s@linux.intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-26Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migrationchenjiankun1-0/+5
JIRA: YARDSTICK-174 This live migration test case is based on share storage, default share storage is enabled. This test case will do some config work. And do live migration and calculate the migration time and downtime. Change-Id: I6601601edebdd0ac6434ba632b1eba9e9bd4fda0 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-06-07Fix configuration error in TC025tjuyinkanglin1-0/+50
JIRA: YARDSTICK-647 Change-Id: Idc2a87d20a631c37f151cc945de155ef8855e9c3 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2017-04-01Yardstick 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>
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>