15:04:31 #startmeeting neutron_northbound 15:04:31 Meeting started Wed Jul 27 15:04:31 2016 UTC. The chair is yamahata. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:04:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:31 The meeting name has been set to 'neutron_northbound' 15:04:43 #chair vthapar mkolesni asomya 15:04:43 Current chairs: asomya mkolesni vthapar yamahata 15:04:50 #topic agenda bashing and roll call 15:04:56 #info yamahata 15:05:02 #info mkolesni 15:05:07 #info asomya 15:05:13 #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings meeting adgenda 15:05:19 #info vthapar 15:05:24 I updated the page. 15:05:57 In addition to usual topics, I newly added "migrating to new features" 15:06:22 I mean, what needs to be done to switch to new features like v2 driver for Newton cycle. 15:06:30 any other agenda items? 15:07:08 what was decided about vlan aware vms? 15:07:17 its pushed back to carbon? 15:07:28 it's for carbon. 15:07:31 yes 15:07:34 ok 15:07:49 #topic Announcements 15:08:09 Boron M5 was past. Now it's code freeze. 15:08:24 #link https://wiki.opendaylight.org/view/NeutronNorthbound:Boron_Release_Plan 15:08:52 Soon the branch will be cut and master branch will be open for Carbon. 15:09:08 Personally I'll focus on networking-odl. 15:09:23 voting for openstack summit is open 15:09:32 #link https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/ 15:09:48 So please vote for our and ODL proposals 15:09:57 +1 15:09:59 any other announcement? 15:10:53 seems nothing, next. 15:10:55 #topic action items from last meeting 15:11:20 yamahata report M5 report, updated meeting page and decidec vlan-aware-vm plan. done 15:12:02 The next planned topic is "migrating to new features". before that I'd like to finish other items before. 15:12:13 #topic patches/bugs 15:12:31 I've uploaded a bunch of patches to enabled new features with devstack 15:12:53 My goal is to enable new features with openstack CI 15:13:31 Any patches/bugs which we need special attention for? 15:14:35 So far I hard from some complaining about logging of networking-odl is too verbose. 15:14:46 Anyway we will see by CI. 15:14:56 there was some report by a guy from hpe 15:15:15 but i think its low priority since he's talking about debug logs 15:15:51 #link https://bugs.launchpad.net/networking-odl/+bug/1605112 q-svc.log if filled with [networking_odl.journal.journal] printouts 15:16:27 #link https://bugs.launchpad.net/networking-odl/+bug/1604678 networking ODL-V1 VS. networking ODL-V2 - PortsAdminExtendedAttrsTestJSON test cases fail 15:16:43 I made 1605112 low priority 15:17:20 any volunteer for 1604678 15:17:38 1605112 might be invalid, i'll triage it 15:17:41 anyway after enabling CI, I expect more will pop up. 15:17:55 asomya: cool thanks. 15:18:49 any other bugs/patches? 15:19:38 okay we can move on to migration to new features. 15:19:42 #topic migrating to new features 15:20:30 Although there are many things to be added for new features, we should also think about how to switch to them. 15:20:39 I put some 15:20:46 #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings 15:20:57 I'll create a wiki page for it 15:21:06 #action yamahata create a wiki page for feature migration 15:21:40 at least we should enable openstack CI and stabilize/harden them. 15:21:42 we need to do it gradually 15:21:54 i.e. first switch to v2 driver 15:22:07 once its stable switch to vpnservice netvirt 15:22:20 if we do all at once we wont know where the problems come from 15:22:53 mkolesni: fully agree. one thing at a time 15:23:24 vpnservice isn't feature parity for Boron. It will take for Carbon. So for newton cycle it will be experimental. 15:23:38 I suppose vpnservice switch will be the last. 15:23:51 makes sense 15:24:38 For v2 driver, in addition to CI, what else should be done? 15:25:04 once ci is stable we should make it default 15:25:21 mkolesni: +1 15:26:09 benchmark with many resources is necessary. e.g. 10k ports 15:26:30 do we have h/w for that? 15:26:34 Probably Rally can be used. and we'd like to know latency increase and CPU usage. 15:26:59 we don't have any in public. 15:27:12 i thought rally is for the api load i.e. running many requests 15:27:30 but not necessarily with many resources 15:27:58 mkolesni: right. 15:28:18 We may have to create simple script for benchmark if rally isn't suitable. 15:28:24 we need to see if its possible upstream 15:28:50 yeah. 15:28:50 should be but well see.. 15:29:15 probably we need tests for full sync 15:29:23 and journal recovery 15:29:38 and other maintenance features we have 15:29:56 new tests would be needed for those. 15:30:18 i dont think its on tempest level 15:30:35 probably we need some system test layer in the project 15:33:04 For pseudo agent port binding, it needs to be tested at first 15:33:04 ill try to work on it but cant guarantee 15:33:12 mkolesni: cool. 15:33:33 I'm also trying to plan benchmark internally first. But right now no guarantee. 15:34:14 mohammed will work on port binding related staff. 15:34:33 ok 15:35:30 The behaviour of v2 driver would be interesting. If it can be a topic at opendaylight/openstack summit, design summit/forum. 15:36:13 anything else? 15:36:26 I'll create a page, so please add your ideas. 15:36:30 ok 15:36:55 #topic open mike 15:37:01 anything else to discuss? 15:37:11 nothing from my side this week 15:37:22 Cool. so we can skip bluejeans 15:37:29 +1 15:37:31 nothing from me either. 15:37:44 one suggestion, would be good to send openstack voting link to mail list 15:38:00 vthapar: can you take it? 15:38:10 yamahata: sure. 15:38:18 #action vthapar send openstack voting link to mail list 15:38:19 the list is rather small, perhaps ask people to spread it around 15:38:24 yay ;-) 15:38:39 will send it to neutron, netvirt and ovsdb. 15:38:40 #action everyone ask people to spread openstack voting around 15:38:42 ovsdb is lot bigger :) 15:38:49 good idea 15:39:19 need to specify which particular topics? the way it is done couldn't extract links to individual submissions. 15:39:31 had to search "Opendaylight" and then find ours. 15:40:33 It seems like that the specific topic can't be linked intentionally. 15:41:07 yeah :) 15:41:28 perhaps yamahata can send you the names to vote for? 15:41:31 want me to give instructions on how to find, just mention use "opendaylight" in search 15:41:41 mkolesni: sure 15:42:07 The evolution of OpenDaylight with OpenStack: big changes for production environment in future 15:42:16 OpenStack Networking SFC and L2GW service through OpenDaylight 15:42:22 the second is for vthapar 15:42:53 yeah, will add those too. 15:43:26 thsoe are the only two from us, right? 15:43:27 you can search for "Isaku" ;P 15:43:49 Have a bite of 1K+ nodes with a handful of servers 15:44:02 found that one when searching for Isaku :) 15:44:15 there are many odl proposal. SFC seems hot topic 15:44:55 okay anyother topics? 15:45:02 otherwise I'll give you back 15mins. 15:45:06 +1 15:45:27 thank you everyone! 15:45:33 thanks Isaku 15:45:35 #topic cookies 15:45:41 have a nice day everyone 15:45:43 #endmeeting