14:00:15 #startmeeting OPNFV TSC 14:00:15 Meeting started Tue May 31 14:00:15 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:15 The meeting name has been set to 'opnfv_tsc' 14:00:19 #topic Roll Call 14:00:26 #info Chris PRice 14:00:33 #info Gerald Kunzmann 14:00:34 #info Morgan Richomme (IRC) 14:00:43 #info Mark Beierl (Proxy for Edgar StPierre) 14:00:49 #info DENG Hui 14:00:51 #info Jonas Arndt 14:00:58 #info Jack Morgan 14:01:04 #info Bin Hu (for Bryan Sullivan) 14:01:09 #info Dave Neary (for Chris Wright) 14:01:31 #info Frank Brockners 14:01:43 #info Uli Kleber 14:01:57 #topic Approval of previous minutes of meeting 14:02:03 #info rprakash 14:02:07 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-May24,2016 previous minutes 14:02:32 #agree the TSC approved the previous minutes of meeting 14:02:40 #topic Agenda Bashing 14:02:51 #link https://wiki.opnfv.org/display/meetings/TSC current agenda 14:02:52 #info Tapio Tallgren 14:03:26 we now have a quorum 14:05:21 #info ChrisPriceAB wants to add a design summit update 14:06:19 #info Uli-K adds we should review the SFC scope adjustment 14:06:58 #topic Joint Board-TSC meeting in Berlin 14:07:18 # info Parviz Yegani 14:07:32 #info Chris has not made any progress on the joint TSC Board meeting agenda 14:08:10 #info The two current topics from the TSC are TSC composition, and SPC interactions 14:09:17 #info rpaik adds there may be room to present and discuss the bitergia dashboard and planning proposals. 14:10:11 #info chrispriceab adds it may be worth having an infra WG readout 14:10:37 #topic OPNFV Code of Conduct 14:11:03 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=6816470 code of conduct proposal 14:11:25 #link https://wiki.opnfv.org/display/SKETCH/Proposed+change+to+the+TSC+Charter proposed changes to the TSC charter 14:15:36 #startvote Does the TSC approve the code of conduct and propose the identified changes to the charter to the board? (-1, 0, +1) 14:15:36 Begin voting on: Does the TSC approve the code of conduct and propose the identified changes to the charter to the board? Valid vote options are , -1, 0, +1, . 14:15:36 Vote using '#vote OPTION'. Only your last vote counts. 14:15:53 #vote +1 14:15:54 #info JUlien 14:15:54 #vote +1 14:15:54 #vote +1 14:15:55 #vote +1 14:15:56 #info Julien 14:15:57 #vote +1 14:15:58 vote +1 14:16:01 #vote #1 14:16:01 mbeierl: #1 is not a valid option. Valid options are , -1, 0, +1, . 14:16:01 #vote +1 14:16:04 #vote +1 14:16:07 #vote +1 14:16:08 #vote +1 14:16:12 #vote +1 14:16:13 #info proxy for Parviz 14:16:21 #endvote 14:16:21 Voted on "Does the TSC approve the code of conduct and propose the identified changes to the charter to the board?" Results are 14:16:21 +1 (10): dneary, GeraldK, Julien-zte, ChrisPriceAB, ttallgren, JonasArndt, DENG, mbeierl, rpaik, ulik 14:16:52 #action rpaik to have the legal team review the changes to the charter prior to presenting it to the board. 14:17:15 #topic Colorado planning and activities 14:17:19 #chair rpaik 14:17:19 Current chairs: ChrisPriceAB rpaik 14:18:11 #info The PTL community have responded strongly around the code freeze date for Colorado resolving to the date of August 15 to code freeze 14:18:35 #info this closes the last pending items to resolve on the Colorado timeplane 14:18:35 #link https://wiki.opnfv.org/display/meetings/Release?preview=/6819702/6821665/colorado%20r6.pdf 14:19:43 #info proposed release date is September 22nd 14:21:13 #info ebrjohn Brady Johnson, SFC Project Lead 14:21:55 #info frankbrockners notes that OpenDaylight will not code freeze by August 15th and this may mean that we need to go with ODL Be for the Colorado release 14:23:55 sorry for pointing the obvious but having different odl versions will impact test projects 14:25:16 fdegir: I guess we should have scenarios defined for those versions that should help with prep for the impact 14:25:55 that's right ildikov 14:26:47 fdegir: /me is sorry too for stating the obvious :) 14:28:20 I think the idea of the code freeze is that we ensure scenario's are not changing versions of upstream after the code freeze date to allow for testing to focus on stable (if faulty) scenario's 14:29:06 these can then be updated with iterative releases providing bug fixes and greater stability. 14:31:58 #action dmcbride to update the project release diagram with code freeze dates and nomenclature. 14:32:04 #topic SFC scope adjustment 14:32:08 #link https://wiki.opnfv.org/display/sfc/Service+Function+Chaining+Home SFC Wiki 14:33:41 #info the scope change is described in the section of the above wiki page under: Proposed Scope change for the Colorado release 14:34:10 #info scope change request is to add the VNF Manager 14:34:34 #info Final point: In subsequent releases, OPNFV SFC may also use MANO-based Orchestration 14:36:24 rpaik: just FYI its not just a VNF Manager, but also NFV Orchestrator 14:36:55 trozet, yup I think ebrjohn added that note 14:36:59 ah 14:40:16 #info SFC project just want to use Tacker as the VNFM not develop or test for Tacker 14:42:49 #info ebrjohn notes that the plan is to use Tacker for Colorado 14:43:00 #startvote Does the TSC approve the proposed scope change of the SFC project as described on the SFC wiki? (-1, 0, +1) 14:43:00 Begin voting on: Does the TSC approve the proposed scope change of the SFC project as described on the SFC wiki? Valid vote options are , -1, 0, +1, . 14:43:00 Vote using '#vote OPTION'. Only your last vote counts. 14:43:03 as we use Cloudify for the vIMS test case in Functest (we did not validate any Mano stack just use one to perform the test...) 14:43:06 #vote +1 14:43:08 #vote +1 14:43:09 #vote +1 14:43:09 #vote +1 14:43:10 #vote +1 14:43:14 #vote +1 14:43:14 #vote +1 14:43:16 #vote +1 14:43:23 #vote +1 14:43:25 #vote +1 14:43:32 #vote +1 14:43:34 #info proxy for Parviz 14:43:38 #endvote 14:43:38 Voted on "Does the TSC approve the proposed scope change of the SFC project as described on the SFC wiki?" Results are 14:43:38 +1 (11): dneary, frankbrockners, ChrisPriceAB, Julien-zte, bin_, ttallgren, GeraldK, DENG, mbeierl, rpaik, ulik 14:43:51 Thanks everybody!! 14:43:52 #agree The TSC agrees to the proposed scope change 14:43:55 morgan_orange, do you mean any requrirement to vote for use Cloudify? 14:44:18 #topic Project proposal review of the VNF Event Stream project 14:44:37 #link https://wiki.opnfv.org/display/PROJ/VNF+Event+Stream project proposal wiki 14:44:42 Julien-zte: no it is already in Brahmaputra 14:45:08 yes, morgan_orange. I don't think there is scope change. 14:45:22 #info the scope includes; a common event data model, platform support for generating the event stream, development of an even collector (for MANO components) to consume the event stream. 14:45:33 Just take Cloudify as another open source tools 14:45:43 Julien-zte: exactly 14:48:02 #info additional contributors will be added to the project from other companies. 14:48:19 no additional committers? 14:48:19 #info dneary asks how this project will engage with other projects. 14:48:48 * ChrisPriceAB thinks its good to keep the list short and build it through weight of contribution. :) 14:54:21 https://github.com/Open-O/vnf-monitor 14:57:27 bin_, I sent you an email several days ago that one of colleague(Li yuanzhen) will contribute as a committer, can you add it in the list 14:59:08 #info Trevor Coopee 14:59:29 #startvote Does the TSC approve the creation of the VNF event stream project? (-1, 0, +1) 14:59:29 Begin voting on: Does the TSC approve the creation of the VNF event stream project? Valid vote options are , -1, 0, +1, . 14:59:29 Vote using '#vote OPTION'. Only your last vote counts. 14:59:31 #vote +1 14:59:32 #vote +1 14:59:33 #vote +1 14:59:37 #vote #1 14:59:37 bin_: #1 is not a valid option. Valid options are , -1, 0, +1, . 14:59:40 #vote +1 14:59:40 #vote +1 15:00:02 #vote +1 15:00:04 #vote +1 15:00:05 #vote +1 15:00:05 #vote +1 15:00:06 #vote +1 15:00:12 #vote +1 15:00:18 #endvote 15:00:18 Voted on "Does the TSC approve the creation of the VNF event stream project?" Results are 15:00:18 +1 (11): frankbrockners, Julien-zte, dneary, GeraldK, bin_, ChrisPriceAB, ttallgren, JonasArndt, DENG, mbeierl, ulik 15:00:38 #agree the TSC approves the creation of the VNF event stream projects. 15:00:46 I will udpate the email from ZTE, bin_ 15:00:52 #endmeeting