16:00:42 #startmeeting interopwg 16:00:43 Meeting started Wed Oct 10 16:00:42 2018 UTC and is due to finish in 60 minutes. The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:47 The meeting name has been set to 'interopwg' 16:00:53 #chair hogepodge markvoelker 16:00:54 Current chairs: eglute hogepodge markvoelker 16:00:59 #topic agenda 16:01:06 #link https://etherpad.openstack.org/p/InteropWhistler.20 16:01:32 Hello everyone, raise your hand if you are here for interopwg meeting 16:01:55 o/ 16:02:06 Hello Mark! 16:02:15 wonder if it is just the two of us here! 16:02:31 hi 16:02:35 hogepodge was on the community meeting a few minutes ago, may still be wrapping up from that 16:02:45 ah, ok. I missed that one 16:03:02 Slides from the meeting. https://docs.google.com/presentation/d/1YBiTNVidXh0dT22ezR-pD_rganRfGjo_KE-owegkFIM/edit?usp=sharing 16:03:22 thank you hogepodge! 16:03:24 Unfortunately, I didn't capture sound from the recording. Technical jitters. 16:04:08 bad tech days happen even to the best tech. 16:04:47 #topic gate job 16:05:01 thanks for creating this. it was merged :) 16:05:30 #topic guideline 16:06:15 i think we have all the changes in place for the next guideline, is that correct? Unless you think there will be more updates for neutron, keystone or swift? 16:06:40 I think we're good. I do still need to get a patch posted for the Heat add-on 16:06:54 But the main guideline I think is in good shape. 16:07:24 markvoelker are there going to be changes for heat add on? 16:07:41 In a customer discussion, I just noticed that we don't have nova availability-zone-list ... 16:08:08 Just moving advisory->required 16:08:10 aka GET /v2/$OS_PROJECT_ID/os-availability-zone/detail 16:08:32 thanks markvoelker 16:08:41 garloff: No? https://github.com/openstack/interop/blob/master/next.json#L104 16:08:43 o/ 16:08:49 markvoelker: Ah, so that's on the list already? Good. 16:09:26 YEs, since about a year ago looks like: https://github.com/openstack/interop/blob/master/next.json#L251-L273 16:09:41 yes, it is in the 2018.02 guideline 16:09:52 Discoverability is kind of useful ... 16:10:38 garloff right, we try to cover the most used features 16:10:41 Discovery as in listing API versions/microversions, or something else? 16:10:44 I'll double-check ... 16:11:14 we still have a little time to re-score nova features if needed, but not too much time 16:11:22 Berlin is in 1 month! 16:12:15 anything else on the scoring? 16:12:41 hogepodge did you have a chance to confirm that there are no changes for keystone and swift? 16:13:05 I wonder how we passed 2017.09 then. So maybe a regression :-O 16:13:37 Oh, look at that, I'm a week off on my interop invite :-/ 16:13:51 eglute: no update 16:14:06 garloff you mean for your company? maybe an older guideline? 16:14:11 Let me verify before the week ends, I'll send up a patch if there are changes 16:14:13 hogepodge sorry. I sent out one yesterday? 16:14:24 hogepodge thanks! I assume that probably no changes 16:14:42 eglute: Yeah, I just saw nova availability-zone-list fail which made me wonder how such a basic thing might not be covered ... 16:15:28 garloff ah ok. maybe there is an unexpected feature (bug) on your side that is making it fail. 16:17:00 I'll check the tempest test -- sorry, did not want to derail the meeting 16:17:24 garloff no worries! 16:17:49 ok, anything else for the 2018.11 guideline? 16:18:48 cool, moving on then 16:18:58 #guideline frequency 16:19:39 I think we already talked some about this. What do you all think about moving to once a year for guidelines? I think we might need to take this discussion to the board as well, but most features are pretty stable now 16:20:39 +1 16:20:42 I think it's a reasonable discussion to have with the Board since we're going to be meeting with hem in person in Berlin anyway. 16:20:51 +1 16:20:52 If not a year, maybe 9 months. 16:21:55 I guess changes/innovation happen more strongly in projects not (yet?) covered by InterOp 16:22:07 ok, will take it to the board then 16:22:12 Question is how aggressivelywe want to standardize add-on guidelines ... 16:22:36 This is actually something I do think is worth bringing up to the board, if we want this WG to be OpenStack Project level or possible extend to Foundation level. 16:22:38 garloff i think you are right. i dont think there is a huge demand for add-on guidelines, but hogepodge can correct me 16:22:52 hogepodge can you elaborate? 16:23:10 hasn't been a huge demand, we're also resource constrained on developing new marks and pushing them to the marketplace 16:23:51 eglute: do we want to extend the program to things like Kata or Airship? Or at least give them the opportunity to take advantage of the process and resources 16:24:56 hogepodge oh i see. do you think they need guidelines as well? 16:25:10 I still think that fragmentation is one of the main risks for OpenStack (and Open Infra), and InterOp helps ... 16:25:25 eglute: I don't know, tbh. It's never too early to start thinking about interop though 16:26:54 hogepodge we can bring it up as discussion to the board. but would be good to know adoption rate of these other projects and whether they need things like interop guidelines. One of the reasons that openstack needs it is that it is so customizable and big. 16:27:31 yeah, I'm not strong either way, just something that's crossed my mind in the last few weeks 16:28:43 hogepodge worth looking into it, i am sure. thank you for bringing it up. 16:29:02 #topic Berlin Summit 16:29:12 do we have any interop sessions in Berlin? 16:29:33 i think I failed at submitting anything 16:29:45 Hmmm, I have not (yet?) seen any 16:30:01 Should we plan for meeting there somehow at least? 16:30:29 there is this one: #link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/21956/the-need-to-succeed-tearing-down-nfv-interoperability-walls 16:30:44 hogepodge are there working group sessions this time? do you know? 16:31:11 I think I signed us up for an interop working session 16:31:20 It's not posted to the schedule yet. I'll keep you updated 16:31:25 thank you hogepodge 16:31:49 eglute: nova list-availability-zones does a GET on av-zone/details whereas the tempest test just test GET av-zone -- thus the discrepancy ... 16:32:24 garloff ah ok 16:34:07 Regarding the rest of the meetings before the summit: i will be traveling the week before the summit, so looks like we will have only one other meeting before then. Unless you all think we need additional meeting 16:35:29 I'll actually be away the week of Oct. 24th myself... 16:36:07 ok... so how about moving meeting to October 31? 16:36:16 spooky! 16:36:27 👻 16:36:28 haha 16:37:10 so besides being a scary date, any objections? 16:37:19 I should actually be around that day so works for me (too bad we can't see everyone's Halloween costumes over IRC...) 16:37:34 I'm good with that day 16:37:38 markvoelker you will need to send us pics of your costume 16:37:43 works for me as well 16:38:08 cool, then i will send an email with the updated date 16:38:09 anything else for today? 16:38:19 Just these. https://review.openstack.org/#/c/601633/ 16:38:23 * markvoelker has an excellent "engineer who drinks too much coffee and has too many meetings" costume that he's wearing today... 16:38:29 https://review.openstack.org/#/c/608151/ 16:38:51 hogepodge yep, they are both merged! 16:38:51 Interop and Tempest are co-gating now. (non-voting on the tempest side) 16:38:54 thank you! 16:39:05 Zuul helping us not merge broken guidelines. :-) 16:39:06 is there anything else we need to do? 16:39:10 :D 16:39:24 * eglute thinks markvoelker has a brilliant costume 16:39:29 Nope, we should get notifications early if there are inconsistencies now. 16:39:48 awesome!!! 16:40:08 thank you hogepodge and everyone who worked on them 16:40:27 if there is nothing else, you have extra 20 minutes for coffee or halloween costumes. 16:40:37 see you all back here in 3 weeks! 16:40:44 thank you 16:40:48 #endmeeting