14:59:33 #startmeeting Weekly OPNFV TSC meeting 14:59:33 Meeting started Tue Feb 21 14:59:33 2017 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:33 The meeting name has been set to 'weekly_opnfv_tsc_meeting' 14:59:39 #chair rpaik 14:59:39 Current chairs: rpaik tallgren 14:59:43 #info Bryan Sullivan 14:59:48 #info Uli 14:59:56 #info hongbo 15:00:28 #info Tapio Tallgren 15:01:18 #info Tim Irnich 15:01:19 #info Fatih Degirmenci 15:01:22 #info Rossella Sblendido 15:01:31 #info Jack Morgan 15:01:38 #info Brian Skerry 15:02:03 #info Xavier Costa 15:02:21 we now have a quorum 15:02:46 #info Dan Radez (proxy Dave Neary) 15:02:48 #topic approval of previous minutes 15:02:52 dneary: ^^ fyi 15:02:54 #info Edgar StPierre 15:03:11 Thanks Dan! 15:03:12 #info typo fixed and no other feedback. minutes apporved 15:03:29 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-February21,2017 today's agenda 15:05:21 #info tallgren notes that there are two new project proposals (Bamboo, VINA) will be discussed during Thursday's weekly community call 15:05:59 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/015156.html E-release naming nomination 15:06:34 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/015153.html graduation review discussion 15:06:58 #info tallgren also noted that CFP for OPNFV Summit is now open 15:07:38 #link http://artifacts.opnfv.org/octopus/review/28443/scenario-lifecycle/index.html 15:08:09 #link https://gerrit.opnfv.org/gerrit/#/c/28443 15:08:09 #link https://gerrit.opnfv.org/gerrit/#/c/28443 15:08:15 :-) 15:09:23 #topic OPNFV End User Advisory Group survey discussion 15:09:54 #link (for VNF survey) https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html 15:10:51 #info Steven Wright gives an overview of the first EUAG survey that was conducted in January 15:12:14 #info survey shows that OPNFV is being used (not in production yet) with Fuel being the most popular installer 15:13:53 #info many respondents did not fully understand scenarios 15:14:43 #info respondents are interested in projects like DPACC, Pinpoint, etc. being included in future releases 15:15:37 #info key pain points are interoperability, real-time performance monitoring & fast fault detection, resiliency at scale, etc. 15:16:42 #info Julien 15:19:21 #info many build or partner for their "NFV platforms" 15:19:43 #info follow-up survey planned prior to the Beijing Summit 15:20:30 #info there were mostly 1 respondent from each operator for the survey 15:25:14 #info rpaik asks how the TSC can take the results of the EUAG survey into account in planning the E release 15:26:42 #info Brandon Wick notes that sharing key EUAG pain points with the TSC maybe a good start 15:29:52 #info discussion bringing the EUAG pain points topic (e.g. with EPIC statements) to the TSC call in the next few weeks 15:30:17 is it worth have a discussion with the PTL's to discuss what is on their plans that address these needs? Maybe a useful call. 15:31:06 to Chris: support 15:31:22 #info future call can be used to identify work already in progress, gaps, etc. 15:33:36 #topic Danube/E-release planning 15:34:20 #info rprakash 15:34:21 #info MS6 was Feb. 17th and dmcbride will be evaluating project compliance 15:35:19 #info E-release schedule discussion on-going 15:36:45 #info a reminder that MS7 (stable branch) is March 10th 15:37:19 #info APAC targeted release meeting is tonight at 7pm PT 15:41:47 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/015084.html e-release timeline discussion 15:43:03 #info goal is to vote on the E-release schedule in the next few weeks 15:44:19 #link (thread with Randy's and my comments) https://lists.opnfv.org/pipermail/opnfv-project-leads/2017-February/000790.html 15:44:31 #action rpaik to add E-release timeline discussion to the TSC agenda next week 15:44:47 #topic OPNFV Architecture 15:45:41 #link https://wiki.opnfv.org/display/DOC/OPNFV+Architecture+for+Danube+release 15:46:38 #link https://wiki.opnfv.org/display/DOC/OPNFV+Projects+mapping 15:48:32 #info we had some clarification on this in a recent call (TSC or community, I can't recall) that the goal of this is to generate an infographic type view of the OPNFV project, somewhat in the style of an arch diagram but not implying any concrete (or specific) "architecture" for the OPNFV reference platforms. 15:51:08 #info MANO viewpoint is listed on link https://wiki.opnfv.org/display/mano/MANO+Group+Home 15:51:24 #info discussion on "evolving" the Colorado architecture diagram vs. also looking at this from a different angle 15:51:36 #info for example, in AT&T the role of ODL is substantially different from what might be implied in the diagram, vs OpenContrail and ONOS, and in fact all three have a role in the overall set of use cases and market-specific deployments that make up our "D2" platform vision. 15:53:42 #info this diagram also does not consider the role of public clouds that may not be based upon openstack, but nonetheless an infra environment of significance to the upper layers of the "MANO" stack. 15:57:42 #info discussion that face-to-face sessions maybe needed to continue looking at the architecture from a different angle 15:58:32 #info for Danube infographics LF team can take a first cut at this and get feedback from the TSC 16:00:32 #info bryann_att encourages community members to respond to intern's request for VNF catalog (https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html) 16:01:10 #endmeeting