14:10:57 #startmeeting bottlenecks weekly meeting 14:10:57 Meeting started Wed Nov 18 14:10:57 2015 UTC. The chair is matthewli_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:10:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:10:57 The meeting name has been set to 'bottlenecks_weekly_meeting' 14:11:11 yes 14:11:41 I think it is the deadline of milestone D, not B release 14:11:59 yes milestone D is improtant 14:12:17 we need finish the work for milestone D 14:12:33 and I have discussed with ana, Testing project can continue coding and fixing bug after the milestone D 14:13:01 #action finish the debug hongbo and mattewli 14:13:12 for milestone D 14:13:23 patrick_1: how many milestone D we have? 14:13:28 we need to integrate into dashboad and CI 14:13:39 hongbo: that's OK 14:14:12 #action CI integration for CI 14:14:24 #action CI mattewli 14:14:46 #action dashboad and db hongbo and mattewli 14:15:06 we need to finish these things as soon as possible 14:15:08 hongbo: it's fine for me, I am familiar with CI 14:15:15 good 14:15:39 I can do some help for dashboard and test result 14:15:48 just as yardstick did 14:16:06 patrick_1: it's fine 14:16:07 MR-sandvine is interested in the bottlenecks documents 14:16:27 so I will set the task to him 14:16:55 So we can give an action to MR_Sandvine 14:17:11 #action discuss with MR how to define the bottlenecks 14:17:14 yes 14:17:19 hongbo, the language by bottlenecks framework is java, is it right? 14:17:39 java is part of framework 14:17:58 most are ssh and other scrips 14:18:00 C 14:18:03 and so on 14:18:08 ok 14:18:29 you know that benchmark are conposed by many components 14:18:30 the dashboard and db code in functest and yardstick is python script. 14:18:55 that fine, we can add them into our framework 14:18:59 patrick_1: we can work together with the dashboard 14:19:17 I am trying to recontruct the framwork by python 14:19:24 great 14:19:39 I want to do this thing also 14:19:44 I finished the design, but I need time to do that 14:19:48 ok 14:20:07 since other testers will perfer the python scripts 14:20:32 #action patrick reconstruct the framwork by python 14:20:40 hongbo: it's great 14:20:51 yes 14:21:02 I will show the codes toyou 14:21:09 and we can reuse the common codes in functest and yardstick, like the db and dushboard 14:21:13 ok 14:21:21 yes, 14:21:27 but I am not sure we can use 14:21:37 if we can use, I think, we can use 14:21:59 I and mattewli will try work for that 14:22:03 ok 14:22:20 and other guys will help us to speed up 14:22:26 ok 14:22:34 that is great 14:23:09 tomorrow, I will meeting someone to discuss the benchmarks 14:23:25 sounds great 14:23:32 these benchmarks can help us to test bottlenecks for OVS 14:24:02 #action prepare ovs bottlenecks hongbo 14:24:23 Fine 14:24:32 also, I need to discuss with story project to discuss story bottlenecks 14:24:43 they sent the email to me 14:24:48 storperf? 14:24:50 yes 14:24:58 ok 14:25:11 I have disucced with EMC lead 14:25:31 he told me that EMC are willing to join the bottlenecks 14:25:58 Good to have experts in storage area 14:26:08 yes 14:26:43 for the next, we will add more people to join bottlenecks 14:27:23 one thing we need to do is that we need to finish the framwork and add more benchmarks to analysis the bottlenecks 14:27:26 to be honestly, few people are commit in storperf, and the PTL is concerning integrating with Qtip, Yardstick and Bottlenecks. 14:27:40 but we can discuss with him first. 14:27:50 the other is that we need to collaborate with other projects 14:28:02 ok 14:28:07 exactly 14:28:32 aslo, bottlenecks will help dovetail to do some certisficaiton 14:28:48 we need connect with other projects. 14:28:54 ok 14:29:17 and compass will also integrate with bottlenecks 14:29:22 yes 14:29:33 we can try to do that 14:29:34 I have talked with weidong 14:29:40 ok,good 14:29:44 patrick_1: good idea 14:29:55 He said it is not difficult 14:30:02 good 14:30:15 but we should have finished our framework first 14:30:25 yes that is the point 14:31:33 Qiliang has some experience for test framework design, I will ask him for help also. 14:31:56 ok, we need more people to speed us the project 14:32:01 welcome 14:32:02 That's fine 14:32:22 we should try best to finish this framework in B release 14:32:32 yes 14:32:47 great. So let's do it 14:32:52 ok 14:33:30 so next, we will achive more 14:33:38 matthew and hongbo, when do you come back to china? 14:33:51 Next week 14:33:52 saturday 14:34:00 this week 14:34:12 Yep weekend 14:34:38 great, I have a meetup in Beijing this weekend. about the openstack test and analysis 14:34:44 ok, that is all for today's meeting 14:34:48 ok 14:35:23 do you have other informaiton for share 14:35:24 they will give some speech on openstack performance testing 14:35:30 good 14:35:45 we can learn something from openstack testing 14:35:52 patrick_1: hope to take some material for us 14:35:56 I will introduce bottlenecks with them also. 14:36:03 ok 14:36:06 no problem 14:36:13 great 14:36:33 one more thing 14:37:22 we will try to make a OPNFV meetup in china 14:37:32 when? 14:37:48 Liang Gao is preparing for this 14:37:53 soon. 14:37:58 ok 14:38:03 "We" here means? 14:38:22 how many people? 14:38:57 now it means the opnfv guys in China 14:39:03 we need to prepare for our breakfest. we can disucc more latter 14:39:08 good idea 14:39:22 ok 14:39:24 we can meet more guys 14:39:42 maybe we can give a speech about bottlenecks 14:39:46 yes 14:40:02 I will try 14:40:09 Fine 14:40:10 we need more people to know this projects 14:40:24 ok all guys, thank for joining 14:40:30 this meeting 14:40:31 ok 14:40:31 Bye 14:40:35 bye 14:40:39 bye 14:40:45 #endmeeting