15:29:00 #startmeeting bgpvpn 15:29:01 Meeting started Tue Jul 11 15:29:00 2017 UTC and is due to finish in 60 minutes. The chair is tmorin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:29:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:29:05 The meeting name has been set to 'bgpvpn' 15:30:11 #topic rollcall 15:30:16 let's see who's around today 15:30:58 hi 15:31:24 hi paul 15:31:46 maybe doude ? bobmel ? 15:31:56 I know matrohon is on holidays 15:32:09 hi 15:34:37 hey doude 15:34:41 ok let's start 15:34:49 #topic agenda 15:34:55 here is what I see for today 15:35:07 a) bgpvpn-routes-control extension work in progress 15:35:15 b) driver feature support matrix 15:35:23 c) bug review 15:35:33 anything else ? 15:35:55 ah yes: d) new tempest tests 15:36:39 #topic bgpvpn-routes-control extension work in progress 15:37:05 while implementing the framework and DB for the bgpvpn-routes-control extension, I found out about issuess in the API definition in neutron-lib 15:37:27 https://review.openstack.org/#/c/481088/ is in flight to fix these, mostly landed now 15:38:06 the change with the framework/db work for port associations is here: https://review.openstack.org/#/c/481125/ 15:38:12 I think it's fairly complete 15:38:37 not passing tempest tests because we'll need a neutron-lib release with our API extension first 15:39:12 reviews are welcome, in particular on the driver hooks (doude, if you want to have a look) 15:40:13 that said, even with this work, given that I'll be off until end of July starting next Friday, I don't plan to try to land the bgpvpn-routes-control extension for Pike 15:40:27 comments ? 15:40:48 tmorin: ok 15:41:12 thanks! 15:42:55 #topic driver feature support matrix 15:43:17 pcarver has pushed a change to add a driver feature matrix to the doc: 15:43:40 thanks pcarver ! 15:43:44 #link https://review.openstack.org/#/c/482357/ 15:43:56 discussion ongoing on the content 15:44:05 it will definitly be a good addition 15:44:25 this also was the trigger to identifiy that we need updated doc on opencontrail and odl drivers 15:44:46 to document that their v1 drivers are obsolete, and provide minimal proper info on how to use the non-obsolete ones 15:45:00 I'll provide an update. I didn't actually realize that there was a new opencontrail driver 15:45:27 it's in opencontrail repo 15:45:28 doude: ok to push a change to update the doc for opencontrail ? 15:46:54 yes tmorin. But i also think to push a patch to completely remove the old driver 15:47:45 I think is better to remove it now as nobody use it for the moment and only let the active one 15:48:13 I agree we should remove the old one but maybe there should be a deprecation notice first, then a removal as a second step 15:48:21 doude: it depends whether or not you want to provide a driver for contrail < 4 15:48:35 doude: wouldn't this be a reason to /not/ remove it yet ? 15:48:55 doude: perhaps instead have it raise a runtime warning that it is obsolete 15:49:28 the v1 code was more a PoC than a release, it does not use the correct way to se RT on VRF 15:50:28 we can deprecate it if you prefer 15:50:42 what will be the deprecation schedule? 15:52:33 doude: I think it has to be determined consistently with the deprecation schedule for the last version of opencontrail that does not have what is required by the v2 driver (3.2 ?) 15:52:33 I guess we don't know for sure who's using anything, but I suspect you're right that nobody is really using it in production so a short time should be fine. 15:53:07 pcarver: ok 15:53:09 I'm just thinking maybe update with a pointer to the replacement and then a month or two later remove it completely. 15:53:52 tmorin: no it's not recommended to use the v1 with contrail release < 4 as there is no migration path to move to the new driver 15:54:26 doude: then a "short" deprecation schedule would make sene 15:54:27 sense 15:54:36 pcarver: I don't think we can work with month step but with release step 15:54:57 pcarver: yes 15:55:15 "will be removed in Queens" would be reasonable I think 15:55:31 tmorin: sure, that's fine 15:55:35 ok 15:55:38 ok, next topic ? 15:55:48 #topic bug review 15:55:50 the 15:56:16 there were/are a few things needed for the horizon dashboard, to adapt to recent horizon changes 15:56:24 some fixes have merged (cedric's work) 15:56:32 and some others are in flights 15:57:12 #topic new tempest tests 15:57:21 some new tempest tests are beeing refined 15:57:32 I think they should soon be ready for merging 15:58:07 #link https://review.openstack.org/#/c/480142/ 15:58:42 #topic open discuss 15:58:45 anything else ? 15:58:49 2min left :) 15:58:54 doude ? pcarver ? 15:59:05 ok for me 15:59:08 nothing else for me 15:59:30 ah yes, one more thing: no meeting next week 15:59:48 two weeks for now: I'm not sure (I'll be off, matrohon may be back) 15:59:54 three weeks from now: ditto 16:00:02 thanks folks! 16:00:20 leaving the floor for next meeting... 16:00:21 bye 16:00:26 #endmeeting