21:02:53 #startmeeting Networking 21:02:54 Meeting started Mon Feb 3 21:02:53 2014 UTC and is due to finish in 60 minutes. The chair is markmcclain. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:02:58 The meeting name has been set to 'networking' 21:03:13 #link https://wiki.openstack.org/wiki/Network/Meetings 21:03:21 #topic Announcements 21:03:43 salv-orlando was able to isolate the kernel bug that has been causing our tests to fail. 21:04:14 Salvatore spent a lot of time working to isolate it. Huge Thank you to him 21:04:17 * pcm claping 21:04:22 Yay salv-orlando! 21:04:33 \o/ 21:04:33 great job 21:04:34 Yay! 21:04:36 thank you! 21:04:38 salv-orlando: great work! 21:04:43 thanks! 21:04:54 salv-orlando: bravo!! 21:05:04 we're still not out of the woods yet as our workaround doesn't always work 21:05:09 thanks salv-orlando 21:05:09 thanks I'm humbled 21:05:22 salv-orlando: beers for you! 21:05:36 indeed, we're still pretty much where we were last week. Even worse perhaps. 21:05:52 we'll be working with the Infra, QA, and Nova teams to get a workaround that is acceptable to everyone 21:06:41 I think we need lifeless's patch to merge so that the metadata service can be used while they work on it: https://review.openstack.org/#/c/70549/ 21:06:58 markmcclain: my understanding is that failure rate for patches is 100% because some job will always try to do the guestfs mount 21:07:13 salv-orlando: correct 21:07:22 nova is going to disable file injection by default soon anyway - I think file injection tests should be a new, separate job 21:07:45 as the default will have it off, we want to test that the default works :) 21:07:46 lifeless: I agree.. we have 2 different viable alternatives to key injection 21:08:00 salv-orlando, markmcclain: Great! What would be the best place to look for more info on the issue? 21:08:05 2? one being metadata.. and the other? config-drive? 21:08:20 salv-orlando: yes 21:08:32 3 technically - can always upload a new VM image with stuff pre-baked in it 21:08:47 edhall: the actual kernel bug info is here: https://bugs.launchpad.net/neutron/+bug/1273386 21:09:00 edhall: for bug 1273386, it's all in the bug report comments. I still need to provide crash dump info and a repro script independent from openstack for the ubuntu-kernel guys 21:09:08 the work around discussion should be in the channel logs from last Thursday 21:09:22 markmcclain, thanks, I've bookmarked it 21:10:10 edhall: bottom line is that the issue in unlikely to affect production systems, unless you deploy the compute service on the same host as the network services such as dhcp agent and l3 agent 21:10:11 Ok so we still need to wait until workaround is in place before we start approving patches again 21:10:30 I'll send out an email to left everyone know when +As will succeed again 21:11:04 but even then don't forget bug 1253896 and 1272012 are still lurking, so please let the patches for those bugs go first 21:11:32 salv-orlando, thanks; that might affect our dev environment so I'll pass that on 21:11:39 correct.. I'll get a few critical patches merged before I signal the all clear to start approvals 21:11:59 edhall: the exact conditions you have to met to be affected are in one of the last comments on the bug 21:12:41 #info Feature proposal deadline is Feb 18th 21:13:01 got it; thanks agai! 21:13:29 Anything code for blueprints must be proposed by the end of the day on Feb 18th. This will give the team time to review before the feature freeze 21:13:52 #link https://launchpad.net/neutron/+milestone/icehouse-3 21:14:18 We've have lots of items proposed for Icehouse-3. If you know something is not going to make, please PM me and we'll get it scheduled for Juno 21:14:27 #topic Bugs 21:14:50 We've spent time talking about the kernel bug. Are there any bugs the team needs to discuss this week? 21:15:50 #topic Tempest 21:15:57 Hi 21:16:09 mlavalle: has to leave at the bottom of the hour so moving his report up 21:16:22 I want to report to the team that api tests development has continued at a good pace 21:16:28 great 21:16:42 we have around 10 people actively pushing code 21:16:51 so I have been doing a lot of reviews 21:17:07 Thanks to all the people contributing to this effort 21:17:30 I am keeping a list of patchstes in review in the Neutron meeting agenda 21:17:41 mlavalle: thanks for keeping it updated 21:17:57 I encourage the core devs to take a look and help us with reviews 21:18:00 mlavalle: good job! we need to get more reviewers from tempest core team 21:18:38 the tempest core reviewers are hesitant to start merging tests until the problems in the gate with Neutron start imp[roving 21:18:46 mlavalle: once we get past this kernel bug, I expect we'll have more core neutron cycles to look at the tempest tests 21:18:51 mlavalle: https://review.openstack.org/#/c/70351/ is not in the list, but seems to duplicate another patch 21:19:08 https://review.openstack.org/#/c/63999/2 21:19:17 salv-orlando: Thanks 21:19:30 mlavalle: I think that is a good stance by the tempest team… we need a good baseline before we start merging new tests 21:19:31 mlavalle: that was just because I felt the need to be pedant. Sorry I could not resist it. 21:19:46 that's all I have 21:20:09 mlavalle: thanks for updating 21:20:27 #topic Docs 21:20:29 emagana: hi 21:20:37 markmcclain: hello! 21:21:07 I updated the wiki 21:21:14 thanks for keeping it current 21:21:28 there is a new proposal to create a Create Stand-alone OpenStack Networking Guide 21:21:54 ok so this undoing the combination effort we started a few weeks back? 21:21:57 #link https://blueprints.launchpad.net/openstack-manuals/+spec/create-networking-guide 21:22:36 but it will collect information from cloud admin guide and install guide 21:22:45 ok 21:22:52 the idea is to have anew book for networking deatils 21:23:01 ah cool 21:23:04 it will also help to review and update the other two! 21:23:32 Nick, Matt, Phil and I come together in a hang out meeting to plan it 21:23:51 a wiki with the propose index will be available 21:24:22 nice 21:24:26 that all I nave from my side 21:24:33 might I ask where we are with developer docs? jaypipes started this effort (https://review.openstack.org/#/c/64205/) and I would like to see more community members picking it up 21:24:35 Any docs questions? 21:25:23 salv-orlando: I'll chip in 21:25:23 salv-orlando: I could bring this topic into the Docs meeting 21:25:28 salv-orlando: good question… might make sense to start tracking dev docs initative 21:25:40 I actually registered a BP on friday for this 21:25:46 onboarding new folks is something we need to make easier 21:26:21 https://blueprints.launchpad.net/neutron/+spec/developer-documentation 21:26:50 salv-orlando: I would like to work on more docs. sorry for delay. should be able to work on more this week and next. 21:27:00 I have two devs that I'm in the process of onboarding - so I'll reach out to jaypipes and work with him 21:27:11 sc68cal: sounds good sean! 21:27:15 sc68cal, jaypipes: great 21:27:35 sc68cal and jaypipes: please add the details in the wiki 21:27:48 #topic nova-parity 21:27:50 beagles: hi 21:27:54 emagana: will do 21:27:56 hi! 21:28:53 there was a bit of progress last week on getting the bugs for unimplemented nova-net api methods. That means some of the bugs that were opened on that will be closed (yay!) 21:29:23 aweseome 21:29:42 the details of some discussions regarding the remaing high level gaps were captured in a wiki... https://wiki.openstack.org/wiki/NovaNeutronGapHighlights 21:30:28 it is *high level* so don't go looking expecting lots of technical details :) chances are the high level will be enough if its a topic you are interested in 21:30:33 beagles: thanks for creating it 21:30:52 it is perhaps encouraging that it is really short :) 21:31:02 it does touch on some rough spots we need to clean up 21:31:50 for those of you that may have missed the ML thread, there was a well-reasoned email thread on the deprecating nova network in Icehouse... worthwhile read. I captured the link in the minutes 21:32:42 russellb and I had a good conversation before that thread was started 21:33:08 I was focused on kernel bug last week, but will be adding in more information from Neutron side this evening 21:33:17 * beagles nods 21:34:13 Anything else to add? 21:34:22 the last item for now would be the pending reviews on the nova front... I suspect much energy was directed elsewhere last week so perhaps if/when things calm down with the gate these will get closure 21:34:31 and that .. is that 21:34:47 For those that missed the thread 21:34:48 #link http://lists.openstack.org/pipermail/openstack-dev/2014-January/025824.html 21:34:54 beagles: thanks for the update 21:35:06 #topic L3 21:35:09 carl_baldwin: hi 21:35:18 markmcclain: hi 21:35:26 I’m currently considering time slots for a team meeting. In the mean time, I encourage those who are interested to attend the DVR sub team meeting an Wednesdays run by Swami. I will be attending regularly. 21:35:33 #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam 21:35:43 Recent meetings have shown good progress and collaboration with DVR and HA routers. 21:35:58 great 21:36:00 Speaking of DVR, Swami asked me to “pass on the information that we will be having a ‘F2F meeting’ at the Bay in HP Palo Alto office to finalize the DVR options. I plan to attend virtually. 21:36:18 “Venue: HP Plato Alto office 21:36:19 “Date and Time: Feb 13th 11.a.m to 1p.m. 21:36:19 “Lunch will be provided” 21:36:23 Swami will update the ML with information about the virtual meeting room and dial in. If interested, please email him. 21:36:49 great 21:36:54 Anything else? 21:36:54 I'll be attending virtually. That’s all I have. 21:36:56 "Plato Alto" being a relative of the greek philosopher? ;) 21:37:10 sorry for the stupid joke 21:37:15 haha 21:37:17 Oops, copy/pasted directly from his email. 21:37:20 #topic IPv6 21:37:22 That should be Palo Alto. 21:37:37 sc68cal: hi 21:37:47 hello 21:38:18 We've got some new patches for review - adding the new attributes to the API, and then a patch that changes the behavior of dnsmasq when those attribtes are set 21:38:35 they're still a bit rough around the edges currently, we need to get the second patch to be based on top of the first 21:38:36 ok.. I've only briefly looked at them 21:38:59 I expect tomorrow's meeting will go in depth into them 21:39:01 yeah that would be nice so that gate properly handles them 21:39:04 great 21:39:21 Anything else? 21:39:26 the Nova hairpin patch has been fixed up to avoid the race bug 21:39:34 we're adding ... yet another flag to nova.conf however 21:39:45 but the good news is someone requested that, and it was a wishlist item 21:39:51 so two birds with one stone 21:39:55 ah nice 21:40:02 that's it for me 21:40:25 well neutron and nova conf now have more flags than the united nations headquarters in NYC. 21:40:27 ok.. would be nice to have a few members of the neutron team to look at https://review.openstack.org/#/c/56381/ 21:40:29 * salv-orlando ducks and runs 21:40:36 salv-orlando: :) 21:41:10 salv-orlando: haha 21:41:21 sc68cal: thanks for the update 21:41:23 #topic ML2 21:41:32 mestery & rkukura: hi 21:42:01 not sure if mestery is around 21:42:17 quite a few BPs in the works for icehouse 21:42:36 most for new drivers, but a couple with impact on the plugin itself 21:43:05 oh my 21:43:26 * mestery is having network problems 21:43:34 * rkukura is too 21:43:42 rkukura: ok please PM me to make sure I've got the right priority on the blueprints that impact all drivers 21:43:44 not me 21:43:56 I think freenode isn't stable today.. Is this only for me? 21:44:08 looks like we had a netsplit again 21:44:09 I've also started working on tightening up some unit test coverage 21:44:19 Would be good to get some discussion/feedback on http://lists.openstack.org/pipermail/openstack-dev/2014-January/025812.html 21:44:30 nati_ueno: it's been going on since before I started this mornign 21:44:38 nati_ueno: +1 21:44:43 markmcclain: gotcha 21:45:47 Would also like to know if progress is being made on https://blueprints.launchpad.net/neutron/+spec/ml2-deprecated-plugin-migration 21:47:04 the migration is really important as we cannot remove the OVS and Bridge plugins until we have it 21:47:25 +1 to that markmcclain 21:48:07 anybody has received an update from the assignee? 21:48:37 I've emailed Prakash and he seems to expect to get it done, but I'd like to see if he needs any help 21:49:02 Anyone know his nic? 21:49:22 rkukura: might be good encourage the code to be posted and regular WIP updates 21:49:35 that way we can start testing early versions of the migration 21:49:53 I'll followup his email, and hopefully we'll know more for next Monday 21:50:15 Anything else for ML2? 21:50:37 not from me 21:50:42 Thanks for the update 21:50:48 #topic Group Policy 21:51:08 This is a new item. The team has been regularly meeting and I wanted to give an opportunity to share back with the team 21:51:12 mestery: hi 21:51:14 Hi 21:51:22 Thanks markcmcclain 21:51:40 Have started coding for a PoC 21:51:41 So we have been meeting very week since Hong Kong 21:51:57 Yes as Vanir says we are entering PoC stage 21:52:06 banix sorry 21:52:19 Please see our Meeting page for more details 21:52:28 But we hope to get this into Juno 21:52:39 great 21:52:42 We will be scheduling design summit sessions for Atlanta 21:52:49 Thanks markmcclain 21:53:28 mestery: thanks for sharing 21:53:34 #topic Open Discussion 21:53:40 mestery: planning for Juno is a considerate decision, in my opinion. It will also give us a chance to synchronise this effort with api framework changes. 21:53:44 markmcclain: let's me update vpn brifly 21:53:58 nati_ueno: go ahead 21:54:02 Thanks salv-orlando, good point! 21:54:25 markmcclain: Thanks. I updated wiki. We have api wiki doc. https://wiki.openstack.org/wiki/Neutron/VPNaaS/SSLVPN client patch https://review.openstack.org/#/c/70254/ agent code comming soon 21:54:28 mestery: can you add a link to the meeting agenda page - for the policy group meeting discussions, that is…. 21:54:31 markmcclain: That's all. 21:55:04 Wondering if there is any interest in an IRC about vendor drivers for L3 services (discussing validation, client feedback, error reporting/handling, persistence)? 21:55:05 Sukhdev: yes I will do that I am mobile from iOS at the moment :) 21:55:19 nati_ueno: thanks for the update 21:55:37 Would any of the other sub teams like to update? 21:55:42 Group policy: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy 21:55:55 markmcclain: for FWaaS, SridarK put significant effort in testing to check if we are ready for enabling FWaaS in the gate 21:56:06 no major updates from lbaas 21:56:15 SumitNaiksatam: great 21:56:17 markmcclain: results of his testing have posted at: https://wiki.openstack.org/wiki/Quantum/FWaaS/Testing 21:56:29 sukhdev: pls see the link posted above. 21:56:36 we'll probably want to a few days after we get the gate going again before we enable 21:56:39 SridarK: is also here, so he can chip in as well 21:56:42 just so we can get a good baseline 21:56:48 markmcclain: i totally understand 21:56:51 banix: thanks 21:56:56 Running thru tempest API tests with FwaaS enabled, comparison with baseline looks good as well. 21:57:02 markmcclain: just want to convey that we are prepared 21:57:15 markmcclain: you can make a call whenever 21:57:19 SridarK: good 21:57:21 SumitNaiksatam: thanks for being ready 21:57:47 enikanorov__: ok thanks for letting me know 21:57:56 Any other items for this week? 21:58:50 Wondering if any interest in L3 services discussions, regarding vendor impl.? 21:58:59 pcm: +1 21:59:24 Wanted to discuss handling for persistence, validation, client feedback, err handling, etc. 21:59:44 maybe in a manner that will be consistent across services and between vendor and ref impl? 21:59:56 pcm: might be good to post a time and have everyone discuss in #openstack-neutron 22:00:09 the channel is logged for those that can't make the discussion 22:00:31 Ok we're at time. Thanks to everyone for stopping in this week. I'll send an update to the mailing list once we get the gate fixes in place and tested. 22:00:35 OK. didn't know if should have something in meeting channel. 22:00:48 thanks 22:00:58 Those still around, what time/date would be good to meet? 22:01:09 pcm: It's good solicit interest here 22:01:09 #endmeeting