16:01:32 #startmeeting interopwg 16:01:33 Meeting started Wed Dec 6 16:01:32 2017 UTC and is due to finish in 60 minutes. The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:37 The meeting name has been set to 'interopwg' 16:01:55 o/ 16:01:59 o/ 16:02:02 hi 16:02:10 #link https://etherpad.openstack.org/p/InteropWhistler.1 Today's etherppd 16:02:30 Hmm...which looks oddly sparse. One moment. 16:03:51 Ok, we have a pretty short agenda today as we noted that multiple folks would be out this week 16:04:00 (Kubecon, life in general, etc) 16:04:35 MOstly we just wanted to hit on a couple of points. First up: wrapping up 2018.02 16:04:43 #topic 2018.02 Guideline 16:05:12 I spent some time last week picking through recent updates to Neutron and seeing what was out there in terms of adoption 16:05:42 I think that for this time around, we'll probably not propose anything new 16:06:08 However, LBaaS might actually be worth looking at once we get it sorted in the vertical programs...adoption seems pretty high these days 16:06:35 (this puts us right back in the "which implementation" spot, hence why I think we tackle it on the vertical side first and see how that goes) 16:07:37 Any other comments on Neutron? 16:07:45 (or on 2018.02 generally?) 16:08:03 not from my side 16:08:23 nope! 16:08:38 Ok, easy enough 16:09:30 #topic add-on programs 16:09:55 Not a whole lot to talk about here this week either with the small audience. First up: NFV 16:11:20 We had a little conversation last week about scenario tests that might be useful here. georgk, anything particularly new to discuss there? 16:11:40 I pushed an update after Luz´s review 16:11:58 more reviews are appreciated. 16:12:10 Oh, drat...I totally missed that somehow 16:12:18 I'll have a look at it today, thanks! 16:12:20 I´ll have a chat with the networking-bgp team tomorrow 16:12:30 * mguiney will check out 16:12:58 to clarify what we need in terms of tests and to get input for the scoring 16:13:27 one question: this seems to depend on https://review.openstack.org/#/c/521602/ 16:13:48 any updates on this? 16:14:04 Yeah, I was going to bring that up later in the agenda so let's talk about it now 16:14:17 #link https://review.openstack.org/#/c/521602/ Clarify testing for interop programs 16:14:46 So there's been a little more discussion on the patch, but it seems a little stuck still. 16:15:17 For the moment, I think we can proceed without worrying about it too much. Basically: let's identify useful tests regardless of their current location. 16:15:39 If the TC decides they want things to live in a particular place later, that's ok--we can work on moving them then. 16:15:59 I do not think the TC would want the discussion around this patch to stall forward progress on interop programs. =) 16:16:13 ok. technically refstack can pull in everything transparently due to the plugin mechanism? 16:16:20 Pretty much, yes. 16:16:24 ok, cool 16:17:45 I would also encourage folks with opinions or comments (or comments on the existing comments) to chime in...the TC have been asking for more input on the matter 16:18:36 On a somewhat related note, Designate is now a tc:approved-release project in case folks didn't see it 16:18:51 #link https://review.openstack.org/#/c/521587/ Add designate to the tc:approved-release tag 16:19:17 thanks for the hint 16:20:21 Ok, getting back to the NFV vertical patch just for the meeting notes... 16:20:28 #link https://review.openstack.org/#/c/519732/ First attempt at scoring trunk ports for NFV vertical 16:21:25 I'll have a look at this one in a bit. For the question about which Tempest SHA to use: I generally do a test run and make sure the current HEAD revision is working, then record that. 16:21:48 We can update it to be slightly more current after retesting once we get closer to finalizing the guideline 16:21:52 ok, so we pin it to that hash 16:22:04 ok 16:22:16 Correct. Bascially the SHA we put in here is a "known good" version at the time the Guideline is published. 16:22:38 Folks are generally encouraged to use recent Tempests and many just use the current HEAD revision since it may contain bugfixes 16:22:52 But if there's a problem, this SHA is a known-good point of reference. 16:23:03 (e.g. newer revs can introduce bugs too) 16:23:33 Ok, anything else on this todaY? 16:23:47 one thing 16:24:06 last week you mentioned that networking-bgp would be more ¨controversal¨ 16:24:14 I was wondering abot why 16:26:30 Basically deployment and product inclusion I think. I also recall some questions around what was really needed (e.g. something like bagpipe vs networking-bpb, etc) 16:27:47 ok, from a NFV perspective, I think this feature is very well deployed. I even participated in interop testing between Ericsson, Cisco, Juniper and Nokia 16:28:25 Hopefully less controversial than I'd feared then. =) 16:28:28 I am more worried about it not meeting other criteria such as test coverage. But I´ll include that in the scoring 16:28:34 ok, thanks 16:28:35 ++ 16:29:08 Ok, short agenda today, anything else we need to talk about? 16:29:11 #topic open floor 16:30:46 Hearing nothing, I guess we get some time back in our workdays today. =) Thanks folks! 16:31:00 #endmeeting