15:03:12 #startmeeting bgpvpn 15:03:12 Meeting started Tue May 17 15:03:12 2016 UTC and is due to finish in 60 minutes. The chair is tmorin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:16 The meeting name has been set to 'bgpvpn' 15:03:32 hi doude, enikher, matrohon, timirnich 15:03:36 hi 15:03:52 #info Nikolas Hermanns 15:03:54 hi 15:03:58 hi 15:04:01 hey 15:05:22 enikher: I've proposed Jan and Georg to join as well... do you know if they may come ? 15:05:42 I will contact them internally 15:05:52 enikher: k, thanks 15:07:31 georg will come, jan does not have time. 15:07:55 ok 15:08:00 let's start 15:08:58 for the agenda, I think we can discuss: Neutron stadium expected implications on bgpvpn (let's be shorter than last week), mitaka release, doc update, ongoing work on API new features 15:09:03 anything else you see ? 15:09:32 fine gor me 15:10:17 #topic Neutron stadium expected implications on bgpvpn 15:10:30 this is about https://review.openstack.org/#/c/312199/ 15:10:53 a clarification has been brought up: the API we have now for BGPVPN would be accepted as a starting point 15:11:03 no need to restart from scratch 15:11:53 further evolution will happen via neutron-api/neutron-lib/neutron-specs (details not settled yet), but in a way which would have net-bgpvpn core have +2 rights 15:12:04 +w rights would remain at the end of Neutron's cores 15:12:48 comments ? 15:13:24 as far as I can tell, I think staying in the stadium will work out fine 15:14:27 matrohon, enikher, doude: any comment ? 15:14:34 I am reading :-) 15:14:46 nope, I'm fine with that 15:14:53 ok 15:15:39 I am as well 15:16:03 I'm in favor of APIs in general and BGPVPN APIs in particular being "part of Neutron" whereas backend implementations don't need to be. I think the dicussion is headed in an acceptable direction. 15:16:27 networking APIs, I mean. Obviously not all APIs. 15:16:31 pcarver: +1 15:17:04 ok 15:17:09 next topic ? 15:17:47 #topic mitaka release 15:17:53 our mitaka release is pending 15:18:01 the request to release has been waiting for some time now 15:18:11 * tmorin trying to find a link 15:18:27 https://bugs.launchpad.net/bgpvpn/+bug/1576384 15:18:28 Launchpad bug 1576384 in neutron "Request Mitaka release for networking-bgpvpn" [Undecided,Confirmed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka) 15:19:03 ihrachys is assigned to it, but must have been busy post-Austin 15:19:33 hm, I thought it's merged?.. lemme check 15:19:46 oh it's 4.0.0 15:19:50 ihrachys: 3.0.1 was released 15:19:51 I mixed things I guess. 15:19:54 ihrachys: yes 15:19:59 lemme handle that now 15:20:15 ok, cool! :) 15:20:44 having a stable/mitaka branch will be handy 15:21:31 next topic ? 15:22:34 #topic Documentation 15:22:51 I've pushed minor doc updates today 15:23:09 base Nuage networks driver info 15:23:15 and base install/config information 15:23:33 pcarver: any update on what you mentioned last week ? 15:24:23 tmorin: Do you mean API docs? I'm still reading about Swagger and looking at examples. 15:24:37 pcarver: yes, that's what I meant 15:24:39 pcarver: ok 15:24:52 I think I've got the general idea but haven't started on BGPVPN APIs yet. 15:25:17 I need to figure out the toolchain first. 15:25:31 There seem to be a few different options. 15:26:18 ok 15:26:19 I haven't found a definitive step-by-step one way to do it guide, but there is a lot of info available so I should be fine 15:26:50 It's basically a YAML based syntax with tools to generate the dynamic web pages 15:26:52 don't hesitate to ping #openstack-net-bgpvpn if you think that a discussion between available options can be useful 15:28:00 pcarver: thanks for the update 15:28:03 next topic ? 15:28:43 #topic "advanced" routing-related new API features 15:29:16 we had dicussed static routes, aggregation, Port associations in Austin 15:29:49 Georg Kunz pinged me and Jan to proceed where our discussions had stopped 15:30:02 georgk1: is it you ^^ ? 15:30:09 yes, it is me 15:30:13 :) 15:30:28 I was basically just courious to find out about your plans on port association 15:30:33 the result of the restarted discussion is a summary of the things we want to address in this pad 15:30:36 #link https://etherpad.openstack.org/p/bgpvpn_advanced_features 15:31:12 the next step is to move from these use case to a list of primitives to add to the API to address the use cases 15:32:21 doude, enikher: don't hesitate to have a look, you may already have an idea of how these use cases may map to the controllers you know better 15:33:31 I will discuss this with Jan and come back to you Thomas 15:33:38 ok ! 15:33:56 i'll update the static routes and port association blueprints with a link to this pad 15:33:59 tmorin: we will have a meeting the OPNFV NetReady project at 6PM to discuss L3VPN use cases 15:34:12 ah, good 15:34:21 except I won't be able to attend 15:34:32 ok, that a shame 15:34:39 do you have a link on where the discuss would be archived 15:34:53 hopefully its not gomeeting only ? 15:35:03 well.... mostly, i am afraid 15:35:16 i´ll try to take some notes 15:35:41 and eventually we are working on a document 15:35:56 so that could be something I´ll send to you later 15:36:07 I'll appreciate any doc/link you have, to read tomoroow 15:36:09 yes :) 15:36:13 anyway, I would be nice to get your input at some point 15:36:29 ok, great 15:37:38 yes, it's good if everyone around net-bgpvpn can comment 15:37:40 thanks 15:37:44 next topic ? 15:38:00 #topic open discuss 15:38:49 one thing I wanted to announce: we have work in progress on an Horizon plugin for the BGPVPN API, hopefully ready in a few weeks 15:40:13 tmorin: https://review.openstack.org/317582 the release request 15:40:21 tmorin: tag and branch are already in your repo 15:41:05 ihrachys: thanks a lot! 15:42:45 do we have anything else to discuss ? 15:42:55 doude, enikher, matrohon, pcarver ? 15:43:08 not for me 15:43:15 nop 15:43:29 Horizon +1 that is cool! 15:44:19 I don't have anything else 15:44:30 nothing for me 15:44:44 ok, we're done then! 15:44:54 thanks everyone... 15:44:59 #endmeeting