15:01:11 #startmeeting neutron_l3 15:01:11 Meeting started Thu Apr 10 15:01:11 2014 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:14 The meeting name has been set to 'neutron_l3' 15:01:38 #topic Announcements 15:01:49 #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam 15:02:06 hi 15:02:14 hi 15:02:33 Deadline to submit summit design topics is April 20th. About a week away. Is anyone planning to submit a topic (or already submitted)? 15:03:27 I'll probably have some time to read through some if you want an extra set of eyes on it before submitting. 15:03:54 I'm busy myself trying to get a couple of blueprints written up to submit. 15:04:47 Does anyone have the link for the page for submitting these handy? 15:05:04 http://summit.openstack.org/cfp/create 15:05:48 overlayer: Thanks. 15:06:22 #topic l3-high-availability 15:06:42 safchain: any updates? I saw some update to the blueprint. Accepted for Juno. 15:07:13 carl_baldwin, hi, just got some interesting comments 15:07:39 carl_baldwin, I have to check if there is overlaps with le l3 dvr patch 15:08:23 Yes, working closely with DVR will be a good thing. 15:08:30 carl_baldwin, I will ping swami to talk about that 15:08:57 carl_baldwin, that's all for me 15:09:04 Swami will join a bit later. 15:09:42 For me, reviewing this has fallen below some Icehouse stuff and the summit topics. I plan to get back to it after the 20th. I imagine others are in the same boat. 15:09:53 Thanks for your update. 15:10:09 #topic bgp-dynamic-routing 15:10:11 carl_baldwin, sure, np 15:10:17 nextone92: hi 15:10:24 Hi carl! 15:10:39 I had an action to update the use cases. I have done that and they are linked from the sub team page. 15:10:44 Unfortunately I haven't gotten any additional feedback about the document 15:11:27 I did have another look and I like the changes you've made to it. 15:11:47 Thank you Carl 15:11:51 Do you plan to suggest a summit session? 15:12:06 Would that be okay? 15:12:50 Yes, I think it would be great. I'd be happy to discuss it sometime during the next week. 15:13:21 Thank you! I will submit the proposal 15:13:40 And looking forward to any additional comments and feedback 15:13:59 Great. Feel free to ping me on IRC. 15:14:02 Anything else? 15:14:16 That's all on dynamic routing 15:14:36 Thanks. 15:14:51 #topic rootwrap-daemon-mode 15:15:01 ajo, YorikSar : hi 15:15:17 o/ 15:15:20 I've been out of the loop on these reviews this week. 15:15:32 I don't have much updates this week. 15:15:59 Okay, let's talk more about it after the 20th. 15:16:20 I've ran into unpleasant bug in stdlib that isn't fixed on 12.04 that's used in gate but was fixed in the very next version of Python (2.7.4) 15:17:17 Ok 15:17:26 YorikSar: Could we bring it up with infra to see if an upgrade is possible? 15:17:59 carl_baldwin: I suppose we should support vanilla Ubuntu 12.04 15:18:19 And I don't think it's possible to upgrade Python in Ubuntu LTS release 15:18:21 hi carl_baldwin , YorikSar , sorry, it seems that I was a little bit confused with the meeting time , and time shifts 15:18:30 (reading) 15:18:42 ajo: Thanks for joining. 15:19:00 YorikSar, 15:19:03 what's the bug exactly? 15:19:07 But I can ask on #openstack-infra about it. 15:19:16 http://bugs.python.org/issue6065 15:19:19 I mean, in RH they use py2.6 15:19:27 so I'll need to make sure this is backported in place 15:19:42 Oh... 15:19:49 YorikSar: It might help to understand. The worst that can happen is they will tell us we can't upgrade. 15:19:54 Is the bug also in 2.6? 15:20:00 I'm trying to come up with workaround for that. 15:20:14 are you sure it's http://bugs.python.org/issue6065 ? 15:20:21 it looks like MSI installer related 15:21:02 Hm... I have no idea about 2.6 I guess it hasn't been fixed in that branch since it was already not supported by then. 15:21:16 Oh... I've lost some digit. Let me check. 15:22:00 YorikSar: ajo: I'll let you take it offline. Looks like you've got some things to try. 15:22:28 thanks carl_baldwin 15:22:36 #topic Multiple Subnets on External Network 15:22:46 carl_baldwin: ok 15:22:55 This is a new topic on the agenda this week. 15:23:30 I've heard this from a few people now and it is a problem that I have as well. 15:24:32 It was http://bugs.python.org/issue6056 15:24:49 (sorry for interrupting) 15:25:03 YorikSar: (no worries) 15:25:30 The use case for this is to allow growing the floating IP pool by adding subnets to an external network. 15:26:43 I don't have much more than that, just an introduction to the topic. Please contact me if this use case is interesting to you and you would like to participate in making it work like it should. 15:27:34 I hope to understand it a little better next week. 15:27:54 carl_baldwin, I am interested in it a lot :-) any information to learn more about this? 15:28:11 carl_baldwin, sure, I'm interested too 15:29:00 carl: hi 15:29:03 xuhanp: Not really yet. I'll keep you in the loop. 15:29:08 safchain: you too. 15:29:12 carl_baldwin, thanks 15:29:16 carl_baldwin, thanks 15:29:25 Swami, hi 15:29:30 If you get ambitious and start looking in to it, do the same for me. :) 15:29:31 safchain: hi 15:29:51 Swami: your timing is impeccable 15:30:08 #topic neutron-ovs-dvr 15:30:23 DVR progress update 15:30:54 As mentioned in the previous meeting we could not post the L2 Agent and L3 Agent code this week, since we were busy with some merging work. 15:31:24 The plugin code comments have been addressed and patch5 is up for review. 15:31:36 Still working on some more unit testing before removing the WIP. 15:32:01 We are targeting to push the L2 Agent and L3 Agent code by next week. 15:32:35 Meanwhile in yesterday's discussion there was question that was raised about the multiple external networks and using the br-int instead of the br-ex. 15:32:56 I am not sure if there was a discussion on this with safchain in this meeting today. 15:33:07 Swami, not yet 15:33:29 That will be fine. I imagine that the community will have more time for reviewing as Icehouse winds down and after the deadline for submitting summit sessions on the 20th. 15:33:45 safchain: Today in Icehouse when we use multiple external networks, the networks are bridged from the br-int and not from the br-ex. 15:33:54 Swami, that was the subject of the email I sent to you 15:34:15 safchain: Yes I did not understand the complete context when you sent me the email. 15:34:17 Swami, yes with provider networks and bridges_mappings 15:34:24 sorry it was my mistake. 15:34:28 Swami, np 15:35:04 So when provider networks are in place where is the actual SNAT happening. 15:35:12 Is it in the network node or in the provider network. 15:35:20 Swami, so yes with multiple networks there is a veth between br-int and the external bridge 15:35:54 in the network node, between the qg- and the qr 15:36:07 but the qg is in the br-int 15:37:13 So if the qg is in the br-int then what is the use of the veth pair between the external bridge and the br-int 15:38:03 so today it is a veth but with this patch https://review.openstack.org/#/c/76685/, it will use a patch interface 15:38:35 Swami, map the local vlan to the ext vlan 15:39:26 safchain: So the external traffic will hit the br-int qg_ and will leave the network node without touching the br-ex 15:39:38 right, no more br-ex 15:40:23 In this case will the existing services such as VPN will it still work. 15:40:44 safchain, but the external bridge is still needed just like other physical interface bridge, right? 15:40:47 Swami, but you can use provider network for a service network private or shared 15:41:09 xuhanp, no not needed 15:41:23 xuhanp, you can define a provider network as external 15:41:37 safchain: Ok got it. 15:41:45 safchain, OK. I see 15:41:50 In this case all the services will then be rendered by the provider network. 15:42:12 we have a lot of customers which use provider networks 15:42:13 Does the provider network also takes care of assigning the Floating ip 15:42:46 Swami, it is exactly the same as with the br-ex 15:43:25 safchain: got it. 15:43:36 Swami, it is just the ovs lib which doesn't create the interface in the same way thanks to the bridge_mappings config parameter 15:43:56 If I have more questions I will ping you on this, while we are working on the North-South DVR implementation. 15:44:12 Swami, but you could have any external network, so any ext bridge 15:44:38 Swami, I would like to talk with you about the l3 patch you submit and the vrrp 15:44:59 I don't have the time today, will you available tomorrow 15:45:10 safchain: Feel free to shoot me an email. 15:45:19 Swami, great, i'll do 15:45:30 I will be available tomorrow. If you would like to chat on IRC send me an email and I can log in. 15:46:00 Swami, ok, and we could talk about the ext net. as well 15:46:25 safchain: Swami: Is there a summary of what needs to happen wrt br-int/br-ex in the context of DVR or VRRP? 15:47:00 carl: Yes the DVR team need to evaluate the Ovs rules for the provider network case and validate the scenario. 15:47:11 I will probably give an update in the next week about this. 15:47:30 carl_baldwin, I think for the VRRP part it should be ok 15:47:43 Swami: safchain: Great, thank you. 15:47:51 In the context of the DVR - L3 vrrp patch I will work with safchain and see how we can bring it together. 15:47:54 carl_baldwin, already tested, but of course needs more tests 15:48:46 carl: That's all I have from the DVR team. 15:48:55 Swami: Thanks for the update. 15:48:58 sorry guys I have to go now, Swami see you tomorrow, carl_baldwin thx for the meeting 15:49:12 safchain: bye 15:49:17 bye 15:49:19 safchain: thank you 15:49:27 #topic Open Discussion 15:50:58 safchain, cya 15:51:39 Thanks to all who have participated. Have a great week! 15:51:54 bye 15:52:02 #endmeeting