Monday, 2018-08-27

*** imacdonn has quit IRC01:18
*** imacdonn has joined #openstack-keystone01:18
openstackgerritwangxiyuan proposed openstack/oslo.limit master: [WIP]Add limit check func
openstackgerritwangqiang-bj proposed openstack/keystone master: fix wrong url link in release notes
*** wxy-xiyuan has joined #openstack-keystone02:20
*** wxy-xiyuan has quit IRC02:21
*** wxy-xiyuan has joined #openstack-keystone02:21
kmallocknikolla: o/ power out here.03:10
kmallocMight be 24+ hrs, just let folks know for me tomorrow03:10
*** Dinesh_Bhor has joined #openstack-keystone03:50
*** viks__ has joined #openstack-keystone03:52
*** Dinesh_Bhor has quit IRC04:00
*** Dinesh_Bhor has joined #openstack-keystone04:54
adriantkmalloc: you still about?05:06
*** gagehugo has joined #openstack-keystone05:50
vishakhawxy-xiyuan, kmalloc Regarding The bug seems invalid now as only the exceptions are getting translated not the logs according to the latest code. Pl confirm . Thanks06:26
openstackLaunchpad bug 1777671 in OpenStack Identity (keystone) "Incorrect use of translation _()" [Medium,Triaged] - Assigned to sonu (sonu-bhumca11)06:26
wxy-xiyuanvishakha: There are still some areas need to be fixed. For example:
vishakhawxy-xiyuan: Thanks. I will update a patch for these.06:41
vishakhawxy-xiyuan: Also can you pl review
wxy-xiyuanvishakha: sure, looking.06:44
*** pcaruana has joined #openstack-keystone06:49
*** dmellado has quit IRC07:00
*** dmellado has joined #openstack-keystone07:02
*** Dinesh_Bhor has quit IRC07:13
*** rcernin has quit IRC07:31
*** d0ugal has joined #openstack-keystone07:54
*** Dinesh_Bhor has joined #openstack-keystone07:55
openstackgerritwangxiyuan proposed openstack/oslo.limit master: [WIP]Add limit check func
*** josecastroleon has joined #openstack-keystone08:27
*** josecastroleon has quit IRC08:30
*** josecastroleon has joined #openstack-keystone08:42
*** Emine has joined #openstack-keystone08:53
*** Dinesh_Bhor has quit IRC09:07
*** Dinesh_Bhor has joined #openstack-keystone09:15
openstackgerritVishakha Agarwal proposed openstack/python-keystoneclient master: create() call in is wrong
openstackgerritVishakha Agarwal proposed openstack/python-keystoneclient master: create() call in is wrong
openstackgerritVishakha Agarwal proposed openstack/python-keystoneclient master: create() call in is wrong
vishakhagagehugo: waiting for your response on Pl have a look.Thanks09:52
*** sapd1 has joined #openstack-keystone10:01
*** Dinesh_Bhor has quit IRC10:08
openstackgerritVishakha Agarwal proposed openstack/keystone master: Incorrect use of translation _()
*** Dinesh_Bhor has joined #openstack-keystone10:22
*** jaosorior has joined #openstack-keystone10:25
openstackgerritVishakha Agarwal proposed openstack/keystone master: Incorrect use of translation _()
*** pcaruana has quit IRC10:32
*** pcaruana has joined #openstack-keystone10:32
*** Dinesh_Bhor has quit IRC10:58
*** nicolasbock has joined #openstack-keystone11:13
*** jroll has quit IRC11:43
*** jroll has joined #openstack-keystone11:44
*** raildo has joined #openstack-keystone11:59
*** mchlumsky has joined #openstack-keystone13:16
*** josecastroleon has quit IRC13:30
*** lbragstad has joined #openstack-keystone13:47
*** ChanServ sets mode: +o lbragstad13:47
*** Emine has quit IRC13:55
*** mchlumsky has quit IRC13:55
*** mchlumsky has joined #openstack-keystone13:57
*** raildo_ has joined #openstack-keystone14:03
*** raildo has quit IRC14:03
*** r-daneel has joined #openstack-keystone14:05
*** rmascena__ has joined #openstack-keystone14:06
*** raildo_ has quit IRC14:09
*** Emine has joined #openstack-keystone14:13
lbragstadgagehugo: is felipe going to be at the PTG?14:14
ildikovlbragstad: morning14:21
*** r-daneel_ has joined #openstack-keystone14:24
*** r-daneel has quit IRC14:24
*** r-daneel_ is now known as r-daneel14:24
lbragstadildikov: o/14:30
ildikovlbragstad: I saw the agenda for the Keystone team is up on the etherpad and the federation topic is scheduled for Thursday14:32
lbragstadildikov: aha - i was going to put that on Tuesday wasn't I?14:32
ildikovlbragstad: we will probably have discussions related to Keystone before Thursday and I'll try to get those scheduled for Wednesday as I saw that day is the most open14:32
lbragstadyeah - you're right14:32
ildikovlbragstad: we said Monday or Tuesday14:32
ildikovlbragstad: we have the next weekly call tomorrow with the Edge Computing Group and on Wednesday with StarlingX14:33
lbragstadthe tough part is that i think we're only guaranteed rooms on monday, thursday, and friday14:33
ildikovso I will sync up with them, but also wanted to ask whether you have any flexibility in your agenda in case people wouldn't be available whole week14:33
ildikovthe Edge group has a room an Tuesday and StarlingX has one for Wednesday14:34
lbragstadyeah - i think we'll have flexibility on tuesday and wednesday, it's just a matter of finding a place to visit i think?14:34
ildikovso I'm not worried about finding a place, just trying to figure out how to get everyone interested in the topic in one of those rooms :)14:34
ildikovok, I will collect feedback on preferences from other teams and get beck to you prolly on Wednesday14:35
ildikovdoes that sound good?14:35
lbragstadsure - for now i'll stage the federation discussions for tuesday14:36
ildikovok, sounds good14:36
lbragstadand then i'll keep a small window open on thursday for us to go through follow-ups if needed14:36
lbragstadthanks for catching that ildikov14:37
ildikovok, sounds good14:37
ildikovwill try to get all the Keystone related topics for that slot so we have the relevant people in the room for one slot and then we can figure out follow ups later if needed14:37
lbragstadworks for me14:38
ildikovcool, thanks much!14:38
lbragstadnot a problem, thanks for catching that14:39
*** marvin_mhg has joined #openstack-keystone14:41
gagehugolbragstad yes14:45
lbragstadgagehugo: sweet - i was wondering if he would be interested in the testing specific aspects of lines 43 - 53
gagehugolemme ping him14:47
*** felipemonteiro has joined #openstack-keystone14:52
*** markvoelker has joined #openstack-keystone14:55
gagehugofelipemonteiro o/14:55
felipemonteirogagehugo: hi14:57
lbragstadfelipemonteiro: o/ i'm working through the schedule for the PTG and curious how free you are on Monday?
felipemonteirolbradstad: not sure yet. qa one is here:
felipemonteirogmann is out on vacation atm so i don't believe we've gotten around to ironing out a schedule, so so long as i don't have to present/co-present on something i should be able to swing by15:00
lbragstadfelipemonteiro: ok - sounds good15:00
lbragstadif there is a conflict on your end, just let me know and i'll see if i can make adjustments15:00
felipemonteiroreading your schedule15:01
lbragstadbut if we're going to talk about the system scope/system role testing bits, it'd be good to have y'all around for that15:01
kmalloclbragstad: I have to miss Friday of the PTG15:01
lbragstadkmalloc: ack - thank for the heads up15:01
lbragstadright now i'm just planning on doing release recapping on friday15:01
kmallocAnd will likely need to leave early Thursday, since I have to be home Thursday night15:01
lbragstadok - if there is anything you want to have ironed out on friday then just let me know, we can discuss it during the week to15:02
lbragstadunless we need to go over other discussions, i plan to work through the stein schedule and see if we can get the roadmap squared away before we leave denver15:03
felipemonteirolbragstad: looks like wednesday is free as per schedule if monday doesn't work? should be fine then due to flexibility on both ends15:04
lbragstadfelipemonteiro: yeah - i think monday is going to be the cross-project day for us, but we should be able to meet wednesday, too15:05
lbragstadif we need to go through testing stuff specifically15:05
lbragstadkmalloc: you'll be around on monday, right?15:07
lbragstadi'd like to get line 31 written down on paper or a specification
*** r-daneel_ has joined #openstack-keystone15:17
*** r-daneel has quit IRC15:17
*** r-daneel_ is now known as r-daneel15:17
*** rmascena__ is now known as raildo15:26
*** pcaruana has quit IRC15:29
*** markvoelker has quit IRC15:36
*** nicolasbock has quit IRC15:49
*** Emine has quit IRC16:00
lbragstadnote regarding the PTG schedule - i'm only going to propose separate etherpads for larger topics16:16
lbragstadotherwise, for relatively light or quick discussions, we can just reuse the schedule etherpad16:16
lbragstadi'm hoping that will help with less jumping around and hunting down links16:16
lbragstadildikov: do you have an etherpad for keystone specific edge architecture discussions, yet?16:20
lbragstadif so - i can just link to it from our schedule, otherwise i can bootstrap one16:20
gagehugolbragstad it's not a true PTG if you don't have to click on 3+ etherpad links to get to the current topic :)16:23
ildikovlbragstad: just the overall etherpad for the Edge group16:25
lbragstadack - created one here
*** pcaruana has joined #openstack-keystone16:26
lbragstadyeah - following the links can get exhausting if there is only 10 lines in the smaller ones16:27
*** itlinux has joined #openstack-keystone16:29
ildikovlbragstad: thanks, I added the link to the main group etherpad and will move the topics to the specific one16:31
*** raildo_ has joined #openstack-keystone16:31
lbragstadildikov: sounds good, thanks!16:31
ildikovlbragstad: I agree that separate etherpads are better to capture details16:31
*** raildo has quit IRC16:32
*** jlviva-viva is now known as jlvillal16:40
*** raildo_ is now known as raildo16:41
lbragstadfyi - our specification repository appears to be broken with stestr
*** raildo has quit IRC16:48
*** raildo has joined #openstack-keystone16:48
kmalloclbragstad: that is unfortunate17:02
*** raildo_ has joined #openstack-keystone17:03
kmalloclbragstad: +2 on tht chain17:04
*** openstackgerrit has quit IRC17:04
kmallocgagehugo: we need to make it a full on hunt to find the correct etherpad. it's the new game ;)17:05
*** raildo has quit IRC17:05
*** rmascena__ has joined #openstack-keystone17:16
*** openstackgerrit has joined #openstack-keystone17:16
openstackgerritLance Bragstad proposed openstack/keystone-specs master: Repropose JWT specification for Stein
*** raildo has joined #openstack-keystone17:18
*** raildo_ has quit IRC17:18
*** rmascena__ has quit IRC17:21
*** raildo_ has joined #openstack-keystone17:22
*** raildo has quit IRC17:23
*** raildo_ has quit IRC17:28
*** raildo has joined #openstack-keystone17:40
*** r-daneel has quit IRC18:04
*** r-daneel has joined #openstack-keystone18:12
*** gyee has joined #openstack-keystone18:27
*** gyee has quit IRC18:28
*** gyee has joined #openstack-keystone18:28
* kmalloc does the happy-getting-a-new-desk dance.18:32
kmallocmy current desk(s) are falling apart.18:32
kmallocsomehow i don't think i'll have the same problem with this:18:32
lbragstadlooks solid18:37
lbragstadyou should throw a butcherblock slab on it18:41
kmallocthat is my plan18:42
kmalloci am probably going to need to buy a 1/4" steel support plate between the two legs too18:42
kmallocthe butcherblock slab i want is only 1.25" thick vs 2"18:42
openstackgerritMerged openstack/keystone-specs master: Switch to stestr
kmallocand i worry that center weight will be too much18:43
kmalloc160lbs cast iron desk.18:43
kmallocwithout top ;)18:43
lbragstadyeah, that's heavy...18:44
kmallocthe other option is a hot rolled steel top.18:44
kmallocwell other options: Steel Top, Tile(ed) Slate, Glass (gross no no no), Granite18:44
lbragstadfancy :)18:45
kmallocooh, 1/2 steel will only weigh 400lbs :P18:48
gagehugokmalloc oh my18:52
kmalloci think a 600-800 lbs desk would damage the floor (even carpet) somewhat.18:53
gagehugo++ on glass, I can never understand putting anything of value on one18:53
kmallocglass is gross to keep clean too18:53
kmallocfinger prints...18:53
gagehugoglossy plastic desktop18:53
kmalloceven worse :P18:53
kmalloci know, a 2" sheet of acrylic18:53
kmallocso it can scratch super easily AND be disgusting with fingerprints18:54
*** itlinux has quit IRC18:54
gagehugocan it randomly shatter though?18:54
kmallocyeah, it's acrylic! so you get the benefits of easy to shatter (no tensile strength) too!18:55
kmalloc2-3" thick tempered glass is unlikely to randomly shatter18:57
kmalloci've dropped 1/2" tempered glass from 3 feet before and it bounced.18:57
* gagehugo is always paranoid18:57
kmallocbut oh god, if 2" glass did go, it would be quite the explosion18:57
kmallocthere is a LOT of energy in 2" tempered glass.18:58
kmallocmaybe i should get "bullet resistent" laminated glass, you know, 4+" thick stuff :P18:58
gagehugothat might be a bit heavy19:00
*** itlinux has joined #openstack-keystone19:11
*** pcaruana has quit IRC19:13
*** itlinux has quit IRC19:16
mnaserit looks like identity:change_password was removed20:27
mnaseris there a policy that can know if a user is trying to change their own password (vs update_user)20:28
mnaser this commit made horizon start showing the edit user password field even though it doesn't allow the user to edit their password20:28
*** nicolasbock has joined #openstack-keystone20:30
*** raildo has quit IRC20:32
mnaserit does look like there is no policy enforcement on that?20:33
lbragstadi want to say we had to add it back in because someone was trying to prevent users from changing their passwords20:34
lbragstadwe have it in a bug report20:34
mnaseri was just wondering so that i know if i should make a commit to horizon to either add that policy change *or* just enforce update_user20:34
mnaseri don't spot anything here
* lbragstad digs for a bug report20:38
lbragstadthis happened in pike
openstackLaunchpad bug 1705485 in OpenStack Identity (keystone) "policy rule identity:change password is no longer needed" [Low,Fix released] - Assigned to Lance Bragstad (lbragstad)20:41
lbragstadbut we had something else happen recently related to that, too20:43
mnaserlbragstad: this should fix up the horizon side of the story then, i think20:43
lbragstadaha - yep20:44
openstackLaunchpad bug 1755874 in OpenStack Identity (keystone) "Ability to block users from changing passwords is missing in Keystone v3" [Undecided,Fix released] - Assigned to Morgan Fainberg (mdrnstm)20:44
lbragstadso - we technically added the ability for an admin to prevent a user from changing their password, but we didn't do it via policy20:45
lbragstadinstead we used resource options20:45
lbragstadso yeah, it looks like that policy is dead to horizon20:45
*** raildo has joined #openstack-keystone20:54
*** raildo has quit IRC20:54
*** r-daneel_ has joined #openstack-keystone20:57
*** r-daneel has quit IRC20:59
*** r-daneel_ is now known as r-daneel20:59
*** idlemind has joined #openstack-keystone21:04
*** markvoelker has joined #openstack-keystone21:04
*** markvoelker has quit IRC21:13
*** rcernin has joined #openstack-keystone21:51
openstackgerritGage Hugo proposed openstack/keystone master: Add details and clarify examples on casing
openstackgerritLance Bragstad proposed openstack/keystone master: Implement scope_type checking for credentials
kmallocmnaser, lbragstad: there is no way to do enforcement on password (self-service) change, so we had to use a resource option22:22
kmallocmnaser, lbragstad: you don't know what the roles for the user are at that point, and we were unable to craft the magic in a meaningful way with @protected22:23
kmallocmnaser, lbragstad: with the new RBACEnforcer, it is much much easier to do, that said, still easier to use a resource option flag22:23
*** nicolasbock has quit IRC22:39
*** nicolasbock has joined #openstack-keystone22:44
*** nicolasbock has quit IRC23:07
*** r-daneel has quit IRC23:08
*** Tahvok_ has joined #openstack-keystone23:24
*** Tahvok has quit IRC23:24
*** Tahvok_ is now known as Tahvok23:24
openstackgerritMerged openstack/keystone-specs master: Repropose capability lists to Stein
*** zul has quit IRC23:29
openstackgerritMerged openstack/keystoneauth master: Add Keystone2Keystone example

Generated by 2.15.3 by Marius Gedminas - find it at!