Wednesday, 2015-10-07

*** sdake has joined #openstack-keystone00:00
*** jbell8 has joined #openstack-keystone00:02
*** btully has quit IRC00:02
*** jbell8 has quit IRC00:03
*** dsirrine has quit IRC00:03
*** geoffarn_ has quit IRC00:03
*** geoffarnold has joined #openstack-keystone00:04
*** jbell8 has joined #openstack-keystone00:04
*** btully has joined #openstack-keystone00:08
*** woodster_ has quit IRC00:09
*** dims_ has quit IRC00:13
*** dims_ has joined #openstack-keystone00:14
*** dsirrine has joined #openstack-keystone00:15
*** _cjones_ has quit IRC00:16
openstackgerritOpenStack Proposal Bot proposed openstack/keystoneauth: Updated from global requirements  https://review.openstack.org/23046400:17
*** jbell8 has quit IRC00:17
*** darrenc_afk is now known as darrenc00:18
*** dims_ has quit IRC00:19
*** ayoung has joined #openstack-keystone00:19
*** ChanServ sets mode: +v ayoung00:19
*** shadower has quit IRC00:23
*** shadower has joined #openstack-keystone00:23
*** dims_ has joined #openstack-keystone00:25
*** geoffarn_ has joined #openstack-keystone00:25
*** geoffarnold has quit IRC00:25
*** su_zhang has quit IRC00:26
*** dims_ has quit IRC00:26
*** dims_ has joined #openstack-keystone00:26
*** lhcheng_ has quit IRC00:27
*** roxanagh_ has joined #openstack-keystone00:27
*** roxanagh_ has quit IRC00:36
*** geoffarn_ has quit IRC00:46
*** geoffarnold has joined #openstack-keystone00:47
*** su_zhang has joined #openstack-keystone00:47
*** jaosorior has quit IRC00:53
*** jaosorior has joined #openstack-keystone00:54
*** browne has quit IRC00:57
*** gyee has quit IRC00:58
*** dsirrine has quit IRC00:59
openstackgerritSam Leong proposed openstack/keystone: add initiator to v2 calls for additional auditing  https://review.openstack.org/23112301:04
openstackgerritSam Leong proposed openstack/keystone: add initiator to v2 calls for additional auditing  https://review.openstack.org/23112301:05
*** su_zhang has quit IRC01:07
*** geoffarn_ has joined #openstack-keystone01:08
*** stevemar_ has quit IRC01:11
*** geoffarnold has quit IRC01:12
*** topol has joined #openstack-keystone01:19
*** ChanServ sets mode: +v topol01:19
openstackgerritMerged openstack/keystone: Correct docstrings  https://review.openstack.org/22699601:21
*** richm has joined #openstack-keystone01:22
*** csoukup has joined #openstack-keystone01:23
*** topol has quit IRC01:23
ayoungI don't know how to parse this. http://finance.yahoo.com/news/rackspace-announces-aws-managed-offerings-130000686.html?.tsrc=applewf01:23
*** markvoelker has quit IRC01:27
*** csoukup has quit IRC01:27
*** geoffarn_ has quit IRC01:29
*** geoffarnold has joined #openstack-keystone01:29
lifelessayoung: seems straight forward to me01:31
openstackgerritOpenStack Proposal Bot proposed openstack/keystone: Updated from global requirements  https://review.openstack.org/23056401:42
ayounglifeless, Good.  You can explain it to me01:47
lifelessayoung: rackspace are getting paid to look after aws instances by their customers01:48
lifelessayoung: and getting a cut on the revenue of those same instances01:48
ayounglifeless, becasue Amazon can't or won't do it themselves?01:48
lifelessayoung: I don't know /why/01:49
lifelessayoung: I imagine rackspace saw enough demand from their users for things only available on AWS01:49
lifelessayoung: e.g. third party services01:49
ayounglifeless, I smells like SuSE/Microsoft to me.01:49
lifelessayoung: yeah, I don't super like the smell of it either01:49
*** geoffarnold has quit IRC01:50
*** geoffarnold has joined #openstack-keystone01:51
*** sdake has quit IRC01:53
*** sdake has joined #openstack-keystone01:56
*** fawadkhaliq has joined #openstack-keystone01:58
*** fawadkhaliq has quit IRC01:59
*** stevemar_ has joined #openstack-keystone02:00
*** ChanServ sets mode: +o stevemar_02:00
*** jbell8 has joined #openstack-keystone02:10
*** geoffarnold has quit IRC02:11
*** geoffarnold has joined #openstack-keystone02:12
*** jbell8 has quit IRC02:13
*** jbell8 has joined #openstack-keystone02:14
*** ayoung has quit IRC02:14
*** woodster_ has joined #openstack-keystone02:14
*** lhcheng has joined #openstack-keystone02:19
*** ChanServ sets mode: +v lhcheng02:19
*** sdake has quit IRC02:19
*** sdake_ has joined #openstack-keystone02:22
*** topol has joined #openstack-keystone02:24
*** ChanServ sets mode: +v topol02:24
*** browne has joined #openstack-keystone02:31
*** geoffarnold has quit IRC02:33
*** geoffarnold has joined #openstack-keystone02:33
*** ngupta has joined #openstack-keystone02:34
stevemar_mordred: so about https://pypi.python.org/pypi/keystoneauth102:35
stevemar_and removing https://pypi.python.org/pypi/keystoneauth02:35
stevemar_i'm a bit confused here, what repo do i clone to alter the README of https://pypi.python.org/pypi/keystoneauth02:35
stevemar_since it looks like they are both coming from https://github.com/openstack/keystoneauth02:36
*** richm has quit IRC02:36
*** _cjones_ has joined #openstack-keystone02:43
*** dikonoor has joined #openstack-keystone02:43
*** btully has quit IRC02:44
*** _cjones_ has quit IRC02:45
*** _cjones_ has joined #openstack-keystone02:46
*** darrenc is now known as darrenc_afk02:53
*** sdake_ is now known as sdake02:54
*** zzzeek has quit IRC02:55
stevemar_lhcheng: issued a quick refresh for the osc plugin doc02:55
*** geoffarn_ has joined #openstack-keystone02:55
lhchengcool02:56
lhchengstevemar_: when is the planned next release of OSC?02:56
lhchengstevemar_: thanks for documenting the plugins, that would be helpful02:58
stevemar_lhcheng: whenever you want it to me big guy02:58
lhchengstevemar_: hah02:58
lhchengstevemar_: I suppose when we get all the glance and swift related changes?02:58
stevemar_lhcheng: i'm of the opinion to do small releases and often02:58
stevemar_lhcheng: normally we do once a month, but i could be convinced to do it sooner02:59
stevemar_that sounds like a good plan02:59
*** geoffarnold has quit IRC02:59
stevemar_i'd also like to fix the issue that zigo brought up02:59
stevemar_but i think that's more of a cliff issue02:59
lhchengstevemar_: how about the password thing?03:00
lhchengstevemar_: that's probably good to have as well03:00
lhchengstevemar_: do we have a library for masking/scraping confidential values?03:01
lhchengI know we do it in KSC, but I think we manually performed the hashing of the auth_token03:03
*** csoukup has joined #openstack-keystone03:05
stevemar_ohhh right password03:05
stevemar_hmmm03:05
stevemar_do we have a bug for that03:05
stevemar_i'm going to forget it otherwise03:05
stevemar_lhcheng: ugh, i knew non-ascii characters wont work03:06
*** c_soukup has joined #openstack-keystone03:06
lhchengpm'd you the bug03:06
lhchengstevemar_: non-ascii is a known issue?03:06
stevemar_lhcheng: not known-issue, but when i was coding it up, i thought 'you know, i get non-ascii characters won't work here'03:07
stevemar_bet*03:07
*** csoukup has quit IRC03:10
lhchengah that was for the property set command.. I didn't expect that even "create container" would fail03:10
lhchengusing non-ascii works for "user create"03:10
lhchengstevemar_: the non-ascii issue might be local to the swift commands, I'll take a look at it.03:11
lhchengI just logged it so I won't forget03:11
*** geoffarn_ has quit IRC03:16
*** geoffarnold has joined #openstack-keystone03:16
*** markvoelker has joined #openstack-keystone03:19
stevemar_lhcheng: you thinking swift cause it's in URLs?03:21
*** links has joined #openstack-keystone03:21
lhchengstevemar_: not sure yet, have to dig around.03:22
lhchengplanning to work on the password thingy first03:22
lhchengthen try to get the non-ascii character to work on swift commands03:22
stevemar_lhcheng: cool cool, i'm hoping to fix zigo's issue, let me log that one03:22
openstackgerritMerged openstack/keystone: Cleanup _build_federated_info  https://review.openstack.org/22065803:23
openstackgerritMerged openstack/keystone: Add LimitRequestBody to sample httpd config  https://review.openstack.org/20820803:23
openstackgerritMerged openstack/keystone: Unit tests for fernet validate_v3_token  https://review.openstack.org/22655703:23
*** markvoelker_ has joined #openstack-keystone03:23
openstackgerritMerged openstack/keystone: Remove unused get_user_projects()  https://review.openstack.org/22936903:23
lhchenghorizon got a lot of report related to escaping of the swift url, due to special characters, so I do think it would be valuable to make it more for swift commands in OSC too03:23
lhchengmake it more -> make it work03:23
*** markvoelker has quit IRC03:25
stevemar_lhcheng: 73 bugs for osc, we need a bug squash day >.<03:25
*** ngupta has quit IRC03:27
*** dikonoor has quit IRC03:27
*** btully has joined #openstack-keystone03:29
openstackgerritMerged openstack/keystone: Add test case passing is_domain flag as False  https://review.openstack.org/22954903:29
*** jbonjean has quit IRC03:32
*** jbonjean has joined #openstack-keystone03:32
*** markvoelker has joined #openstack-keystone03:33
*** markvoelker has quit IRC03:33
*** markvoelker_ has quit IRC03:33
*** btully has quit IRC03:33
*** sdake has quit IRC03:37
*** geoffarnold has quit IRC03:37
*** sdake has joined #openstack-keystone03:37
*** geoffarnold has joined #openstack-keystone03:37
mordredstevemar_: I have a patch03:41
*** mylu has joined #openstack-keystone03:43
*** topol has quit IRC03:46
*** mylu has quit IRC03:48
*** darrenc_afk is now known as darrenc03:48
stevemar_mordred: hook it up03:49
stevemar_lhcheng: thoughts on https://bugs.launchpad.net/python-openstackclient/+bug/1476772 i think we can close this one out03:50
openstackLaunchpad bug 1476772 in python-openstackclient "image set v2 uses visibility option instead of public and private" [Undecided,In progress] - Assigned to Sean Perry (sean-perry-a)03:50
*** jbell8 has quit IRC03:55
*** jbell8 has joined #openstack-keystone03:55
*** jbell8 has quit IRC03:58
lhchengstevemar_: yup, I added the link to the patch that resolved the issue reported03:58
*** jbell8 has joined #openstack-keystone03:58
*** geoffarn_ has joined #openstack-keystone03:58
stevemar_lhcheng: i closed a bunch of bugs as invalid03:59
lhcheng73 bugs wow, we need to recruit more OSC contributors03:59
*** geoffarnold has quit IRC03:59
lhchengstevemar_: I also submitted a patch for the password masking03:59
* lhcheng stevemar the "bug squasher"04:01
lhcheng\o/04:01
stevemar_lhcheng: down to 67!04:02
lhchengyay04:02
*** hrou has quit IRC04:03
stevemar_lhcheng: good patch, provided a suggestion04:06
lhchenggood catch04:07
lhchengI might be able to test at least the admin_token04:08
lhchengthanks for the review04:08
stevemar_np04:08
stevemar_thanks for the patch04:09
*** lhcheng has quit IRC04:09
*** fawadkhaliq has joined #openstack-keystone04:10
*** fawadk has joined #openstack-keystone04:11
*** fawadkhaliq has quit IRC04:15
*** su_zhang has joined #openstack-keystone04:17
*** jbonjean has quit IRC04:17
*** fawadkhaliq has joined #openstack-keystone04:18
*** jbonjean has joined #openstack-keystone04:18
*** jbonjean has quit IRC04:18
*** jbonjean has joined #openstack-keystone04:18
*** woodster_ has quit IRC04:19
*** fawadk has quit IRC04:19
*** geoffarn_ has quit IRC04:19
*** geoffarnold has joined #openstack-keystone04:20
mordredstevemar_: done04:27
mordredstevemar_: I did not upload a patch anywhere - I just upload the stub package04:28
mordredstevemar_: because meh04:28
*** lhcheng has joined #openstack-keystone04:28
*** ChanServ sets mode: +v lhcheng04:28
mordredstevemar_: https://pypi.python.org/pypi/keystoneauth should make you happy now04:28
stevemar_mordred: looking04:31
stevemar_mordred: looks good to me!04:31
mordredmordred@camelot:~$ crap/bin/pip install keystoneauth04:32
mordredCollecting keystoneauth04:32
mordred  Downloading keystoneauth-0.5.0-py2.py3-none-any.whl04:32
mordredCollecting keystoneauth1>=1.0.0 (from keystoneauth)04:32
mordred:)04:32
stevemar_a link to the new package would have been nice, but beggards can't be choosers04:32
stevemar_oh shit04:32
stevemar_how'd you do that magic04:32
mordredI have magic man04:32
stevemar_requirements change?04:32
mordredyup04:32
stevemar_i see "sdirector" is there now04:33
stevemar_i assume that is the source of your magic04:33
mordredyup04:33
mordred:)04:33
stevemar_dolphm: https://pypi.python.org/pypi/keystoneauth should make you happy now04:33
stevemar_this deserves a tweet04:34
*** jbonjean has quit IRC04:34
*** topol has joined #openstack-keystone04:34
*** ChanServ sets mode: +v topol04:34
*** jbonjean has joined #openstack-keystone04:34
*** jaosorior has quit IRC04:34
*** jaosorior has joined #openstack-keystone04:34
*** miyagishi_t has joined #openstack-keystone04:36
*** csd has quit IRC04:38
*** topol has quit IRC04:38
*** markvoelker has joined #openstack-keystone04:40
*** Nirupama has joined #openstack-keystone04:40
*** geoffarnold has quit IRC04:41
*** geoffarnold has joined #openstack-keystone04:41
stevemar_it has been done04:41
*** fawadk has joined #openstack-keystone04:42
*** markvoelker has quit IRC04:45
*** fawadkhaliq has quit IRC04:45
*** btully has joined #openstack-keystone04:48
*** markvoelker has joined #openstack-keystone04:50
*** agireud has joined #openstack-keystone04:51
*** dims_ has quit IRC04:52
*** c_soukup has quit IRC04:52
*** markvoelker has quit IRC04:55
*** geoffarn_ has joined #openstack-keystone05:02
*** markvoelker has joined #openstack-keystone05:02
*** markvoelker has quit IRC05:03
*** geoffarnold has quit IRC05:07
*** markvoelker has joined #openstack-keystone05:13
*** markvoelker has quit IRC05:21
*** geoffarnold has joined #openstack-keystone05:24
*** geoffarn_ has quit IRC05:28
*** e0ne has joined #openstack-keystone05:28
*** markvoelker has joined #openstack-keystone05:28
*** e0ne has quit IRC05:30
*** jamielennox is now known as jamielennox|away05:30
*** stevemar_ has quit IRC05:31
*** e0ne has joined #openstack-keystone05:34
*** markvoelker has quit IRC05:36
*** e0ne has quit IRC05:37
*** markvoelker has joined #openstack-keystone05:41
*** e0ne has joined #openstack-keystone05:42
*** markvoelker_ has joined #openstack-keystone05:42
*** henrynash has joined #openstack-keystone05:42
*** ChanServ sets mode: +v henrynash05:42
*** markvoelker_ has quit IRC05:43
*** geoffarnold has quit IRC05:45
*** geoffarnold has joined #openstack-keystone05:45
*** markvoelker has quit IRC05:45
*** su_zhang has quit IRC05:46
*** e0ne has quit IRC05:49
*** e0ne has joined #openstack-keystone05:53
*** e0ne has quit IRC05:54
*** markvoelker has joined #openstack-keystone05:58
*** e0ne has joined #openstack-keystone05:58
*** markvoelker_ has joined #openstack-keystone06:00
*** markvoelker has quit IRC06:00
*** e0ne has quit IRC06:02
*** markvoelker_ has quit IRC06:05
*** geoffarnold has quit IRC06:06
*** geoffarnold has joined #openstack-keystone06:06
*** ParsectiX has joined #openstack-keystone06:18
*** akanksha_ has quit IRC06:18
*** markvoelker has joined #openstack-keystone06:19
*** e0ne has joined #openstack-keystone06:21
*** jamielennox|away is now known as jamielennox06:21
*** markvoelker has quit IRC06:25
*** mtreinish has quit IRC06:26
*** e0ne has quit IRC06:26
*** geoffarnold has quit IRC06:27
*** geoffarnold has joined #openstack-keystone06:28
*** rudolfvriend has joined #openstack-keystone06:31
*** mtreinish has joined #openstack-keystone06:31
*** e0ne has joined #openstack-keystone06:31
*** e0ne has quit IRC06:35
*** e0ne has joined #openstack-keystone06:39
*** markvoelker has joined #openstack-keystone06:47
*** fawadk has quit IRC06:48
*** geoffarn_ has joined #openstack-keystone06:49
*** geoffarnold has quit IRC06:49
*** fawadkhaliq has joined #openstack-keystone06:50
*** fawadkhaliq has quit IRC06:51
*** markvoelker has quit IRC06:52
*** e0ne has quit IRC06:55
*** fhubik has joined #openstack-keystone06:56
*** itlinux has joined #openstack-keystone06:57
*** markvoelker has joined #openstack-keystone07:02
*** markvoelker has quit IRC07:07
*** geoffarn_ has quit IRC07:10
*** geoffarnold has joined #openstack-keystone07:10
*** fawadkhaliq has joined #openstack-keystone07:11
*** markvoelker has joined #openstack-keystone07:16
*** markvoelker has quit IRC07:21
*** vivekd has joined #openstack-keystone07:22
openstackgerritMorgan Fainberg proposed openstack/keystone: Remove LDAP Resource and LDAP Assignment backends  https://review.openstack.org/23187207:29
openstackgerritMorgan Fainberg proposed openstack/keystone: Remove LDAP Resource and LDAP Assignment backends  https://review.openstack.org/23187207:30
*** markvoelker has joined #openstack-keystone07:31
*** geoffarnold has quit IRC07:31
*** geoffarnold has joined #openstack-keystone07:32
*** marzif has joined #openstack-keystone07:34
*** markvoelker has quit IRC07:36
*** lhcheng has quit IRC07:42
*** markvoelker has joined #openstack-keystone07:46
*** markvoelker has quit IRC07:50
openstackgerritMorgan Fainberg proposed openstack/keystone: Remove LDAP Resource and LDAP Assignment backends  https://review.openstack.org/23187207:51
*** csoukup has joined #openstack-keystone07:52
openstackgerritMorgan Fainberg proposed openstack/keystone: Remove LDAP Resource and LDAP Assignment backends  https://review.openstack.org/23187207:53
*** geoffarnold has quit IRC07:53
*** geoffarnold has joined #openstack-keystone07:53
*** csoukup has quit IRC07:56
*** markvoelker has joined #openstack-keystone08:00
*** marzif has quit IRC08:02
*** drjones has joined #openstack-keystone08:02
*** _cjones_ has quit IRC08:05
*** markvoelker has quit IRC08:05
*** e0ne has joined #openstack-keystone08:10
*** browne has quit IRC08:14
*** geoffarnold has quit IRC08:14
*** geoffarnold has joined #openstack-keystone08:15
*** markvoelker has joined #openstack-keystone08:15
*** markvoelker has quit IRC08:19
*** fawadkhaliq has quit IRC08:21
*** fawadkhaliq has joined #openstack-keystone08:21
*** sdake has quit IRC08:23
openstackgerritMorgan Fainberg proposed openstack/keystone: Remove LDAP Resource and LDAP Assignment backends  https://review.openstack.org/23187208:25
*** sdake has joined #openstack-keystone08:26
*** markvoelker has joined #openstack-keystone08:29
*** e0ne has quit IRC08:30
*** e0ne has joined #openstack-keystone08:32
*** markvoelker has quit IRC08:34
*** btully has quit IRC08:35
*** jistr has joined #openstack-keystone08:36
*** markvoelker has joined #openstack-keystone08:36
*** amakarov_away is now known as amakarov08:37
*** links has quit IRC08:38
*** pnavarro has joined #openstack-keystone08:38
*** markvoelker has quit IRC08:41
*** markvoelker has joined #openstack-keystone08:44
*** fawadkhaliq has quit IRC08:48
*** fawadkhaliq has joined #openstack-keystone08:48
*** lhcheng has joined #openstack-keystone08:49
*** ChanServ sets mode: +v lhcheng08:49
*** geoffarnold has quit IRC08:50
*** markvoelker has quit IRC08:51
*** geoffarnold has joined #openstack-keystone08:51
*** markvoelker has joined #openstack-keystone08:51
*** aix has joined #openstack-keystone08:53
*** markvoelker has quit IRC08:56
*** jaosorior has quit IRC08:57
*** jaosorior has joined #openstack-keystone08:58
*** topol has joined #openstack-keystone08:59
*** ChanServ sets mode: +v topol08:59
*** markvoelker has joined #openstack-keystone09:01
*** topol has quit IRC09:03
*** markvoelker has quit IRC09:06
*** geoffarnold has quit IRC09:11
*** geoffarnold has joined #openstack-keystone09:12
*** markvoelker has joined #openstack-keystone09:16
*** markvoelker has quit IRC09:20
*** links has joined #openstack-keystone09:25
*** markvoelker has joined #openstack-keystone09:27
*** markvoelker has quit IRC09:31
*** miyagishi_t has quit IRC09:33
*** geoffarnold has quit IRC09:33
*** geoffarnold has joined #openstack-keystone09:33
*** markvoelker has joined #openstack-keystone09:37
*** jbell8 has quit IRC09:37
*** btully has joined #openstack-keystone09:39
*** GB21 has joined #openstack-keystone09:41
*** GB21_ has joined #openstack-keystone09:41
*** GB21_ has quit IRC09:42
*** markvoelker has quit IRC09:42
*** btully has quit IRC09:43
*** markvoelker has joined #openstack-keystone09:52
*** lhcheng has quit IRC09:52
openstackgerritMerged openstack/keystone: Updated from global requirements  https://review.openstack.org/23056409:53
*** geoffarn_ has joined #openstack-keystone09:55
*** jaosorior has quit IRC09:55
*** geoffarnold has quit IRC09:55
*** jaosorior has joined #openstack-keystone09:55
*** markvoelker has quit IRC09:57
*** e0ne has quit IRC10:06
*** hidekazu has quit IRC10:06
*** markvoelker has joined #openstack-keystone10:06
*** e0ne has joined #openstack-keystone10:09
*** markvoelker has quit IRC10:11
*** geoffarnold has joined #openstack-keystone10:16
*** geoffarn_ has quit IRC10:16
*** markvoelker has joined #openstack-keystone10:21
*** markvoelker has quit IRC10:26
*** jaosorior has quit IRC10:33
*** jaosorior has joined #openstack-keystone10:34
*** markvoelker has joined #openstack-keystone10:35
*** geoffarnold has quit IRC10:37
*** geoffarnold has joined #openstack-keystone10:37
*** markvoelker has quit IRC10:40
*** mdavidson has joined #openstack-keystone10:40
*** markvoelker has joined #openstack-keystone10:45
*** wwwjfy has joined #openstack-keystone10:50
*** wwwjfy_ has quit IRC10:51
*** markvoelker has quit IRC10:54
*** geoffarn_ has joined #openstack-keystone10:59
*** geoffarnold has quit IRC10:59
*** markvoelker has joined #openstack-keystone11:00
*** markvoelker has quit IRC11:05
*** pnavarro is now known as pnavarro|lunch11:14
*** markvoelker has joined #openstack-keystone11:14
*** markvoelker has quit IRC11:19
*** jamielennox is now known as jamielennox|away11:19
*** geoffarn_ has quit IRC11:19
*** geoffarnold has joined #openstack-keystone11:20
*** aix has quit IRC11:29
*** markvoelker has joined #openstack-keystone11:29
*** wwwjfy has quit IRC11:30
*** wwwjfy has joined #openstack-keystone11:31
*** markvoelker has quit IRC11:34
*** geoffarnold has quit IRC11:41
*** geoffarnold has joined #openstack-keystone11:41
*** henrynash has quit IRC11:41
*** henrynash has joined #openstack-keystone11:43
*** ChanServ sets mode: +v henrynash11:43
*** markvoelker has joined #openstack-keystone11:44
*** henrynash has quit IRC11:46
*** markvoelker has quit IRC11:49
*** markvoelker has joined #openstack-keystone11:50
*** markvoelker has quit IRC11:56
*** Nirupama has quit IRC12:01
*** geoffarn_ has joined #openstack-keystone12:03
*** geoffarnold has quit IRC12:06
*** markvoelker has joined #openstack-keystone12:07
*** david-ly_ has joined #openstack-keystone12:07
*** david-lyle has quit IRC12:09
*** david-ly_ is now known as david-lyle12:09
amakarovHello, everybody! Have somebody installed federation with oidc under Apache 2.4?12:10
*** richm has joined #openstack-keystone12:10
*** markvoelker has quit IRC12:12
*** fawadkhaliq has quit IRC12:15
*** GB21 has quit IRC12:16
odyssey4meamakarov I'm not sure if this will make much sense to you, but this may help you on your way: https://review.openstack.org/#/c/226617/12:20
*** markvoelker has joined #openstack-keystone12:21
amakarovodyssey4me, thank you, I'm reading12:21
*** mylu has joined #openstack-keystone12:23
*** geoffarn_ has quit IRC12:23
*** su_zhang has joined #openstack-keystone12:23
*** geoffarnold has joined #openstack-keystone12:24
*** markvoelker has quit IRC12:26
*** vivekd has quit IRC12:27
*** mylu has quit IRC12:28
*** richm has quit IRC12:28
*** richm has joined #openstack-keystone12:29
*** markvoelker has joined #openstack-keystone12:31
*** gordc has joined #openstack-keystone12:34
*** markvoelker has quit IRC12:36
*** edmondsw has joined #openstack-keystone12:37
*** aix has joined #openstack-keystone12:43
*** dims_ has joined #openstack-keystone12:44
*** geoffarnold has quit IRC12:45
*** geoffarnold has joined #openstack-keystone12:45
*** markvoelker has joined #openstack-keystone12:46
*** markvoelker_ has joined #openstack-keystone12:49
*** raildo-afk is now known as raildo12:51
*** dikonoor has joined #openstack-keystone12:53
*** markvoelker has quit IRC12:53
*** markvoelker_ has quit IRC12:54
*** markvoelker has joined #openstack-keystone12:56
*** su_zhang has quit IRC12:56
*** hrou has joined #openstack-keystone13:00
*** links has quit IRC13:02
*** geoffarn_ has joined #openstack-keystone13:06
*** gildub has quit IRC13:10
*** geoffarnold has quit IRC13:11
*** pnavarro|lunch is now known as pnavarro13:13
*** fawadkhaliq has joined #openstack-keystone13:15
*** su_zhang has joined #openstack-keystone13:16
*** david-lyle has quit IRC13:16
*** gordc has quit IRC13:18
*** fawadkhaliq has quit IRC13:20
*** geoffarn_ has quit IRC13:28
*** geoffarnold has joined #openstack-keystone13:28
*** jaosorior has quit IRC13:31
*** jaosorior has joined #openstack-keystone13:32
*** david-lyle has joined #openstack-keystone13:32
lbragstadbknudson: have you pushed a patch for renaming the int -> float fernet methods yet?13:33
bknudsonlbragstad: no, I didn't have a chance to work on it yesterday13:35
dolphmbknudson: i assume it's going to be a part of this series? https://review.openstack.org/#/c/231711/13:35
lbragstadbknudson: i can start working on it13:35
*** LukeHinds has joined #openstack-keystone13:38
*** doug-fish has quit IRC13:40
*** doug-fish has joined #openstack-keystone13:41
*** dikonoor has quit IRC13:45
*** doug-fish has quit IRC13:46
*** links has joined #openstack-keystone13:46
*** ngupta has joined #openstack-keystone13:48
*** geoffarnold has quit IRC13:48
*** geoffarnold has joined #openstack-keystone13:49
*** dsirrine has joined #openstack-keystone13:50
*** zzzeek has joined #openstack-keystone13:53
openstackgerritHenrique Truta proposed openstack/keystone: Manager support for projects acting as domains  https://review.openstack.org/21344813:53
openstackgerritLance Bragstad proposed openstack/keystone: Rename fernet methods to match expiration timestamp  https://review.openstack.org/23201013:54
lbragstaddolphm: bknudson ^13:54
*** jaosorior has quit IRC13:55
*** EinstCrazy has joined #openstack-keystone13:55
*** jaosorior has joined #openstack-keystone13:55
lbragstaddolphm: would you be able to revisit this one, too... when you get a chance - https://review.openstack.org/#/c/221799/13:55
*** doug-fish has joined #openstack-keystone14:01
*** csoukup has joined #openstack-keystone14:01
*** markvoelker_ has joined #openstack-keystone14:04
*** gordc has joined #openstack-keystone14:04
*** markvoelker has quit IRC14:08
*** ParsectiX has quit IRC14:09
*** geoffarnold has quit IRC14:10
*** geoffarnold has joined #openstack-keystone14:10
*** GB21 has joined #openstack-keystone14:11
*** markvoelker_ has quit IRC14:12
openstackgerritLance Bragstad proposed openstack/keystone: Rename fernet methods to match expiration timestamp  https://review.openstack.org/23201014:14
*** topol has joined #openstack-keystone14:14
*** ChanServ sets mode: +v topol14:14
*** topol_ has joined #openstack-keystone14:15
*** ChanServ sets mode: +v topol_14:15
openstackgerritHenrique Truta proposed openstack/keystone: Change project name constraints  https://review.openstack.org/15837214:15
openstackgerritHenrique Truta proposed openstack/keystone: Add is_domain parameter to get_project_by_name  https://review.openstack.org/21060014:15
*** sigmavirus24_awa is now known as sigmavirus2414:16
*** btully has joined #openstack-keystone14:16
*** ayoung has joined #openstack-keystone14:17
*** ChanServ sets mode: +v ayoung14:17
*** sweetjeebus has joined #openstack-keystone14:17
sweetjeebusHi everyone. I have a quick question about keystone and apache14:17
*** topol has quit IRC14:18
sweetjeebusMainly, why would I prefer to launch keystone as an apache service rather than a basic service? (using wsgi instead of 'service keystone start')14:18
sweetjeebusI see mention in documentation that it allows external authentication. Are there any other reasons? Is apache preferred over upstart/systemd?14:19
dolphmsweetjeebus: because as of juno or kilo (i don't recall which) we deprecated support for "as a basic service" in favor of whatever real, big-kid application server you want to use14:20
sweetjeebusright on14:20
dolphmsweetjeebus: keystone is just a wsgi application. there was no reason for a proprietary http server to be hardcoded on top.14:20
sweetjeebusI already have apache set up. Someone went onto the server and disabled it in favor of the 'basic service' approach14:21
sweetjeebusso... thanks @dolphm :)14:21
dolphmsweetjeebus: if you're not seeing deprecation warnings on startup, you likely will when you upgrade!14:22
*** timcline has joined #openstack-keystone14:23
sweetjeebus@dolphm: yeah, I just upgraded to kilo. So I stripped out usage of 'service keystone start' in favor of apache-wsgi14:24
sweetjeebusI think my team didn't like it, so when I came back in this morning, apache was down and the service is up14:24
sweetjeebusso now I'm just digging to get all the facts straight :)14:24
dolphmsweetjeebus: lol hopefully your orchestration is version controlled :)14:24
sweetjeebushehe... well... about that14:25
sweetjeebuswe want everything brought up to keystone, but we14:25
sweetjeebus're stepping the components up14:25
sweetjeebuser... 'we want everything brought up to -kilo-'14:26
dolphmsweetjeebus: for reference, https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg46449.html14:26
*** timcline has quit IRC14:27
bknudsoneventlet server doesn't have the security features that apache has. We had to implement sizelimit middleware.14:27
sweetjeebus@dophm Thanks!14:27
*** timcline has joined #openstack-keystone14:27
dolphmalthough, any mention of eventlet support being explicitly deprecated is missing from juno's release notes https://wiki.openstack.org/wiki/ReleaseNotes/Kilo14:28
sweetjeebusyeah... I just stepped through juno with nothing but a db upgrade and went straight to kilo14:30
sweetjeebusit worked really well. Just a couple of extra sql statements had to be issued14:31
*** geoffarn_ has joined #openstack-keystone14:32
*** markvoelker has joined #openstack-keystone14:32
dolphmsweetjeebus: what was missing from db_sync ?14:33
*** alextricity has quit IRC14:33
sweetjeebus@dolphm: give me a minute, I'll gather all the details from my cookbook/playbook combo14:33
sweetjeebusOkay... first, I built a throw-away server with access to the juno cloud repos (ubuntu). I installed the keystone packages, but the only configuration I did was to point keystone.conf at the proper db.14:35
sweetjeebusThen, from that throw-away (juno.upgrade.server) I ran the db_sync14:36
*** geoffarnold has quit IRC14:36
sweetjeebusIn order to upgrade it again to kilo, I first had to log into the db and issue these statements:14:37
*** fawadkhaliq has joined #openstack-keystone14:37
sweetjeebusalter table revocation_event convert to character set utf8 collate utf8_unicode_ci ;         alter database keystone CHARACTER SET utf8 COLLATE utf8_unicode_ci;14:37
sweetjeebusafter that, the kilo version of keystone-manage ran the db_sync just fine14:37
dolphmsweetjeebus: this was the latest branch of kilo?14:38
sweetjeebusYes. The latest branch that ubuntu is serving. I'll get you the version info on keystone-manage14:38
sweetjeebusa6000798@dtl07sbcid001:~$ keystone-manage --version 2015.1.114:39
sweetjeebusthe version number is the actual output14:39
sweetjeebusalso...14:39
*** EinstCrazy has quit IRC14:39
sweetjeebussudo keystone-manage --nodebug db_version 6714:39
dolphmsweetjeebus: we've actually had that exact problem release after release, but i'm not aware of any such open bugs against kilo14:39
sweetjeebus6714:39
*** ayoung has quit IRC14:41
sweetjeebusyeah, I -think- there's a bug stating that we don't need that db check to fail the db_sync14:41
*** phalmos has joined #openstack-keystone14:41
sweetjeebusbut anyway... the db_sync to juno didn't throw the errors. It came from the sync to kilo14:42
*** ayoung has joined #openstack-keystone14:42
*** ChanServ sets mode: +v ayoung14:42
sweetjeebus@dolphm: you want me to do anything further with this info? Otherwise, I'm going to go do some werk14:44
*** agireud has quit IRC14:44
dolphmsweetjeebus: no, go be productive! i'm poking around to see if it makes sense to file a bug14:44
*** ngupta has quit IRC14:45
sweetjeebusaye aye.14:45
sweetjeebusI think I can reproduce the bug pretty quick, if you need14:46
*** GB21_ has joined #openstack-keystone14:47
*** ayoung has quit IRC14:47
*** GB21 has quit IRC14:49
*** HenryG has quit IRC14:49
*** shadower has quit IRC14:49
*** martinus__ has quit IRC14:49
*** hogepodge has quit IRC14:50
*** slberger has joined #openstack-keystone14:50
*** hogepodge has joined #openstack-keystone14:51
*** stevemar_ has joined #openstack-keystone14:51
*** ChanServ sets mode: +o stevemar_14:51
*** martinus__ has joined #openstack-keystone14:51
stevemar_anyone have time to try this out with master? https://bugs.launchpad.net/keystone/+bug/150371214:51
openstackLaunchpad bug 1503712 in Keystone "Cannot delete tenant in openstack Juno" [Undecided,New]14:51
*** HenryG has joined #openstack-keystone14:52
*** geoffarn_ has quit IRC14:52
*** browne has joined #openstack-keystone14:53
*** geoffarnold has joined #openstack-keystone14:53
*** petertr7 has quit IRC14:55
*** petertr7_away has joined #openstack-keystone14:55
*** petertr7_away is now known as petertr714:55
*** alejandrito has joined #openstack-keystone14:57
dolphmstevemar_: might be a configuration error? i have no other clue why their trust_api driver would be called Revoke, otherwise...14:58
stevemar_dolphm: i assume deleting projects caused the revocation extension to be engaged, which then checked for trusty bits...14:59
dolphmstevemar_: that's not what i'm reading from the stack trace14:59
*** ayoung has joined #openstack-keystone14:59
*** ChanServ sets mode: +v ayoung14:59
stevemar__emit_invalidate_user_project_tokens_notification15:00
*** diazjf has joined #openstack-keystone15:00
*** sweetjeebus has quit IRC15:00
*** diazjf has left #openstack-keystone15:01
dolphmstevemar_: look further down. a call to self.trust_api.list_trusts_for_trustee() fails with "'Revoke' object has no attribute 'list_trusts_for_trustee'"15:01
stevemar_yeah, i'm looking around there now15:01
*** david_cu has joined #openstack-keystone15:01
*** timcline_ has joined #openstack-keystone15:03
*** timcline has quit IRC15:03
*** agireud has joined #openstack-keystone15:05
*** timcline_ has quit IRC15:05
*** timcline has joined #openstack-keystone15:06
*** jaosorior has quit IRC15:06
*** jaosorior has joined #openstack-keystone15:06
*** ngupta has joined #openstack-keystone15:07
stevemar_dolphm: maybe the user has CONF.token.revoke_by_id enabled, but no revocation driver in pipeline?15:08
*** jdennis1 has joined #openstack-keystone15:09
dolphmstevemar_: not sure what you mean (drivers aren't in the pipeline?)15:10
*** jdennis has quit IRC15:10
*** sdake has quit IRC15:11
*** sdake has joined #openstack-keystone15:14
*** jistr is now known as jistr|mtg15:14
bknudsonshould keystone be dealing internally with unicode strs or regular strs?15:15
bknudsonin python3 some things don't work if you try to mix and match str with unicode15:16
*** jistr|mtg is now known as jistr15:17
dolphmbknudson: i would think unicode, and decode them when they're being written somewhere that doesn't understand them?15:17
*** pnavarro has quit IRC15:18
bknudsonI'll give it a try. there's a lot of python apis that generate strings rather than unicode15:19
bknudsondata from clients is unicode so seems like it would be better to keep it that way as long as we can.15:23
bknudsonor, convert it right away15:23
dolphmbknudson: are you looking at the cryptography one?15:23
dolphmbknudson: right15:23
dolphmbknudson: and we need to support unicode user input... so i would think we'd be unicode internally15:23
bknudsonok, I'll try it.15:24
dolphmbut i know we're inconsistent, in part because character encodings are super subtle to keep track of in code reviews15:24
bknudsonI'm looking into the unit test failures in my py3 changes: http://logs.openstack.org/11/231711/1/check/gate-keystone-python27/cdd7f8d/console.html#_2015-10-06_21_26_25_96315:25
bknudsonI tried changing the code so that the audit id generated is a str15:25
bknudsonbut when you rescope a token, the original audit_id comes from the token15:25
bknudsonand the original audit_id is coming in as a unicode15:25
*** EinstCrazy has joined #openstack-keystone15:25
bknudsonso we wind up with a list of ['new_audit_id', u'original_audit_id']  which is hard to work with15:26
bknudsonso should be either 2 unicodes or both strs15:26
bknudsonI've been trying to make them both strs but I'll try making them both unicodes.15:27
bknudsonhere's token_ref from keystone/token/providers/fernet/core.py(94)issue_v2_token() : http://paste.openstack.org/show/475625/15:29
bknudsonit's a mishmash of unicodes and strs15:29
*** roxanagh_ has joined #openstack-keystone15:30
bknudsonit's just the tenant values that are strs15:30
*** geoffarn_ has joined #openstack-keystone15:31
*** geoffarnold has quit IRC15:31
dolphmbknudson: passing dictionaries around is probably the first mistake that led to that ;)15:32
bknudsonok, I'll just fix that.15:32
bknudsonbe back in a few weeks15:33
dolphmlol15:33
stevemar_hehe15:34
*** dims_ has quit IRC15:34
*** EinstCrazy has quit IRC15:34
openstackgerritDolph Mathews proposed openstack/keystone: Additional documentation for services  https://review.openstack.org/21118415:38
*** david-lyle has quit IRC15:41
*** david-lyle has joined #openstack-keystone15:42
*** links has quit IRC15:42
*** dims_ has joined #openstack-keystone15:44
*** arunkant has quit IRC15:48
*** rudolfvriend has quit IRC15:50
*** timcline_ has joined #openstack-keystone15:51
*** geoffarn_ has quit IRC15:52
*** timcline has quit IRC15:52
*** geoffarnold has joined #openstack-keystone15:52
*** nicodemos has joined #openstack-keystone15:54
*** david-ly_ has joined #openstack-keystone15:55
dstanekreading RFCs makes me feel dumb15:55
*** david-lyle has quit IRC15:55
*** david-ly_ has quit IRC15:56
lbragstaddolphm: I see you just rechecked https://review.openstack.org/#/c/231191/15:56
*** david-lyle has joined #openstack-keystone15:56
lbragstaddolphm: thanks, cinder issues?15:57
*** flwang has quit IRC15:58
notmynamestevemar_: I'd like to talk about the service catalog spec. got any time? https://review.openstack.org/#/c/181393/14/specs/service-catalog.rst15:58
jgriffithlbragstad: looks like grenade didn't deploy succesfuly15:58
stevemar_notmyname: for you, always15:58
dolphmlbragstad: volume already attached, you gotta detach it first15:58
notmynamelol15:58
lbragstadjgriffith: dolphm gotcha, makes sense15:59
stevemar_dstanek: they use a lot of complicated sentences15:59
notmynamestevemar_: specifically, the tenant_id removal from the catalog. (the rest of it I'm generally ok with).15:59
notmynamethe tenant_id part is what I'm concerned about15:59
dstanekstevemar_: i think most just need a tldr; section to get you started15:59
*** dims__ has joined #openstack-keystone15:59
morgannotmyname: why?15:59
stevemar_notmyname: cool - what are your concerns15:59
jgriffithdolphm: I'm kinda curious about that16:00
*** fawadkhaliq has quit IRC16:00
notmynamemy first one is a general one, and I'm curious how you see this playing out. this sounds like something that's going to require client changes to be able to use it. is that true?16:00
*** fawadk has joined #openstack-keystone16:00
jgriffithdolphm: you state "cinder fragility"... what makes you say that?16:00
notmynamewhat is the new client request pattern?16:01
jgriffithdolphm: looking at the console log it appears stack.sh failed16:01
jgriffithbut I'm likely missing something you saw so looking for education :)16:01
notmyname(I think understanding what the expected client changes are in other openstack projects will either alleviate or reenforce my concerns about the proposal)16:02
stevemar_notmyname: sec, looking at swiftclient code16:02
notmynamestevemar_: no, don't worry about that :-)16:03
notmynamestevemar_: just in general16:03
*** arunkant has joined #openstack-keystone16:03
morgannotmyname: ideally, client changes would be minimal. The client should still know where to place in the tenant id if needed. However, with tokens, the server already has the tenant so for discovery the server can produce appropriate links16:03
*** dims_ has quit IRC16:03
stevemar_notmyname: well in general it would mean that the client needs to know the tenant id as well16:03
notmynameso today a client give id creds to keystone and gets back a catalog, including the endpoint for the service16:03
notmynameand in the new world a client makes the request to keystone and then has to construct somethign locally to know the endpoint, right? ie clients need to be rewritten to use this16:04
stevemar_notmyname: it would involve client work, yes16:05
morganThe fact we have random substitutions in the catalog is a little silly - the catalog should indicate host/port/base url, but not need the substitution parts.16:05
bknudsonin the case of nova, there's no client changes necessary. The client doesn't care about the tenant_id in the url, and the server doesn't need the tenant from the URL since it gets it from the token.16:05
*** jistr has quit IRC16:05
morganbknudson: ++16:05
bknudsonI think notmyname is saying that swift can't get the tenant from the token?16:06
notmynamebknudson: well, tell me more about that. I'm not terribly familiar with the nova API, but looking at the docs yesterday it does look like the tenant id is required16:06
notmynamemorgan: I'm not sure I understand the "should" in your statement16:06
morgannotmyname: it is today. The goal is that nova shouldnt need that16:06
stevemar_notmyname: s/should/ideally16:06
bknudsonnotmyname: for now the tenant_id is required, but what they said is that they're going to change it so that nova works without the tenant id.16:06
morganIt is superfluous info in almost all cases to add it16:06
notmynamebecause nova can get the tenant from the token?16:07
stevemar_oui16:07
morganYep. As part of token validation the tenant_id is passed down to the app :)16:07
bknudsonnotmyname: right, the tenant id is in the token (nova gets it from the request env set by the auth_token middleware)16:07
notmynameand the tenant id isn't referring to an actual resource the client is using in nova16:07
bknudsonI think there's a check now that verifies that URL tenant_id matches token tenant_id16:08
notmynamemorgan: ok, so the tenant id is part of the actual token? or just part of the identity record that the server-side gets after validating the token?16:08
morgannotmyname: yes16:08
morgannotmyname: part of the token16:08
stevemar_notmyname: it's part of the token16:08
notmynamemorgan: that wasn't a yes/no question ;-)16:08
notmynameoh ok16:08
notmynameas in a substring?16:08
bknudsonthe tenant_id is a field in the token (the token is json)16:09
notmynameis that true for uuid tokens? pki tokens? fernet tokens?16:09
bknudsonit's the scope16:09
morgannotmyname: it is in the token body, services do not care about the token itself. The token when we say something is part of it is part of the body returned16:09
notmynameok, so we have different ideas of what a "token" is. I'm talking about the thing that the client sends to be authorized16:09
morgannotmyname: the token id (what the client sends) is opaque16:10
bknudsondoes swift match the client's tenant_id against the tenant ID in the URL?16:10
stevemar_notmyname: the project id is part of the token payload, http://paste.openstack.org/show/475631/16:10
morganThe migration path for nova is to support urls with both tenant_id in them and once that dont. Since nova knows the tentant_id and checks that tenant-id from token body and passed as part of the url matches explicitly16:11
bknudsonas in, could I change the request URL to use a different tenant?16:11
bknudsonwith the same token16:11
notmynamebknudson: the part of the URL that keystone is historically using the tenant id for is what we call the "swift account". it's just a storage area. we don't have any requirements on it, really, other than being unique16:11
notmynamebknudson: ie your account is differnet than mine16:11
bknudsonnotmyname: so swift doesn't care about the token scope?16:11
bknudsonhow do you give auth to different accounts?16:12
bknudsonmaybe there's some docs somewhere we should look at16:12
morgannotmyname: this seems like apriori knowledge. You would either extract it from the initial token request or be specifying it. (Please correct me if i am wrong)16:12
notmynamewell the swift account is an actual resource that clients interact with and its name is part of the data placement and namespace for everything16:12
bknudsonhow do you tell if a user has authority to an account?16:13
morganE.g. With an env or cli option if it wasnt extracted from the token?16:13
notmynamebknudson: well now were getting closer to some of my concerns with this spec :-)16:13
notmynamebknudson: in swift, the account name is unique. you have one and I have one16:13
bknudsoncan I give you access to my account?16:13
notmynamebknudson: in the account we can create containers, and in the containers we can put objects. the names of those are unique per account16:14
*** geoffarn_ has joined #openstack-keystone16:14
notmynamegettign there :-)16:14
*** geoffarnold has quit IRC16:14
*** su_zhang has quit IRC16:14
notmynameso we can both create and "images" container with an object called "cat.jpg"16:14
notmynameso we've now got "AUTH_notmyname/images/cat.jpg" and "AUTH_bknudson/images.cat.jpg"16:15
stevemar_this is because both our "images" containers are namespaced by the account IDs (project IDs)16:15
notmynamewith keystone today, s/notmyname/<whatever my tenant id is/16:15
notmynamestevemar_: right16:15
notmynameso we can also give each other access to resources in our own account16:15
bknudsonAUTH_ is a hardcoded string?16:15
stevemar_bknudson: yes it is, AFAICT16:15
notmynamebknudson: no. sortof. it's unique per auth system that's used in the cluster. many clusters have more than one auth system installed16:16
notmynameso keystone eg gets KEY_ and something else gets OTHER_ and something else gets AUTH_. etc16:16
bknudsonare you still using keystone role assignments to control access to different accounts?16:16
bknudsonI admit it will be strange for nova to have resources with the same path but different meanings based on the token scope16:17
notmynamewhen swift is determining authz for a request, it gets the roles from keystone and compares them to the roles allowed for that resource. if there is an intersection, the request is allowed16:17
bknudsonmost of the nova resources use uuids but I think flavors are named by the user16:17
notmynameso you could set read access for me on your images contianer and read/write access for morgan on your images container16:18
stevemar_notmyname: ah, is that where swft ACLs come into play?16:18
notmynamestevemar_: yes, exactly16:18
bknudsonbut you're expecting them to get a token scoped to the other project so that they can get the URL16:18
morgannotmyname: so in this case, swiftclient would know when using keystone to do the url construction. The account name can just be accquired when the token is initially requested or on the cli/by env or have the client validate the token for the info. You still need to get the account id16:19
*** dims__ is now known as dims16:19
morgannotmyname: the only difference is the keystone catalog wont say "put account id here" it may say: <swift url>/base_path_for_keystone_auth/16:19
bknudsonsay I've got a token scoped to my account and I want to read morgan's files, now I need a new token?16:20
notmynameso therefore I've got to get a different token for every potential resource I'm accessing? eg if I'm sharing content in swift, then I could have up to one token for every tenant in the system, right?16:20
bknudsonnotmyname: we're asking each other the same question... but this is how it works now16:20
morganOnly if you rely on the token to extract the id16:20
notmynamebknudson: heh16:20
morganBut if you specify the id in another way (cli option?) it wouldnt be needed16:21
morganYou already need that info client side16:21
morganHow do you get it today?16:21
bknudsonseems like swift will need to get the roles the user has on the other account16:21
bknudsonso it's going to need another token with the different scope.16:21
notmynamebknudson: but I don't think it does work that way now. basically, the keystone id comes back with some roles on it (we call them groups in swift)16:21
bknudsonit doesn't really need the project ID in the catalog if the user tells it what the project ID is.16:22
morganbknudson: ++16:22
*** drjones has quit IRC16:22
bknudsonor if the client can figure out the project ID itself somehow (ask keystone to pull it out of the token or something)16:22
notmynameyeah, but how do I, the client, know that I'm supposed to access your images/cat.jpg instead of mine? or instead of anyone else's?16:22
*** _cjones_ has joined #openstack-keystone16:23
bknudsonhow did the client know before? it must have been told.16:23
*** zzzeek has quit IRC16:23
*** agireud has quit IRC16:24
notmynamethe client gets an auth token with his own identity creds and then uses that token[id] to access the URL you gave me (which includes your account string, which today is your tenant id by convenience/accident)16:24
bknudsonhow did the client even know that keystone auth was being used instead of something else?16:24
bknudsonis there a sample application somewhere we could look at?16:24
notmynameheh16:24
notmynameI'll try to put together a sample16:25
notmynamebut before that...16:25
notmynamewell, maybe not :-)16:26
*** agireud has joined #openstack-keystone16:27
notmynameah, here16:28
notmynamehttp://docs.openstack.org/developer/swift/overview_auth.html#access-control-using-keystoneauth16:28
notmynametl;dr I set <other_project_id:other_user_id> in the ACL on the swift resource to your project:user and you get access16:30
*** geoffarnold has joined #openstack-keystone16:35
*** geoffarn_ has quit IRC16:35
stevemar_notmyname: okay, so there is a way to allow others access16:36
notmynameright16:37
stevemar_i think we went crazy off-topic though :)16:37
stevemar_notmyname: the way i imagine it would flow is: create a keystone session with a user's name/password and project, this can get us a token16:38
stevemar_get the service catalog, and with the new session in place, we already know the project that the user is authenticated again16:38
stevemar_st16:38
notmynamethat's the part I'm not sure about16:39
notmynameI don't think you do16:39
notmynamesince if I get a keystone session/token, then that doesn't say anything about my access to your resources16:39
notmynameso you give me a link to your cat.jpg and then I have to get another keystone session/token to access it?16:40
morgannotmyname: how does the client know what the account_id is today?16:41
notmynamethe swift account or the keystone tenant id?16:41
*** geoffarnold has quit IRC16:41
morganThe swift account id16:41
notmynamethat's part of the URL16:41
notmynameeg http://swift.example.com/v1/AUTH_morgan/awesome/content/lives/here.data16:42
morganOk, so you already know it16:42
morganIf you are doing a get, nothing changes16:42
morganYou dont use the tenant_id directly16:42
notmynameok. thanks. I wasn't sure about that part16:42
morganYou arent constructing /tenant_id/url16:43
morganYou just. Get "url" ;)16:43
openstackgerritDolph Mathews proposed openstack/keystone: Explain default domain in docs for other services  https://review.openstack.org/23209816:43
morganYou use roles, user, whatever for the ACLs16:44
notmynameto be pedantic, the only mapping that a tenant_id and swift account have is because that's what keystone has chosen to use. they aren't required to be the same at all. all swift cares about is that they hash to a unique value16:44
morganRight16:44
morganIt seems you mostly ignore tenant_id and act on known urls.16:44
*** lhcheng has joined #openstack-keystone16:45
*** ChanServ sets mode: +v lhcheng16:45
notmynameok, so aside for the client having to be rewritten, everything is mostly the same if there is a token ;-)16:45
*** belmoreira has joined #openstack-keystone16:45
notmynamewhat if there isn't a token?16:45
notmynameeg with public access?16:45
morganSame again as today.16:45
*** lhcheng has quit IRC16:45
morganYou bypass the keystonemiddleware because you dont care16:46
morganIt isnt a protected resource16:46
*** lhcheng has joined #openstack-keystone16:46
*** ChanServ sets mode: +v lhcheng16:46
morganYou still know the url for the resource and do a get, token validation sets (for your case) identity_invalid header but you're not blocking access16:47
notmynameyou have to have knowledge of the swift account up front through some other changel16:47
notmynamecould be a PUT16:47
morganCorrect.16:47
notmynamechangel? channel16:47
* morgan is fluent in typoese16:47
notmynameI'm a native speaker16:48
morganAs long as you know the url, you are good. If you are trying to "construct" the url, the client needs a slight bit more smarts16:48
morganBut again, the client already has to be told this today16:48
morganSomehow16:49
notmyname?16:49
*** tonytan4ever has joined #openstack-keystone16:49
morganI dont think swift constructs the url16:49
morganSwiftclient16:49
morganBut in hav not looked16:49
morganYou dont say "get me cat.jpg" you say get me <url>16:50
morganright?16:50
notmynameright16:50
notmynameit means that for auth'd access to a resource in swift, the client needs to adopt a new protocol: now they get a catalog and construct something whereas before they used what was in the catalog. after that point it's largely the same16:50
notmynameso this is keystone v4?16:50
morganNo16:50
notmynameto which one?16:50
morganNot keystone v416:50
notmynamewhy not? the auth conversation changes16:51
morganThe auth is the same.16:51
notmynamebreaking existing clients16:51
morganOk so i have no idea what swiftclient is constructing16:51
morganWhat is swiftclient constructing16:51
morganWe are talking past each other here somehow16:52
notmynameswiftclient grabs the endpoint that was in the catalog and sends requests to that16:52
morganWhat is passed to swiftclient?16:52
morganFor the url16:52
bknudsonwhat if you're not using keystoneauth, then you don't have a catalog16:53
morganIs it the whole url or just image/cat.jpg?16:53
notmynamemorgan: I don't understand. to do auth?16:53
morgannotmyname: ignore auth.16:53
notmynameok16:54
morganAssume you are using keystone16:54
notmynameok16:54
bknudsonI think a sample application would explain things16:54
morganWhat is the swiftclient command look like16:54
morganOr pseudocode using as a library16:54
*** itlinux has quit IRC16:54
notmynameswiftclient has a CLI tool, a low-level client SDK, and a high-level SDK. that's where I'm tripping up on "send to swiftclient"16:55
morganSo lets get a clear example of each.16:55
notmynamehere's a simple example using curl and auth v1 https://gist.githubusercontent.com/notmyname/47d948e864c6185e2c88/raw/2136f89ba9e66c4a4b00e29edf715a6ce808539a/gistfile1.txt16:55
*** exploreshaifali has joined #openstack-keystone16:56
notmynamehere's something very similar using the CLI from swiftclient16:57
notmynamehttps://gist.github.com/notmyname/72fa6f934b1e7a7410aa16:57
*** ngupta_ has joined #openstack-keystone16:57
bknudsonnotmyname: where did you tell it the account ^16:58
bknudsonthis one isn't using keystone ^ ?16:58
notmynameit's returned in the "catalog" (with auth v1 that's a header like the token. see x-storage-url)16:58
notmynamecorrect. this is using swift's tempauth. I can get keystone-specific examples, but it will take a while. the concepts are the same16:59
bknudsonis it in the ST_USER?16:59
dstaneklooking at how swift auth works made this clearer to me; you send username/password to swift and get back a storage url and token; that storage url is the entry point to listing containers, etc.17:00
morganFwiw, this might be something that can be solved at the summit in ~5mintues17:00
morganThis looks like IRC is not working for clear communication.17:00
notmynamedstanek: almost exactly 100% correct. the slight update is that "you send username/password [ie creds] to the auth system and get back a storage url and token..."17:01
*** ngupta has quit IRC17:01
bknudsonhow does it know the account from the username / password?17:01
bknudsonthere's multiple accounts and it doesn't know which one I'm going to talk to.17:01
notmynamein today's keystone, that's the storage url that comes back in the catalog17:01
dstanekbknudson: probably the same as what keystone does now17:01
bknudsondstanek: default project?17:01
dstanekbknudson: probably their account id/user id/ or something in the auth17:02
notmynamethe auth system (today) is responsible for mapping the user creds to a default swift account endpoint, if one exists. the auth system maintains that mapping. today keystone constructs that from the base url and tenant id17:02
bknudsonok, so seems like the catalog is only important because you take advantage of the user's default project17:04
bknudsonnotmyname: what if the user doesn't have a default swift account endpoint?17:05
bknudsonor they want to override the default, they can do that?17:05
bknudsonthe token response does have the project, or given a token you can query keystone to get the project, so the client can use that to construct the URL17:06
bknudsonor if the user passes a different project then the client can just stuff that in the url17:07
dstanekbknudson: here's my example code http://paste.openstack.org/show/475638/17:07
dstaneknot sure it if works because i deleted my swift container17:07
*** fhubik has quit IRC17:08
bknudsonso then it would be interesting to see how you'd change the sample code to use a different account with the same user.17:08
notmynamedstanek: yeah, that's using the low-level SDK17:09
dstaneknotmyname: would it be possible for swift to take a token and figure out it tenant_id instead of having it in the url17:09
notmynamedstanek: it seems like all the info is there, so yes. aside from the fact that every existing client breaks17:09
bknudsonthe catalog rework is going to be a long-term project.17:09
dstaneknotmyname: would the clients break? do they assume they can parse the URL?17:10
dstanekbknudson: i would give you a URL and you would use that with your token (i think)17:10
dstaneknotmyname: in my example i have no idea what the URL is and it really doesn't matter17:10
notmynamedstanek: because after getting that catalog back, the next thing to do is the equiv of `curl -XPUT <storage url endpoint from catalog>/my_new_container`17:11
notmynamedstanek: swiftclient is the client in this case. not you, the end user17:11
notmynameclient == the program that is using the API to access storage17:11
*** su_zhang has joined #openstack-keystone17:11
*** geoffarnold has joined #openstack-keystone17:11
dstaneknotmyname: so you are not following links at all? and actually constructing them in the client?17:12
notmynamewhat links?17:13
notmynameyou give me an opaque string that I assume works. I append the thing I'm creating to it and do an HTTP PUT request17:13
dstaneknotmyname: getting a list of containers, or whatever else.17:13
dstaneknotmyname: and i'm assuming the client doesn't support redirects17:13
notmynamefor a list of containers, the client today does a GET to the storage url that was in the catalog17:14
notmynameand no, there is no support for redirects. does keystone return 3xx response codes?17:14
notmynamecurrently swift doesn't respond with anythign in the 3xx series, so there's no support for that in our client library17:15
bknudsonwe can't stop anyone from putting a proxy in front of keystone that does 3xx.17:15
dstanekif that line were to http://swift/v1.0 and it could use the auth token to either redirect to /v1.0/tenant_id or just return the data17:15
dstaneks/line/link/17:16
*** itlinux has joined #openstack-keystone17:17
*** x58 has quit IRC17:18
dstaneki want to dig into the architecture a little more because it seems strange that the auth system would control the IDs if swift can simultaneously use multiple auth systems17:18
notmynamedstanek: yes. but that means that the client needs to be rewritten. not just swiftclient. every client17:18
notmynameok, so I think I can imagine a path forward17:18
*** x58 has joined #openstack-keystone17:18
dstaneknotmyname: i was hoping that the client would just follow the redirect, get a list of container URLs that would have the tenant_id in them and use those17:19
*** itlinux has quit IRC17:19
notmynamekeystone updates the catalog (IMO this still sounds like a breaking API change requiring an update to the version). then swift implements a 3xx to redirect iff the account isn't give and there is also a valid token in the reuqest. then the swiftclient is taught how to follow the redirect17:20
dstaneknotmyname: don't you use requests in your client?17:20
notmynamedstanek: yes we do17:20
dstanekit should be able to follow the redirect just fine. the part that would change is if it uses the original URL to do things instead of using URLs from the response17:21
morgannotmyname: for what it is worth, the catalog has not been well defined - there are a lot of cases where random cruft/non-conforming things are randomly added17:21
*** itlinux has joined #openstack-keystone17:21
notmynamethe client ecosystem that will have to change is a lot larger than just swiftclient. swiftclient is just the one that we have some control over17:22
morgannotmyname: and the catalog is part of the token not the API version17:22
dstaneknotmyname: unless swiftclient has the default redirect following behavior turned off17:22
bknudsonkeystone doesn't define the catalog, it just holds whatever the deployer puts in it.17:22
notmynamedstanek: I don't know17:22
dstaneknotmyname: ah, non-openstack clients17:22
bknudsonmaybe that's part of the problem17:23
morgannotmyname: so it would *not* be keystone v4, but an alternative to auth.17:23
dstanekbut would a change in keystone matter to them anyway?17:23
morganbknudson: that is what this spec is looking to change - define the catalog specification, then we can start being more opinionated about the catalog17:23
notmynamedstanek: yes, if deployers upgrade to a new keystone that has a different catalog, then yes I think they care very much17:23
dstaneknotmyname: no i mean other non-openstack clients17:24
notmynamedstanek: yeah, me too17:24
dstaneknotmyname: i guess i'm not following - unless they are using keystone auth too17:24
notmynamedstanek: eg if ruby fog starts getting new stuff back from the auth request, it's likely it could break. or jclouds, or any of the hundreds of custom scrips written for a particular deployment17:25
dstaneknotmyname: and those things are used against keystone?17:25
notmynamedstanek: many times. how many devs have written a script to talk to rax cloud files or hp object storage? those use keystone (or look-alikes--doesn't matter from the client perspective)17:27
dstaneki would expect that existing auth systems would work the same way and "deep link" to the tenant url; i would also expect any rest client to handle redirects properly and my only concern would be hateos17:27
notmynamehateos? is that like iOS? or BeOS? or...17:27
dstanekoops...no. meant hateoas and in the rest constraint17:28
dstanekhateos is what i'm calling my personal bsd distro17:29
notmyname:-)17:30
*** e0ne has quit IRC17:30
dstaneknotmyname: i'd love to see an example of a script that you are worried about to that i can get a clearer picture17:30
dstaneknot necessarily not though :-)17:31
dolphmbknudson: i'd be happy to submit a revised patchset for this one, but i wanted to make sure you at least saw my comment first https://review.openstack.org/#/c/225692/ -- let me know if you want to revise it or if you'd like me to17:34
bknudsondolphm: moving the part about the arguments being safe to the beginning makes sense17:35
*** _cjones_ has quit IRC17:35
notmynamedstanek: what I have locally is all based on swiftclient, so they wouldn't change themselves, but swiftclient would17:36
notmynamedstanek: here https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py#L35417:36
bknudsondolphm: if you have time to make the change go ahead since I'm in the middle of py3 unicode work.17:36
dolphmbknudson: ack17:36
notmynamealso, to everyone, I know I've taken up a ton of time with this. thank you for helping me understand17:37
*** itlinux has quit IRC17:37
*** GB21_ is now known as GB2117:37
bknudsonnotmyname: we need to know if this is going to work for swift otherwise it's a non-starter, so it'll save time to know.17:37
notmynamebknudson: the swift account part of the request is essential for every request to swift. the debate seems to be around if it's ok to not provide that in the service catalog any more17:39
dstaneknotmyname: i wouldn't expect that to need to change - the endpoint from Keystone would be http://swift/v1.0 and the swift server would handle the redirect17:39
notmynameI don't like the implied client changes required by this proposal, and I'm concerned about how this impacts use cases where a lot of users are sharing a lot of data with each other17:40
dstanekif anything i would expect that https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py#L494 would need to change, but a brief look at the code makes me think not17:40
notmynamedstanek: actually, wouldn't the version be dropped too? ;-)17:40
dstaneknotmyname: probably17:40
*** jbell8 has joined #openstack-keystone17:40
openstackgerritDolph Mathews proposed openstack/keystone: Enable subprocess_without_shell_equals_true Bandit test  https://review.openstack.org/22569217:41
dstanekthe only thing the url in get_account seems to be used for is to get the objects (which would be fine in the redirect case) and to log the request17:41
dolphmbknudson: uploaded this diff ^ http://cdn.pasteraw.com/4316vg9ju2a0au36u5wkgruokobtt8917:41
bknudsonthe endpoints should all be under a namespace rather than separate ports, e.g., https://host/openstack/swift17:41
notmynamedstanek: that method is for getting a list of the containers in a specific account. I think it's unrelated to this proposal17:42
notmynamedstanek: ie that information would be available before that method is called17:42
dstaneki think it's very related. i don't expect swift's auth to change at all; it's the things that use the endpoint returned from the catalog that are the problem17:43
notmynamebknudson: actually, that's normally a terrible idea for swift. you don't want user-specified data at the same domain as other protected content. opens up a lot of security holes17:43
dstaneki would return xxx://yyyy.zzzz in the catalog and i would expect the auth stuff to work fine, but that thing that tried to use that url will be broken17:44
*** LukeHinds has quit IRC17:45
*** _cjones_ has joined #openstack-keystone17:45
dstaneks/i would return/i could return/  -  my typing is just terrible today17:45
notmynamedstanek: right. I think I see what you're getting at. the code is structured so that the internal calls to do the auth return the endpoint that includes the swift account. so that's where the changes would be17:46
dstaneknotmyname: why change it there instead of letting the subsequent call to the swift server do a redirect?17:50
*** sdake has quit IRC17:51
dstaneknotmyname: the only thing i don't know is how those PUT URLs are constructed17:51
notmynamedstanek: where any particular code changes go isn't really important. if we need to make changes, we'll do it and try to put them in the best place17:52
*** dims has quit IRC17:52
*** dims has joined #openstack-keystone17:53
*** sdake has joined #openstack-keystone17:57
*** raildo is now known as raildo-afk17:59
*** dims_ has joined #openstack-keystone18:00
*** jvarlamova has quit IRC18:00
*** e0ne has joined #openstack-keystone18:03
*** doug-fis_ has joined #openstack-keystone18:03
*** dims has quit IRC18:04
*** raildo-afk is now known as raildo18:04
notmynameso if keystone is no longer returning the account mapping in the catalog and swift is deriving that and sending it back based on the token, doesn't that mean that swift is now maintaining the mapping between keystone identities and swift accounts?18:04
notmynameeg if swift wanted to use the ROT13(username), it could. or it could keep a static mapping of that. or it could use the tenant_id18:05
openstackgerritMerged openstack/python-keystoneclient: List creation could be rewritten as a list literal  https://review.openstack.org/22769118:05
*** doug-fi__ has joined #openstack-keystone18:05
openstackgerritMerged openstack/python-keystoneclient: Use dictionary literal for dictionary creation  https://review.openstack.org/22769018:06
notmynameIOW, swift maintains the mapping, not keystone. and this would apply to every openstack project. they would each maintain their own mapping of keystone identity to the resources they manage18:06
*** doug-fish has quit IRC18:06
openstackgerritDolph Mathews proposed openstack/keystone: Enable subprocess_without_shell_equals_true Bandit test  https://review.openstack.org/22569218:07
*** doug-fis_ has quit IRC18:08
*** doug-fi__ is now known as doug-fish18:08
*** dims_ has quit IRC18:08
notmynameis my understanding of the change of responsibility accurate?18:10
*** e0ne has quit IRC18:12
dstaneknotmyname: not sure the overall intent, but isn't that how it is now for nova, glance, etc? they do use tenant_id, but in theory i don't know that they have to other than the policy files18:13
*** su_zhang has quit IRC18:14
*** geoffarnold has quit IRC18:15
notmynameis it? I don't know18:15
*** belmoreira has quit IRC18:15
dstaneknotmyname: i think swift is the only thing that has the tenant_id in the endpoint in devstack18:16
notmynamedstanek: again, to be pedantic, swift doesn't care what that string is. the fact it's an equivalent string to a tenant_id in keystone is a coincidence18:16
notmynamethe fact that there *is* a string, swift cares very much about18:17
dstaneknotmyname: but it differs between users; i don't think other services do that by default18:17
*** e0ne has joined #openstack-keystone18:18
notmynameit might be 1:1 to identities. it might not be. I've seen swift clusters that have an endpoint per department or similar. I've also seen deployments with a 1:1 mapping between user identities and swift accounts18:18
notmynamefor the first case, you might have one swift account for the IT department and one for HR18:18
notmynameor, at the risk of giving too much away, one swift account for this game studio, and another for that game studio for a gaming company that has a lot of different games18:19
*** geoffarnold has joined #openstack-keystone18:20
dstaneknotmyname: nope, it looks like nova does have tenant_id in it's endpoint in devstack18:21
notmynameat a very high level, a user is given an endpoint where they can store stuff (account). that's it. today that endpoint mapping of user identity->account is managed by keystone. AIUI (and I want to make sure I do), this means swift manages it18:21
dstanekstevemar_: morgan: bknudson: does that mean nova will have the same issues that we've been talking about for swift?18:21
notmynamedstanek: so nova would also have to maintain a mapping18:21
dstaneknotmyname: not entirely sure :-(18:21
bknudsondstanek: nova is going to pull the project id from the token18:22
bknudsoni.e., from the env as set by auth_token middleware18:22
bknudsonnova uses auth_token.18:22
dstanekbknudson: on the server side with no client changes then?18:22
bknudsondstanek: yes.18:22
notmynamethat's somethign I'm curious about18:22
notmynameno client changes because every nova client already understands redirects?18:22
*** phalmos has quit IRC18:23
notmynameor because there's a different implementation that they're doing?18:23
bknudsonnova doesn't need redirect, it'll work with either tenant in the url or without the tenant18:24
bknudsonif you use the tenant url it'll use that and if you don't pass the tenant in the url it'll get it from the token18:25
notmynamebknudson: where does the client get the tenant url from to pass it to nova?18:25
*** aix has quit IRC18:26
dstanekkeystone catalog18:26
bknudsonyou had to specify the project when you got a token18:26
bknudsonright now when it uses the catalog to build the nova url it'll have the project id in it18:26
notmynameok, so if the keystone catalog changes, the client no longer has the tenant id? or the tenant id is a priori knowledge?18:26
bknudsonin future, it'll use the catalog to build the nova url but it won't have the project in it18:27
bknudsonthe tenant id is a-priori knowledge18:27
bknudsonthe client doesn't care if there's a project id in the url or not18:27
*** geoffarnold is now known as geoffarnoldX18:28
notmynamebknudson: project id == tenant id?18:28
bknudsonnotmyname: yes18:28
dstaneki was going to do a quick hack to see if this would work, but installing swift in my devstack seems to be borked at the moment18:31
notmynamethis happens every so often when I try to understand something in openstack: I feel like I'm beating my head against a wall, and then some little piece of info is revealed and it clicks18:31
notmynamedstanek: if you've got vagrant/virtual box, this is really fast: https://github.com/swiftstack/vagrant-swift-all-in-one18:32
dstaneknotmyname: does that do openstacky stuff too?18:32
notmynameso the piece that just clicked is that there is a priori knowledge of the tenant id18:32
notmynamedstanek: swift is openstacky ;-)18:32
dstaneknotmyname: no i mean keystone instead of tempauth (or other)18:32
notmyname:-) I know18:33
*** phalmos has joined #openstack-keystone18:33
notmynamelooking. I know there's been some work on that to do it automatically. but it's also possible to set the keystone config parts by hand and it will work18:33
*** su_zhang has joined #openstack-keystone18:34
dstanekhmmm...can't create swift domain because multi domain is off in devstack18:34
notmynamehelp me understand this: if the client is expected to know the tenant_id, where does that come from originally?18:35
notmynameis there any way the client can query it?18:35
lbragstaddstanek: do you do anything like this with vim? http://vim.wikia.com/wiki/Moving_lines_up_or_down18:35
dstaneknotmyname: in the case of horizon the user may pick it from their list of projects18:35
lbragstaddolphm: ^18:35
dstaneknotmyname: or i know mine from rax from their control panel18:36
notmynamedstanek: is that written down at account provisioning time? or is it discoverable later?18:36
dstaneknotmyname: openstack-client has a nice yaml format that i setup once and never think about again18:36
dolphmlbragstad: which part?18:36
dstaneknotmyname: at rax i can find the info in my control panel18:36
bknudsondevstack will update your clouds.yaml18:36
dstanekbknudson: automatically?18:37
lbragstaddolphm: using mappings to move lines18:37
notmynamedstanek: sure, but it could have just been written down at account provisioning time inside of rax. same for horizon18:37
dstaneksure18:37
notmynamewhat happens if you lose it?18:37
dstaneki would login and get it again18:37
david-lylenotmyname: if the user obtains an unscoped token they have access to list projects they have a role on18:38
dstaneklbragstad: i've done a few of those18:38
lbragstaddstanek: kinda handy18:38
david-lyleso username and password is enough to provide the list of projects18:38
notmynamedavid-lyle: and one of those would be the project id (tenant_id) that is used in the api requests?18:38
dolphmlbragstad: nope, but that's cool18:38
bknudsondstanek: yes, when you run devstack it updates your clouds.yaml18:39
dstaneknotmyname: used in the token request to get a scoped token (right now that is also jammed into the catalog for some things)18:39
bknudsonit creates a couple of entries for devstack-admin or something18:39
dstanekbknudson: neat. i didn't know that18:39
david-lylenotmyname: should be, but you would have to pick one and scope to it18:40
*** dims has joined #openstack-keystone18:40
dstanekbknudson: yep, devstack and devstack-admin18:40
bknudsondstanek: I did that a while ago and have meant to make some more updates in that area... actually to have devstack use the clouds.yaml rather than env vars18:41
bknudsonshould be able to do that now that it's all v3.18:41
* david-lyle not entirely sure of the API workflow in swift, so not sure he's answering the right question18:41
dolphmlbragstad: i think it's a single key shorter than the generic method to copy-delete, move the cursor, and paste. does it feel worthwhile to you?18:41
lbragstaddolphm: not sure yet, in the process of playing with it18:42
dstanekcan we stop new reviews in gerrit so i can catch up?18:44
*** jaosorior has quit IRC18:47
*** jaosorior has joined #openstack-keystone18:47
*** timcline_ has quit IRC18:48
*** timcline has joined #openstack-keystone18:49
*** GB21 has quit IRC18:50
*** geoffarnoldX has quit IRC18:56
*** geoffarnold has joined #openstack-keystone18:56
dolphmdstanek: if there is a button for that i will push it18:57
*** itlinux has joined #openstack-keystone18:59
*** flwang has joined #openstack-keystone19:01
*** su_zhang has quit IRC19:02
dstaneki'd appreciate that :-)19:07
*** dims has quit IRC19:10
dolphmstevemar_: please stop tagging bugs as "kestone" [sic] it does not provide us any benefit https://bugs.launchpad.net/keystone/+bug/150371219:10
openstackLaunchpad bug 1503712 in Keystone "Error while deleting tenant in openstack Juno" [High,Invalid]19:10
stevemar_dolphm: i didn't tag that one as keystone, it was already there19:10
stevemar_i added the tag juno19:10
dolphmstevemar_: "kestone"19:11
stevemar_dolphm: huh, what the..19:11
stevemar_err, dont know how it got there19:11
dolphmstevemar_: you edited the bug in a 3 hour old browser tab after i had deleted "kestone" as a tag long before19:12
stevemar_dolphm: it was an old browser tag19:12
*** diazjf has joined #openstack-keystone19:12
stevemar_err tab19:12
stevemar_well now weve come full circle19:13
*** dims has joined #openstack-keystone19:13
*** diazjf has left #openstack-keystone19:14
*** fawadk has quit IRC19:16
stevemar_ouch19:16
stevemar_[trust] driver = keystone.contrib.revoke.backends.sql.Revoke19:16
*** tonytan4ever has quit IRC19:17
stevemar_dolphm: well, thanks for the bug triaging dude19:17
dolphmstevemar_: do i win?19:18
stevemar_dolphm: you *always* win in keystone19:18
dolphmI WINNERED!19:18
*** roxanagh_ has quit IRC19:19
stevemar_dstanek: s/openstack-client/openstackclient19:21
lbragstadbknudson: regarding https://review.openstack.org/#/c/196877/ - do you have any suggestions on how we should go about that?19:21
*** nicodemos has quit IRC19:24
*** akanksha_ has joined #openstack-keystone19:24
*** tonytan4ever has joined #openstack-keystone19:24
bknudsonlbragstad: I'll have to think about it. maybe a base class for nonpersistent providers would make it clearer?19:25
bknudsonand a base class for persistent providers19:25
*** e0ne has quit IRC19:25
*** amakarov is now known as amakarov_away19:26
lbragstadbknudson: that would make sense19:26
*** pnavarro has joined #openstack-keystone19:26
*** itlinux has quit IRC19:27
*** itlinux has joined #openstack-keystone19:27
*** dims has quit IRC19:28
*** dims has joined #openstack-keystone19:28
*** timcline_ has joined #openstack-keystone19:30
*** timcline has quit IRC19:30
*** fawadkhaliq has joined #openstack-keystone19:31
*** su_zhang has joined #openstack-keystone19:33
*** sdake has quit IRC19:33
openstackgerritMerged openstack/keystone: Add user domain info to federated fernet tokens  https://review.openstack.org/21374219:34
*** sdake has joined #openstack-keystone19:35
*** jaosorior has quit IRC19:36
openstackgerritMerged openstack/keystone: Add user_domain_id, project_domain_id to auth context  https://review.openstack.org/21379219:36
openstackgerritMerged openstack/keystone: Add unit test for creating RequestContext  https://review.openstack.org/22826919:37
*** su_zhang has quit IRC19:37
*** timcline_ has quit IRC19:38
*** sdake_ has joined #openstack-keystone19:38
openstackgerritHenrique Truta proposed openstack/keystone: Tests for projects acting as domains  https://review.openstack.org/21121919:38
*** timcline has joined #openstack-keystone19:38
*** sdake has quit IRC19:39
*** timcline_ has joined #openstack-keystone19:40
*** e0ne has joined #openstack-keystone19:43
*** timcline has quit IRC19:43
*** pnavarro has quit IRC19:44
*** dobson` has quit IRC19:47
*** afazekas has quit IRC19:47
*** jamiec has quit IRC19:47
*** dhellmann has quit IRC19:47
*** dhellmann has joined #openstack-keystone19:47
*** jamiec has joined #openstack-keystone19:48
*** dobson has joined #openstack-keystone19:48
*** markvoelker has quit IRC19:51
*** afazekas has joined #openstack-keystone19:55
*** markvoelker has joined #openstack-keystone19:55
*** andrewbogott has joined #openstack-keystone20:02
andrewbogottIf I’m using keystone with an ldap backend… would domains be defined in ldap, or in a keystone db?20:02
*** e0ne has quit IRC20:05
browneandrewbogott: keystone db would be used for the domains20:06
andrewbogottok.  And there’s no commandline tool for manipulating domains, right?  Just curl?20:06
browneyou can use ldap for assignment (roles, projects, etc), but i don't recommend it20:06
*** geoffarnold is now known as geoffarnoldX20:06
brownewith the openstack CLI you can modify domains20:06
andrewbogottoh?  In kilo?20:07
browneyep, kilo has the openstack cli20:07
andrewbogottI’ve been staring at ‘openstack —help’ for a while now, don’t see any commands for domain creation.  What am I missing?20:08
browneonly the openstack cli supports keystone v320:08
andrewbogottyep, moving to v3 is my main objective right now.  I’ve noticed that I need to define someone as ‘cloudadmin’ which means I need to create an account in the ‘admin’ domain which means I need to /create/ the admin domain which...20:09
andrewbogott…how do I do that?20:09
*** ayoung has quit IRC20:11
*** csoukup has quit IRC20:11
browneandrewbogott: http://docs.openstack.org/developer/python-openstackclient/command-objects/domain.html20:12
andrewbogotthm… that documents a tool named ‘os’ which I do not have20:13
brownewell os = openstack20:14
andrewbogottroot@labcontrol1001:~# openstack --version20:14
andrewbogottopenstack 1.0.320:14
andrewbogottroot@labcontrol1001:~# openstack domain create20:14
andrewbogottERROR: openstack Unknown command ['domain', 'create']20:14
brownemake sure the identity api version env var is set to 320:15
andrewbogotthm, yep, that’s it.  Thank you20:16
*** timcline_ has quit IRC20:17
andrewbogottooh, I like that the usage statement changes based on an env variable.  Very unobvious :)20:18
browneyeah, IMO, openstack cli needs some work.  not quite there yet20:18
*** roxanagh_ has joined #openstack-keystone20:20
*** roxanagh_ has quit IRC20:24
*** timcline has joined #openstack-keystone20:25
*** timcline has quit IRC20:26
*** timcline has joined #openstack-keystone20:26
andrewbogotthm, $ openstack domain list gets me a 40420:28
*** pnavarro has joined #openstack-keystone20:28
*** timcline_ has joined #openstack-keystone20:28
andrewbogottoh, wait, nm, it’s entirely broken :)20:28
bknudsonandrewbogott: you should be using a clouds.yaml file instead of setting a bunch of env vars20:29
brownebknudson: i don't think clouds.yaml is supported in kilo20:30
bknudsonupgrade your openstack package to the latest.20:32
*** timcline has quit IRC20:32
dolphmmorgan: unable to review myself https://review.openstack.org/#/c/221799/20:32
*** pnavarro has quit IRC20:34
*** itlinux has quit IRC20:36
*** roxanagh_ has joined #openstack-keystone20:37
dolphmrofl just saw your review on https://review.openstack.org/#/c/228603/20:38
*** exploreshaifali has quit IRC20:39
*** ayoung has joined #openstack-keystone20:42
*** ChanServ sets mode: +v ayoung20:42
*** sdake_ has quit IRC20:43
bretoncloud.yaml?20:46
bretonI though everyone uses `source openrc`20:46
browneclouds.yaml is the newest, bestest way!20:46
bretonwhat's bad in the old way?20:46
*** roxanagh_ has quit IRC20:46
openstackgerritHenrique Truta proposed openstack/keystone: Tests for projects acting as domains  https://review.openstack.org/21121920:47
openstackgerritHenrique Truta proposed openstack/keystone: Projects acting as domains  https://review.openstack.org/23128920:47
brownemaybe somewhat easier to understand for new people20:47
openstackgerritMerged openstack/keystone: Documentation for other services  https://review.openstack.org/20480120:47
openstackgerritMerged openstack/keystone: Rename fernet methods to match expiration timestamp  https://review.openstack.org/23201020:48
bknudsonclouds.yaml will allow us to support more interesting auth, for example keystone2keystone that a bunch of env vars isn't going to work with.20:48
stevemar_i think i crossed bknudson by approving patches he -1'ed20:49
dolphmbknudson: E_OXYMORON ^interesting auth20:49
stevemar_i am forever blacklisted20:49
*** pnavarro has joined #openstack-keystone20:49
bknudsonstevemar_: what goes around comes around.20:50
bknudsonI'll find something you -1d and +2 it.20:50
*** topol_ has quit IRC20:50
stevemar_bknudson: except you'll probably be right about it!20:50
*** njohnston is now known as nate_gone20:51
* bknudson will switch to -2ing everything.20:51
*** sdake has joined #openstack-keystone20:51
*** su_zhang has joined #openstack-keystone20:52
*** ankurgupta has joined #openstack-keystone20:52
*** roxanagh_ has joined #openstack-keystone20:53
*** atiwari1 has quit IRC20:53
ayoungbrowne, and andrewbogott sorry, must have been disconnected, I had aanswered your questions, but the messages didn't go through20:54
ayoungIf you are using the ldap backend, you can't do domains20:54
ayoungyou should use the sql backend for identity and then do a domain specific backend for the LDAP portion20:54
ayoungand, you can use the openstack common client to manipulate domains20:54
ayoungyou can do the env vars approach like this: http://adam.younglogic.com/2015/08/template-for-a-keystonev3-rc/20:55
andrewbogottayoung: ok, that makes sense…  in that case would I be using file-based domain configs or db-based?  Or does it not matter?20:55
* ayoung does env vars, not ymal20:55
ayoungyaml20:55
ayoungandrewbogott, I do file based.  SQL based is newer...have not tested myself yet20:55
andrewbogottyeah, I have a ready-made script that sets up my env vars, it’s just a question of knowing which ones :)20:55
ayoungit *shold* work too, though20:55
ayoungandrewbogott, ^^20:55
ayoungthose are the right ones, and unset any other OS_* ones20:56
ayoungOS_DOMAIN esp will mess you up, or the OS_ENDPOINT*20:56
andrewbogottayoung: so, given that I already have everything in ldap… I would just create a file for the Default domain and point that to the same ldap config, right?20:56
ayounghttp://adam.younglogic.com/2014/08/getting-service-users-out-of-ldap/  a little dated but still applied20:56
*** thiagop has quit IRC20:57
ayoungandrewbogott, and,  if you get stuck:20:57
ayounghttp://adam.younglogic.com/2015/03/troubleshoot-new-keystone/20:57
*** zhenq has joined #openstack-keystone20:59
dstanekbknudson: go for the -2s!20:59
stevemar_bknudson: do it up!21:00
*** timcline_ has quit IRC21:01
zhenqqq, why keystone API v3 doc doesn't differentiate admin URI from other API while v2 does: http://developer.openstack.org/api-ref-identity-v3.html21:01
*** timcline has joined #openstack-keystone21:02
stevemar_zhenq: because we now check the roles the user has, so we don't need 2 ports, just the one (5000)21:02
*** ankurgupta has quit IRC21:04
ayoung44321:04
*** csoukup has joined #openstack-keystone21:05
ayoung$ grep " 5000/tcp" /etc/services21:05
ayoungcommplex-main   5000/tcp                #21:05
openstackgerritHenrique Truta proposed openstack/keystone: Prevents creating is_domain=True projects in v2  https://review.openstack.org/22487621:05
ayoungI don;t even know wnat commplex-main is21:05
zhenqstevemar_: thanks! since which version identity V3 is the default? kilo?21:06
*** annasort has quit IRC21:06
ayoungHere's everything that lays claim to port 5000 http://www.speedguide.net/port.php?port=500021:06
ayoungKeystone doesn't even  make the list21:07
bknudsonyou're not a player unless you're on speedguide.net.21:08
bknudsonthat should be our goal21:08
*** harlowja has quit IRC21:08
ayoungOUr goal shoudl be to get off ports 35357 and 500021:08
brownewhy does the port number matter.  you can still run keystone in apache with port 500021:10
stevemar_zhenq: v2 and v3 run side by side since grizzly21:10
*** Guest62625 is now known as mfisch21:10
*** john5223 is now known as zz_john522321:10
*** mfisch is now known as Guest4916721:10
*** zz_john5223 is now known as john522321:10
ayoungbrowne, quick, tell me if 5000 is running tls or not?21:11
zhenqstevemar_: thanks21:11
ayoungalso, it conflicts with all those other services, but the real deal is that Keystone is a web API, and already has a well known port21:11
ayoung443 for HTTPS21:11
ayoungwe should be doing this https://wiki.openstack.org/wiki/URLs21:12
browneayoung: you can use tls with any port number21:12
ayoungnot if uniersal plug and play is listening on it21:12
ayoungor yahoo messenger...hopefull not on your Keystone server21:12
browneayoung: ok, well i don't know anything about that.  what if something else is using 443?21:13
ayoungKeystone, or openstack identity is not a protocol.21:13
ayoungbrowne, that something else should be apache HTTPD, and they should both be configured to work together21:13
browneayoung: keystone is not a protocol, https is the protocol21:13
ayoungbrowne, exaclt21:13
ayounggetent services https21:14
ayounghttps                 443/tcp21:14
brownebut its not uncommon to redefine https port of a service to something other than 44321:14
brownemostly to avoid conflicts with other products21:14
ayoungmakes firewall admins really happy when you do, too21:14
ayoungbrowne, so, yeah, that was why originally.  We used a separate process for Nova, Keystone, And GLance21:14
brownei should hope firewall admins are used to that21:14
ayoungpre-quantum those days21:14
ayoungHeh...nope.  Its why we did this...21:15
ayounghttp://adam.younglogic.com/2012/05/path-to-kerberos-443/21:15
openstackgerritLance Bragstad proposed openstack/keystone: Enable try_except_pass Bandit test  https://review.openstack.org/22573821:15
ayoungMS-KKDCP support21:15
ayoungcuz I am too long winded21:15
brownei like the idea of going to apache.  don't disagree.  but i haven't done it because it gets harder to maintain the service.  starting/stopping/configuring.  just was more hassle for the time being21:17
ayoungbrowne, devstack does httpd already, but on port 500021:18
ayoungWe have support in the puppet modules, too21:18
browneyeah, i don't use devstack21:18
browneor puppet21:19
browneuse ansible, but not openstack-ansible21:19
*** john5223 is now known as zz_john522321:22
andrewbogottayoung: you have better things to do than review my puppet code, but is this the right idea?  https://gerrit.wikimedia.org/r/#/c/244350/221:22
ayoungandrewbogott, actually, reviewing puppet code is probably somethig I should do more of21:23
ayounglooking...21:23
*** fawadkhaliq has quit IRC21:23
ayoungmy puppet-fu is weak, though21:23
ayoungandrewbogott, all the tenant stuff needs to go.  That is assignment, and we don't support that anymore.  Just identity21:24
ayounguser and group values only21:24
*** zz_john5223 is now known as john522321:24
ayounglook at the block I have http://adam.younglogic.com/2014/08/getting-service-users-out-of-ldap/21:24
andrewbogottayoung: I know that tenants in ldap are deprecated, but fixing that is for another day21:25
ayoungyou might need a value or two more for users or groups depending21:25
andrewbogott(and will be ugly)21:25
ayoungyou can;'t do assignemt via a domain specific backend, though21:25
andrewbogottayoung: do you think I have to do that migration before I can do this one?21:25
ayoungonly identity, so those values will be ignored21:25
ayoungmigration?21:25
andrewbogott‘migration’ of all my tenant data from ldap into mysql21:25
ayounghttps://gerrit.wikimedia.org/r/#/c/244350/2/modules/openstack/templates/kilo/keystone/domains/keystone.Default.conf.erb  looks like a new file21:26
ayoungohh21:26
ayoungyou inheriteds Ryan's mess, didn't you?21:26
andrewbogott:)21:26
andrewbogottIt’s my mess now21:27
ayoungandrewbogott, so, yeah, migrate, or no domains for you21:27
ayoungmigration should not be too bad.  The structure is relatively parallel21:28
bknudsonhere's my proposed change to get keystone accepting on paths: https://review.openstack.org/#/c/195766/21:28
bknudsonit's not getting much traction21:28
*** lhcheng has quit IRC21:28
ayoungandrewbogott, so...you probably want to do the assignemt piece first, then switch to ldap in a domain specific backend21:29
andrewbogottayoung: I don’t think I’ve ever read the phrase ‘No one is using this’ in an Openstack email without thinking, ‘I am'21:29
*** Guest49167 is now known as mfisch21:29
*** mfisch has quit IRC21:29
*** mfisch has joined #openstack-keystone21:29
ayoungbknudson, I'd +3 it if I could21:29
openstackgerritTom Cocozzello proposed openstack/keystone: Fix direct paths inside filter_factory  https://review.openstack.org/23172221:30
andrewbogottayoung:  I believe you don’t don’t totally follow why domains depend on my moving tenants out of ldap.  Clearly the code is there to read them since it’s working now...21:30
andrewbogottIs the domains code not being traversed at all right now?21:30
ayoungandrewbogott, Nope21:31
andrewbogottAh21:31
ayoungandrewbogott, we tapdance around domains in LDAP...long boring story21:31
andrewbogottThe interface implies that the difference is between multi-domain and single-domain, not between multi-domain and something-unrelated-to-domains21:31
andrewbogottbut, ok21:31
*** doug-fish has quit IRC21:32
ayounghttp://git.openstack.org/cgit/openstack/keystone/tree/keystone/identity/core.py#n68921:32
ayoungif (not driver.is_domain_aware() ....21:32
*** jamielennox|away is now known as jamielennox21:32
*** doug-fish has joined #openstack-keystone21:32
ayoungandrewbogott, so your big problem, is to get assignment over to SQL first.  THe identity stuff won't be hard after that21:33
ayoungyou want to do a migration...and then flip a switch21:33
*** lhcheng has joined #openstack-keystone21:33
*** ChanServ sets mode: +v lhcheng21:33
openstackgerritMerged openstack/keystoneauth: Make __all__ immutable  https://review.openstack.org/23003421:36
*** doug-fish has quit IRC21:36
andrewbogottayoung: so… here’s how I got here.  I switched to the v3 api and discovered that lots of my normal workflows are broken21:37
andrewbogottbecause v3 only permits me to do things like ‘list projects’ if I’m cloudadmin21:37
andrewbogottand to be cloudadmin I have to be in the admin domain21:37
andrewbogottSo...21:37
andrewbogottthis means that I have to revert to v2, yes?21:37
andrewbogottSince v3 implies this whole dependency cascade?21:37
stevemar_bknudson: whats ExecCGI?21:38
*** doug-fish has joined #openstack-keystone21:38
bknudsonstevemar_: that tells apache that you can exec the files in the directory.21:38
bknudsonhttps://www.google.com/search?q=apache+execcgi&ie=utf-8&oe=utf-821:38
ayoungandrewbogott, v2 is going to be deprecated, aand ldap assignment is already.21:38
ayoungHow many projects we talking about here? andrewbogott21:39
andrewbogott176 projects21:39
andrewbogottI take it that was a ‘yes'21:39
*** diazjf has joined #openstack-keystone21:40
ayoungandrewbogott, yeah, you need to move forward or we won't be able to supporty ou21:40
*** sdake_ has joined #openstack-keystone21:40
stevemar_bknudson: you should have done: http://lmgtfy.com/?q=apache+execcgi21:40
*** sdake has quit IRC21:41
ayoungprojects should be pretty easy, then.  I would try this:21:41
openstackgerritMerged openstack/python-keystoneclient: Make __all__ immutable  https://review.openstack.org/23002021:41
bknudsonstevemar_: he he. too much work.21:41
andrewbogottayoung: "this means that I have to revert to v2, yes?”  There’s no other way to enable21:41
andrewbogott$ openstack project list21:41
ayoungandrewbogott, I have no real idea what would or would not work trying to do v3 ...you are on what realse?21:42
ayoungrelease21:42
*** doug-fish has quit IRC21:42
andrewbogottkilo21:42
morganstevemar_: will plan on circling up on the LDAP removal thing soon.21:42
morganstevemar_: FYI21:42
ayoungandrewbogott, https://openstack.nimeyo.com/29408/openstack-keystone-deprecation-assignment-project-assignment21:43
bknudsontjcocozz: here's the auth_token middleware I was talking about -- http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/__init__.py#n62721:43
ayoungandrewbogott, so you get a one-cycle reprieve21:43
bknudsonif you wanted to add the paste entrypoints for it.21:44
andrewbogottayoung: yes, I’ve read that, which is why I thought I didn’t have to migrate21:44
andrewbogottimmediately21:44
ayoung" Most deployers using LDAP Assignment already have plans on how to Migrate. The Keystone team will be happy to provide advice (come chat with us in #openstack-keystone on Freenode) but we do not expect to provide a canned script to make the migration happen."21:45
ayoungandrewbogott, so,  I think for V3 we had a hack in place that assumed the domain to be "Default"  but I'd have to look htroug hte code to be sure21:45
ayoungwe did this a while ago21:46
morganayoung: i think we still assume "default"21:46
morganin most cases21:46
andrewbogottayoung: yes, that’s what I’m seeing21:46
ayoungandrewbogott, so V3 should work21:46
andrewbogottbut the security engine assumes that there’s also an admin domain21:46
andrewbogottI can probably rewrite policy.json to assume otherwise21:47
ayoungandrewbogott, this is an issue just in keystone?21:49
andrewbogottso far.  I haven’t done a complete audit of what works and what doesn't21:49
*** ngupta_ has quit IRC21:50
openstackgerritEric Brown proposed openstack/keystone: Handle 16-char non-uuid user IDs in payload  https://review.openstack.org/22612121:50
*** harlowja has joined #openstack-keystone21:53
openstackgerritHenrique Truta proposed openstack/keystone: Create tests for set_default_is_domain in LDAP  https://review.openstack.org/22953621:54
andrewbogottayoung: in our cloud we have another class of user that OpenStack doesn’t really account for.  Project members who get automatic ssh access (and other forms of access) to instances in a project but do not have the ability to manipulate instances directly.21:55
*** john5223 is now known as zz_john522321:55
andrewbogottThis membership is handled in ldap.21:55
ayoungandrewbogott, is it a role assignment?21:55
ayoungandrewbogott, I think I get it.21:55
ayoungdo you put anewl;y created hosts into host groups and do LDAP Host based access control?21:56
andrewbogottSo removing tenants from ldap will break access for 90% of my users.  Migrating tenants out of ldap is not going to be trivial21:56
andrewbogottas any logic that currently checks for project membership in ldap will have to do so via a keystone change instead.21:56
stevemar_morgan: thanks for the heads up21:56
*** geoffarnoldX is now known as geoffarnold21:57
andrewbogottsince of course pam doesn’t come with built-in keystone integration...21:57
openstackgerritBrant Knudson proposed openstack/keystone: Fix fernet key writing for python 3  https://review.openstack.org/23171021:57
openstackgerritBrant Knudson proposed openstack/keystone: Fix fernet padding for python 3  https://review.openstack.org/23171121:57
andrewbogottwell21:57
andrewbogottObviously the train has sailed, regarding tenants in ldap.  But it’s not like this is a 3-hour trivial switchover21:57
*** timcline_ has joined #openstack-keystone21:59
*** timcline_ has quit IRC22:00
*** phalmos has quit IRC22:00
*** timcline has quit IRC22:03
*** edmondsw has quit IRC22:03
morganstevemar_: it shouldn't be hard to finish up. just annoying to play "find the test" whack-a-mole22:05
ayoungandrewbogott, you will be really interested in what we are doing with FreeIPA and automatic LDAP Host group registration for new instances.  We will Demo in Tokyo.  What LDAP backend are you using (OpnLDAP IIRC)?22:06
andrewbogottopendj but we hope to move to openldap sometime this year22:06
*** csoukup has quit IRC22:07
*** su_zhang_ has joined #openstack-keystone22:07
stevemar_morgan: we broke shade \o/22:08
stevemar_well devstack broke them22:08
stevemar_but that's cause we are trying to push our v3 only agenda22:08
morganstevemar_: that isn't the worst thing in the world22:08
stevemar_v3 default22:08
stevemar_nope22:08
jamielennoxstevemar_: what happened?22:08
morganwe may know someone involved in shade that can help us out ( SpamapS, mordred, etc ) ;)22:08
jamielennoxyay v3 agenda22:09
mordredaroo?22:09
mordredah. yes22:09
mordredso22:10
mordredit turns out that we were in the middle of landing keystone support to shade22:10
stevemar_jamielennox: refer to mordred's reply22:10
mordredand this has shown us some places where the v3 api is different22:10
stevemar_oh timely!22:10
mordredsuch as services.create now takes type instead of service_type22:10
*** sdake_ has quit IRC22:10
stevemar_because repeating things is silly22:10
mordredsure22:10
*** hrou has quit IRC22:11
mordredexcept now I get to add an "if v3: type: else: service_type" block in my code and glower at you22:11
* mordred glowers at stevemar_22:11
morganstevemar_: because repeating things is silly22:11
*** su_zhang has quit IRC22:11
mordredI'd like to suggest for when you do v422:11
morganmordred: REALMS!22:11
mordredthat you make the python code for v4 accept both names and silently translate it to the new name for the user22:11
morganmordred: actually I hope we can split up auth from CRUD so a move to v4 isn't breaking everything/everyone's auth :( too.22:12
mordredwell22:12
morganif a v4 is a thing22:12
mordredwhat I meant was22:12
stevemar_v4 will happen when star wars episode 18 comes out22:12
mordrednext time you make a thing with a new version of a python library22:12
morganstevemar_: jokes on you, that's next year22:12
morganstevemar_: :P22:12
mordredplease help users with backwards compat on kwargs22:12
ayoungandrewbogott, are you going to Tokyo?22:13
morganmordred: I think everything should be kwargs and nothing should be taken as positional. and stuff.22:13
andrewbogottno, I have a conflict22:13
mordredmorgan: right22:13
mordredmorgan: but key name22:13
morganmordred: and more stuff. but yah, makes sense to support the kwargs names22:14
mordredmorgan: if you change the key name you accept, and stop accepting the old keyname, it just makes it hard on the programmer22:14
morganmordred: or at the very least... make the v3 mode (for example) translate to the v4 mode (for example)22:14
mordredwho just wants to love you22:14
mordredyes22:14
mordredthat's a great example22:14
mordredOR22:14
andrewbogottayoung: anyway, I will roll back to v2 for now22:14
*** sdake has joined #openstack-keystone22:14
mordredandrewbogott: oh - you don' tneed to rollback for shade22:14
morganso when v4 is a thing v3 -> v4 (internal to lib) -> server22:14
ayoungandrewbogott, yeah starting with that...then we can help you come up with a sane plan22:15
morganor... v4.compat22:15
morganor *something*22:15
ayoungno more versions...22:15
andrewbogottIf you have a fix for my use case, it would be awesome if it could be implemented before the code I’m using /now/ is ripped out :)22:15
morganayoung: there will always need to be new versions22:15
morganayoung: it just depends on how you slice it up22:15
morganmicroversions, major versions, etc22:15
andrewbogottI mean, more than it is already22:15
ayoungmorgan, I should say "no more monolithic versions"22:15
ayoungfor across all of Keystone22:15
mordredoh - andrewbogott's rollback is different than my issue22:15
jamielennoxno to microversions22:16
ayoungjamielennox, no to microversions as well22:16
morganayoung: in an ideal world, (imo) subsystem = own version.22:16
*** mylu has joined #openstack-keystone22:16
ayoungmorgan, that is what I would prefer22:16
morganayoung: you still need CRUD interface support that does like V4, V5, etc22:17
ayounglet identity, assignment, policy, catalog, and auth vary independently22:17
bknudsonwe can split up keystone into microservices22:17
morganbknudson: we mostly have.22:17
morganbknudson: just not in separate process space. but with wsgi... almost doable22:17
*** gordc has quit IRC22:18
ayoungautopep25722:18
ayoungNo package autopep257 available.22:19
ayoungError: Unable to find a match.22:19
ayoungdamn22:19
*** david_cu has quit IRC22:19
*** henrynash has joined #openstack-keystone22:20
*** ChanServ sets mode: +v henrynash22:20
*** pnavarro has quit IRC22:20
*** tonytan4ever has quit IRC22:21
*** mylu has quit IRC22:25
*** mylu has joined #openstack-keystone22:26
*** aix has joined #openstack-keystone22:26
*** mylu has quit IRC22:28
*** mylu has joined #openstack-keystone22:29
*** dims has quit IRC22:29
*** markvoelker has quit IRC22:31
*** roxanagh_ has quit IRC22:32
*** roxanagh_ has joined #openstack-keystone22:33
*** markvoelker has joined #openstack-keystone22:33
*** mylu has quit IRC22:33
*** stevemar_ has quit IRC22:36
*** stevemar_ has joined #openstack-keystone22:37
*** ChanServ sets mode: +o stevemar_22:37
*** annasort has joined #openstack-keystone22:39
*** jbell8 has quit IRC22:40
*** stevemar_ has quit IRC22:41
*** su_zhang has joined #openstack-keystone22:49
*** su_zhang_ has quit IRC22:52
*** david-lyle has quit IRC22:54
*** zhenq has quit IRC22:54
*** mylu has joined #openstack-keystone22:55
*** david-lyle has joined #openstack-keystone22:55
*** mylu has quit IRC22:56
*** mylu has joined #openstack-keystone22:56
*** stevemar_ has joined #openstack-keystone22:59
*** ChanServ sets mode: +o stevemar_22:59
*** mylu has quit IRC23:01
*** mylu has joined #openstack-keystone23:03
*** markvoelker has quit IRC23:04
*** alejandrito has quit IRC23:04
*** mylu has quit IRC23:06
*** markvoelker has joined #openstack-keystone23:08
*** harlowja has quit IRC23:10
*** david-lyle has quit IRC23:10
*** harlowja has joined #openstack-keystone23:10
*** david-lyle has joined #openstack-keystone23:10
*** mylu has joined #openstack-keystone23:14
*** david-lyle has quit IRC23:14
*** gildub has joined #openstack-keystone23:16
*** david-lyle has joined #openstack-keystone23:17
*** david-ly_ has joined #openstack-keystone23:19
*** sigmavirus24 is now known as sigmavirus24_awa23:19
*** david-lyle has quit IRC23:21
*** dims has joined #openstack-keystone23:22
*** hrou has joined #openstack-keystone23:23
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Remove auth headers in AuthProtocol  https://review.openstack.org/22975123:28
*** david-ly_ is now known as david-lyle23:31
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Use request helpers for token_info/token_auth  https://review.openstack.org/22916123:32
marekdjamielennox: just curious why 'no to microversions' ?23:37
openstackgerritHenrique Truta proposed openstack/keystone: Create tests for set_default_is_domain in LDAP  https://review.openstack.org/22953623:37
*** mylu has quit IRC23:37
jamielennoxmarekd: i really dislike them, i realize that major versions are a pain, but microversions just offloads all the problems of dealing with versions onto the clients23:37
*** _hrou_ has joined #openstack-keystone23:38
jamielennoxyou need to do all sorts of negotiation, and different providers are going to get really diverse in which microversions they provide23:38
marekdok23:38
jamielennoxi think it's cleaner to do a new major version if you really need to break23:38
stevemar_jamielennox: marekd as far as micros go, i like microservices more than microversions23:39
stevemar_microphones are good23:39
jamielennoxi thought you were joking with that - how much more micro do you want to go23:40
*** dims has quit IRC23:40
jamielennoxcan i get some movement on reviews like: https://review.openstack.org/#/c/212341/ - i realize it's not that interesting but there's stuff there it's blocking23:41
*** hrou has quit IRC23:41
*** geoffarnold is now known as geoffarnoldX23:42
*** markvoelker has quit IRC23:42
openstackgerritMerged openstack/keystone: Deprecate httpd/keystone.py  https://review.openstack.org/22197523:43
*** markvoelker has joined #openstack-keystone23:43
*** richm has quit IRC23:44
openstackgerritMerged openstack/keystone: Additional documentation for services  https://review.openstack.org/21118423:46
stevemar_i shall do it later tonight sir23:47
stevemar_jamielennox:23:47
*** stevemar_ has quit IRC23:47
*** lhcheng has quit IRC23:51
*** markvoelker has quit IRC23:53
*** dims has joined #openstack-keystone23:54
*** slberger has left #openstack-keystone23:55

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!