00:33:44 #startmeeting Yardstick 00:33:44 Meeting started Tue Jan 10 00:33:44 2017 UTC. The chair is trevor_intel. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:33:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 00:33:44 The meeting name has been set to 'yardstick' 00:33:58 i cant hear 00:34:02 i'll reconnect 00:36:03 #topic Action follow-up 00:37:32 link: https://wiki.opnfv.org/display/yardstick/Yardstick+Framework+Architecture+Evolution 00:37:52 #info Action was to create Yardstick architecture Wiki, see https://wiki.opnfv.org/display/yardstick/Yardstick+Framework+Architecture+Evolution 00:39:03 #info Will be included in Danube documentation 00:39:51 #info Looking for feedback in next weeks meeting 00:40:08 I'm online, sorry for the late, there was something wrong with hotel 00:40:30 network 00:40:37 kubi001: no problem 00:43:43 #action Ross will update diagram for NSB 00:46:10 #info See Jira ticket for status - waiting for Ruijing to reply https://jira.opnfv.org/browse/YARDSTICK-529 00:46:53 #topic Python 3 00:47:15 #info Ross proposed plan in Etherpad https://etherpad.opnfv.org/p/YardstickPython3 00:49:14 #info Everybody read Open Stack porting 3 guidelines 00:49:45 #info We are in step 1 today 00:50:42 please review https://gerrit.opnfv.org/gerrit/#/c/25539/ 00:50:48 #info Step 2 commit is in Gerrit for review - committers please review it 00:51:26 #info Ross would like to merge soon - touches lots of other files so have to keep re-basing 00:52:14 #info Adding Python 3 support https://gerrit.opnfv.org/gerrit/#/c/25539/ 00:52:58 yes, otherwise, it will become a heavy work for rebasing 00:53:40 I have tested it with opnfv_smoke suite, but it needs more testing. 00:54:32 #info yardstick team should review about the patch: kubi, jing, jack, rex, kanglin, zhihui 00:55:31 within two days? is it ok for everyone? 00:56:09 limingjiang@huawei.com 00:57:43 Mingjiang: maybe, you can help to do some local verify besides review 00:58:45 #info Ross indicated Python 3 unit tests are key ... do it before or after Danube? 00:59:08 #info Rex suggested to do ASAP or will be harder 01:00:09 +1 to before Danube. 01:00:17 #info Deepak has proposed patches ... not sure if compatible with Python 3 ... Ross will inform Deepak to prepare accordingly and will help 01:01:10 #info Agreed to enable before Danube 01:01:44 #agree Enable Python 3 before Danube 01:02:04 kubi001: i'll do that 01:02:53 #info Ross is willing to help anybody with porting to Python 3 01:03:02 great 01:03:24 #topic Yardstick-Qtip integration 01:04:06 link: https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration 01:05:33 #info #link https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration 01:05:47 #info https://etherpad.opnfv.org/p/qtip-yardstick 01:06:00 #undo 01:06:00 Removing item from minutes: 01:06:06 #link https://etherpad.opnfv.org/p/qtip-yardstick 01:22:47 The Framework can run 5 computing benchmarks: 1. Dhrystone 2. Whetstone 3. RamBandwidth 4. SSL 5. nDPI 01:24:42 #info Discussion on Qtip relationship to Yardstick for integration is unclear 01:24:55 agree 01:25:02 #info Needs some discussion between Yardstick and Qtip team 01:26:21 #info Qtip benchmarks listed in Wiki The Framework can run 5 computing benchmarks: 1. Dhrystone 2. Whetstone 3. RamBandwidth 4. SSL 5. nDPI 01:26:55 https://github.com/ntop/nDPI.git 01:27:46 I guess "1. Dhrystone 2. Whetstone 3. RamBandwidth " should be similar with yardstick test case 01:27:52 #info nDPI is an open source LGPLv3 library for deep-packet inspection. 01:28:21 #info These benchmarks can be run in 2 test cases: 1. VM vs Baremetal 2. Baremetal vs Baremetal 01:29:46 #topic Sprint 01:30:01 yujun told me that Qtip will mainly calculate score based on yardstick test result instead of testing by themself 01:30:32 #link https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=145&view=planning&selectedIssue=YARDSTICK-529&versions=visible 01:31:24 #link https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=145&view=detail&selectedIssue=YARDSTICK-524 01:31:38 kubi001: ok I think that is also what Bottleneck said ... but maybe its for a different purpose? 01:31:59 Detecting bottlenecks vs measuring performance 01:32:50 #info the sprint page is to show what yardstick is in progress/to do/done in the active sprint 01:33:13 you can easily move it to modify the status of the jira task 01:34:07 #info all of this is in the "Agile of YARDSTICK" board: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=145&view=planning&selectedIssue=YARDSTICK-529&versions=visible 01:37:17 trevor_intel: yes, different purpose, and Bottleneck worked as a load manger, that would be call yardstick iteratively. and Qtip will work as a kind of yardstick result interpreter based on some algorithmic 01:39:06 old qtip info here: https://wiki.opnfv.org/display/qtip/Brahmaputra 01:40:38 rbbratta 01:40:45 rbbratta: thanks 01:41:33 rbbratta: thanks,here is some update from Qtip link https://goo.gl/g16hEG 01:43:00 kubi001: yes that presentation is linked as the introduction to Qtip on project wiki 01:43:59 I have looked through it a few times but still have questions 01:44:50 trevor_intel: :) shall we have a joint meeting with Qtip at next Yardstick meeting 01:45:09 kubi001: good idea! 01:45:13 agree 01:45:17 +1 01:45:18 +1 01:45:25 compute QPI: https://git.opnfv.org/qtip/tree/benchmarks/suite/compute.yaml weighted arithemetic mean of various stats 01:45:29 +1 01:45:38 Ok, I will contract with Qtip team 01:45:53 +1 01:46:16 #action kubi will contract with Qtip team to have a joint meeting at next weekly meeting 01:46:49 #action kubi will contract with Qtip team to have a joint meeting at next weekly meeting 01:47:09 #endmeeting