13:59:24 #startmeeting OPNFV TSC 13:59:24 Meeting started Tue Aug 9 13:59:24 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:24 The meeting name has been set to 'opnfv_tsc' 13:59:30 #topic Roll Call 13:59:35 #info Chris Price 13:59:38 #info Uli Kleber 13:59:40 #info Jonas Arndt 13:59:47 #info Ceciliacorbi 14:00:12 #info Dave Neary 14:01:21 #info Gerald Kunzmann 14:01:24 #info Brian Skerry 14:01:33 #info Bryan Sullivan 14:01:49 we have a quorum 14:01:55 #info Dirk Kutscher 14:02:05 #info Edgar StPierre 14:02:11 #topic Approval of previous minutes of meeting 14:02:16 #info Frank Brockners 14:02:19 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-August2,2016 previous minutes as recorded 14:02:48 #info After one minor correction the minutes are approved. 14:02:52 #topic Agenda Bashing 14:03:08 #link https://wiki.opnfv.org/display/meetings/TSC todays agenda 14:03:33 #info rprakash 14:04:25 #info no further topics proposed to the agenda 14:04:40 #topic OPNFV Board meeting recap 14:04:59 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-August/011907.html board meeting update e-mail 14:06:27 #info ChrisPriceAB noted that he discussed reporting status for the Colorado release during the board meeting 14:07:15 #info Adding 5 Committer-at-Large TSC members were approved by the Board 14:07:29 #info Julien 14:07:41 #info Tapio Tallgren 14:09:15 #info Borard resolutions affecting Bylaws will be published going forward 14:09:48 #info The title of Board President will change to Vice Chairperson 14:10:45 #topic Committer-at-Large elections to the TSC 14:10:57 #chair rpaik 14:10:57 Current chairs: ChrisPriceAB rpaik 14:11:32 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-August/011798.html Community TSC election announcement 14:12:08 #link https://wiki.opnfv.org/display/DEV/Community+Election+Procedure community election procedure 14:14:46 #info ChrisPriceAB discusses proposed procedures when more than 2 members are elected from same member companies and alternates 14:16:41 #link https://www.opnfv.org/developers/technical-project-governance/tsc-charter TSC Charter (Section 4) 14:20:49 #agree the TSC agrees that any company needs to ensure it does not have more than two TSC representatives in which ever way that company feels is best. We will not enforce a rule on how this should be handled. 14:22:51 #agree the TSC agrees that they do not want to enforce rules around who should be delegates, however in the event that there are three members of any company on a TSC call only two of the votes would count. 14:24:20 #action chrispriceab to update the commnity elections procedure wiki 14:28:39 #agree the TSC agrees that the list established during the elections is valid only for those elections and should not be used for future roles. 14:29:24 #info rpaik reminds the comunity either nominate themselves or send in nominations 14:29:29 #topic TSC meeting schedule 14:29:35 ChrisPriceAB, You mentioned a discussion on these details - was there a filter on those emails? I do not see the thread in opnfv-tech-discuss or opnfv-tsc 14:29:50 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-August/011840.html email discussion on TSC calls 14:30:26 ChrisPriceAB, Thanks for the detail (conversations in other calls, not email thread) 14:31:27 #agree the TSC agrees to postpone this discussion until the new TSC members are active. 14:31:39 #topic Colorado planning and activities 14:32:09 #info dmcbride reminds the community that the documentation milestone is coming up next week. 14:32:25 #info the stable branch mielstone is also coming up which has resulted in community discussion 14:33:40 #info dmcbride outlines activity to improve the activity around the stable branch milestone, including strong communication, and establishing a window for cutting stable which would start on MS9 and would last a week. 14:34:48 #info dmcbride raises concerns that some projects may be forking upstream projects, which is not necessarily an issue. 14:35:21 #info some projects are not as aware as others on how to effectively upstream patches anc code form their project work. 14:35:52 #info dmcbride has been working with these projects to ensure that we are able to get our code upstream and work with upstream communities. 14:36:20 #info dmcbride outlines a need to work with and educate projects on how this can best be done. 14:36:49 #link https://wiki.opnfv.org/display/octopus/Finalizing+OPNFV+Releases the process for finalising the Colorado release. 14:37:47 #topic Opera project creation review 14:37:54 #link https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O opera project proposal 14:39:48 #info the Opera project will focus in the short term on the integration of open-o NFVO, a VNFM based on Juju, and an OpenStack based VIM 14:40:23 #info TOSCA and HEAT are the primary target interfaces models for this integration 14:41:43 #info Opera will start with a vCPE use case to establish the work 14:42:11 #info Opera intends to work closely with other projects defining interfaces and capabilities and intends to participate actively in the MANO working group 14:42:38 #info Opera intends to participate in the D-Release 14:43:13 #info dneary asks which VNFD and NSD will be used in the first iteration of the project. 14:43:59 #info Yingjun answers that they intend to use TOSCA, and a TOSCA parser to translate to other models (including any needed translations for selected components) 14:44:25 #info dneary asks if the Parser project in OPNFV will be used as the parser in question. 14:45:15 #info this does not seem to be the case as different source implementations seem to be selected for this purpose 14:47:01 #info frankbrockners asks if there will be additional scenarios included based on JOID to accommodate opera? 14:48:34 #info aria is another open source project to deal with tosca template 14:48:36 #info Yingju responds that the L3VPN based scenario's would be preferred. 14:48:37 #link http://ariatosca.org/ 14:49:55 #info prakash responds that the team is not sure about which scenario's they would be using, nor if the existing installation toolchains are sufficient 14:51:56 #info frankbrockners brought up a great point. New projects should clearly specify which scenarios they intend to work with, and whether they intend to create a new scenario. 14:52:04 #info there are technical investigations required to determine how this project will interact with the installer projects and scenario's. This is unknown at this time. 14:56:19 #info repo name will be changed to "opera" (all lower case) 14:59:51 #startvote Does the TSC agree to create the opera project as an incubation project in OPNFV? (-1, 0, +1) 14:59:51 Begin voting on: Does the TSC agree to create the opera project as an incubation project in OPNFV? Valid vote options are , -1, 0, +1, . 14:59:51 Vote using '#vote OPTION'. Only your last vote counts. 14:59:53 #vote +1 14:59:53 #vote +1 14:59:58 #vote +1 15:00:00 #vote +1 15:00:01 #vote +1 15:00:04 #vote +1 15:00:04 #vote +1 15:00:09 #vote +1 15:00:09 #vote +1 15:00:19 #vote +1 15:00:22 #vote +1 15:00:36 #info proxy for Brian Skerry 15:00:37 #endvote 15:00:37 Voted on "Does the TSC agree to create the opera project as an incubation project in OPNFV?" Results are 15:00:37 +1 (11): frankbrockners, dku, dneary, bryan_att, Julien-zte, ChrisPriceAB, rpaik, JonasArndt, tallgren, edgarstp, ulik 15:01:05 #endmeeting