13:03:45 <bh526r> #startmeeting Weekly Technical Community Meeting 13:03:45 <collabot> Meeting started Thu Jul 27 13:03:45 2017 UTC. The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:03:45 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:03:45 <collabot> The meeting name has been set to 'weekly_technical_community_meeting' 13:04:25 <bh526r> #topic SampleVNF Project Update (Deepak S and Kannan Babu Ramia) 13:05:11 <bh526r> #info Deepak shared wiki page of SampleVNF E Release Update 13:05:30 <huzhj> Hi Bin, this is Zhijiang, not able to use GTM now, so I am only available on IRC. 13:06:35 <bh526r> Zhijiang, thank you for joining 13:06:53 <bh526r> #info The table in the wiki page details the update 13:08:40 <bh526r> #info David M asked if the first item includes the VNF item EUAG is interested in? 13:09:22 <bh526r> #info Deepak said that those can be used for NFV characterization and other intended use case in OPNFV 13:12:53 <bh526r> #link https://wiki.opnfv.org/display/SAM/SampleVNF+-+E+Release+Update 13:19:37 <bh526r> #info Deepak also gives details of VNF catalog 13:19:52 <bh526r> #link https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Open+Source+VNF+catalog 13:24:11 <bh526r> #topic Continue Discussion of Auto project proposal (Tina Tsou, Bob Monkman and Bryan Sullivan) 13:24:37 <bh526r> #info Bryan updated the wiki, although the slides deck hasn't changed 13:26:54 <bh526r> #info The changes addressed most of comments received last week 13:28:30 <bh526r> #info Stephen asked what is the relationship with Opera? 13:30:32 <bh526r> #info Bryan indicated that we intend to evolve to cloud native for example, not limited to OpenStack, and packaging is also a big task 13:45:14 <bh526r> #info Group achieved consensus to recommend this proposal for TSC creation review in next TSC meeting once 2-week period completes 13:47:23 <bh526r> #topic ODL Scenarios in Installers - odl-l2, odl-l3 and potential consolidation (Ulrich Kleber) 13:48:22 <bh526r> #info Uli introduced background of this topic - in last week's release meeting, we reviewed different scenarios 13:48:45 <bh526r> #info There are variants of ODL scenarios - odl-l2 and odl-l3 13:49:07 <bh526r> #info There are 7 scenarios has odl-2 or odl-l3 in their names 13:49:36 <bh526r> #info The other majority scenarios doesn't have l3 in names, but odl only with l3 functionality 13:50:10 <bh526r> #info 1st question: should we consolidate odl-l2 and odl-l3? 13:50:27 <bh526r> #info question 2: should we do it in E or F release? 13:50:35 <huzhj> really do not know who will use L2 and why they use it. more background will be appreciated :) If no one will use it in future, then Daisy is OK to do consolidation and change odl-l3 to odl. 13:50:37 <bh526r> #info the discussion started 13:52:05 <huzhj> Or we can change ODL-L3 to ODL now, and retain ODL-L2 for future reference? 13:53:18 <uli-k> Do you have specific users requiring odl-l2? 13:53:42 <huzhj> uli-k , no 13:58:10 <bh526r> #info Uli and Bin discuss offline to find a way to continue the discussion with PTL of all installers 13:59:19 <bh526r> #topic Name Change of Project OpenRetriever (Xuan Jia) 13:59:32 <xuanjia> container4NFV 13:59:43 <bh526r> #info Xuan proposed to change the name of OpenRetriever to match its scope more accurately 14:02:11 <bh526r> #info Group achieved consensus to recommend to TSC for consideration of this name change request in next TSC meeting once 2-week period finishes 14:02:24 <bh526r> #info Meeting adjourned 14:02:27 <bh526r> #endmeeting