15:03:33 #startmeeting vpnaas 15:03:33 Meeting started Tue Jan 6 15:03:33 2015 UTC and is due to finish in 60 minutes. The chair is pc_m. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:37 The meeting name has been set to 'vpnaas' 15:03:43 Hi 15:03:57 hi matrohon: mhanif: 15:04:15 Hope everyone had a good break 15:04:46 #topic announcements 15:05:06 really nice! I saw you had hard time debugging ipsec connection during your vacations 15:05:29 matrohon: Yeah, will bring up under open discussion. 15:05:40 Initial L3 refactoring for VPN is upstreamed. Please update any reviews. 15:05:50 UTs are operational as well. 15:06:08 pc_m : cool! 15:06:23 We had to move to meeting-4 (I missed that meeting-3 was in use). 15:06:37 #topic Bugs 15:06:59 I see these bugs: 15:07:17 #link https://review.openstack.org/#/c/143203/1 15:07:36 Looks like it needs a rebase and some cleanup. 15:08:22 * pc_m don't see Swaminathan on. 15:08:39 #link https://review.openstack.org/#/c/145005/1 15:09:03 Wondering what peoples thoughts are on this one? 15:09:33 Should we resolve the FQDN versus use next hop? 15:10:28 resolving fqdn sounds better, no? 15:10:42 matrohon: Yeah, that's what I'm thinking. 15:10:58 Will note that in review. 15:11:08 #link https://review.openstack.org/#/c/142484/ 15:11:35 This looks fine to me. Please review (and other bugs listed). 15:12:15 #link https://review.openstack.org/#/c/143203/ 15:12:49 you already talked about this one 15:13:02 whoops... 15:13:20 #link https://review.openstack.org/#/c/145219/ 15:13:31 So this is just a place holder. 15:14:02 Idea here is to eventually remove all these methods from the VPNService class, once we have a router instance. 15:14:37 Carl and others are refactoring L3 to pull out a router class and once we have that, the device drivers can 15:15:01 communicate with the router directly. 15:15:12 Any other bugs to consider? 15:15:36 * pc_m wish the bot was working to expand the review summary 15:16:13 #topic Open Discussion 15:16:35 Anyone have anything else to discuss (I know I do, but will give others' a chance)? 15:16:59 Update on couple of action items from last meeting 15:17:02 mhanif : did you ping any core to have a clear understanding 15:17:17 mhanif: Great... go ahead... 15:17:17 about stackforge project or not 15:17:26 mhanif : +1 15:17:28 Yes, as we all know the L3Gateway is now being done in stackforge 15:17:53 For edge VPN, we are also asked to work in stackforge 15:18:18 I am setting up stackforge for edge VPN work as we speak 15:18:25 cool 15:18:43 Hope to share with the team the link to the project as soon as I am done. 15:18:51 pc_m: Thanks! 15:18:57 you are going to implement your spec as is 15:19:01 for edge vpn? 15:19:01 mhanif: That would be great. 15:19:40 mhanif: Do you have a link to the spec for those curious? 15:19:45 matrohon: It will be up for review and contribution. Very open to any and all suggestions. 15:20:35 pc_m: Here you go: https://review.openstack.org/#/c/136929 15:20:40 ty 15:20:57 #link https://review.openstack.org/#/c/136929 15:21:28 mhanif : do you have the spec for l3gateway? 15:21:28 Will be breaking new ground with all this. 15:22:03 matrohon: No. not yet. 15:22:45 mhanif : you were mentioning that l3gateway will land in stackforge. There is no associated spec? 15:22:56 or were you talking about l2gateway? 15:23:15 It was l2gateway. sorry 15:24:27 The link to L2Gateway project is at: #link https://review.openstack.org/#/c/141289/ 15:25:01 mhanif: Thanks for the link 15:25:45 what will be the overlap between edge vpn and l2gateway? 15:26:43 Crrently, l2gw only talks about overlay networks to vlans bridging 15:27:01 mhanif : I mean for l2 vpn, your PE can be considered as a l2gateway 15:27:32 mhanif : does it sounds crasy? 15:28:07 Yes, it can be. The distinction is edge VPN also talk about provisioning of VPNs 15:28:14 * pc_m need to read up on L2 VPN... 15:29:21 I did have some questions for the group about VPN testing... 15:29:24 matrohon: There is little overlap 15:30:05 I've been trying to figure out how to test VPN using VMs (versus bare metal). 15:30:34 mhanif : it would be really fine if edge vpn only deals with VPN attachment to the cloud, and not how this attachment is done technically 15:31:16 mhanif : lets continue during review 15:31:27 matrohon: +1 15:31:44 +1 15:31:45 matrohon: sure 15:31:52 matrohon: Thanks 15:32:22 pc_m : so what is the current status of your tests? 15:32:25 Has anyone setup VPN on VMs (one or two) and been able to test IPSec connections? 15:32:41 Over break, I was looking at A) one DevStack with two routers and two private nets, and B) two DevStacks in two VMs. 15:33:20 a while ago, I've been testing B) 15:33:33 but A) looks better... 15:33:36 With A) I create a second router and what I see is that from the second router's namespace, I can ping the private interface of router1 15:33:48 Not expecting that to be possible. 15:34:00 And don't see that on bare metal. 15:34:06 really weird 15:34:33 and VM can ping each others? 15:34:44 I started a bit on B), but had a bunch of problems, but I was running OoO and I guess there was some issue with nested virtualizations. 15:35:21 matrohon: Well, didn't go that far yet as I was worried about the connectivity as it stands. 15:35:56 the main benefit with A) is that we could have a corresponding functional test upstream 15:36:22 So, hoping for some help on trying to get A working. Later, I'll try B) under virtualbox. 15:36:27 markmcclain: ping 15:37:32 I can imagine that swami needs a test config for its patch : https://review.openstack.org/#/c/143203/ 15:37:48 s/its/his 15:38:12 matrohon: Yeah not sure how much people are testing actual connectivity... 15:38:43 pc_m: pong but in a meeting 15:39:14 markmcclain: Yeah, we are discussing VPN on VM in VPNaaS subteam meeting. 15:39:35 markmcclain: Maybe we can discuss in Neutron channel later? Need some help. 15:40:09 #action pc_m to hook up with markmcclain on VPN testing in VMs 15:40:34 I'd like to get this working, so that we can have a VPN scenario test case (which we are lacking). 15:41:11 If anyone has gotten it to work, or has B working, please let me know your config. 15:41:35 I'll keep plugging away at A) and later on try B) again. 15:41:52 pc_m : can you share your config somewhere? 15:42:35 matrohon: For A, sure. It is very basic. One min. 15:43:34 pc_m : I mean our local.conf and the steps to provision IPSec connections 15:44:17 I would really love ta have a test like A) in the gate 15:44:39 The local.conf I have is: http://paste.openstack.org/show/155740/ 15:45:55 pc_m : do you have a script to provision IPSec connection? 15:46:59 matrohon: Mostly manual steps right now (including creating the second router/subnet/net. But I have the notes in a text file. 15:48:12 gathering together... 15:48:24 pc_m : +1 15:49:10 Here are the commands to create the connections... http://paste.openstack.org/show/155741/ 15:50:09 pc_m : cool I will try to test this. 15:50:20 Here are some notes on setting up the second router/net/subnet: http://paste.openstack.org/show/155742/ 15:50:28 pc_m : I dindn't understand why anteaya told you to add an item to infra meeting 15:50:39 I have sever other notes, some with trying to use a separate tenant. 15:51:05 matrohon: She was suggesting I ask infra at meeting on how to setup (A), I think. 15:51:11 yes 15:51:18 if you reach a dead end 15:51:29 and are tired of bouncing your skull off a brick wall 15:51:37 you are welcome to ask for guidance and direction 15:51:40 you don't have to 15:51:48 anteaya: Yeah. Will see if I can hook up with Mark. 15:51:50 if you prefer the rhythm of a bouncing skull 15:51:54 just an option 15:52:06 Maybe I can try to ask in open discussion, if I'm still stuck... 15:52:17 pc_m: was a suggestion for you 15:52:23 not a requirement or expectation 15:52:30 we don't tend to make it to open discussion 15:52:34 but you never know 15:52:48 anteaya: yeah, sure understood. Appreciate the suggestion! 15:52:54 anytime 15:53:02 * pc_m I'm looking for any way to relieve the pain 15:53:09 that is what I thought 15:53:27 #action pc_m will ask at infra meeting, if still stuck. 15:53:41 That's all I have... any other open discussion items? 15:54:47 OK. Thanks for joining in! 15:54:55 #endmeeting