15:02:30 #startmeeting weekly meeting 15:02:30 Meeting started Mon Apr 30 15:02:30 2018 UTC. The chair is mpeterson. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:02:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:30 The meeting name has been set to 'weekly_meeting' 15:02:32 hello 15:02:38 #topic Agenda 15:02:45 #info Regular topics: action items from last meeting, announcements, patches 15:02:48 Any other topics to discuss? 15:03:02 anyone going to openstack summit ? 15:03:23 I don't think so 15:03:34 but I'd ask on the mailing list 15:03:41 I might be going, would be good to meet n-odl team there 15:04:09 I can't travel because of company policy 15:04:44 since I'm a part-time worker until I finish my studies 15:04:58 hi 15:05:10 mkolesni: hi, are you going to the summit? 15:05:19 mkolesni: manjeets was asking 15:05:40 vancouver? 15:05:44 yes 15:06:12 no, generally only going to ptgs now 15:06:39 #info another topic: review of v3 spec 15:06:45 moving on... 15:06:55 #topic Action items from last meeting 15:07:04 #info no pending items 15:07:17 #topic Announcements 15:07:23 any announcements? 15:07:53 manjeets, mkolesni, poothia__ ? 15:08:04 none from my side 15:08:07 sorry was sick last week, didnt get much done 15:08:08 not any 15:08:13 #info no announcements 15:08:25 #topic Patches 15:08:35 before we get into the spec of v3 15:08:47 any patch that should be taken into our attention? 15:09:00 *brought 15:09:43 I'm still waiting for you guys to review my implementation of enginefacade 15:09:50 so I'm going to add that as a pending item 15:10:12 #action all to review the implementation of the enginefacade db pattern ( https://review.openstack.org/#/q/status:open+project:openstack/networking-odl+branch:master+topic:bp/enginefacade-switch ) 15:10:48 any other patches you'd like to discuss? manjeets, mkolesni, poothia__ 15:11:06 none from me 15:11:22 l3 flavors patch (currently blocked by neutron but very close to completion in networking-odl) 15:11:34 https://review.openstack.org/#/c/504182/ 15:12:54 okey, I'll review it soon... I've been postponing it for long enough 15:13:13 #action all to review the L3 flavors patch ( https://review.openstack.org/#/c/504182/ ) 15:13:19 ok 15:13:25 thanks ! 15:13:33 is there a gate failure in networking-odl-fullstack-carbon? 15:13:45 poothia__: it is failing randomly :/ 15:13:58 okey... 15:14:07 poothia__: if it persists we should look into it 15:14:23 #topic v3 Spec 15:14:34 okey, so did you get time to review the spec? 15:15:15 not yet, was sick 15:15:27 manjeets, poothia__ ? 15:16:00 unless there is a big pushback on it, my idea is to publish it this wednesday for broader review 15:16:02 mpeterson, I reviewed it most of it looked good and but haven't completed review yet 15:16:12 mpeterson, +1 15:16:34 i reviewed it, i found it plausible... 15:16:57 any doubts ? 15:17:52 mpeterson, I guess its time to get eyes of more audience ? 15:18:00 manjeets: yes it is :) 15:18:09 manjeets: I'll do that in my next working day 15:18:16 cool sounds good 15:18:18 sounds good to me 15:18:19 perhaps even tomorrow morning 15:18:24 otherwise wednesday 15:18:35 we can obviously continue on the gerrit 15:18:55 yup, it's going to be even easier to review 15:20:01 awesome 15:20:13 okey, I close this topic 15:20:40 mkolesni, manjeets, poothia__: any other topic you'd want to discuss? or should I end the meeting? 15:20:57 mpeterson, mkolesni wanna go over bugs list ? 15:20:59 https://bugs.launchpad.net/networking-odl 15:21:03 if we have time today, we can do some bug triaging... 15:21:09 #topic bug triage 15:21:15 okey, let's do it 15:21:28 manjeets: guide us through :) 15:22:05 first bug is marked critical and incomplete ? 15:22:30 it was for networking-ovn mostly but seems like was added to n-odl too 15:23:33 multinode CI is still a dream for networking-odl 15:24:06 couple of times I was very close to fix but other issues and work always got my attention 15:24:10 manjeets: yes, the first one I think we could close it... anyways it's a tempest test so if we see it again we can re-open 15:24:54 mpeterson, makes sense to close it for now 15:25:34 +1 15:25:36 mmm I don't have permissions to close it 15:25:46 neither do I 15:25:57 mkolesni: :) 15:27:01 trying 15:27:23 i marked it invalid 15:27:43 okeyt 15:27:46 next one is grenade job, I got it passing twice but it again broke due to changes in devstack code way it handles legacy neutron-lib 15:28:10 manjeets: but we are not using legacy neutron-lib anymore, are we? 15:28:41 mpeterson, for grenade jobs yes even neutron and other networking-* project are use using it 15:29:13 the reason was grenade code wasn't updated so we have to stick with it and grenade jobs are the only exception afaik 15:30:02 manjeets: mmm and the fix in devstack is a difficult one? perhaps you can even contribute the fix to grenade ;) 15:30:45 i started with a patch in grenade, but almost no response from grenade team 15:31:16 https://review.openstack.org/#/c/546745/ 15:32:25 if i get time this week i'll see if I can do a work around in networking-odl 15:32:54 manjeets: I added two cores of grenade as reviewers 15:34:02 thanks 15:34:23 next are full_sync I see one of them just got closed 15:34:51 is rajiv still working on https://bugs.launchpad.net/networking-odl/+bug/1711114 ? 15:34:57 re: full sync and recovery, I expect those to be addressed by rajiv as part of the refactor 15:35:13 so I'd just make sure he has them assigned and skip them over 15:35:53 ok https://bugs.launchpad.net/networking-odl/+bug/1713697 journal recovery is also assigned to him 15:36:25 re: https://bugs.launchpad.net/networking-odl/+bug/1376563 I think we should create more functional tests, should we re-define it? 15:36:36 yes please 15:37:48 manjeets: I'll remove you as assignee because I doubt you are working on that 15:38:02 i removed already 15:39:34 continuing https://bugs.launchpad.net/networking-odl/+bug/1686625 what to do with this one? 15:40:07 mkolesni: and are you working on this one still? https://bugs.launchpad.net/networking-odl/+bug/1713487 15:40:44 not right now 15:40:54 I'll put it as triaged and unassigned 15:41:33 ok 15:41:45 mpeterson, https://review.openstack.org/#/c/558554/ for https://bugs.launchpad.net/networking-odl/+bug/1686625 15:42:24 manjeets: oh, great 15:42:55 I think feature fetch from odl for qos will cover it 15:43:21 indeed 15:43:50 now https://bugs.launchpad.net/networking-odl/+bug/1738246 I think it's related to https://bugs.launchpad.net/networking-odl/+bug/1713487 and https://bugs.launchpad.net/networking-odl/+bug/1713487 15:44:33 this one will be fixed by l3 flavors 15:45:03 dont think its related to the other ones, but maybe 15:45:44 great, so let's leave them as they are 15:46:34 ok 15:46:48 next is https://bugs.launchpad.net/networking-odl/+bug/1738247 15:47:00 manjeets, can we assign https://bugs.launchpad.net/networking-odl/+bug/1738246 to you? 15:47:09 since it will be fixed by l3 flavor 15:47:32 mkolesni, sure 15:48:14 mpeterson, this one might be related to l3 flavor as well but im not sure 15:50:44 okey, next https://bugs.launchpad.net/networking-odl/+bug/1627749 15:50:49 manjeets: you are assigned? 15:52:08 mpeterson, I did some fixes to qos driver last not sure if this bug is still valid but i'll check 15:53:22 manjeets: great 15:53:33 actually mpeterson it can closed it was reported when notification driver was used which is no longer in use with qos_v2 15:53:49 manjeets: even more great 15:54:55 mpeterson, i remember patch for adapting new driver for qos https://review.openstack.org/#/c/454300/ 15:55:38 next https://bugs.launchpad.net/networking-odl/+bug/1660911 mkolesni tells me it's going to be handled in ODL's side 15:56:11 https://jira.opendaylight.org/browse/NEUTRON-158 15:56:18 I'll add that to the bug 15:56:44 yes 15:57:21 should I close the n-odl bug then or just leave it open until that's fixed? 15:58:22 okey, I think that's as far as we can reach today 15:59:21 cool ! we got some bugs off the list 15:59:51 i think it can be closed 15:59:58 thanks mpeterson ! 16:00:01 cya guys 16:00:03 thank you everyone !! 16:00:13 thank you all... 16:00:43 we can continue this in next meetings as well, if we have time! 16:00:56 thanks 16:01:21 awesome 16:01:23 thanks 16:01:28 see you next week 16:01:29 #endmeeting