17:03:09 <Sukhdev> #startmeeting networking_l2gw 17:03:10 <openstack> Meeting started Mon Jul 20 17:03:09 2015 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:03:14 <openstack> The meeting name has been set to 'networking_l2gw' 17:03:36 <Sukhdev> #topic: Agenda 17:03:41 <Sukhdev> #link: https://wiki.openstack.org/wiki/Meetings/L2Gateway 17:03:52 <Sukhdev> armax: are you here? 17:03:59 <armax> yes 17:04:25 <Sukhdev> Anybody wants to add/change to the agenda? 17:04:46 <Sukhdev> #topic: Announcements 17:05:17 <Sukhdev> Liberty feature freeze is only month and a half away 17:05:34 <Sukhdev> see release schedule - https://wiki.openstack.org/wiki/Liberty_Release_Schedule 17:06:20 <Sukhdev> #topic: Discussion on the new meeting time 17:06:40 <Sukhdev> I tried to find alternate times for the early morning meeting - 17:07:02 <Sukhdev> I could not find any available channel at 8 or 9AM slots 17:07:07 <Sukhdev> I sent an email about this 17:07:18 <Sukhdev> So, we have few choices: 17:07:31 <Sukhdev> 1) Do not make any change and stay with present slot 17:07:50 <Sukhdev> 2) Move the meeting to PM slot (India AM) 17:08:23 <Sukhdev> time to express opinions :-) 17:08:58 <phanipawan> I would go with option 2 :-) 17:09:01 <marutikamat> With choice 1) it's difficult to get all the developers in the meeting 17:09:30 <Sukhdev> armax and I chatted a bit about option 2 - 17:09:39 <Sukhdev> that has to do with the day and time 17:10:02 <Sukhdev> what time works best for everybody - if we go with option 2 17:10:28 <Sukhdev> armax: is not available on Tuesday PM 17:10:42 <armax> Sukhdev: no, it’s a Monday I am not available 17:10:45 <Sukhdev> India team will not like Friday PM :-):_ 17:11:06 <Sukhdev> armax: oppss…my bad - I meant Monday 17:11:09 <marutikamat> Sukhdev, you and armax suggest some time and we will see whether we are ok with it. 17:11:53 <Sukhdev> Tuesday is actually bad for me and I blamed it on armax :-):-) 17:12:00 <marutikamat> :-) 17:12:02 <armax> marutikamat: it’s probably better the other way 17:12:10 <Sukhdev> so, we have Wednesday and Thursday 17:12:17 <armax> because Sukhdev and I are just two of us 17:12:35 <Sukhdev> armax: +1 17:12:43 <marutikamat> Wednesday evening (Thursday morning for us) looks good to me. 17:13:01 <Sukhdev> marutikamat: what is a good time? 17:13:22 <marutikamat> Any time after 8.00am would be OK with me. 17:13:40 <marutikamat> phanipawan, your suggestion please 17:13:57 <Sukhdev> marutikamat: 8am is 7:30PM for us, right? 17:14:00 <phanipawan> yes, i am also ok with maruti's suggestion 17:14:13 <marutikamat> yes Sukhdev 17:14:15 <phanipawan> 9 AM to 10 AM would be suitable for us 17:14:44 <marutikamat> 9.00am would be 8.30pm for the US folks 17:15:10 <Sukhdev> phanipawan: so, you are saying anytime between 7:30-9:30pm pacific time works for you guys 17:15:25 <Sukhdev> armax: do you any preference? 17:15:40 <armax> Sukhdev: I can’t do during that slot 17:15:54 <armax> Sukhdev: this is getting too difficult I am probably just gonna start not attending anymore 17:15:58 <armax> and be done with it 17:16:00 <armax> :) 17:16:12 <armax> it’s probably easier if we start lifting constraints 17:16:15 <Sukhdev> armax: ha ha funy!!! 17:16:18 <armax> you don’t need nme anyway 17:16:29 <armax> I provide no input whatsover to these meetings 17:16:40 <Sukhdev> armax: really? that is what you think? 17:16:46 <armax> so you guys go ahead…I’ll read the minutes 17:16:59 <armax> and follow up via email if need be 17:17:16 <Sukhdev> armax: does it help if we move to Tuesday in that slot? 17:17:17 <armax> Sukhdev: it’s been a month we’re talking about finding a new slot 17:17:31 <armax> I don’t see any other option, do you? 17:17:54 <marutikamat> I have another suggestion. Let us not change any timings. Let us retain the same timing what we have. And we will do our best to get the maximum attendance. 17:17:56 <Sukhdev> armax: with a bit of compromise, we can come up with a slot 17:18:14 <armax> right, the compromise is: don’t count on my presence :) 17:18:43 <Sukhdev> armax: that is no compromise - you need to upgrade your dictionary :-) 17:19:01 <armax> Sukhdev: probably, but I can provide as much as input as I could offline 17:19:12 <armax> I don’t see my attendance as a must 17:19:23 <Sukhdev> armax: we all do 17:19:40 <armax> I’d rather see ourselves spend time coding/reviewing than scrambling to find a slot 17:19:53 <marutikamat> armax: what if we retain the same timings. Is that OK with you? 17:20:07 <armax> it seems we’ve only done most of the latter than the former lately :) 17:20:22 <marutikamat> :) 17:20:41 <armax> marutikamat: but that doesn’t solve the issue that triggered this quest in the first place 17:21:17 <Sukhdev> armax: I believe part of the reason is that most of the India team can not sign on 17:21:20 <armax> so sure, it’s ok with me, but what’s the point in keeping the slot if that makes harder for you guys to participate? 17:21:34 <armax> Sukhdev: right that’s my point 17:22:10 <Sukhdev> armax: Is Tuesday evening any better for you? 17:22:25 <marutikamat> phanipawan, what is your thought on this given that this meeting occurs once in 15 days. 17:23:07 <phanipawan> marutikamat: i am ok with the same time slot for now 17:23:15 <marutikamat> According to me, let us not spend time in finding a new slot and continue how it is. We will see how the next meeting goes. 17:23:27 <phanipawan> If everyone is able to attend on this time then we will not change it 17:23:28 <armax> Sukhdev: yes 17:23:45 <Sukhdev> Looks like we are reaching somewhere folks - 17:24:04 <Sukhdev> how about we try Tuesday 8:30pm (PT)? 17:24:37 <Sukhdev> armax seems to be OK on Tuesday - I have something else, but, I can punt it (as it is only every 15 days) 17:24:40 <marutikamat> I am OK with this time. 17:24:52 <phanipawan> i am ok with this time 17:25:21 <Sukhdev> armax: but, keep in mind, we need you here - you are equal partner in crime :-):-) 17:25:44 <marutikamat> :) 17:25:51 <marutikamat> +1 Sukhdev 17:25:52 <Sukhdev> I will look for a channel on Tuesday PM - and let you guys know 17:25:56 <armax> ok 17:26:04 <armax> I said that 8.30 PST doesn’t work for me 17:26:11 <armax> I told you this is hopeless 17:26:22 <armax> either PST or PDT 17:26:31 <marutikamat> Sukhdev, if you don't find a channel, then let us not discuss further and retain the current timing. 17:26:59 <armax> Sukhdev: I am sorry, I don’t want to be one getting in the way hence I said I won’t be joining 17:27:36 <Sukhdev> armax: OK - let me see what can I do - otherwise, we will stay with the current time 17:27:50 <Sukhdev> enough time on this - lets move on 17:27:51 <marutikamat> I agree 17:27:53 <armax> Sukhdev: ok 17:28:00 <Sukhdev> #topic: CI breakage 17:28:16 <Sukhdev> #link - https://review.openstack.org/#/c/200210/ 17:28:41 <Sukhdev> I see several comments on this patch - trying to get a sense as to what is going on 17:28:43 <armax> Sukhdev: I am working on it 17:28:46 <Sukhdev> I saw email from marutikamat as well 17:28:53 <armax> bear with me until I get this sorted 17:29:18 <Sukhdev> armax: OK - as long as you are on top of it, then I can sleep easy :-) 17:29:35 <armax> Sukhdev: this has to do with poor management of python depedencies 17:29:41 <Sukhdev> marutikamat: you want to say something about failure as well 17:29:46 <armax> Sukhdev: we’re in a bit of a pickle but we’ll figure it out 17:30:17 <Sukhdev> armax: I have wasted tons of time sorting these things for Arista CI as well :-) 17:30:23 <Sukhdev> armax: it is nightmare 17:30:30 <armax> Sukhdev: that’s the openstack way 17:30:38 <armax> Sukhdev: enjoy 17:30:41 <armax> :) 17:30:46 <marutikamat> check_migration fails for all the services. this is the reason pep8 fails on l2gw master branch. other services like lbaas and vpnaas have disabled check_migration in tox.ini for the time being. 17:30:53 <Sukhdev> At one point I was seeing py27 errors - are those gone? 17:31:03 <armax> marutikamat: this must be a regression 17:31:22 <armax> marutikamat: the projects that you mentioned had that check disabled long time ao 17:31:23 <armax> ago 17:31:47 <marutikamat> ok 17:31:55 <armax> I’ll check with HenryG 17:32:06 <marutikamat> Thanks armax 17:32:54 <Sukhdev> armax: thanks - and, BTW, did you say we do not need you here? 17:33:08 <Sukhdev> :-) 17:33:10 <marutikamat> :) 17:33:22 <Sukhdev> #topic: Bugs 17:33:24 <phanipawan> :-) 17:33:33 <armax> Sukhdev: well I can do this via email 17:33:34 <armax> :) 17:33:37 <armax> Sukhdev: as I just did 17:33:48 <Sukhdev> I wanted to discuss our bugs a bit 17:34:02 <Sukhdev> I see several unassigned 17:34:09 <Sukhdev> those are mainly features 17:34:31 <marutikamat> Yes. Last week, I went through the list and found that most of them are enhacements. 17:34:35 <Sukhdev> We are only 1 1/2 month away from the feature freeze 17:34:57 <Sukhdev> shall we discuss which one makes sense? 17:35:08 <marutikamat> I have posted a new patch for one of the bugs where a bare metal is not able to ping a VM 17:35:13 <Sukhdev> Do we have cycles to pull any of those off? 17:35:35 <Sukhdev> marutikamat: yes - saw that - thanks - 17:36:11 <Sukhdev> marutikamat: we are trying to test it - we ran into a snag on our side - wanted to provide the feedback in this meeting, but, unfortunately could not resolved our issue 17:36:34 <marutikamat> Sukhdev: ok no problem. 17:36:48 <Sukhdev> marutikamat: it is on my list of things to do this week - 17:37:21 <marutikamat> we have phanipawan, vikas and preeti full time resources working on the project. 17:37:33 <Sukhdev> marutikamat: is it possible to pull off the other bug that I filed - i.e. OVSDB server initiating connection - that we discussed in Vancouver 17:37:48 <marutikamat> I am working on l2gw things whenever I get time. 17:38:13 <marutikamat> Sukhdev: I am analysing that one 17:38:51 <Sukhdev> marutikamat: we sort of discussed its details in person, but, I am available to provide feedback - whenever needed 17:38:53 <marutikamat> Sukhdev: Is there a benefit for supporting manager table? 17:39:26 <Sukhdev> marutikamat: did not get that - manager table? elaborate, please 17:40:18 <marutikamat> Sukhdev: we populate the manager table in OVSDB schema and then OVSDB server opens connection to the clients. 17:40:52 <marutikamat> OVSDB client IP is to be inserted into the Managers table. 17:41:03 <Sukhdev> marutikamat: Oh I see - now I get it 17:41:10 <marutikamat> Sukhdev: let us discuss that offline 17:41:34 <Sukhdev> marutikamat: yes, let me ping you via email - 17:41:37 <marutikamat> I will initiate a thread on that one. 17:41:47 <Sukhdev> marutikamat: cool 17:42:43 <Sukhdev> marutikamat: any other feature you can think of? - any low hanging fruit? 17:43:56 <marutikamat> Sukhdev: Let me go through the list one more time and I will update you on it. 17:44:08 <Sukhdev> marutikamat: sounds good 17:44:55 <Sukhdev> We have few patches, but, mainly held up because of CI issue - 17:45:24 <Sukhdev> I was looking at - https://review.openstack.org/#/c/189708/ 17:45:38 <Sukhdev> I noticed no body has reviewed it - any reason? 17:46:53 <marutikamat> I will check with the author why the third party CI is failing 17:47:29 <Sukhdev> marutikamat: other than this all other patches are blocked on CI 17:49:08 <Sukhdev> sorry - was disconnected - back again 17:49:32 <Sukhdev> Any other patch or bug we need to discuss? 17:51:00 <Sukhdev> Do we want to address anything else here? 17:51:07 <phanipawan> sukhdev: we have couple of bug fixes pending due to the CI 17:51:30 <phanipawan> once it gets resolved then i think we are unblocked 17:51:45 <Sukhdev> phanipawan: I have been waiting for CI issue to be resolved 17:52:09 <Sukhdev> phanipawan: In the meantime if you want me to review anything, feel free to ping me 17:52:43 <phanipawan> sukhdev: surely i will let you know 17:52:56 <Sukhdev> Anything else? 17:53:22 <phanipawan> nothing for now 17:54:04 <Sukhdev> I will look for channel on Tuesday PM and send a note via email - 17:54:14 <Sukhdev> Looks like we are done. 17:54:23 <Sukhdev> Thanks for attending 17:54:31 <Sukhdev> bye 17:54:40 <phanipawan> bye 17:55:07 <marutikamat> Thanks Sukhdev and armax 17:55:13 <Sukhdev> #endmeeting