20:00:06 #startmeeting keystone_horizon 20:00:07 Meeting started Thu Mar 9 20:00:06 2017 UTC and is due to finish in 60 minutes. The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:11 The meeting name has been set to 'keystone_horizon' 20:00:19 o/ 20:00:31 ehlo 20:00:35 o/ 20:00:51 * lbragstad is on another call - will be multi-tasking :-/ 20:01:04 o/ 20:01:07 o/ 20:01:22 No problem, I think it'll be a quick one today, still havent had much time to get things moving 20:01:25 #link https://etherpad.openstack.org/p/keystone-horizon 20:02:08 o/ 20:02:21 Most of this is waiting on Horizon, though I might be pestering keystone for some expertise too. Spent a bunch of time last week properly wrapping my head around scopy-ness 20:02:43 I was hoping someone could offer some insight on https://review.openstack.org/#/c/339487/ 20:03:33 cmurphy noted that the issue couldnt be easily reproduced, so I was wondering if it was fixed by some of the domain handling patches that went in fairly recently, or if this is a sepatate issue 20:03:45 separate* 20:04:47 I haven't tried to repro yet 20:05:06 not sure if it's related or not 20:05:49 Yeah, a lot of Horizons policy handling was written by a madman before my time :p 20:05:57 but if domain context was being messed up, it's highly likely to have effected these tasks 20:05:57 o/ 20:06:31 Yeah, that was my thinking, and I expect rdopiera's patches may have fixed it, or at least affected it 20:07:48 The second question I had was regarding PCI-DSS 8.2.6 - there's a comment on the keystone side saying "We still need a way to express that the 401 was the result of an expired password" 20:08:25 rderose: ^^ do you know if that was resolved on the keystone side, before we start trying to use it on the Horizon side? 20:08:29 I'm not sure, but I don't think it touched any related code 20:08:33 robcresswell: not yet 20:08:50 rderose: Any relevant patches I could link to? 20:08:55 robcresswell: yeah, we still need to do this, so that you know auth was success, but password is expired 20:09:00 o/ sorry i'm late. 20:09:10 robcresswell: not yet, but I'll try to get something up soon 20:09:46 rderose: Sure no rush, it's mainly us holding things up as it is; just wanted to be able to track status accurately 20:09:53 I've made a note to wait for keystone to do that bit 20:10:06 robcresswell: cool 20:10:16 robcresswell: the other PCI stuff is ready to go 20:10:51 Awesome. I've been trying to get a couple of our easier blueprints reviewed the past week, so havent really written much code myself. 20:11:04 Should start getting some time to move things soon 20:11:26 So those are both of things I wanted to bring up 20:11:41 Any other topics for discussion? 20:12:26 I don't think i have anything 20:12:47 I've been off in the weeds 20:12:59 haha 20:13:20 No problem, we can call it early and give everyone their time back 20:13:30 woo - thanks robcresswell 20:13:34 will try to target some time on finishing is_admin_project support 20:13:43 If anyone has any concerns or discussion points please feel free to add to the etherpad 20:14:08 Things like specs that we could weigh in on, I know lbragstad has pinged me about a couple 20:14:25 Thanks everyone! 20:14:36 #endmeeting