17:03:27 #startmeeting: networking_l2gw 17:03:27 Meeting started Mon May 23 17:03:27 2016 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:03:31 The meeting name has been set to '__networking_l2gw' 17:03:50 #topic: Agenda 17:03:54 #link: https://wiki.openstack.org/wiki/Meetings/L2Gateway#Meeting_May_23.2C_2016 17:04:11 #topic: Announcements 17:04:28 We released Mitaka release few weeks back 17:04:40 has anybody had a chance to play with it ? 17:04:56 was no aware that it was out.... 17:04:59 not 17:05:52 oferby : yes - you can pull it from pypi - it was tagged 2016.1.0 17:06:07 will do that tomorrow 17:06:36 https://pypi.python.org/pypi/networking-l2gw 17:07:46 #topic: Patches under review 17:08:05 #link: https://review.openstack.org/#/q/status:open+project:openstack/networking-l2gw,n,z 17:08:34 We are looking good from the patches point of view 17:09:26 #topic: L2GW as cloud interconnect 17:09:56 oferby : I heard you had back issue and hence, could not attend the summit 17:10:06 I was looking forward to meet with you 17:10:16 yes .... too bad for me. really wanted to be there. 17:10:25 to meet you guys. 17:10:43 armax had planned a session on Friday for L2GW 17:10:52 :-( 17:11:21 but, we cancelled it as not many people were not there to participate 17:12:02 before we move on, did you have a chance to check the patch I added for the DVR fix? 17:12:36 oferby : that was on my mind - and kind of slipped 17:12:57 I started to look at it and got distracted - will go back and look at it 17:13:17 no warriesno worries 17:14:27 so, if I understand correctly - in the present implementation - if we have a L2GW connected to a neutron n/w 17:14:35 the new API blueprint was not committed yet. can move to implementation? 17:14:51 we can not route to the gateway from other n/w by using router 17:14:59 the problem is 17:15:41 that in DVR, there is no host attached to the router, so the process fails 17:16:38 so I added a method to look for the SNAT router that is located on the NN and put that host's IP 17:17:56 one time armax was explaining to me an issue which had to do with on the similar line - but, sounded a bit different 17:19:05 if you have a network which is connected to L2Gw and you have other networks which are routed - VMs from the attached network could connect to the L2GW, but the VMs from the other network could not 17:20:07 when you say that you have other that are routed, what L2 is it? is the L2 connected to neutron too? 17:22:04 two different neutron subnets - L3 routing between them - one of these segments is connected to L2GW 17:22:27 the VMs from the other routed subnet could not route to the L2GW 17:22:43 is there a bug on this? didn't see one. I can check this tomorrow. 17:23:57 no - I do not think he filed the bug - he just mentioned to me over a beer 17:24:19 ok. I will check it. 17:24:21 If you have a setup, you can test it - 17:24:28 I will. 17:24:31 this will impact the cloud interconnect 17:24:36 yep. 17:24:39 hence, I thought I mention to you 17:25:53 I will review the DVR patch and will ask others to review as well 17:26:04 great 17:27:56 Are you going to pick the work on the cloud inter-connect work in N release? 17:28:48 I would like to start working on splitting the API from impl, add the new API and start impl, OK? 17:29:58 sorry - did not follow 17:30:58 we talk some time before on splitting the API from implementation 17:31:28 so that others can use their own implementation (Midokura) 17:31:47 Oh I see - got it - I thought you said you were splitting the API itself 17:31:54 this is with the current API 17:32:26 after that I would like to start working on the new API. The one that I posted the blueprint . 17:32:46 got it - 17:33:08 is there a better time to move this meeting to so that more people can attend this meeting? 17:33:36 I can look for alternate slot and move the meeting, if it works better that way 17:33:59 I'm open for suggestions ... just rimember that I'm on GMT +2 17:35:39 so, this is 6PM for you? 17:35:53 20:30 17:36:38 oh I see - that is kind of tight - 17:37:08 I just found out that I'm +3 and not +2 (daylight saving time probably) 17:38:21 so, if we move this meeting to afternoon - say 3pm, will that be better for you? 17:38:24 or 4pm? 17:38:31 sure 17:38:39 4pm PDT 17:39:18 PDT ??? that is in middle of the night for me 17:39:59 yup - I just checked :-) 17:40:25 I was confused between AM and PM :-) 17:40:30 :-) 17:41:13 check with midokura guys as well - and come up with couple of time slots - if it helps, I can move the time around 17:41:29 we could move it one or 1.5 hour earlier 17:42:06 that will be good. midokura guys are in my time zone too 17:42:43 only if we can have more people attend, will be worthwhile to change 17:42:56 right 17:42:57 I can ask India folks as well - this time is bad for them as well 17:43:04 ok 17:43:10 Sounds good 17:43:21 Do we need to discuss anything else? 17:43:59 I just wanted to update you that the fix I made to IDL to support passive mode was committed in OVS project 17:44:13 we can add IDL to L2GW now 17:44:21 oh - cool 17:44:31 great - lets do that 17:44:55 can you send me the link - I will add it to the wiki 17:46:12 https://github.com/openvswitch/ovs/commit/af3582371193ad296801fe5e32803b8faa0dced6 17:46:24 #link: https://github.com/openvswitch/ovs/commit/af3582371193ad296801fe5e32803b8faa0dced6 17:47:37 Thanks 17:48:21 Anything else? 17:48:28 nop 17:48:46 so, let me know after you speak with midokura folks 17:49:01 sure. will email you. 17:49:11 I have to check if the channels are available - 17:49:15 sounds good 17:49:21 thanks 17:49:23 we are done for today 17:49:30 ok. 17:49:34 bye 17:49:36 bye. 17:49:41 #endmeeting