16:02:35 #startmeeting neutron_northbound 16:02:35 Meeting started Fri Jan 22 16:02:35 2016 UTC. The chair is yamahata. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:02:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:35 The meeting name has been set to 'neutron_northbound' 16:02:44 #topic agenda bashing and roll call 16:02:47 #info yamahata 16:02:58 #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings meeting page 16:03:05 I missed to update the agenda, though 16:03:58 are there special topic? 16:04:25 I'd like to discuss https://review.openstack.org/#/c/215612/ vhost user patch 16:04:55 in addition to routine topics 16:05:56 #topic Announcements 16:06:34 The deu date for call-for-speakers for openstack summit is approaching. Feb 1. 16:06:55 If you're interested in it, please contact me and review the abstract 16:07:52 #link https://docs.google.com/document/d/15BLN2hAXep5_6KhVFeiVu4M2wDiwzkT30Rhv88XX2_I/edit?usp=sharing draft of abstrct for openstack summit 16:08:27 ODL design summit is also planned on Feb 29 and Mar 1. 16:08:40 We should prepair our toics 16:08:54 #action yamahata prepare wiki page for design forum. 16:09:28 lastly openstack CI had an issue yesterday. But I suppose it's already okay. 16:10:26 The new job gate-tempest-dsvm-networking-odl-lithium-snapshot and gate-tempest-dsvm-networking-odl-beryllium-snapshot is run instead of gate-tempest-dsvm-networking-odl 16:10:41 rcurran: Are you seeing still the issue? 16:10:54 no, CI working again 16:11:05 working as in it's running :-) 16:11:33 Cool. If any issues, don't hesitate to raise it. 16:11:39 any other announcement? 16:13:46 #topic action items from last meeting 16:14:03 flavio sent out the mail 16:14:42 Isaku hasn't the bug yet, but looking into it. there are a finding. If you're curious, I'll share it later. 16:15:18 #topics patch review 16:15:40 Is there any patch that needs special attention? 16:15:58 I'd like to discuss https://review.openstack.org/#/c/215612/ vhost user patch 16:16:32 Wojciech Dec has raised an issue on the patch. 16:16:55 Is wojciech here? 16:17:42 If he has real concern, I'd like to address it. 16:17:52 I guess he isn't but I work with Woj on some of our vhost implementations 16:18:06 do you know his concern or I can check with him 16:18:21 I need to review that change closely myself 16:18:28 He left review comment on the gerrit review. 16:18:55 If no, I'd like to make progress with the patch. 16:19:17 To be honest, I'm not very satisfied with the patch state for reasons. 16:19:30 I agree with his comments 16:20:24 a host does not need to be dedicated and we have to ensure the change is generic as there are other implementations using vhostuser 16:21:04 let me review before Monday and provide specific comments on how to make it more general 16:21:14 john_a_joyce: thanks. 16:21:27 #action john_a_joyce review before Monday and provide specific comments on how to make it more general 16:22:00 At this point ODL lacks functionalities to provide networking-odl backend capability 16:22:31 and the conversion neutron host-id to ODL node-id 16:22:41 you mean for vhostuser connections? 16:22:45 At least we should address it in Boron cycle. 16:23:17 I mean backend like ovsdb/netvirt, vtn, gbp can supports dpdk or not 16:23:50 Ah openflow feature. 16:24:00 ok 16:24:03 ovs-dpdk isn't fully compatible with plan ovs 16:24:18 the backend needs to be aware of it. 16:24:38 so that only supported flows(match/action) are used 16:25:24 we can discuss on details offline. Is it okay? 16:26:17 any other patches to discuss? 16:26:32 sure ok for me 16:27:40 move on... 16:27:43 #topic bugs 16:27:59 any bugs that needs attention? 16:28:42 I beg for scrubbing/attacking filed bugs. 16:29:20 #topic ML2 ODL driver rewrite 16:29:39 any update or discussion? 16:29:54 there are several patches floating around. should be reviewed. 16:29:59 not from me, just looking for reviwers 16:30:14 serveral patches? for ODL v2 driver? 16:30:33 yes 16:30:37 https://review.openstack.org/#/c/266583/ 16:30:42 there's just - https://review.openstack.org/#/c/266583 16:30:58 Oh only one. 16:31:22 yes, there is the *DO NOT REVIEW/MERGE* patch that I use to test v2 against the CI 16:32:02 can you add 'DO NOT REVIEW/MERGE' at the subject line? so that we don't have to open the page. 16:32:17 sure 16:33:01 #topic OpenStack release support 16:33:17 there is no update. 16:33:37 #topic Beryllium release preparation and Boron planning 16:34:03 The boron release is fast approaching. Let's squash bugs. 16:34:16 #topic open mike 16:34:26 any opens? 16:34:45 one topic that came up during bgpvpn discussion earlier today 16:35:19 there is a use case where driver may need to get some information from backend. applies to all bgpvpn drivers... 16:35:35 are there any plans for some framework which allows this? 16:36:03 What kind of information? 16:36:05 or we'll always be 'push to odl' driver? 16:36:30 At least for port-binding, we need ODL to provide its capability. 16:36:47 in this particular case about some ip prefixes learnt by ODL/BGP/vpnservice 16:37:26 not allow a subnet to be associated with a VPN if it has been learned already [might not be wording it 100% correctly] 16:37:57 driver retrieving info from ODL wouldn't be difficult 16:38:06 I'd like to discuss it for Boron. 16:38:08 and sometime back a similar request came for an L2GW use case too. 16:38:34 ODL callback to networking-odl would require more work. 16:38:40 +1 for discussing in Boron. 16:39:05 I think this should be good enough for starters. 16:41:04 #action vthapar, yamahata file a discussion topic for boron planning 16:41:26 any other topic? 16:41:43 I'd like to discuss about logistics. 16:42:13 So far we've just discussed on IRC meeting. and didn't use other tools to track tasks. 16:42:37 In the past, there was an attempt to use trello board 16:43:22 #link https://trello.com/b/LhIIQ8Z0/odl-neutronnorthbound trello board neutron northbound 16:43:36 Do we want to use it? or the current style is okay? 16:44:10 Personally either is okay as long as we're productive. 16:44:51 I am also okay either ways. you're the one doing tracking so your vote matters the most :) 16:45:59 okay. Anyway if we adapt new way, it will be after Beryllium release. 16:46:06 any other topics? 16:47:17 Then I'd like to share finding during digging into CI timeout 16:47:44 Some assumption by tempest isn't satisfied. So it should be properly setup. 16:48:07 scenario tests requires public network access, but it isn't for now. 16:48:23 That's first thing to fix. 16:48:32 that's all from me. 16:48:52 if no more topics, we can close meeting early today. 16:48:54 going once... 16:49:08 going twice... 16:49:20 thanks every one 16:49:23 thanks 16:49:25 #topic cookies 16:49:29 #endmeeting