15:02:21 #startmeeting distributed_virtual_router 15:02:22 Meeting started Wed Sep 3 15:02:21 2014 UTC and is due to finish in 60 minutes. The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:25 The meeting name has been set to 'distributed_virtual_router' 15:02:50 #info Today will be the Juno 3 cut off date 15:02:59 mrsmith: hi 15:03:40 So today will be the last day for all Juno features to get in. 15:03:53 Swami: hiya 15:03:54 Rajeev: hi 15:04:02 Swami: Hi 15:04:10 #topic Agenda 15:04:18 #topic DVR Update 15:04:59 All our DVR patches have landed upstream. 15:05:22 We are still working on bugs. 15:06:39 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-dvr-backlog 15:06:59 Link provides a list of all bugs. 15:08:20 Most of the High bugs have assignee's and are worked out right now. 15:08:53 There were couple of new bugs that was filed yesterday by Viveknarashimhan 15:09:34 Swami: one thing to keep in mind, Jenkin queues are backed up so give sufficient time for runs 15:09:39 #link https://bugs.launchpad.net/neutron/+bug/1364215 15:09:40 Launchpad bug 1364215 in neutron "L2 Agent switch to non-dvr mode on first RPC failure" [Undecided,New] 15:10:07 i raised that to handle 15:10:11 #link https://bugs.launchpad.net/neutron/+bug/1364839 15:10:12 Launchpad bug 1364839 in neutron "DVR namespaces not deleted on LBaaS VIP Port removal" [Undecided,In progress] 15:10:23 the situation discussed in yesterdady meeting 15:10:43 1364839 is to address removal LBaaS and DHCP Ports on dvr subnets from service nodes 15:11:44 viveknarasimhan: thanks for the update 15:12:34 viveknarasimhan: the check_vm_exists_on_host does it not take care of the dvr related ports right now. 15:12:44 that takes care 15:13:07 so what was missing, in there 15:13:10 but delete_port logic in ml2_plugin does not invoke deletion of namespaces for service pors. it was handling only 15:13:12 for vm ports 15:13:16 i posted review here: 15:13:29 viveknarasimhan: ok 15:13:59 for the 1364215 do we have fix 15:14:09 How severe is this bug 15:14:15 that i am not fixing now 15:14:33 will fix if we have a consensue that it needs to be fixed 15:14:49 that was raised as a placeholder for issue seen in TriploO deployment of DVR 15:14:53 Ok let us wait till armax triages it 15:15:08 review link for 1364839 here: https://review.openstack.org/118580 15:15:17 ok 15:15:34 Is this issue seen in devstack or can be reproduced in devstack 15:16:16 reproducible in devstack also 15:16:20 if nodes start before controller 15:17:03 i presumed the issue you ask here is 1364215... 15:17:17 viveknarasimhan: yes 15:17:43 yes, that is seen in devstack if nodes start much earlier than controlelr 15:18:24 viveknarasimhan: have you posted the patch for the SNAT namespace deletion that you added to the SNAT patch 15:18:40 i posted that here: 15:18:41 as a separate patch 15:18:49 and then it was Abandoned by armax 15:18:57 since similar patch was posted by Carl here: 15:19:04 ok 15:19:40 There are couple of other patches that are pending review. 15:19:48 SNAT patch that gets rid of hints. 15:19:58 is there plan to divide teh 'Refactor hints' patch 15:20:02 into two 15:20:07 or that is already being pursued? 15:20:21 Carl_baldwin: mentioned that he is trying to break it up into chunks instead of pushing it as a single patch 15:20:38 So I am waiting on it. 15:20:44 Swami: I posted a link to my proposed work in the patch. 15:20:47 swami: ok 15:21:06 carl_baldwin: Yes I took a look at the proposed patch. 15:21:39 carl_baldwin: are you planning to push the individual patches to gerrit 15:22:19 Swami: I wanted your thoughts on it first. Then, either you or I could post them to gerrit. 15:22:47 ok, I will review it once again today and will ping you 15:23:02 and then we can proceed 15:23:05 viveknarasimhan: I did not realize that you were duplicating that patch I posted. 15:23:20 Carl: that is ok carl 15:23:33 i did that patch as it fixed teh SNAT namespace deletion 15:23:39 in conjunction with the refactor hints patch 15:23:40 viveknarasimhan: I just happened across it after having already approved the original patch that changed the name. 15:23:49 so i put that change as dependency to refactor hints patch 15:24:17 viveknarasimhan: ok 15:24:52 The migration patch also is waiting for review. 15:24:55 carl: thanks for finding and pushing that up 15:24:56 #link https://review.openstack.org/#/c/105855/ 15:25:36 There is also another patch that is related to migration that I pushed in yesterday 15:25:40 #link https://review.openstack.org/#/c/118491/ 15:26:17 mrsmith: Did you get a chance to review the migration patch, I cleaned it a bit after your commit. 15:26:28 not yet 15:26:33 I will this morning 15:26:41 mrsmith: thanks 15:27:19 I think we are done with bugs 15:27:28 #topic Services 15:27:37 I have one review targeted for Juno-3 waiting 15:27:42 Stop tracking connections in DVR FIP Namespace: https://review.openstack.org/#/c/116412/ 15:27:46 The FWaaS team have posted a patch for DVR N-S support. 15:28:18 Swami: sorry to interrupt, since juno-3 is tomorrow 15:28:49 Rajeev: Actually, with the current gate pileup, nothing more will make juno-3. 15:28:54 Ok thanks 15:29:02 hockeynut, yt? 15:29:25 atiwari yessir 15:29:32 carl_baldwin: thanks. 15:29:38 carl_baldwin: Does it mean even the bug fixes will not go through Juno 3 15:29:49 I have addressed some of your comments in my latest patch 15:29:59 Bug fixes can still go in after juno-3. 15:30:07 I have also answered your questions 15:30:26 carl_baldwin: thanks that what I wanted to confirm 15:30:29 regarding the \ comment, is it ok to address in separate cr? 15:30:36 certainly 15:30:36 hockeynut, ^ 15:30:41 atiwari: what patch are you talking about 15:31:11 sorry wrong room, I am very sorry 15:31:20 its ok 15:31:22 atiwari: :) 15:31:33 carl_baldwin, :) 15:31:40 Let me get back to the Services discussion 15:31:48 The FWaaS team have posted a patch for DVR. 15:31:52 #link https://review.openstack.org/#/c/113359/ 15:33:01 FWaaS team had some issues in their rules not getting honored by the SNAT namespace. 15:33:39 Swami: I have couple of DVR patches I am working on, will try to take a look at FWaaS alongwith 15:34:02 SumitNaiksatam requested for a half hour call, if possible we should address that issue, since this patch has to go in today. 15:34:39 amotoki: hi 15:34:54 Swami: hi 15:35:44 Ok, we can go through the FWaaS issues with the FWaaS team today. 15:36:14 #topic horizon 15:36:21 amotoki: hi 15:36:38 I just got home a while ago :) 15:37:02 patch series of DVR support in horizon have been merged. 15:37:03 amotoki: did you get a chance to work on the router edit page on horizon, sorry just checking. 15:37:38 enable_distributed_router flag is added to horizon settings. 15:37:52 Swami: both patches have been merged. 15:37:53 amotoki: great! 15:38:11 amotoki: can you provide me the links to both patches 15:38:40 If you don't have it handy, it can do a look up in gerrit. 15:39:31 Swami: looking for it but my browser is now slow... 15:39:54 amotoki: fine, if you can send me an email later or I can take a look at it. 15:40:03 amotok: no worries 15:40:15 amotoki: thanks for your help 15:40:32 https://review.openstack.org/#/q/project:openstack/horizon+branch:master+topic:bp/enhance-horizon-for-dvr,n,z 15:41:08 amotoki: Thanks for the links 15:41:42 amotoki: bhooshan: great job. Well done in a short span 15:41:48 amotoki: thanks a lot for your timely help in horizon for dvr 15:41:59 #topic Open-Discussion 15:42:17 Any other open discussion for the DVR 15:42:44 one question. how does DVR experimental job run? 15:43:00 do we use multinode testing? 15:43:08 From next week let us plan on addressing some features for the Kilo 15:43:29 amotoki: I don't think the multinode is up yet 15:43:38 amotoki: Still no multi-node testing. I think there has been some slow progress on it but it is not here. 15:43:43 we are still using the single node setup. 15:44:13 amotoki: there was a patch for review on mutlinode but it is still under review. 15:44:27 I had a question just come up about attaching a vlan network to a distributed router. 15:44:50 Will there be an error if one attempts to do this or will it fail silently under the hood? 15:45:01 Swami: carl_baldwin: thanks. will check the review. 15:45:03 viveknarasimhan: any comments on the vlan 15:45:29 vlan 15:45:41 is not supported in teh current architecture 15:45:48 viveknarasimhan: see the message above from carl_baldwin 15:46:05 will it throw an error or fail silently 15:46:18 i have to check about routing. 15:46:25 switching will continue to work e 15:46:45 it will not throw errors 15:46:52 if network type is vlan, we donot apply any flows 15:46:57 routing will fail 15:47:03 switching will continue to work 15:47:21 viveknarasimhan: So, there will be no API error? The end user will see success from the API? 15:47:39 yes, he will see success 15:47:57 not sure if the plugin validates if this is a tunneltype network 15:48:02 rathern than vlan network 15:48:12 swami: can you please clarify on that question by carl 15:48:31 viveknarasimhan: Will there be an error if one attempts to do this or will it fail silently under the hood? 15:48:31 it is not checked, so it will succeed 15:48:43 what do we mean by failure? 15:48:47 viveknarasimhan: I think you have answered 15:48:48 routing will fail 15:48:51 switching will succeed 15:49:06 viveknarasimhan: I mean will the API call fail. Sounds like it will not. 15:49:08 from an api perspective it will not through any errors. 15:49:15 the plugin does not stop adding vlan subnet to dvr 15:49:19 Okay. Thanks. 15:49:24 I’ll put a bug in to the backlog. 15:50:14 carl_baldwin: thanks that would help 15:50:25 thanks everyone for joining the call. 15:50:29 See you all next week 15:50:38 bye 15:50:49 #endmeeting