14:30:07 <debrascott> #startmeeting Brahmaputra Daily Standup
14:30:07 <collabot`> Meeting started Thu Mar  3 14:30:07 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:07 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:30:07 <collabot`> The meeting name has been set to 'brahmaputra_daily_standup'
14:30:17 <debrascott> #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes
14:30:21 <debrascott> #topic roll call
14:30:32 <radez> #info Dan Radez
14:30:41 <DanSmithEricsson> #info Dan Smith
14:31:42 <ashyoung> #info Ashlee Young
14:32:00 <radez> 238069
14:32:10 <debrascott> will wait a minute for people to join
14:32:31 <debrascott> understand some may be multitasking with technical call
14:33:16 <narindergupta> #info Narinder Gupta
14:34:21 <joekidder> #info Joe Kidder
14:34:33 <debrascott> #topic proposed schedule
14:34:39 <debrascott> #link https://etherpad.opnfv.org/p/steps_to_brahmaputra
14:35:33 <debrascott> to all: is this schedule reasonable?
14:36:33 <debrascott> we could push out a few days into the last week of Mar
14:36:50 <debrascott> so as not to release on a Monday
14:38:01 <debrascott> radez, narindergupta, ashyoung, DanSmithEricsson: ^^
14:39:26 <narindergupta> debrascott: yeah release should not be on Monday any last minute changes need runs to be on weekend. So would suggest delay it by couple of more days
14:39:32 <narindergupta> rest looks ok to me
14:39:44 <radez> +1
14:39:48 <radez> to narindergupta's comment
14:39:52 <ashyoung> debrascott: +1
14:40:18 <debrascott> OK, I will propose then that we move it to Thursday of the same week
14:40:34 <narindergupta> thats sounds good to me
14:40:48 <debrascott> Will anyone be taking time off over spring break that might impact other dates?
14:41:58 <debrascott> I will be out at least part of the time but could be online as needed
14:42:29 <debrascott> ok if no other feedback will moce on
14:42:45 <debrascott> #topic Installer scenario status
14:42:57 <debrascott> radez: Apex progress?
14:43:46 <debrascott> were you able to try odl-l3?
14:44:10 <radez> sry I got disonnected, debrascott was that directed at me?
14:44:35 <debrascott> radez: yes, had pinged you for Apex progress
14:44:45 <radez> Spent good time yesterday in discussion with ashyoung on ONOS and got an ODL-L3 env spun up and tested
14:45:10 <radez> we're still working on some of the ODL-L3 configs, at this point is looks like ODL-L3 may have the same gateway problem we're having with ONOS
14:45:25 <radez> I plan to be back in touch with ODL folks today to conitniue debugging
14:45:41 <debrascott> oh interesting
14:45:56 <ashyoung> debrascott: Bob Zhou on our side also reproduced this on ODL last night
14:46:18 <radez> I've not looked at his email yet... I saw there was one from him
14:46:47 <ashyoung> radez: Yeah, he let you know
14:46:57 <radez> cool, thx ashyoung
14:46:59 <ashyoung> We are looking into a community solution for both controllers
14:47:23 <ashyoung> Our concern is fixing this to break another area
14:47:39 <debrascott> #info Apex got an ODL-L3 env spun up and tested. Still working on some of the ODL-L3 configs, at this point it looks like ODL-L3 may have the same gateway problem we're having with ONOS. ONOSFW team reproduced on ODL as well.
14:47:53 <radez> so maybe in the short term we could get an envoronment change for the LF pods
14:48:27 <ashyoung> Or we can change a rule
14:48:50 <debrascott> radez: does this require hardware in LF pods? or configuration change?
14:48:58 <ashyoung> If we were a bit more isolated, it would be easier. That's what Dan proposed, I think
14:49:17 <ashyoung> Otherwise it requires a rules change on the main LF GW
14:49:25 <radez> debrascott: there are multiple options, I'll contact aric and dsicuss our new results
14:50:03 <debrascott> radez: ok, lmk. Seems odd that 2 controllers have issue with industry standards
14:50:49 <debrascott> radez: I wouldn’t think this is a new standard/best practice considering security implications
14:51:31 <radez> debrascott: agreed, I thikn we need to address this in the projects and figure out if there's jusitification for this design
14:51:41 <radez> but we also need to validate what we have
14:51:48 <debrascott> radez: agreed
14:51:57 <radez> so continuing to battle it from both angles seems the best route forward
14:52:17 <debrascott> narindergupta: how is JOID scenario testing doing?
14:52:22 <narindergupta> debrascott: juniper mentioned nonha version of ocl is working and currently debugging HA. And onos we need the MAC of gateway for intel and orange labs as part of CI. As this is requirement deom onos team.
14:52:40 <narindergupta> %s/deom/from
14:53:07 <ashyoung> debrascott: It may not be industry standards
14:54:54 <ashyoung> debrascott: I think we need to be careful how we characterize this. Documenting the issue is a right thing. But we're concluding that 2 SDN controllers are going aginst standards
14:55:16 <ashyoung> debrascott: I think we need to do further work here
14:55:48 <radez> agreed, I'm not sure we've found a document that states this is against standards?
14:55:50 <debrascott> narindergupta: is this similar issue to Apex?
14:56:23 <debrascott> ashyoung, radez: agreed but then again that is what we are here to uncover and bring to the communities
14:56:28 <narindergupta> debrascott: in case of joid it was vping which was failing
14:57:11 <narindergupta> debrascott: and root cause way gateway MAC was not defined in onos-controller
14:57:28 <debrascott> narindergupta: ok so different issues, that’s right. Thanks for reminding me
14:58:31 <ashyoung> debrascott: I think Bob is currently mapping out the network config so we can see what's really going on here. Patrick Liu is also working on this. We have people from both ONOS and ODL on this
14:58:31 <ashyoung> debrascott: Agreed. I'm recommending against drawing conclusions that anyone is violating standards
14:58:54 <debrascott> ashyoung: agreed, tactful messaging is needed
14:59:44 <debrascott> narindergupta: do you have contacts at intel & orange labs working on MAC of gateway?
14:59:57 <narindergupta> debrascott: yes i do
15:00:10 <narindergupta> thanks for asking though
15:00:42 <debrascott> OK just going to info this in and then we can close the meeting
15:00:48 <ashyoung> narindergupta: Are you working with anyone on the updated charm?
15:00:48 <ashyoung> narindergupta: Anything I can do there?
15:01:00 <debrascott> #info: uniper mentioned nonha version of ocl is working and currently debugging HA.
15:01:24 <debrascott> #undo
15:01:24 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2fe1e50>
15:01:49 <narindergupta> ashyoung: yes york is helping me
15:01:52 <ashyoung> debrascott: People get a little sensitive when told they have bugs, which may not be bugs  :)
15:02:32 <debrascott> #info JOID Juniper mentioned non-ha version of ocl is working, debugging ha
15:02:56 <ashyoung> I've gotta run. Sorry!
15:04:30 <ashyoung> narindergupta: Cool!
15:04:40 <debrascott> #info: Joid ONOS need MAC gateway defined for onos-contoller in intel & orange pods
15:04:58 <debrascott> thanks all for attending
15:05:35 <debrascott> #endmeeting