16:02:24 #startmeeting neutron_northbound 16:02:24 Meeting started Mon Feb 13 16:02:24 2017 UTC. The chair is yamahata. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:02:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:24 The meeting name has been set to 'neutron_northbound' 16:02:36 #chair mkolesni 16:02:36 Current chairs: mkolesni yamahata 16:02:38 #chair vthapar 16:02:38 Current chairs: mkolesni vthapar yamahata 16:02:46 #topic agenda bashing and roll call 16:02:53 #info vthapar 16:02:58 #info yamahata 16:03:06 any topics today? 16:03:14 as usual, patch/bug review 16:03:33 this week stable/ocata branch will be cut and final patch review for ocata. 16:04:06 and ptg topics and requirement from daya if possible 16:04:10 any other topics? 16:04:28 none from me. 16:04:48 #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings meeting agenda 16:04:59 #topic Announcements 16:05:08 openstack PTG is next week 16:05:20 stable/ocata branch will be cut this week. 16:05:42 From Pike cycle, we'd like to graduate from independent release cycle. 16:05:52 any other announcement? 16:06:31 none from me. 16:06:36 #topic action items from last meeting 16:06:54 only patch review 16:06:59 move on 16:07:41 #topic Carbon planning 16:07:58 This week there is a request from Daya. 16:08:15 The tech discussion will be continued on mailing list, launchpad, gerrit. 16:08:33 I request her to file RFE bug report and spec for detailed discussion. 16:08:56 vthapar: I suppose you can help with those procedure. 16:09:29 yamahata: yes. some other dev team will be driving it and I'll be helping the out with process. 16:09:43 I'll be more of a reviewer on this one. 16:09:54 I see. 16:10:15 Okay move on 16:10:23 #topic Neutron Stadium effort 16:10:40 For ocata we're okay. At PTG more for Pike will be discussed. 16:10:49 we'd like to stay in Neutron stadium. 16:10:53 Neutron Stadium effort 16:11:00 #topic patches/bugs 16:11:06 Okay, now patch review 16:11:16 Hopefully today I'd like to merge pending patches. 16:11:30 I uploaded one bug fix patch. 16:11:50 driver patches will need rebase and resolve conflict each time one gets merged. 16:11:50 regrading to v2 patch, we have qos/l2gw/vgpvpn/sfc. 16:12:02 Oh. 16:12:20 code will be in conflict in dependency_validations and test_dependency_validations 16:13:07 e.g. https://review.openstack.org/#/c/424064/ 16:13:12 this shows other drivers in conflict. 16:13:46 I can resolve for l2gw and bgpvpn while am around. 16:13:47 Which patch l2gw or bgpvpn do you prefer to merge first? 16:13:58 I think l2gw is already +1 on review and Jenkins 16:14:33 So I'll merge l2gw first. 16:14:42 sorry putting baby to sleep 16:14:55 So can you please rebase bgpvpn on top of it? 16:15:08 yamahata: yep, I'll do it as soon as it is merged. 16:15:30 I'll ask manjeet with qos patch. 16:15:44 So qos/l2gw/bgpvpn are okay. 16:15:57 What do you think about sfc patch? Is it ready to merge? 16:17:27 Silent. Hmm it would be early pike? 16:17:59 sfc is missing test_dependency_validations. 16:18:33 rest of comments are more nitpick, but I think those need to be there. 16:19:27 Okay. 16:19:53 I +2 on l2gw. 16:20:29 Please review bgpvpn and qos patch before merge. 16:20:43 This night, I'll upload patch to cut ocata branch. 16:21:20 I'll also merge 431894 and 432508 as bug fix. 16:21:54 If you'd like to review it, please hurry up. 16:22:01 any other patches for ocata? 16:22:18 what about patches by mkolesni for port status? 16:22:44 theyre not ready yet 16:23:04 ok. will we be backporting them to Ocata? 16:23:29 If we file a bug for it, we have a chance for backport. 16:23:42 maybe i have some problem there atm 16:24:21 if i get it to work properly we can always backport 16:25:00 ok. and I was looking at sfc driver, will we be able to backport that too? 16:25:13 we would like to have all service drivers v2 in Ocata. 16:25:22 Yes, we can. 16:25:36 mkolesni: your thoughts in getting sfc in current form? it is missing test_dependency_validations 16:25:48 rest looks fine 16:25:49 I think it's necessary. 16:26:01 except tests, the code looks good to me. 16:26:11 yeah, I didn't find issues with my dependency validations till I wrote and ran tests for it. 16:26:24 Tomas Cechvala proposed a change to neutron: WIP Hostconfig for VPP https://git.opendaylight.org/gerrit/50742 16:26:50 I'll chck with Anil, he might be ready with tests. 16:27:11 Good. 16:27:36 any other patches/bugs or move on? 16:27:37 if its only tests we can merge it 16:28:06 worst case fix bugs and backport 16:28:30 mkolesni, that is what I was thinking. somewhat broken driver better than none at all. 16:28:38 though code wise it does look good to go. 16:29:04 then, vthapar can you update sfc driver to address you comments? 16:29:16 then we can merge it. 16:29:21 you can backport a few bug fixes but not the whole driver 16:29:29 yamahata, can't commit on it. if am still awake after rebasic bgpvpn, I'll take a shot at it. 16:29:33 (Or to have anil update it in hurry) 16:29:39 s/rebasic/rebasing 16:29:43 since its not on the critical path i see no harm in merging it after the comments are fixed 16:29:45 vthapar: got it. 16:29:49 and add tests in Pike 16:30:12 Okay let's file a bug to track it and merge the patch. 16:30:26 just realized, other than tests there is more work needed. currently delete dependencies will not work. 16:30:44 would be good if you could confirm/deny my comments on that. 16:30:51 sure. 16:31:01 #action yamahata review sfc driver more closely. 16:31:11 and file a bug if necessary. 16:32:12 we're done with ocata patches. 16:32:19 #topic open mike 16:32:48 how do you find the new dependency validations? 16:32:53 The next week, I'll be absent from this meeting due to PTG. 16:32:54 better? 16:33:24 yamahata: obviously 16:33:25 In my case, basically gazing at API definitions. 16:33:37 I wouldn't say it a better way. 16:34:04 #link https://etherpad.openstack.org/p/neutron-ptg-pike 16:34:13 #link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads 16:34:19 unfortunately im not going to ptg 16:34:26 vthapar: you going to ptg? 16:34:28 any input for PTG? 16:34:52 mkolesni: no. 16:35:10 yamahata: i would still like to draft a move of dependency calculations to when journal entry is created 16:35:17 we'd like to start to plan for pike networking-odl 16:35:35 yamahata: haven't gone through agenda yet. had a couple of things for pike. 16:35:39 i think currently is way too error prone 16:36:06 other than that improve the status reflection from odl at least for port status 16:36:25 mkolesni: I see. Do you have sample document or code snippet to show idea? 16:36:47 yamahata: +1 to sample doc 16:36:57 no not yet 16:37:00 Right now Ritu is working on websocket and the next step is to update port status. 16:37:22 yes we have jhershbe already working on that direction 16:37:42 i thought Ritu was more focused on the way to update the port binding data 16:37:44 testing/hardening fullsync and maintenance thread would be Pike candidate. 16:38:20 Ritu is working on both. Anyway we can coordinate to avoid duplication. 16:38:30 not sure how much full sync is actually being done 16:38:54 ok please let her know for now jhershbe is working on it 16:39:22 Sure. She knows it already. 16:39:26 ok cool 16:39:48 i think scale should be also a focus area on pike 16:40:27 i think scale will show us the problem areas and then we need to focus on those 16:40:50 are you moving the project to the cycles with milestones release schedule? 16:41:42 I'm wondering about it. 16:41:57 seems logical were almost doing it anyway 16:42:46 The change would be that it would be more strict to cut branch. 16:43:30 not necessarily bad 16:43:43 but you still have to request the branch cut each time right? 16:43:46 So far I haven't seen any objections, so I'm going to switch it. 16:44:03 No. it's done by openstack release team. Or Neutron team. 16:44:03 +1 to aligning with milestones release schedule. 16:44:19 ok then sounds good 16:45:44 any other topics? 16:46:06 none from me 16:46:11 so no meeting next week? 16:46:22 I won't chair it. It's up to you. 16:46:45 I'll be travelling, might be able to join in, depends on network. 16:46:47 ok ill see if theres interest or not 16:46:56 one more thing I wanted to bring up for Pike... 16:47:05 filtering out columns we're not using in NN... why store then in journal and send across? 16:47:11 #action yamahata mkolesni coordinate next week meeting. 16:47:22 #action yamahata sent absence notice 16:47:35 we haven't done perf testing but it would help scale/perf better. 16:47:59 vthapar: There is no strong reason. 16:48:08 we can see if its a problem as part of scale testing 16:48:17 fair enough. 16:48:17 it was easier to debug journal code with full infomation in db. 16:49:18 I forsee it being an issue for trunks at scale, but we'll cross that bridge when we get there. 16:50:46 anything else? 16:50:53 nothing from me 16:50:55 or I'll return back 10mins to you. 16:51:02 thanks Isaku! 16:51:07 enjoy the PTG :) 16:51:10 thanks everyone! 16:51:19 #topic cookies 16:51:23 #endmeeting