00:58:42 #startmeeting bottlenecks weekly meeting 00:58:42 Meeting started Thu Apr 7 00:58:42 2016 UTC. The chair is MatthewLi_. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:58:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 00:58:42 The meeting name has been set to 'bottlenecks_weekly_meeting' 00:58:56 #info Jun Li 01:00:27 #info Yaoguang Wang 01:11:44 so we begin 01:11:58 okay, 01:12:00 #info agenda 01:12:20 1) Docs: Bottlenecks definition documents (MR) and C release document contribution in OPNFV DOCs project(all) 2) Integration & test workflow improvement newly submitted patches (matthew, yaoguang, Qiliang, etc ) 3) Puppet refactoring codes (yaoguang, Qiliang, matthew, etc) 4) Dashboard progress (mingjiang, Qiliang, matthew, etc) 01:12:36 #info docs 01:12:57 MR_Sandvine: how it going with your document? 01:13:05 #topic Docs: Bottlenecks definition documents 01:15:09 MatthewLi__: ping Manual first 01:15:15 Yaoguang_Wang: do u have any ideas about the definition documents? 01:16:03 is the doc specific for Release C? 01:16:54 Yaoguang_Wang: no, it will satisfy for all release 01:17:07 definitly, it has evolution 01:17:28 i am not sure what the doc will cover, maybe objective, scope, methodology, right? 01:18:11 in the means of content, it will cover VIM and MANO 01:20:19 i agree 01:21:09 i think the project could cover both data plane and control plane 01:21:22 yep 01:22:33 in other words, any aspects that affect the performance can be covered in Bottlenecks 01:23:22 yep that's what we will do 01:25:05 i hope Manuel can divide into several big categories, and then small items 01:25:28 Yaoguang_Wang: yep we will wait for manuel's work 01:25:49 the definition doc is very important, which will guide us to make the Bottlenekcs better 01:26:48 #agree wait for mauel's definition document 01:27:02 +1 01:27:22 let's move on 01:27:47 #topic Integration & test workflow improvement 01:28:16 #info Jun Li has put up some patches about this 01:28:26 great 01:28:37 #info Jun Li is working with the openstack env 01:29:28 #info this will completed soon 01:29:37 Good 01:29:59 since I have a test recently, I don't know if I have enough time :( 01:31:11 I will try to complete this as soon as possible 01:31:15 okay, you have great ability to do many things together 01:31:36 Yaoguang_Wang: thank u 01:31:57 i am not sure if your HOT generator is flexible enough 01:32:33 maybe i will change the configuration parameters in rubbos test suite 01:32:37 Yaoguang_Wang: I will show u the code when it runs correct in openstack env 01:32:44 okay. 01:33:22 we can discuss the interfaces later 01:33:23 Yaoguang_Wang: u can complete the workflow inside the instance for rubbos 01:33:32 Yaoguang_Wang: yep 01:33:43 so we come to an agreement 01:33:48 yep 01:34:33 #agreed Jun Li to complete the Integration & test workflow improvement for instance creation and Yaoguang_Wang will complete the workflow inside instance for rubbos 01:34:55 #agreed 01:35:05 so let's move on 01:35:26 #topic Puppet refactoring codes 01:35:44 Yaoguang_Wang: how it goes? 01:36:46 #info YaoguangWang has completed 6 modules(total 7) for rubbos 01:37:00 Yaoguang_Wang: great job 01:37:16 i will finish all within this week 01:37:19 :) 01:38:09 good 01:38:10 the codes should be flexible and leave some labels or tags in config file, you know 01:38:26 yep 01:38:43 so i must clean the codes before uploading to the repo 01:38:57 i will finish it soon 01:39:03 what do u mean by clean the codes? 01:39:35 adding labels of tags there, i mean 01:39:47 in order to support other test cases 01:39:57 OK, that's good 01:40:16 so maybe u can give some #action here 01:40:32 #info rubbos can be executed in local vms successfully now 01:41:38 #action YaoguangWang will leave some labels or tags in config files to support other test cases 01:42:11 besides, we should consider vstf soon 01:43:19 first, vstf should also be configured in our unified entrance, right 01:44:15 let's make it an action? 01:44:25 Yaoguang_Wang: vstf is included in our workflow 01:44:32 yes 01:45:17 #action vstf integration and test workflow improvement 01:45:32 i mean we should configure vstf test cases flexibly, maybe yaml or cli parameters 01:45:56 #idea configure vstf test cases flexibly, maybe yaml or cli parameters 01:46:12 good 01:46:25 secondly, need vstf implement all Tu test cases in Colorado? 01:46:40 Yaoguang_Wang: it depends our time 01:46:55 we can talk about this next times 01:47:13 we should do things step by step 01:47:21 ok 01:47:30 we can give an idea here 01:47:44 #idea vstf implement all Tu test cases in Colorado 01:47:54 :) 01:48:29 anything else about the refactoring? 01:48:38 #idea should vstf be refactored using puppet 01:49:19 there are three things for vstf, that's all 01:49:39 good 01:49:43 we need more contributors :) 01:49:50 Yaoguang_Wang: yep 01:50:14 so I have an idea, if can we change the meeting to #opnfv-meeting channel 01:51:42 after we can run one rubbos test case in Openstack env? 01:52:18 Yaoguang_Wang: yep 01:52:36 okay. next? 01:52:41 more advertisement I mean 01:53:10 good 01:53:16 next meeting 01:53:26 no more topic? 01:53:45 #agreed weekly meeting changed to #opnfv-meeting channel next time 01:53:55 #topic dashboard 01:53:58 :) 01:54:37 #info waiting for Mingjiang's dashboard progress 01:54:46 :( 01:55:09 #info when Jun Li and Yaoguang_Wang has some time, will pay attention to the dashboard 01:55:36 okay:( 01:56:08 #action Mingjiang preparation for the dashboard research slide 01:56:31 so we come to the end 01:56:39 yep 01:56:43 bye 01:56:49 bye 01:56:51 #endmeeting 01:58:00 #endmeeting 01:59:03 #endmeeting