17:01:01 <Sukhdev> #startmeeting networking_l2gw
17:01:08 <openstack> Meeting started Mon Jul  6 17:01:01 2015 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:11 <openstack> The meeting name has been set to 'networking_l2gw'
17:01:39 <Sukhdev> who is present here - can you shout, please?
17:02:06 <Sukhdev> armax: are you here?
17:02:11 <armax> yes
17:02:19 * regXboi is lurking/auditing
17:02:37 <Sukhdev> waiting for India team to join in
17:02:58 <Sukhdev> #topic: Agenda
17:03:04 <Sukhdev> #link: https://wiki.openstack.org/wiki/Meetings/L2Gateway
17:03:59 <Sukhdev> It is late for folks in India - anybody from India here? please shout...
17:04:10 <marutikamat> Hi Sukhdev, I am here
17:04:23 <Sukhdev> marutikamat: cool -
17:04:25 <marutikamat> How do you do?
17:05:05 <Sukhdev> marutikamat: coming out of long weekend - still sleepy :-)
17:05:16 <marutikamat> :)
17:05:18 <Sukhdev> marutikamat: too much party :-)
17:05:27 <marutikamat> Cool
17:05:35 <Sukhdev> lets get going with the meeting
17:05:40 <marutikamat> sure
17:05:44 <Sukhdev> #topic: Announcements
17:05:52 <Sukhdev> I have no announcement today -
17:05:56 <Sukhdev> anybody has any?
17:06:05 <Sukhdev> marutikamat armax : anything?
17:06:10 <armax> sukhdev: yes
17:06:26 <Sukhdev> armax: please do
17:06:33 <armax> I personally applied a few changes to the repo
17:06:48 <armax> to simplify the integration with Neutorn
17:07:07 <armax> and fix a couple of issues that were caused by changes in openstack/common
17:07:22 <armax> last time I checked the repo was sane and external CI passed
17:07:30 <armax> one more thijng
17:07:51 <armax> there’s a change from mestery do relinquish control for tagging releases to the library release team
17:08:09 <armax> https://review.openstack.org/#/c/198750/
17:08:11 <Sukhdev> armax: yes - I saw that one
17:08:15 <armax> https://review.openstack.org/#/c/198749/
17:09:05 <armax> sukhdev: that’s it from me
17:09:05 <marutikamat> Thanks armax for the info
17:09:32 <Sukhdev> armax: actually I was refereeing to https://review.openstack.org/#/c/193127/
17:10:10 <Sukhdev> armax: I was going to ping mestery to understand the process to figure out - how the pypi versioning is going to work
17:10:24 <mestery> Sukhdev: You have to use semantic versioning
17:10:33 <mestery> And we'll keep all of this under the library-release team
17:10:33 <mestery> Or it's gonna be nuts
17:10:37 <mestery> And error prone, etc.
17:10:42 <mestery> Part of being in the neutron stadium
17:11:05 <Sukhdev> mestery: any write up?
17:11:24 <Sukhdev> mestery: that we can refer to - to understand it a bit better?
17:12:17 <armax> sukhdev: there’s a ML thread about switching to semver
17:12:28 <armax> sukhdev: there was also a session during the summit
17:12:42 <armax> sukhdev: and related etherpad
17:12:54 <armax> sukhdev: not sure if both would be in the shape of your liking
17:12:59 <Sukhdev> armax: do you happen to have a link to any of these?
17:13:28 <mestery> Sukhdev: I have patches to all the networking-foo which convert them to semvar
17:14:01 <Sukhdev> mestery: ah I see armax posted two of them here -
17:14:03 <mestery> #link https://review.openstack.org/#/q/status:open+branch:master+topic:semver-releases,n,z
17:14:49 <Sukhdev> mestery: cool - thanks - let me spend some time reviewing/understanding them - will ping you if have any questions
17:14:58 <mestery> Sukhdev: Ack
17:15:14 <Sukhdev> armax: thanks for the update
17:15:34 <Sukhdev> armax: as to the CI being happy - I have seen two patches sitting with the CI failing -
17:16:04 <Sukhdev> I have not approved them simply waiting for CI to pass on these - armax are you aware of these two?
17:16:06 <armax> sukhdev: which ones?
17:16:24 <Sukhdev> armax: hang on looking
17:16:51 <Sukhdev> #link - https://review.openstack.org/#/c/194921/
17:17:13 <Sukhdev> #link: https://review.openstack.org/#/c/194919/
17:17:56 <armax> sukhdev: a recheck should do
17:17:58 <armax> I’ll watch them
17:18:07 <Sukhdev> armax: cool - thanks
17:18:56 <Sukhdev> We kind of went out of order - but, was good :-)
17:19:02 <Sukhdev> lets get back to the agenda -
17:19:10 <Sukhdev> #topic: Action Items
17:19:13 <armax> sukhdev: sorry
17:19:26 <Sukhdev> armax: no worries - it was actually good
17:19:50 <Sukhdev> I had an action to work with armax to come up with an earlier slot to accomodate India team
17:20:19 <Sukhdev> I completely forgot about it - even though I met armax twice in last two weeks :-):-)
17:20:20 <armax> sukhdev: how early would it suffice?
17:20:22 <Sukhdev> shame on me :-)
17:20:31 <Sukhdev> marutikamat: please chime in
17:21:09 <Sukhdev> I wish more India folks were here - they asked in the last meeting
17:21:14 <marutikamat> If we could reduce by 30 mins, it would be great
17:21:23 <marutikamat> I mean advance by 30 mins
17:21:44 <marutikamat> All of them are on vacation right now
17:21:57 <armax> we can do 9am PDT, but perhaps we’d have to change day
17:22:00 <Sukhdev> marutikamat: we will have to move to other day - I have Ironic meeting which runs from 9am to 10am
17:22:09 <armax> sukhdev: right
17:22:13 <Sukhdev> so, basically I have these two meetings back-to-back
17:22:35 <marutikamat> Moving to some other day would also work.
17:22:38 <Sukhdev> marutikamat: everybody on vacation - wow!! I am moving to India :-)
17:23:18 <marutikamat> Not every one are on vacation. The three developers (manjunath, phani and vikas) are on vacation
17:23:22 <Sukhdev> We could move it to Tuesday at 9am (PT) or Thursday at 9AM -
17:23:36 <Sukhdev> armax: any of these slots work for you?
17:23:37 <armax> thur
17:23:40 <armax> works better for me
17:24:09 <Sukhdev> marutikamat: you think that would work for India team?
17:24:15 <marutikamat> That would be 9.30pm for India folks I think. Is that correct?
17:24:47 <Sukhdev> marutikamat: do not know about India time - it is one hour earlier -
17:25:01 <Sukhdev> is it 10:30 in India now?
17:25:20 <armax> approaching 11pm
17:25:24 <marutikamat> Thursday 9am PST would be 9.30pm Thursday. And that should be fine with us.
17:25:59 <marutikamat> Yes, right now 5 mins for 11.00pm
17:26:14 <Sukhdev> marutikamat: cool - let check the available channels. I hope I can find one - and will send out the announcement for next meeting
17:26:29 <marutikamat> Thanks Sukhdev and armax
17:26:44 <Sukhdev> #topic: Bugs
17:26:56 <Sukhdev> I see tons of unassigned bugs -
17:27:43 <Sukhdev> #link: https://bugs.launchpad.net/networking-l2gw
17:28:30 <Sukhdev> marutikamat: you mentioned last time that you and selva have moved on to another project
17:28:47 <marutikamat> Right now, we have only 3 resources assigned for the bugs. I will assign the owners tomorrow.
17:29:05 <Sukhdev> marutikamat: cool -
17:29:18 <marutikamat> Yes, myself and Selva have been moved into some internal projects.
17:29:42 <marutikamat> If time permits, I will contribute
17:30:16 <Sukhdev> marutikamat: cool - will you be joining for the meetings - now that we are changing the time accomodate you :-):-)
17:30:43 <marutikamat> Yes, I will attend the meetings and I will request others also to join the meetings.
17:31:04 <Sukhdev> marutikamat: cool thanks
17:31:35 <Sukhdev> marutikamat: I had asked Ashwin to join us here this week to address the flood-list issue with L2 GW
17:31:54 <Sukhdev> this has been lingering issue for a while -
17:32:21 <Sukhdev> marutikamat: I thought if I put both of you in the meeting - it may be faster to get the issue resolved/understood
17:32:51 <marutikamat> I think myself and Ashwin are on the same page. I wanted his help in configuring something on the Mcast_Macs_Remote table to ensure that ping from a bare metal server to a VM works.
17:33:22 <Sukhdev> he should be joining shortly
17:33:42 <Sukhdev> before we discuss this - (as he is figuring out how to join in) -
17:33:50 <Sukhdev> is there anything else we want to cover
17:33:51 <marutikamat> That will boost the confidence level for the changes to be made in the code.
17:35:35 <Sukhdev> armax marutikamat : while Ashwin is trying figure out to join in - do we want to cover anything else?
17:35:47 <armax> sukhdev: nothing to add from my side
17:35:55 <Sukhdev> The biggest one in my mind was the unassigned bugs -
17:36:29 <marutikamat> armax: the l2gw CI team has fixed a problem where the run for the older patch was not getting aborted when a new patch is uploaded.
17:36:59 <marutikamat> I will assign the owners tomorrow for the unassigned bugs
17:37:21 <Sukhdev> marutikamat: Oh could that be the reason for CI failures for those two patches I mentioned earlier?
17:37:36 <armax> sukhdev: I don’t htink so
17:38:03 <Sukhdev> armax: ah OK - so something unrelated
17:38:38 <armax> sukhdev: yup, before the cahnge in configuration the CI would report on stale changes too
17:38:58 <marutikamat> I will have someone to look at the build failures
17:39:06 <Sukhdev> armax: ah I see - thanks for clarification
17:39:23 <Sukhdev> Folks, BTW, ashwins is here now
17:39:27 <Sukhdev> let me introduce him
17:39:29 <armax> marutikamat: afaik the failures where py27 related
17:39:40 <armax> I might have solved them during the latest changes I pushed
17:39:48 <Sukhdev> Ashwin is our local expert in Arista for OVSDB related stuff
17:39:57 <armax> if there are failures to the tempest job, that’s a diffrerent can of worms
17:40:15 <armax> welcome ashwins
17:40:18 <Sukhdev> armax: Cool - I will watch those patches as well - and let you know - BTW, those are related to stable/kilo
17:40:18 <ashwins> Hey guys
17:40:30 <marutikamat> Hi ashwin
17:40:34 <armax> sukhdev: ah!
17:40:35 <ashwins> thanks armax
17:40:54 <ashwins> hi marutikamat
17:40:59 <Sukhdev> armax marutikamat : I had asked ashwins to look into the flood list issue
17:41:05 <armax> sukhdek: ok so it must be something different
17:41:11 <armax> sukhdev: sweet
17:41:33 <Sukhdev> ashwins: can you explain your finding so that everybody is on the same page
17:42:14 <marutikamat> ashwin, did you get a chance to create entries in the Mcast_Macs_Remote table using vtep-ctl and whether the BM is able to ping a VM?
17:42:28 <ashwins> marutikamat I haven't had a chance to try out what you mentioned the other day (ie adding the remote flood list in mcast_macs_remote manually on the hardware switch)
17:42:57 <marutikamat> ok
17:43:05 <ashwins> will update after I'm done with that, but I'm fairly confident that it'll work
17:43:50 <ashwins> that is how we do our internal testing, but anyways will confirm just to be sure...
17:43:53 <marutikamat> Great. I will make changes in the code to insert the records in mcast_macs_remote and physical_locator table then.
17:44:05 <ashwins> cool
17:44:07 <Sukhdev> marutikamat: assuming ashwins findings work, how big is the change on the L2GW side to fix this?
17:44:25 <marutikamat> Just wanted to be sure before doing the code changes.
17:44:45 <ashwins> sure
17:45:08 <marutikamat> It is not much.
17:45:30 <Sukhdev> marutikamat: sigh….good to hear this -
17:45:39 <marutikamat> :-)
17:45:50 <Sukhdev> marutikamat: whenever you have the fix, let me know and we can test it
17:45:59 <marutikamat> sure
17:46:14 <Sukhdev> marutikamat: just shoot me an email - it may be faster
17:46:29 <Sukhdev> Cool folks - with this we good with bugs
17:46:54 <Sukhdev> armax: wanted to ask you a question on the neutron api for L2GW
17:47:03 <armax> k
17:47:48 <Sukhdev> now that we are under neutron tent, we should consider using python client to change the 2GW CLI
17:47:57 <Sukhdev> there is a patch sitting in the list
17:48:22 <armax> sukhdev: the cli is extensible and can be plugged cli commands
17:48:30 <armax> sukhdev: we’d need someone who can get it sorted
17:49:20 <Sukhdev> sorry - got disconnected - back now
17:50:03 <Sukhdev> armax: did you get my question before I got disconnected?
17:50:21 <armax> yes
17:50:32 <Sukhdev> good -
17:50:35 <armax> I the cli is extensible and can be plugged cli commands
17:51:00 <armax> it’s my understanding that the author of the cli was unable to make use of it
17:51:06 <armax> sorry the author of the patch
17:51:18 <armax> sukhdev: so that patch would need a nudge by someone capable
17:51:27 <armax> to identify where the problem is
17:52:01 <Sukhdev> armax: I am not familiar with this stuff - otherwise would have jumped in
17:52:06 <armax> sukhdev: but to your point, yes, even outside the tent, it’s technically possible to integrate with the cli
17:52:20 <armax> sukhdev: me neither, and I would have to find time to look into it
17:52:29 <armax> sukhdev: but I have none so far
17:53:04 <Sukhdev> armax: I will spend some time looking at the patch to get some familiarity and see what I find
17:53:26 <armax> sukhdev: it’s only my backlog
17:53:36 <armax> if no-one beats me to it, I will eventually get to it
17:54:23 <Sukhdev> armax: :-)
17:54:52 <Sukhdev> I have exhausted the agenda -
17:55:01 <Sukhdev> anybody has anything want to discuss?
17:55:11 * Sukhdev waiting
17:55:37 <marutikamat> I am helping ODL to make L2gw work with ODL
17:55:53 <marutikamat> I am helping the ODL team to make L2gw work the ODL
17:56:05 <Sukhdev> marutikamat: interesting -
17:56:32 <Sukhdev> marutikamat: I thought they are full blown controller by themselves - how will L2GW fit in there?
17:56:35 <marutikamat> armax is guiding me for this
17:56:52 <armax> am I? Interesting :)
17:56:56 <marutikamat> they want our service plugin to be the NB APIs
17:57:27 <marutikamat> but the switch and the OVSDB hardware_vtep schema will be managed by the ODL controller
17:57:31 <Sukhdev> marutikamat: Oh so, ODL will run as ML2 driver and use L2GW as service plugin - interesting!!
17:58:07 <marutikamat> L2gw neutron will be a thin layer and it will invoke the odl plugin driver.
17:58:26 <marutikamat> yes, sukhdev, something like that.
17:58:40 <marutikamat> they don't want to use our l2gw agent.
17:58:53 <Sukhdev> marutikamat: so, instead of using l2gw agent - se ODL
17:59:01 <Sukhdev> s/se/use
17:59:07 <marutikamat> yes, you are correct.
17:59:20 <Sukhdev> that makes sense -
18:00:00 <Sukhdev> In fact, in our presentation at Vancouver, I mentioned that anybody who do not want to use L2GW agent, they can implement their own agent -
18:00:08 <Sukhdev> so ODL is one such example -
18:00:22 <marutikamat> Yes Sukhdev
18:00:52 <Sukhdev> marutikamat: if you have any document around that integration - it will be helpful for others as well - you may want to put it on our wiki
18:01:23 <Sukhdev> we are past our time -
18:01:35 <marutikamat> Sukhdev: right now, it is not finalized. There was a meeting on Friday. However, it got cancelled due to the holiday in the US,
18:01:57 <marutikamat> Once frozen, I shall update the wiki
18:02:19 <Sukhdev> marutikamat: cool - that would be good - keep it in mind - many others can leverage form it...
18:02:23 <Sukhdev> Thanks folks for attending - this was a good meeting/discussion
18:02:32 <marutikamat> thanks everyone
18:02:34 <Sukhdev> #endmeeting