20:10:24 #startmeeting 20:10:24 Meeting started Thu Mar 20 20:10:24 2014 UTC. The chair is regXboi. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:10:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:10:40 we''re starting real soon 20:10:47 now operational 20:10:49 starting now. 20:10:53 Anyone else hit an issue with connecting to the WebEx ? 20:11:00 #topic minutes from last meeting 20:11:17 #link http://meetings.opendaylight.org/opendaylight-group-policy/2014/opendaylight-group-policy.2014-03-13-20.03.html 20:11:36 I'm now in the WebEx. 20:11:48 people, please #info in if you are attending 20:11:54 #info Ryan Moats (regXboi) 20:11:59 #info Thomas Bachman (tbachman) 20:12:33 @RobDolin please see the URL above 20:12:48 I can send it again 20:12:53 #info Raghurama Bhat (raghu67) 20:13:06 https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4PO9GTADM5ZZWKPF30D5WC98O-9VIB 20:13:12 here it goes. 20:13:57 for all who missed it - webex recording has started 20:14:14 #info discussion of read-only on project wiki page 20:14:25 #action for DConde is to create a Gdoc with Use Cases 20:14:38 #info Rob Dolin (RobDolin) 20:14:39 #info it is not possible to mark project page read-only, best is we can track and follow 20:14:44 #action and link from main Wiki to the Use Case gDoc 20:15:57 #info signup for action items 20:16:32 should we add in the link? 20:16:39 please 20:17:10 #link https://wiki.opendaylight.org/view/Project_Proposals:Group_Based_Policy_Plugin#Design_Tasks 20:17:11 #Info Architectural considerations assigned to Ryan and Mike -- this is item #1 20:17:19 #link https://wiki.opendaylight.org/view/Project_Proposals:Group_Based_Policy_Plugin 20:17:30 ah 20:17:35 regXboi: beat me to it 20:17:37 sorry :) 20:18:04 ryan? 20:18:51 #info repeating previous one is really @regxboi and @dvorkinita 20:21:18 #agreed we will help MD-SAL owners 20:21:49 #topic Model 20:22:43 #agreed we create subgroup to split model. @dvorkinista and regxboi and Dolan 20:24:18 #agreed to add Mickey and Derek from Plexxi 20:24:37 #agreed add s3wong 20:24:44 that was odd 20:24:47 and not fun 20:24:50 but I am back 20:25:01 cool 20:25:01 #info we will review in these weekly meeting but we will have checkpoint meetings for details outside the weekly. 20:25:28 the purpose is to refine the model and to follow-up reviews. 20:25:46 the scope of the model in a wider forum. 20:25:52 but smaller group will work on details. 20:26:20 dconde: Dolan should be RobDolin 20:26:21 alagalah says if we have serious objections it should have been aired already. 20:26:28 Lost my IRC connection around 1:19pm (Pacific), back now 20:26:39 @s3wong - Thanks :) 20:27:31 #topic TOpic 3 is subscribe 20:27:40 #info it means how to subscribe to MD-SAL 20:27:48 #topic handing how subscribe topic 20:27:51 renderers is an arch hashout. 20:28:10 I would also like to work on #2 Model 20:28:26 renderers subscribe to things. 20:28:38 and renderers down to substrate 20:28:43 dconde: 20:28:53 Did you get an agreement on #2 20:28:57 oh ah... 20:29:00 I see part of it 20:29:02 n/m 20:29:05 ack 20:29:16 Alagala we agreed that we split into subgroups. 20:29:23 cool 20:29:25 #agreed on topic 2 to get subgroups. 20:29:53 alagalah: I think dconde listed the members of the model subgroup above 20:29:59 ack 20:30:16 I'll check the minutes and if it's missing, we'll catch it next meeting 20:30:16 #topic 3 NB APIs 20:30:30 #info we should have separate API discussion. 20:30:36 #topic handing out NB APIs 20:30:47 #info topic 3 and 4 falls into architecture. 20:30:51 dconde: it turns out that only I can #topic as the chair :( 20:31:09 #info 3, 4, 5 are architetural 20:31:37 I would like to work on #6 as my team is already doing some work on ODL Host Tracker liker porting to MD-SAL 20:31:37 #info redo 3,4 as architectural as MD-SAL in today's thinking 20:32:31 we need to set up requirements and choose what is possible and what is not in MD-SAL 20:32:32 if 5 isn't architectural, I can take that (though the repo may still be linked to MD-SAL?) 20:33:18 #info maybe we need to pull more people into MD-SAL. 20:33:34 #info we can learn MD-SAL. It's Yang (that part is easy) 20:33:43 the hard part is the implementation 20:34:39 Prasad is also in on MD-SAL 20:34:58 dvorkinista is on 5 20:35:06 which is the policy repsitory. 20:35:17 s3wong is on 5 20:35:30 topic changes to EP R egistry. 20:35:33 #agreed 5 is dvorkinista and s3wong 20:35:40 topic is no. 6 now. 20:35:42 #topic changes to EP Registry 20:36:19 big intersection between EP and GBP Repo 20:36:24 so it needs to be same people; 20:36:32 cannot be designed disjointly. 20:36:42 I would like to be involved in both then 20:36:56 raghu67: of course, thanks! 20:37:16 topic 7 is NBI 20:37:27 #topic impl method/proc 20:37:29 we are now n topic 8 20:37:33 #info this is NBI 20:37:38 #topic datastore 20:37:49 * regXboi looks at the wall quietly 20:38:23 who knows datastore well. 20:38:34 someone who knows scalable distributed datastore 20:39:04 Ready, Fire, Aim 20:39:46 #info datastore has questions (a) are we going to use the MD-SAL? only because it has API Requirements on the Datastore 20:40:00 (b) how are we going to implement it. shall we use off the shelf stuff? 20:40:22 dvorkinista says we need to use a SUITABLE datastore. don't just use Cassandra just because it's there. 20:40:40 Is it safe to assume that AD-SAL is here forever and that ODL as a platform isn't moving to MD-SAL? Is this a GBP decision or ODL decision? 20:40:42 anyone with experience? 20:41:30 regxboi and s3wong and hemand and dvorkinista are on it. 20:41:43 s/hemand/hemant/ 20:41:47 on topic 9 20:41:50 #agreed regxboi and s3wong and hemant and dvorkinista are on 8 20:42:07 operational state - stats and faults. 20:42:21 #topic operational state - stats, faults 20:42:29 it is landing on regxboi 20:42:34 #agreed for regxboi. 20:42:41 anyone else? 20:42:48 we need more hats. 20:43:04 #agreed for raghu67 to be on it. 20:43:07 #info raghu67 can be part of 9 20:43:30 regxboi says we need a real auditing framework into controller and leverage it. 20:43:42 dvorkinista says how it makes sense in what we are building? 20:44:09 #info 9 seems to be general to entire ODL and not specific to GBP 20:44:13 #info oops we have two item 2. 20:44:17 #topic conflict box 20:44:30 topic is now 10 20:44:36 who is doing renderers 20:44:45 how it works, responsibilities, 20:44:57 sitting on the domain substrate 20:45:30 #info mickey says two renderers. Native vs. general 20:45:45 affinity is ONE renderer. 20:45:48 of many. 20:46:10 I will work on 10 Also 20:46:12 it's kind of related to policy and operational stuff 20:46:36 #agreed dlenrow takes that 20:46:42 #info topic includes renders 20:46:46 #agreed lender takes that. 20:46:48 er #info that is renderers 20:47:02 sorry. autocorrect messing with me 20:47:08 #agreed lenrow takes that. 20:47:45 regxboi ask mickey what is promised? 20:47:57 so we can put in placeholders. 20:48:03 Mickey will talk w/ regxboi 20:48:20 prasad is on rendering 20:48:26 I need to drop to walk to another building for a 2pm. :( 20:48:27 #info prasad is on rendering 20:48:36 I'll look forward to reading the minutes. 20:48:47 no kidding - these are going to be schizo 20:49:14 Any plans to use F2F time at Hackfest Napa? 20:49:26 DConde will assign people per action items as listed above. 20:49:39 and figure out meetings which are separate from these weekly meetings. 20:49:54 intention will be that this weekly meeting is a status update. 20:49:58 #topic this meeting going forward 20:50:00 lenrow: it conflicts with OVS hackathon, so I won't be at Napa for ODL hackfest 20:50:08 #info this meeting will be status updstes 20:50:11 in a passive/aggressive way, this meeting becomes meaningless. 20:50:12 #info updates 20:50:25 That was unfortunate hackathon collision 20:50:28 #topic hackfest 20:51:09 #info do we want to try to have a breakout at the hackfest 20:51:22 #info do we want to cancel next week's call for the hackfest? 20:51:28 #info I will be at the Napa Hackfest on both days 20:51:38 +1 for canceling next week's meeting 20:52:06 #agreed next week meeting is canceled 20:52:07 +1 for cancelling next weeks meeting and having a breakout session at Napa 20:52:13 +1 Cancel next call 20:52:38 Aim for Thursday Napa GBP Arch breakout? 20:52:38 #action alagalah to answer networkstatic's email to discuss list on standing meet time and channel 20:52:54 #action alagalah to update wiki page with next week meeting cancelled 20:54:01 #info we realize the hackfest schedule is still loose 20:54:12 #info Thurs seems best for breakout? 20:54:18 #info regXboi will not be physically at the hackfest, will be virtual 20:55:25 we are discussing Cricket now. 20:55:33 #endmeeting