15:01:07 #startmeeting nic weekly 15:01:07 Meeting started Fri Mar 27 15:01:07 2015 UTC. The chair is gzhao. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:07 The meeting name has been set to 'nic_weekly' 15:01:15 #topic roll call 15:01:22 #info gzhao 15:01:34 #info tbachman 15:01:34 #info dlenrow 15:01:42 #info Phil Robb 15:01:57 #info hideyuki 15:02:23 #link https://lists.opendaylight.org/pipermail/nic-dev/2015-March/000609.html <-- agenda 15:03:58 #topic PTL update 15:04:45 #info no self nomination so far 15:05:24 #info gzhao sent David B email 15:06:54 #agree PTL self nomination deadline extends to 4/3 15:07:14 #agreed PTL self nomination deadline extends to 4/3 15:07:21 #info agreed with no opposition on call to push deadline for self-nomination for PL to 4/3 15:10:22 #info mlemay suggest two parallel code repository for NIC 15:10:52 #info mlemay agrees with gzhao time is running short 15:12:38 #info dlenrow suggests cut a snapshot for Lithium and have a long term in parallel. 15:13:16 #info mahesh ask which model should NIC use 15:13:55 #info mahesh asks how to define shim layer 15:15:18 #info mlemay says shim layer will use reservation, GBP, SFC in ODL 15:15:44 gzhao: I would like to add VTN into the list. 15:15:50 #undo 15:15:50 Removing item from minutes: 15:16:05 #info mlemay says shim layer will use reservation, GBP, SFC, VTN in ODL 15:16:10 gzhao: Thank you :) 15:16:12 hideyuki: thanks 15:17:28 #info dlenrow says this is a common layer that northbound will talk and eco system build around. 15:18:08 #info Cathy says API is different than GBP 15:20:05 #info LouisF asks mlemay details about shium 15:22:11 #info dlenrow NIC is common layer that can be mapped to different new or existing projects. 15:22:26 Dave; The shim layer will map the common northbound APIs to multiple southbound implementations. 15:23:04 #action dlenrow will draft a wiki page for NIC direction. 15:23:15 Cathy: the common north bound interface will be different from GBP interface, service chaining will be the use case for this release 15:24:24 cathy_: if you like your notes be captured by minutes, please put #info keyword, otherwise it will be lost. 15:24:39 #action mlemay to prepare two repository for NIC 15:24:42 Dave: the common northbound interface will have endpoint definition, redirect operation definition 15:25:06 #action dlenrow to work with mahesh for HP code pass IPR 15:26:20 Cathy: #info Cathy: we have discussed before to use "operation" instead of "redirect" 15:26:46 #info mlemay will propose architecture for review. 15:26:52 cathy_: thanks 15:26:53 gzhao: I thought we are agreed to do an organic version from scratch 15:30:29 dlenrow: can you #info your sentence? 15:32:17 #info mahesh ask if HP code can be refactored to avoid two code base 15:33:55 #info mlemay says technically HP code is too AD-SAL ish or OSGI-ish. 15:34:05 #info there're two parallel approach for NIC: one is contintuing discussion on data model and others for post-Lithium release; another one is creating shim layer from scratch 15:34:43 #info the second one is from Lithium release 15:35:03 helenc878: mlemay is going to prepare two repositories to do in parallel 15:35:20 #undo 15:35:36 #info the second one is for Lithium release 15:35:56 #undo 15:35:56 Removing item from minutes: 15:36:00 #undo 15:36:00 Removing item from minutes: 15:36:06 #info the second one is for Lithium release 15:36:13 #chair dlenrow mlemay helenc878 15:36:13 Current chairs: dlenrow gzhao helenc878 mlemay 15:36:26 helenc878: need to be chair to undo 15:36:47 gzhao: thanks. I saw you did that.lol 15:36:52 I think worst case we throw away 100% of first gen Li shim. All decisions are temporary. Goal is to learn 15:37:50 #info dlenrow build first shim layer with simple definitions 15:38:54 #info Mahesh asks who will be the consumer for the shim layer 15:39:00 Cathy: info# Dave : we have the SFC use case in the NIC web page, We will try to align our northbound API and model with that 15:39:12 #info dlenrow says will be anything to the north of controller 15:39:39 #info dlenrow says we have the SFC use case in the NIC web page, We will try to align our northbound API and model with that 15:39:47 cathy_: just starts with #info 15:40:43 #info: Dave said we have the SFC use case on the NIC page and we will try to aling our northbound API and model with that 15:40:55 #undo 15:40:55 Removing item from minutes: 15:41:04 cathy_: already added that 15:41:43 #Info: you asked me to use #info, so that is why I rewrite it 15:42:13 * gzhao miss tbachman so much 15:42:26 gzhao: am here! 15:42:27 sorry 15:42:30 #topic M3 status 15:42:32 am also coding :) 15:42:34 lol 15:43:51 #info gzhao asks will NIC define Karaf features 15:44:33 #info hideyuki says yes, NIC should define karaf features 15:45:45 #info mlemay says ETA for feature is next Monday 15:46:45 mlemay: you may want to go on mute when not speaking 15:46:52 (makes it hard to hear gzhao_ 15:46:58 mlemay: thx! 15:47:01 sorry 15:47:10 airflow!.. my bad 15:47:24 mlemay: good mic ;) 15:48:08 #topic others 15:52:58 #info gzhao says NIC should be able to catch up in M4,M5 time frame if high level architecture is determined. 15:53:33 #action mehesh will work on for submit HP code for NIC 15:53:42 #endmeeting