aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-03-08Bugfix: yardstick will create stacks with the same name when run using API ↵chenjiankun13-150/+166
in parallel JIRA: YARDSTICK-575 Currently yardstick will create stacks with the same name when run using API in parallel. The reason is there is a global variable in context base and the core will always deploy the first context in Context.list. When run in parallel, it will run in the one process. So yardstick will deploy stacks with the same name. The solution is do not use Context.list in yardstick core. And using a local variable instead. BTW, if we use API to call yardstick core, we can not config the output way. So I parse yardstick.conf when task start. And I think we can include scenario_cfg, context_cfg, yardstick_cfg in one config object later so that we can get all config in one object. Change-Id: I1ada4ef486bd252e78c3a2e49c6a39b3f8f16a7c Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-08Merge "Add uefi image support for yardstick"Rex Lee3-54/+77
2017-03-03Add uefi image support for yardstickCatalina Focsa3-54/+77
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-03-03Merge "Split reporting_target from http_target in yardstick_verify"Rex Lee1-2/+7
2017-03-02env prepare check openrc already sourcedrexlee87761-5/+11
env prepare should check if openrc is sourced before using os_fetch_utils to fetch openrc JIRA: YARDSTICK-577 Change-Id: I0efb0bae3b408156b1133812c29583ab8c58d94b Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-03-01Merge "fix: remove headers from generated files"Kubi3-27/+1
2017-03-01Merge "heat: replace dict key checking with .get()"Kubi1-9/+6
2017-03-01Merge "Re-enable floating IP tests for bgpvpn"Rex Lee2-0/+8
2017-02-28Split reporting_target from http_target in yardstick_verifychenjiankun1-2/+7
JIRA: YARDSTICK-576 Currently the reporting_target reuse the http_target. But if we want to custom reporting_target, the http_target is also change, and the yardstick result will store in mongoDB. So I add reporting_target to split them. Change-Id: Ib0e4e8ec9a55f49027f9776931fdaa7dc194654b Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-28stream default INFO, filehdr default DEBUGrexlee87762-17/+9
The DEBUG log can be stored as file and pushed into artifacts. Default sys.out level should be INFO. Stream level can be changed to DEBUG if cli "-d" is enabled. remove "-v" since it's not useful for a test framework JIRA: YARDSTICK-507 Change-Id: I3caafd31a2caac73b0e3f33c2762c090e76c707e Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-02-28Re-enable floating IP tests for bgpvpnRomanos Skiadas2-0/+8
Change-Id: I46e4e21787a9b0a3104b2a684d62f50681258205 Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
2017-02-26heat: replace dict key checking with .get()Ross Brattain1-9/+6
We init all the fields to None, so the default value is None, which is what .get() returns when the key is not present it the dictionary. Replace if key in dict: self.val = dict[key] with self.val = dict.get(key) This also has the added beneifit of re-initializing default values to None. In idiomatic Python we do not check a dictionary twice if we can avoid it. Either use dict.get() with a default value or catch the KeyError and do the correct thing. Change-Id: If8d1caeb7288f888f02622d62e8db9f59f50717a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-02-26fix: remove headers from generated filesRoss Brattain3-27/+1
experiment_[12].yaml are generated from templates during the unittest, so they will be overwritten. yardstick/vTC/apexlake/tests/data/generated_templates/vTC.yaml was submitted by Vincenzo Riccobene in gerrit https://gerrit.opnfv.org/gerrit/#/c/11333/ so assign copyright to Intel instead of invalid user@TRAFCLASS-PACKET1.fuel.local Change-Id: If516037c4f4c859e417ca12e6d5300e4e0a3817c Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-02-27Merge "BugFix: Adopt to latest result structure while parsing the results"Rex Lee2-4/+6
2017-02-27Merge "ci in huawei-pod1 do not run test case after tc074"Rex Lee1-1/+5
2017-02-27Merge "BugFix: update to paramiko 1.18.0 to fix TypeError"Kubi1-1/+1
2017-02-26heat context support affinity and anti-affinityrexlee87765-18/+91
JIRA: YARDSTICK-566 Current Heat context support affinity and availability arguments but not support affinity and anti-affinity. Enhance Heat context to support affinity and anti-affinity: 1. can create heat server group with affinity/anti-affinity 2. each server could be specified which server group they are in Change-Id: I46e7376fd116c6e109cb5dcb1c168460918e6d43 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-02-24Add common method of openstack in openstack_utilschenjiankun4-35/+361
JIRA: YARDSTICK-569 We have much redundancy code when using nova/neutron/glance... python client. So I write this code in openstack_utils for calling. Change-Id: I322b7577de4933246a15e6742ae5a28bea16eb02 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-23Merge "Update missing license headers"Rex Lee192-0/+1666
2017-02-23Merge "improving if conditions :)"Rex Lee2-5/+5
2017-02-23Merge "collectd: typo and call super()"Rex Lee1-1/+2
2017-02-23Merge "Add python-pip & flake8 package to install.sh"Rex Lee1-0/+2
2017-02-22BugFix: update to paramiko 1.18.0 to fix TypeErrorRoss Brattain1-1/+1
with python 3 there is a paramiko error due to .keys() usages in python 3 File "python3.5/site-packages/paramiko/ssh_exception.py", line 166, in __init__ body = ', '.join([x[0] for x in addrs[:-1] TypeError: 'dict_keys' object is not subscriptable paramiko 1.16.0 tries to index addr.keys() but addr.keys() is not a dict view in Python 3 and not a list so we need to convert .keys() to a list, using sorted() This was most recently fixed in https://github.com/paramiko/paramiko/commit/0411010d55755913fa7bd5b0a9c719c8548549f4 which should be in paramiko 1.18.0 Change-Id: I6b10664611cab3b21d3aa33ecf1343ff134f59a1 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-02-22Merge "add grafana dashboard for os-nosdn-nofeature-ha"Jing Lu1-0/+5535
2017-02-21add grafana dashboard for os-nosdn-nofeature-harexlee87761-0/+5535
JIRA: YARDSTICK-401 Change-Id: Ibe8eaaf6bf9d283e51ee3fb2a3062344179a11c6 Signed-off-by: rexlee8776 <limingjiang@huawei.com> Signed-off-by: root <limingjiang@huawei.com>
2017-02-22Create Grafana dashboards according config file under root_path/dashboardchenjiankun1-4/+9
JIRA: YARDSTICK-570 Currently we only create ping Grafana dashboard when create Grafana docker container. Actually we need to create some default dashboards. Change-Id: Icee975ad8c1c960b27625274c775f1716edfa03e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-21bottlenecks: stress ping yaml file bug fixliyin1-3/+0
JIRA:YARDSTICK-565 This will remove the limit of "sla" The "sla" will cause a error of bottlenecks. so this patch will change it, so bottlenecks could find the system bottleneck. Change-Id: I8634e34841677a2032cebd26f1b40f6a0cb2bd39 Signed-off-by: liyin <liyin11@huawei.com>
2017-02-21ci in huawei-pod1 do not run test case after tc074chenjiankun1-1/+5
JIRA: YARDSTICK-568 https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/814/consoleFull the test case tc075 and tc027 after tc074 does not run in the ci, which is not correct. the logs shows the suite quit after tc074 finishes. The reason is: In this patch: https://gerrit.opnfv.org/gerrit/#/c/26763/ I add a task_id to the context name, but in tc074, it do not have a name. It will cause a keyError. Change-Id: I09608675d9dadcc3ff0d825ca63db3be5e414120 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-21improving if conditions :)Deepak S2-5/+5
Change-Id: I2fad46b07b252f898acfe116dd6542946b8a26a8 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-02-20Merge "Docs: Adding preliminary documentation for Network Service Benchmarking."Kubi9-11/+452
2017-02-18Add python-pip & flake8 package to install.shDeepak S1-0/+2
On a fresh system, we need "python-pip & flake8" to run yardstick. Adding same to install.sh Change-Id: I3e13ffdf53eed7e976e55e2b23afd1b1ea50ec33 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-02-18Docs: Adding preliminary documentation for Network Service Benchmarking.Deepak S9-11/+452
This patch adds overview & installation instruction to get started on VNF testing. Change-Id: I73c9616d7154f701f542ff9a49c32a9516902ff4 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-02-18Merge "yardstick ping testcase yaml update"Kubi1-0/+58
2017-02-17Update missing license headersDeepak S192-0/+1666
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-02-17Merge " add scenario to solve apex ci fail"Kubi1-0/+21
2017-02-17Merge "solve apex ci problem (new scenario)"Kubi1-0/+21
2017-02-17Merge "tc076 rst documentation"Kubi2-0/+62
2017-02-17 add scenario to solve apex ci failrexlee87761-0/+21
due to https://gerrit.opnfv.org/gerrit/#/c/27605/ os-odl_l2-bgpvpn-ha in apex has already been renamed to be os-odl-bgpvpn-ha, so add a new one. Change-Id: I167bf295b67b2dddbd3da2aa5a2dca666b3fa152 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-02-17solve apex ci problem (new scenario)rexlee87761-0/+21
new scenario os-odl-gluon-noha in apex pod Change-Id: I0151ce227e2a3ff476044f0b5c8d4ed61d20b21a Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-02-17yardstick ping testcase yaml updateliyin1-0/+58
JIRA:YARDSTICK-565 this patch will add a yaml file to sample floder. This yaml will as the yaml file of bottlenecks stress test. some ping test code will be update. Change-Id: Icc336d5857f4484334bab61870b8568be887ec30 Signed-off-by: liyin <liyin11@huawei.com>
2017-02-16tc076 rst documentationrexlee87762-0/+62
JIRA: YARDSTICK-534 Change-Id: Idcd8fb600d64c0300b5aaf9bd4108eca6c866526 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-02-16Merge "This Patch is used to add grafana config to opnfv dashboard for ↵Kubi1-517/+573
kvmfornfv_cyclictest_cpustress_idle,kvmfornfv_cyclictest_memorystress_idle and kvmfornfv_cyclictest_iostress_idle testcases"
2017-02-16Merge "Scenario is reporting result for last test only"Rex Lee3-5/+20
2017-02-16Merge "Bugfix: report date format wrong when upload result data to mongoDB"Jing Lu1-5/+5
2017-02-16Bugfix: report date format wrong when upload result data to mongoDBchenjiankun1-5/+5
JIRA: YARDSTICK-562 Currently we use the follow code to upload data to mongoDB: report $scenario_status $start_date $stop_date And the date format will be '%Y-%m-%d' while we want to it be '%Y-%m-%d %H:%M:%S'ã Change-Id: I07e601a6362c844a77f9b15a6bcd225ac2ab3f95 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-16Merge "Context improvement: add support for configing node environment"Rex Lee3-8/+174
2017-02-16Context improvement: add support for configing node environmentchenjiankun3-8/+174
JIRA: YARDSTICK-556 Currently we do can not config the node environment before heat create a stack. But in lots of scene, we need to config node environment before heat. So I add support for it. Change-Id: Iac1b74dc780eb40e6ab2c9cf04ed14e2b8f91ca8 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-16Merge "Bugfix: AttributeError: 'dict' object has no attribute 'encode'"Jing Lu2-3/+43
2017-02-16Merge "New reliability/availability testcase - IP datagram error rate and etc."Rex Lee6-0/+345
2017-02-16Merge "NSBPerf: fix indent"Rex Lee1-1/+1