08:31:50 #startmeeting Yardstick Work Meeting 08:31:50 Meeting started Mon Sep 26 08:31:50 2016 UTC. The chair is kubi001. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:31:50 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:31:50 The meeting name has been set to 'yardstick_work_meeting' 08:32:02 #topic roll call 08:32:05 #info kubi 08:32:07 #info Jing Lu 08:32:16 #info Mingjiang 08:32:26 #info chenjiankun 08:32:39 tallgren: sorry for late, we started the meeting now 08:33:12 #topic demo plan 08:33:35 #info Tapio Tallgren 08:33:37 JingLu gave a great presentation about Yardstick Plan. thanks 08:33:52 #info wangwulin 08:33:57 #info JingLu gave a great presentation about Yardstick plugin. thanks 08:34:05 :) 08:34:36 chenjiankun will give a other presentation about Yardstick Reporting at this Thursday Meeting 08:34:46 #info chenjiankun will give a other presentation about Yardstick Reporting at this Thursday Meeting 08:35:20 chenjiankun: is it ok for you? 08:35:49 OK~I will give a presentation about Yardstick Reporting this Thursday Meeting 08:35:59 chenjiankun: thank you 08:36:17 #topic Colorado Release 08:36:18 :) 08:37:14 here is the OPNFV Colorado 2.0 & 3.0 schedule https://wiki.opnfv.org/display/SWREL/Colorado+2.0+and+3.0 08:37:22 please check it 08:38:17 "Colorado 2.0 Testing and Documentation Complete" should be end before 10/24 08:39:09 so for 2.0/3.0, we only fix existed bugs or improve documents, right? 08:39:54 Mingjiang: absolutely 08:40:02 https://jira.opnfv.org/projects/YARDSTICK/versions/10337 08:40:30 here is the link of Jira plan in Colorado 2.0 08:40:42 as i see from the schedule, 10/24 we should complete the doc, then in 10/27, 2.0 would be released. 08:41:04 which mean we've got one month 08:41:20 Mingjiang: yes, your are right. testing and documentation should be completed before 10/24 08:42:25 There are some bugs which we delay them to Colorado 2.0, We need to fix them in next month. 08:42:35 such as LXD_support 08:43:58 #topic functest API 08:44:32 here is the link of functest Danube plan 08:44:40 #link https://wiki.opnfv.org/display/functest/Functest+Danube 08:45:44 kubi001: for the existed bugs, i'll also make ipv6 work for fuel in colorado 1.0. 08:45:48 please check it. Functest Team want to converge and leverage with Yardstick Team 08:45:52 1.0->2.0 08:46:44 Mingjiang: yes, Thanks for your great work for IPV6 Testing, I got a great feedback from Bin 08:47:17 Please check the above link, please feel free to comment it. 08:48:30 #topic Yardstick D plan 08:48:30 kubi001: I think we should also draft one for yardstick asap 08:49:25 from the link, it seems functest has listed all candidate change for functest Danube 08:50:05 Mingjiang: https://etherpad.opnfv.org/p/yardstick_release_d 08:51:49 please comment it 08:51:56 #topic others 08:52:00 ok, i'll what i thought in the etherpad for the team to review 08:52:15 Mingjiang: thanks a lot 08:52:37 i've just checked the mail and find in user-group there's a problem for yardstick 08:52:49 so everyone please check if you can help 08:53:13 Mingjiang: thanks for remind 08:54:20 A email from Taseer Ahmed 08:54:47 Any help would be greatly appreciated. 08:54:52 another thing, for kvm dashboard, i'm considering build a sample dashboard for them to use. I've sent a mail to yunhong for this. 08:55:11 Hard to understand what Taseer Ahmed is asking 08:57:04 Can we also have a sample dashboard for local Grafana installations? It was a little difficult to get started with Grafana 08:57:14 Kubi:where is the presentation video in our wiki page? 08:57:41 I think if Tasser switch to use yardstick:stable docker image, this problem will be solved. 08:58:16 tallgren: I guess he just wanted to run Yardstick test case, but failded with Yardstick Framework docker image 08:58:24 JingLu: I think so 08:59:09 The problem I had was that "sudo -E yardstick" did not use the virtual environment 09:00:29 chenjiankun: I will upload the demo video to opnfv channel in the youtube 09:01:28 #link https://wiki.opnfv.org/display/yardstick/How+to+deploy+InfluxDB+and+Grafana+locally 09:02:01 tallgren: the above link is a simple guide about influx and grafana 09:02:42 kubi:thank you for your work. 09:02:48 I used that, but it would be easier to have a sample dashboard to import. 09:03:35 tallgren: There are sample config files in the yardstick repo 09:03:43 for the sample dash board, you can find the dashboard config in $yardstick_root_path/dashboard path 09:04:17 #link https://git.opnfv.org/cgit/yardstick/tree/dashboard 09:04:33 tallgren: what you need to do is import the config file to grafana 09:04:42 here is the git path where all the dashboard config locate 09:06:33 When I looked, the sample Grafana dashboards all showed information from the public labs. Maybe I did not find the correct one. 09:09:10 tallgren: yes, you are right, here is some work to do for the user. we need to change the POD info 09:09:23 tallgren: I guess we can make a improvement about this 09:09:53 tallgren: your suggestion is great. we should have a sample dashboard to import 09:10:57 agree, we'd better create a sample for everybody can use it and improve the userguide to describe exactly about the sample 09:11:21 Sounds great! 09:12:12 I re-installed Yardstick on a Ubuntu Xenial VM and got it work. I will write up what I had to do and send it to the list. 09:12:35 tallgren: great! 09:13:08 tallgren: that would be a part of User guide 09:13:13 sounds great 09:13:37 kubi: tallgren: for the sample grafana, i can do it in 2.0 09:13:58 Mingjiang: thank you very much 09:14:17 #info Mingjiang create a sample for everybody can use it and improve the userguide to describe exactly about the sample 09:15:27 #info tallgren installed Yardstick on a Ubuntu Xenial VM sucessfully, and he will write up what he had to do and send it to the list 09:16:49 anything else? 09:17:24 #endmeeting