14:57:56 #startmeeting OPNFV TSC 14:57:56 Meeting started Tue Feb 3 14:57:56 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:57:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:57:56 The meeting name has been set to 'opnfv_tsc' 14:58:09 #topic roll call 14:58:15 #info Chris Price 14:58:51 #info Uli 15:01:42 #info palani 15:01:52 #info Hui 15:02:30 #info Frank Brockners 15:02:55 #info Thinh Nguyenphu 15:03:54 #info Ashiq Khan 15:04:51 #topic Approval of previous minutes 15:05:09 #info julien_ZTE 15:05:10 #agreed Previous minutes approved. 15:05:18 #topic Agenda Bashing 15:05:20 #info Wenjing 15:05:21 #info Parviz Yegani 15:06:23 #info Tapio Tallgren (Nokia) 15:08:02 #info Adding an item from aric to the agenda related to release 1 topics 15:08:35 #info Lingli, asks to review the dpacc project earlier in the agenda 15:08:42 #agree moved to the first item 15:09:27 #info ashiq asks if we can discuss the deliverable of the requirements on the call 15:09:37 #agree added to the development process discussion 15:10:06 #topic Creation review for the dpacc (Data Path Acceleration) project 15:10:25 #link https://wiki.opnfv.org/requirements_projects/data_plane_acceleration 15:11:26 #chair frankbrockners 15:11:26 Current chairs: ChrisPriceAB frankbrockners 15:11:35 #chair uli 15:11:35 Current chairs: ChrisPriceAB frankbrockners uli 15:11:41 #chair rapik 15:11:41 Warning: Nick not in channel: rapik 15:11:41 Current chairs: ChrisPriceAB frankbrockners rapik uli 15:11:46 #chair rpaik 15:11:46 Current chairs: ChrisPriceAB frankbrockners rapik rpaik uli 15:12:36 #info Lingli describes the histroty for proposing the dpacc project, and outlines the proposal according to a summary of the WiKi description 15:14:41 #info Dirk Kutscher 15:14:43 #info Lingli describes and internal proof of concept for small cell gateways that has identified the needs for dpacc like functionality in the platform 15:15:42 #info the goal is to decouple the application layer from the hardware layer, an issue arises in the performance of virtualized devices that requires higher datapath throughput. 15:16:44 #info there is an identified need for common API's to present the needed capabilities for dataplane acceleration in a common way for high throughput devices in a virtual environment. 15:20:50 #info Lingli outlines the focus interfaces for the activity according to the ETSI NFV functional architecture representative diagram. 15:26:15 #info Joseph asks if the proposed changes recently received by the community have been considered. 15:26:39 #info Bryan Sullivan 15:26:52 #info the changes have not yet been able to be incorporated onto the WiKi page, and that further discussions may be required regarding that contribution 15:27:31 #info the changes are not deemed to impact the scope or deliverables targetted for the project. 15:30:15 #info Bob Monkman identifies some changes that may be resultant of the proposed project scope. 15:32:00 #undo 15:32:00 Removing item from minutes: 15:32:07 #info Bob Monkman identifies some changes that may be resultant on the proposed project scope. 15:38:22 #info suggestion from the TSC is for the dpacc project team to revise the wiki/project proposal and come back for a quick review next week 15:39:20 #topic OPNFV Release 1 updates 15:40:48 #info frankbrockners indicates the team is making progress with two efforts on the installer component. The efforts looks to extend existing installer tools with OPNFV delta's. 15:41:39 #info One approach looks to leverage Fuel as an installer, the other approach looks to leverage quickstack and khaleesi to achieve the same goals. 15:42:23 #info OpenDaylight has been integrated into the tools. Demostrations are planned for these foundations on Monday of next week. 15:43:08 #info once the foundation is established the ability for the broader community to add components of the BGS project and establish a goal for march. 15:43:43 #link https://wiki.opnfv.org/get_started/get_started_installer_approach 15:45:03 #info bryan_att asks for clarifications on the way ODL is integrated. 15:45:45 #info frankbrockners describes some of the options being used to approach this task. 15:46:26 Following Chris's call for volunteers to BGS, docomo will provide one (B. Souville). Hopefully he'll be of some help. 15:47:36 #info Uli outlines the CI updates to the diagram meetings on octopus. Progress is being made on the structure and still awaiting the concrete outputs from BGS. 15:47:43 #link https://etherpad.opnfv.org/p/octopus 15:47:57 #info interfaces/dependancies on other porects are being defined. 15:47:58 #info See https://wiki.opnfv.org/get_started/get_started_installer_approach for the installer approach in BGS (2-phase approach) 15:49:23 I am planning to install BSG on a couple of servers, should I try quickstack and khaleesi? Or Fuel? 15:50:04 #topic Project leads discussion 15:50:46 #info aricg asks for project to nominate leads for the project regarding jira and contact for aricg on the project needs and committer roles. 15:51:54 #info Uli asks if the projects should assign a project leader. 15:52:12 I think I lost audio 15:52:30 * ChrisPriceAB we wil carry the discussion aricg :) 15:53:02 #info Heather clarifies that for administrative and infrastructure needs a project representative is needed. 15:55:13 #info send names of project contact person (from the list of committers) to Aric 15:56:30 in future meeting we should firm up job-description of Project Lead, and then decide when/how we will elect them. 15:57:34 #action Ray/Aric to send emails to mailing lists on project contact persons 15:58:44 #info fbrockners suggests it’d to good to create a teample for project repo names/contact persons/etc. (“key project facts”) 15:59:49 #topic OPNFV Security Discussions 16:00:20 #info Luke Hinds describes that some e-mail discussion has occured around establishing a secuiry community 16:00:36 #info Luke sent an e-mail thread to describe what this might mean 16:03:29 #info areas of interest; security discussion list, advisory group, working with other security groups, governance risk and compliance feedbacks, covering eventually LI and security architectures. (potentially software reviews) 16:07:39 #info frankbrockners describes that some functions of the security group may want to integrate themselves with OPNFV operational activities. 16:09:19 #topic development process 16:28:49 #info discussion occurred :D 16:29:25 #topic Creation review for the Parser project 16:29:49 #link https://wiki.opnfv.org/parser 16:30:31 #info the proposal has been modified to clarify the scope of the project. 16:30:49 #info further discussion on the mailing list for defining methods for working with upstream communities (amongst requirements projects) 16:31:24 #info Parser will provide a template translation engine, in the form of a tool to perform this function 16:32:24 #info Parser provides an interface northbound of the VIM on the NFVI interface 16:32:57 #info intending to be implemented as an integration and testing project 16:34:01 #info Parser aims to deliver a translation to HOT, but could be extended to other formats 16:38:39 #info bryan_att asks if this proposal is adopting some functionality of the orchestrator. 16:39:37 #info uli responds that parser will only consumer deployment templates for functions to HOT 16:50:11 a diverse group of OPNFV community want to work on this. How would approving this project hurt folks who are putting up all this resistance? 16:54:27 TSC job is to allow them to work on what they want to work on. You don't have to like it or care about it or anything else. 16:55:43 I think this is a question of whether this is properly in the scope of OPNFV, as outlined in the founding documents 16:56:37 Also, this needs to fit into the ETSI and OPNFV reference architectures 17:01:38 #vote Vote to create the Parser project in OPNFV? (+1, 0, -1) 17:01:40 #vote +1 17:01:44 #vote +1 17:01:45 #vote +1 17:01:46 #change the repo name to “parser” 17:01:48 +1 17:01:53 #vote +1 17:01:55 #vote +1 17:02:02 #vote +1 17:02:05 #vote +1 17:02:09 #vote +1 17:02:24 #vote +1 17:02:27 #vote +1 17:02:34 #endvote 17:03:25 exit 17:03:26 exit 17:03:34 #agree the Parser project was approved for creation 17:03:37 #endmeeting