15:48:19 #startmeeting bgpvpn 15:48:20 Meeting started Tue Nov 3 15:48:19 2015 UTC and is due to finish in 60 minutes. The chair is matrohon. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:48:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:48:24 The meeting name has been set to 'bgpvpn' 15:48:45 tmorin, doude, jan, pcarver : around? 15:49:14 matrohon: hi 15:49:16 we are messed up with timezone changes 15:49:22 pcarver : hi 15:49:39 hi everyone 15:49:43 we have 10min left for our meeting! 15:50:13 let's start then :) 15:50:35 not that much to announce since our face 2 face meeting last friday 15:50:59 we're pursuing polish toward a first release 15:51:07 mathieu is testing corner cases 15:51:11 see bugs on LP 15:51:55 doude, any status on whether you think you can land the contrail driver soon ? 15:52:30 not sure he's available, but he's currently working on the contrail driver 15:52:36 yes 15:52:36 timirnich_ : any idea when the ODL driver could be submitted in networking-bgpvpn rather than in networking-odl ? 15:52:44 not sure tim is here either 15:53:26 one thing about the kilo backport: a branch has been created today, so the work can be started anytime now 15:53:44 Hi all, ys I'm here 15:53:45 cool 15:53:47 "git review stable/kilo" to submit change for kilo-compatible code 15:53:50 hi tim 15:54:10 Hi tmorin 15:54:38 any idea about the ODL driver question above ? 15:54:46 tmorin, apparently it was a decision by Neutron cores to keep the ODL driver in networking-odl 15:55:39 Key argument was that also other ODL drivers are needed to make use of BGPVPN, which are all in networking-odl 15:56:06 this is not technically correct as far as I can tell 15:56:24 Hm, beyond me to tell 15:56:26 as far as I could see, the ODL BGPVPN driver only talks to the ODL API 15:57:01 it does reuse a few lines of code in networking_odl to implement and HTTP REST client, but nothing more 15:57:22 Yes but to set a VPN up you have to set up other things as well, and that could make use of the other ODL drivers if ODL is your only backend - not sure if I'm getting this right. we should follow up on this 15:57:46 that could be kept as-is (from networking_old import blabla) or rewritten to not depend on it (although this is not necessary) 15:58:44 yes, at deployment time, the BGPVPN ODL driver will depend on ODL, but does not seem to depend on components inside networking-odl like the ML2 mech driver 16:00:34 ok, we are out of time 16:00:36 Hi janscheurich 16:00:45 adrian_otto: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 16:00:46 hi jan 16:00:57 endmeeting bgpvpn 16:01:01 #endmeeting bgpvpn