18:00:26 <bh526r> #startmeeting gluon
18:00:26 <openstack> Meeting started Wed Oct 25 18:00:26 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:29 <openstack> The meeting name has been set to 'gluon'
18:00:36 <bh526r> #topic Roll Call
18:00:39 <krenczewski> Hi Bin
18:00:40 <bh526r> #info Bin Hu
18:00:44 <bh526r> Hi Kamil
18:00:46 <krenczewski> #info Kamil Renczewski
18:01:04 <bh526r> Thank you for joining.
18:01:20 <bh526r> How is everything going?
18:01:40 <krenczewski> Struggling with setting up dev environment
18:01:55 <bh526r> what happened?
18:02:05 <jinli> #info JinLi
18:02:11 <bh526r> Hi Jin
18:02:12 <jinli> Hi bin and kamil
18:02:19 <krenczewski> I am working on integrating networking-opencontrail witn networking-bgpvpn
18:02:25 <krenczewski> Hi Jin
18:02:43 <krenczewski> but I have some troubles with devstack and ubuntu 16
18:02:58 <krenczewski> Nothing unususal
18:03:23 <bh526r> :) I see. What is the rational of "integrating" contrail with bgpvpn?
18:04:17 <krenczewski> to allow bgpvpn to be started by neutron and use contrail as a worker
18:04:51 <krenczewski> networking-bgpvpn is a Nautron api extension
18:04:55 <pcarver> is "integrating" the right word? I think "writing a new driver" might be what you mean
18:05:04 <krenczewski> probably
18:05:16 <bh526r> I see. So use contrail as a backend driver (implementation) of bgpvpn
18:05:25 <krenczewski> right
18:05:28 <pcarver> There has been a Contrail driver for networking-bgpvpn for quite a while, but the networking-opencontrail driver is a newly designed driver
18:06:06 <bh526r> so basically update the original contrail driver of bgpvpn with the new networking-opencontrail
18:06:07 <krenczewski> I'll look into that, I didn't explore this topic yet
18:06:56 <pcarver> I think it's a re-write, I'm not sure, but I don't think it uses the original driver that was written early on
18:07:21 <bh526r> Probably
18:08:02 <krenczewski> current networking-opencontrail has a very little in common with original contrail driver
18:08:03 <bh526r> So in general, the intention is to use opencontrail as backend for everything, while allow to support Neutron's bgpvpn APIs
18:08:20 <krenczewski> yes, something like that
18:08:52 <bh526r> so that is "re-write"
18:09:28 <krenczewski> Paul?
18:09:53 <bh526r> Great. Good luck with those "not unusual" hickups in setting up dev environment
18:10:28 <bh526r> #topic Update
18:10:29 <krenczewski> Thanks :-)
18:10:56 <bh526r> #info Kamil is setting up dev environment to use networking-opencontrail as backend driver of networking-bgpvpn
18:11:18 <bh526r> #info The intention is to use opencontrail as backend for everything, while allow to support Neutron's bgpvpn APIs
18:11:39 <jinli> I wrote the code according to our meeting last week. I will need to run some test case to make sure at least the front end rest api is working
18:11:54 <bh526r> #info Nothing unusual, but some hickups in environment setup
18:12:22 <jinli> I will schedule a meeting with you next week to review code and run a full test
18:12:29 <bh526r> #info Jin is focusing on backend Shim Layer, and working on the code
18:12:35 <bh526r> Sure
18:13:01 <bh526r> #info Jin will run some test case to make sure at least the front end rest api is working
18:13:56 <bh526r> #info Jin and Bin will meet next week to do code review and full test, if possible
18:14:27 <bh526r> Looks like business as usual.
18:14:42 <bh526r> any other update to share?
18:14:56 <jinli> that's all for me
18:15:11 <bh526r> thank you Jin and Kamil.
18:15:27 <krenczewski> Thank you
18:15:41 <jinli> thank you!
18:15:44 <bh526r> If nothing else, we can finish meeting.
18:15:52 <krenczewski> Great
18:15:53 <bh526r> #info Nothing else, meeting adjourned
18:16:13 <bh526r> feel free to hang in and chat, but meeting finished :)
18:16:21 <bh526r> #endmeeting