16:00:53 <eglute> #startmeeting interopwg
16:00:54 <openstack> Meeting started Wed Oct 31 16:00:53 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:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:57 <openstack> The meeting name has been set to 'interopwg'
16:00:58 <openstack> markvoelker: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
16:01:04 <markvoelker> o/
16:01:12 <eglute> heh, perfect timing markvoelker :D
16:01:19 <eglute> #chair markvoelker hogepodge
16:01:20 <openstack> Current chairs: eglute hogepodge markvoelker
16:01:27 <eglute> #topic agenda
16:01:39 <eglute> #link https://etherpad.openstack.org/p/InteropWhistler.21
16:02:17 <eglute> anyone else here for interop meeting?
16:02:53 * markvoelker notes that Halloween is upon us and folks may be off spookin
16:03:42 * eglute has no scary costume
16:03:54 <eglute> I saw hogepodge submit a patch earlier today
16:04:28 <hogepodge> Keystone some capabilities to talk about.
16:04:53 <hogepodge> the most interesting one is token-delete, we don't have a capability for it but there is a test that arrived
16:04:54 <eglute> cool thanks hogepodge
16:04:55 <eglute> #topic time change
16:05:01 <eglute> #topic keystone
16:05:03 <eglute> thanks hogepodge
16:05:11 <eglute> #link
16:05:14 <eglute> #link https://review.openstack.org/#/c/614553/1
16:05:43 <eglute> hogepodge do you want to add that to 2018.11 guideline?
16:06:03 <eglute> we havent created it yet, so if you submit a patch with tests, i think we can still add as advisory
16:07:00 <markvoelker> Hm, I don't think any of those new capabilities met the bar though did they?  Scores are all too low.
16:07:53 <eglute> the score for identity-v3-tokens-validate got updated
16:08:04 <markvoelker> It was already included anyway though
16:08:10 <eglute> ah ok
16:08:21 <eglute> thats what i get reviewing before enough coffee
16:08:26 <eglute> thanks markvoelker and hogepodge
16:08:54 <eglute> ok, then no new capabilities for keystone to be added
16:08:57 <hogepodge> The scoring is mostly preliminary, wanted to bring it up to your attention.
16:09:24 <hogepodge> tokens-validate was in last release, so it got an update
16:09:34 <eglute> yeah, i missed that part
16:09:51 <markvoelker> Thanks...just from a quick eyeballing, seems about right to me.  Will have a closer look later.
16:09:54 <hogepodge> password update is also there, although Luz made some comments previously that it may conflict with public cloud password policies
16:10:32 <hogepodge> application credentials should be available for either the T or U release (first appeared in queens)
16:10:49 <hogepodge> so to me, token delete is the biggest question right now
16:11:24 <eglute> but, it still hasnt scored high enough, correct?
16:13:50 <hogepodge> I wasn't sure if it's used widely by tools.
16:14:07 <markvoelker> As scored now it doesn't...but it might if we called it proximate to identity-v3-tokens-create and identity-v3-tokens-validate I think
16:14:14 <hogepodge> Or about Foundational (that one could probably be switched to 1)
16:14:54 <eglute> ok, so the score could go up and we could add it as advisory
16:15:15 <hogepodge> Foundational probably should be 1, since it's pretty important to be able to revoke compromised tokens.
16:15:47 <eglute> right
16:16:10 <eglute> i think we can update to 1 and include it as advisory
16:16:33 <markvoelker> Makes sense to me
16:16:41 <hogepodge> I just sent the scoring up, and can add a capability after the meeting.
16:16:49 <hogepodge> Seems like a good thing to get into advisory
16:17:37 <eglute> cool, lets do it
16:17:41 <eglute> thank you hogepodge
16:17:47 <hogepodge> thanks, sorry for taking so long
16:18:54 <eglute> np. i think everyone is super busy with a lot of other things
16:19:10 <eglute> #topic guideline 2018.11
16:19:22 <eglute> do we need to review anything else for 2018.11?
16:19:43 <hogepodge> Just keystone patch coming in later today.
16:19:47 <eglute> ok,
16:19:59 <hogepodge> There's also a keystone capability that has one flagged test
16:19:59 <eglute> then we need to create the actual patch for 2018.11
16:20:27 <hogepodge> When we create the patch, we need to update the gate to include 2018.11 in the consistency checks
16:20:35 <markvoelker> One other outstanding item is a patch moving the heat stuff from advisory->required for the heat add-on.  I keep forgetting to actually get that done. =p  Will fix.
16:20:54 <eglute> ok thank you hogepodge and markvoelker
16:21:45 <eglute> anything else on the guideline?
16:22:54 <eglute> #topic meeting time
16:22:59 <eglute> I am traveling next week, and after that we will meet at the summit
16:23:40 <markvoelker> Speaking of: it looks like I'll miss a chunk of the BoD meeting due to when my flight gets in.  Is everyone else going to be there?
16:24:01 <hogepodge> I'll be at the BoD meeting, arriving on Sunday.
16:24:01 <eglute> Yes, i am planning on getting there on Sunday
16:25:02 <eglute> so the next meeting will be in a month or so, though i would propose no meetings for the rest of the year unless we have business to take care of
16:25:23 <hogepodge> +1
16:25:30 <markvoelker> works for me
16:25:51 <hogepodge> Between post-summit vacation and holiday, KubeCon, and end of year holidays, I'm probably booked up and distracted
16:25:58 <eglute> cool, i will send an email at some point to that regard
16:26:13 <eglute> yeah, i need to take a lot of time off to use up my time off
16:26:57 <eglute> there will also be the time change, is it ok to keep it at UTC 16:00? we can also revisit next year
16:27:34 <markvoelker> I think I'm good with keeping 16:00, but can do either.
16:27:59 <eglute> cool, will revisit next year to make sure
16:28:01 <hogepodge> I should be fine
16:28:09 <eglute> #topic board report
16:28:53 <eglute> I will start working on the board report today and send you the link to add anything that is needed. Since I will be traveling, I will try to get most of it done this week
16:28:58 <eglute> so i will appreciate any help you can provide :)
16:29:23 <hogepodge> +1
16:29:53 <eglute> #topic summit
16:30:04 <eglute> we have a session at the summit, thanks hogepodge!
16:30:54 <eglute> i created etherpad: #link https://etherpad.openstack.org/p/InteropBerlin2018
16:30:55 <eglute> please add topics
16:31:25 <eglute> anything else for today?
16:31:42 <hogepodge> Yes
16:32:12 <eglute> go ahead hogepodge
16:32:33 <garloff> Looking fwd to seeing you all in Berlin :-)
16:32:53 <eglute> same here garloff! Thanks for hosting us for the board meeting!
16:33:03 <hogepodge> I’ll be meeting with a Chinese agency that wants to start setting standards for public clouds in a China. I’ll be encouraging adoption of Interop guidelines and contributions
16:33:15 <eglute> hogepodge wow thats huge
16:33:27 <hogepodge> It’s all preliminary
16:34:57 <eglute> hogepodge cool, are they going to be attending the berlin summit? we can setup a meeting if they are
16:34:58 <hogepodge> Our new hire who is based in China, Horace, is the lead on those conversations
16:35:12 <garloff> hogepodge: Let's make sure we'll end up with one worldwide standard ...
16:35:15 <hogepodge> We’re working on setting up the meetings
16:35:22 <eglute> hogepodge sounds good!
16:35:46 <eglute> garloff yes, for openstack, there are only our interop standards
16:37:32 <garloff> good -- if they want to go beyond what we're currently standardizing, we should try to adopt their needs as opposed to having something that's then only adopted in China ...
16:37:46 <garloff> That's what I was trying to express.
16:37:51 <garloff> Anyhow, good discussion for Berlin
16:38:23 <eglute> garloff very true!
16:38:27 <eglute> anything else for today?
16:38:38 <hogepodge> garloff: yes, that's the goal, to adopt InteropWG guidelines as a baseline and contribute to the activities of the WG
16:41:04 <hogepodge> thanks everybody!
16:41:24 <eglute> alright, if nothing else, danke schön!
16:41:38 <eglute> #endmeeting