14:04:20 #startmeeting OPNFV Technical Discussion of Project Proposals 14:04:20 Meeting started Thu Jan 22 14:04:20 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:20 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:04:20 The meeting name has been set to 'opnfv_technical_discussion_of_project_proposals' 14:04:28 #chair bin_ 14:04:28 Current chairs: ChrisPriceAB bin_ 14:06:39 #topic Agenda Bashing 14:07:02 #info bin reviews the planned agenda on the wiki page 14:07:24 #link https://wiki.opnfv.org/wiki/weekly_technical_discussion 14:07:55 #topic OpenStack based VNF forwarding graphs 14:08:26 #link https://wiki.opnfv.org/requirements_projects/openstack_based_vnf_forwarding_graph 14:09:46 #info Eugene leads the discussion outlining the proposal. 14:10:18 #info The project is intended as a requirement project working together with the openstack community 14:16:30 #info the main target components for the requirement project will be on the virtual infrastructure components of the overall architecture. 14:17:08 #info some updates may be made to the proposal to clarify the scope to make the project scope clearer. 14:18:29 #info Bin asks if the project will use an intent model to build the forwarding graph, or another approach. 14:19:02 #info Eugene answers that those details have not been determined at this time. 14:21:07 #info the details of the intended implementations are not able to be described at this time, as a requirement project it is interesting to understand the scopes and yet the detsiled implementation may not be relevant to the requirement project scope. 14:21:44 #info Further e-mail discussion can help clarify the project scope, or e-mail comunication with Cathy can be used to help clarify. 14:22:48 #topic Failure Prediction review 14:23:14 #link https://wiki.opnfv.org/requirements_projects/failure_prediction 14:23:53 #info hailiu describes the project intention according to the wiki description. 14:27:33 #info Ryota asks who is the receiver (or has visilibity into) the meta-data? He describes that monasca may be relevant. 14:29:16 #info Some clarification that the project is focused on data collection, use cases should be possible to be applied to that. 14:29:47 #info further clarification on the use cases is requested to help define the goal of the project proposal to define the actions expected from the use cases. 14:30:30 #info It is expected that other projects, such as the Doctor project, would be able to use the output of this project receiving notifications of potential failures. 14:30:54 #info this would allow preventative actions to be taken by entities receiving the data. 14:36:55 #topic Project review of resource scheduler 14:37:05 #link https://wiki.opnfv.org/requirements_projects/resource_scheduler 14:37:54 #info Zhiqi describes the project according to the wiki page 14:47:12 #info this project has strong relationships with the copper and promise projects, coordination and co-consumption of project findings will be important to the project. 14:48:32 #info enhancements to the Nova scheduler is a key area of development, including resource isolation. 14:50:30 #info some discussion continues around the relationship between promise and the resource scheduler project. This could be made clearer in the project proposal for clarity.