13:59:22 #startmeeting Weekly TSC meeting 13:59:22 Meeting started Tue Mar 21 13:59:22 2017 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:22 The meeting name has been set to 'weekly_tsc_meeting' 13:59:45 #info Tapio Tallgren 13:59:54 #info hongbo 14:00:31 #info Bin Hu 14:00:51 #info Rossella Sblendido 14:01:13 #info Morgan Richomme 14:01:25 #info Edgar StPierre 14:01:29 #info Brian Skerry 14:01:31 #info Frank Brockners 14:01:33 we now have a quorum 14:01:35 #info Fatih Degirmenci 14:01:36 #info naga chumbalkar 14:01:43 #info Uli 14:01:45 #info Dave Neary 14:01:45 #info Jack Morgan 14:02:18 #topic previous minutes 14:02:31 #info no comments on previous minutes, thus approved 14:02:39 #topic agenda bashing 14:02:47 #info Bryan Sullivan 14:02:54 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-March21,2017 today's agenda 14:03:03 #info Tim Irnich 14:03:07 #info no other topics suggested 14:03:21 #info Brady Johnson 14:04:24 #topic creation review for samplevnf 14:05:28 #info rprakash 14:06:20 #info Xavier Costa 14:06:26 #info Kannan notes that the samplevnf project is to create a repository of sample VNFs to help VNF benchmarking and NFVi characterization with real world traffic 14:07:19 #info addressed questions from the community on Apache 2.0 licensing and all source code will be available (no binaries) on OPNFV repos 14:07:45 ##chair rpaik 14:07:48 rpaik: Just talked to Koren - he should be here soon (he has issues connecting) 14:08:50 #info main goal is to help with VNF benchmarking and characterization 14:09:03 #chair rpaik 14:09:03 Current chairs: rpaik tallgren 14:09:40 #info Julien 14:12:17 #info Trevor Cooper 14:12:46 #info The Sample VNFs will consist of several VMs and can be used for load testing the virtual infrastructure 14:14:25 #info also planning to look at service chaining in the future 14:14:25 #info The Sample VNFs could also be used for testing service chaining 14:14:30 #undo 14:14:30 Removing item from minutes: 14:15:31 #info The VNFs are data plane optimized and distributed 14:17:04 #info also plans for distributed instances in the future 14:18:45 #startvote does the TSC approve creation of the sampleVNF project? (+1, 0, -1) 14:18:45 Begin voting on: does the TSC approve creation of the sampleVNF project? Valid vote options are , +1, 0, -1, . 14:18:45 Vote using '#vote OPTION'. Only your last vote counts. 14:18:48 #vote +1 14:18:51 #vote +1 14:18:51 #vote +1 14:18:52 #vote +1 14:18:52 #vote +1 14:18:52 #vote +1 14:18:54 #vote +1 14:18:54 This is a great project 14:18:55 +1 14:18:56 #vote +1 14:18:57 #vote +1 14:18:58 #vote +1 14:18:58 #vote +1 14:19:05 #vote +1 14:19:07 #endvote 14:19:07 Voted on "does the TSC approve creation of the sampleVNF project?" Results are 14:19:07 +1 (12): dneary, frankbrockners, timirnich, fdegir, morgan_orange, uli-k, naga_lenovo, rossella_s, hongbo123456, bjskerry, edgarstp, jmorgan1 14:20:12 #topic creation review for VINA 14:20:54 #info Koren notes that the VINA project addresses assurance and monitoring for VIM 14:22:57 #info focus will be on monitoring, visualization, monitoring, root cause analysis, etc. 14:24:13 I lost network connection for a whil 14:24:17 while 14:28:34 #info Koren notes that VINA aims to take a top-down view (vs. other approaches taken e.g. by skydive) 14:35:25 #startvote does the TSC approve creation of the VINA projects? (+1, 0, -1) 14:35:25 Begin voting on: does the TSC approve creation of the VINA projects? Valid vote options are , +1, 0, -1, . 14:35:25 Vote using '#vote OPTION'. Only your last vote counts. 14:35:34 #vote +1 14:35:36 #vote +1 14:35:36 #vote +1 14:35:38 #vote +1 14:35:41 #vote +1 14:35:43 #vote +1 14:35:44 #vote +1 14:35:47 #vote +1 14:35:47 #vote +1 14:35:50 #vote +1 14:36:02 #endvote 14:36:02 Voted on "does the TSC approve creation of the VINA projects?" Results are 14:36:02 +1 (10): frankbrockners, fdegir, morgan_orange, Julien-zte, tallgren, rossella_s, XavierCosta, bjskerry, edgarstp, jmorgan1 14:36:05 #vote +1 14:36:07 #vote 0 14:36:16 #vote +1 14:36:20 rpaik, A bit fast on the trigger there 14:36:34 all good 14:36:43 We are short on time... 14:36:46 * ebrjohn Is Phill Collins on the call?!?!? 14:36:51 #topic Danube planning and timeline 14:37:18 tallgrenSure, but having voting open for 30s is a bit quick 14:37:42 ... 14:38:19 #info dmcbride notes that community is continuing to make progress on Danube 1.0, but a bit behind compared to the Colorado release 14:38:28 dneary: I see you voted "0". We need to update that to the minutes somehow 14:39:34 tallgren: There were also 2 missing +1s 14:39:38 #info less than 1/2 of the Danube 1.0 target scenarios have been deployed 14:40:00 Yep.. 14:40:06 #info handful of scenarios are having successful Functest runs 14:42:09 #info few projects like onosfw, bottlenecks, etc. are still working through some issues 14:44:04 #info tallgren notes that we probably do not have sufficient information on making a decision on Danube 1.0 14:44:55 Seems a bit sketchy with so much variance less than a week before release... just my 2 cents 14:46:27 #info morgan_orange notes that more time is needed for troubleshooting in general 14:49:26 #info also more time is needed on documentation 14:50:17 1 week would give more iterations to fill up the status of each scenario 14:50:27 but it doesnt mean the issues will be fixed 14:51:18 jose_lausuch: +1 14:53:06 It would be interesting to get the point of view from the application projects... OPNFV SFC for instance didnt have a CI deployable scenario available until Thursday last week 14:53:15 #info consensus to create a revised schedule/get well plan in the release meeting 14:53:20 That doesnt leave much time to react 14:54:53 #topic ODL release timing 14:56:12 #info colindixon notes that release timing for ODL has not always worked with OPNFV and ODL community is considering twice a year release cycle 14:57:28 #info question to the OPNFV community is when is the ideal time for ODL to release? 14:59:59 #info ebrjohn says that he'd like to see a 3 month shift from ODL release to OPNFV release 15:00:13 #info discussion of aligning ODL with OpenStack release 15:00:26 #info colindixon and phrobb point out that the pushback on that is that it might incentivize shipping features in ODL SRs vs. waiting for the next release 15:01:03 #info there's some suggestions that ODL line up with OpenStack and then OPNFV come some time after that 15:01:51 +1 for F2F session on Monday 4th 15:01:59 Monday 3rd 15:02:48 #endmeeting