Friday, 2014-12-05

*** bknudson has joined #openstack-keystone00:01
*** ChanServ sets mode: +v bknudson00:01
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Allow loading other auth methods in auth_token  https://review.openstack.org/12955200:01
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Split identity server into v2 and v3  https://review.openstack.org/13053400:01
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Use real discovery object in auth_token middleware.  https://review.openstack.org/13053200:02
*** gus_ is now known as gus00:02
*** henrynash has joined #openstack-keystone00:04
*** ChanServ sets mode: +v henrynash00:04
henrynashstevemar: yes, I know it looks odd, but that is the technique used on a lot of the user/group not found execptions…the right data still ends up in msg being raised00:10
openstackgerritMerged openstack/keystone: Updated from global requirements  https://review.openstack.org/13923000:12
openstackgerritMerged openstack/keystone: Moves hacking tests to unit directory  https://review.openstack.org/13612500:12
*** henrynash has quit IRC00:13
morganfainberghm.00:18
morganfainbergdarn missed henrynash00:18
*** openstackgerrit has quit IRC00:18
morganfainbergwill have to ask him questions later.... i guess00:19
*** openstackgerrit has joined #openstack-keystone00:19
*** marcoemorais has quit IRC00:31
*** marcoemorais has joined #openstack-keystone00:31
*** marcoemorais has quit IRC00:33
*** marcoemorais has joined #openstack-keystone00:33
*** david-lyle is now known as david-lyle_afk00:39
*** saipandi has joined #openstack-keystone00:41
*** _cjones_ has quit IRC00:47
*** shakamunyi has quit IRC00:50
*** Tahmina has joined #openstack-keystone00:52
*** boris-42 has quit IRC00:57
*** Tahmina has quit IRC00:59
*** dims_ has quit IRC01:00
bknudsonthe merge conflict checker must have broken01:02
openstackgerritBrant Knudson proposed openstack/python-keystoneclient: Correct Session docstring  https://review.openstack.org/12780501:06
openstackgerritBrant Knudson proposed openstack/python-keystoneclient: Correct documenting constructor parameters  https://review.openstack.org/12781201:06
*** samuelms_ has joined #openstack-keystone01:08
*** zzzeek has quit IRC01:09
jamielennoxbknudson: ah - i was just updating that01:10
bknudsonI asked on infra about the merge conflict checker and apparently it is brokenr.01:11
openstackgerritJamie Lennox proposed openstack/python-keystoneclient: Pass all adapter parameters through to adapter  https://review.openstack.org/13822801:12
*** packet has quit IRC01:24
*** dims has joined #openstack-keystone01:31
*** diegows has quit IRC01:35
ayoungjamielennox, bknudson -1 says "needs bug or blueprint"  we have that?01:35
jamielennoxayoung: didn't i do that/01:36
jamielennoxayoung: i filed the bug, and i'm sure i added that - but i di a few rebases01:36
openstackgerritJamie Lennox proposed openstack/python-keystoneclient: Pass all adapter parameters through to adapter  https://review.openstack.org/13822801:38
jamielennoxayoung: done01:38
ayoung bknudson care to bless that one:  https://review.openstack.org/#/c/138228  as it seems like he's hit all your comments.  We need it in before we can release a new client, and we have other work queued up behind that01:42
jamielennoxayoung: to approve that requires approving https://review.openstack.org/#/c/127805/601:50
jamielennoxayoung: https://review.openstack.org/#/c/130532/ needs second +201:53
ayoungdone02:00
jamielennoxayoung: cheers - this one has taken so long02:01
ayoungdeal02:01
ayounglbragstad, hey, I just -2ed AE tokens again02:20
*** erkules_ has joined #openstack-keystone02:21
ayoungI once again have significant enough concerns that I'm afraid of it getting rushed through without proper forethought.02:21
*** erkules has quit IRC02:23
ayoungbknudson, , what if we treated trusts as specialized role assignments, and then an AE token could point to the role-assignment-id?02:25
*** marcoemorais has quit IRC02:37
*** darren-wang has joined #openstack-keystone02:40
darren-wangHi, I have a question, "02:45
darren-wangThe separation into admin and main interfaces is an historical anomaly. The new V3 API provides the same interface on both the admin and main interfaces". if what I want is v3 API only, can I merge [composite:main] and [composite:admin] in Paste ini file? If I can, what should I do?02:45
darren-wangI don't need v2 API02:45
*** htruta_ has quit IRC02:46
*** r-daneel has quit IRC02:50
*** shakamunyi has joined #openstack-keystone02:50
*** shakamunyi has quit IRC02:50
jamielennoxdarren-wang: in which case you theoretically don't need composite:admin02:52
jamielennoxyou will still need to set the admin endpoint to the public endpoint in the service catalog02:52
jamielennoxdarren-wang: if you look at the bottom of keystone-all you'll see where it loads the information for the 'admin' and 'main' apps02:53
jamielennoxso if you are using keystone-all (dont) then you will need to modify that02:53
jamielennoxayoung: still here?02:53
darren-wangyeah02:53
ayoungjamielennox, nope.  Nope. Nope.....Um...Yep02:54
jamielennoxayoung: can you just kick off https://review.openstack.org/#/c/127805/602:54
jamielennoxit was approved before but got rebased02:54
jamielennoxit's bknudson's but there is stuff based on it02:54
*** harlowja_ is now known as harlowja_away02:54
ayoungDone02:54
ayoungjamielennox, so...policy.  I'm going put a file, I think right under keystoneclient named policy.py  and base it on the guts of what Nova and Keystone are doing.02:55
ayoungBut...02:55
ayoungI'm trying to figure out how to fetch the policy file in a generic (version non-specific) way02:55
jamielennoxayoung: so i think enforcement should go to oslo.policy02:56
ayoungNope02:56
jamielennoxand i actually think oslo is a fine place to have it02:56
ayoungthat should be the rules engine itself02:56
ayoungnot the binding to the keystone context02:56
jamielennoxoh - right02:56
jamielennoxi've been looking at policy as well just from a very different aspect02:57
jamielennoxso what is the keystone context here?02:57
ayoungjamielennox, this is what Nova starts with https://github.com/openstack/nova/blob/master/nova/policy.py02:57
ayoungfetching the policy file from the keystone server, and using the token data to enforce it02:58
jamielennoxayoung: you want that in keystoneclient?02:58
ayoungI've said that all along02:58
jamielennoxif we made that an object i have no problem with that in oslo.policy02:58
jamielennoxother than the is_admin crap02:58
ayoungwrong abstraction02:59
ayoungyeah, is_admin must die02:59
ayoungthere is also code from Keystone to mix in...02:59
*** shakamunyi has joined #openstack-keystone02:59
ayoungalso generic, and that might make its way into oslo eventually02:59
jamielennoxayoung: so i want auth_token to create an object with all the data that policy needs02:59
ayoungright...02:59
ayoungthat is exactly it02:59
jamielennoxand i want that to be the object that is passed to policy so that we can control both ends of that exchange03:00
ayoungso take the token, unpack  and parse it,  then  figure out what policy file to use03:00
darren-wangayoung, you mean keystone play as a center policy manager?03:00
ayoungdarren-wang, heh yep03:00
ayoungdarren-wang, https://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/03:00
*** lhcheng_ has quit IRC03:01
jamielennoxright, so that's ok - however if you ignore the is_admin from that nova policy file all you have is an init which should be __init__ and a enforce() and a singleton03:01
jamielennoxenforce() takes a currently oslo.context object03:01
jamielennoxand that's what i want to change, i want that to be my middleware object03:02
jamielennoxhow you handle fetching the policy from keystone i don't really care at this level03:02
jamielennoxit makes sense for something like that to be in keystoneclient that knows how to fetch and return something that can be set within the enforcer object03:03
ayoungjamielennox, right.  So it is basically how do we find the right policy file03:03
jamielennoxayoung: not really, it's a fetch03:03
ayoungcan't be to start03:04
jamielennoxayoung: GET /policy/nova then install to enforcer03:04
jamielennoxi don't think we need client smarts there right?03:04
ayoungjamielennox, we need to avoid breaking if there is no policy file03:04
jamielennoxyea - that's fairly easy03:04
ayoungwe don't even have the right API yet.  We don't have a default policy file API, and we don't know our own endpoint id03:05
ayoungBut I figure I'd do:  fetch by endpointid (handwave how to get it) and if there is none, use the config file to get the path03:06
ayoungsecond step is to fix the API so that there is a default policy file, and get by endpoint Id will fall back to that if there is none03:06
ayoungjamielennox, I guess I am OK putting this in middleware, but its going to depend on https://review.openstack.org/#/c/138519/  in client, so doing it in client means I can actually tes ti03:08
ayoungtest it03:08
jamielennoxayoung: i don't think i want that in client03:08
jamielennoxit doesn't belong03:08
jamielennoxwhy would auth_token need to have a builder? or anyone other than keystone?03:09
jamielennoxayoung: https://review.openstack.org/#/c/137268/ is where i was thinking03:09
ayoungyeah, well, ....policy checks are not just for servers, they are also for things that have to call servers and figure out "what can I do with this"  or "will I be able to do this?"03:09
jamielennoxit doesn't need to know about the catalog03:09
jamielennoxit just needs to know those basic id fields03:09
ayoungjamielennox, we're on the same track, but look at mine.03:10
ayoungits going to be the canonical token data03:10
ayoungdoes similar things to what you are doing.  I made sure already that it worked with revocation events03:10
jamielennoxayoung: right - yours reflects the token structure - even with the user fields03:10
jamielennoxi don't think we care, and i'd prefer to just not03:11
jamielennoxkeep it simple and flat with just a couple of properties03:11
ayoungI want to be able to use it in the token provider code as well.  Have one canonical token object that allows us to both build and work with the token data03:11
ayoungthere is no "simple" here03:11
jamielennoxayoung: i can see it being useful in the provider03:12
ayoungand revocation spans both keystone and other services,as will policy03:12
jamielennoxso at the point where i'm looking i already have a fairly heavy investment in the current AccessInfo object03:12
ayoungso we have a single object for all of that03:12
ayoungWe can adapt to that03:12
jamielennoxbut revocation is similar to policy - we don't care about the whole token structure just a couple of id and expiry fields03:13
ayoungHave you ever looked at the code?03:13
ayoungit cares about everything03:13
*** jdennis has quit IRC03:13
ayoungV.Re.Thing03:13
jamielennoxrevocation?03:14
ayoungjamielennox, you can revoke by domain, project, role03:15
jamielennoxright - these are what i'm exposing03:16
*** hilo has joined #openstack-keystone03:17
ayoungah you mean it only cares about the ids of objects03:17
*** hilo has left #openstack-keystone03:17
jamielennoxayoung: right, you've got layers of different objects and validation of those objects - and i just don't think we get anything for that complexity on the client side03:17
jamielennoxall i want is to expose the individual properties that are required03:18
*** kobtea has joined #openstack-keystone03:18
ayoungclient needs all the data03:19
ayoungHorizon needs to display it,03:19
ayoungyour way is actuall more complicated03:19
jamielennoxcan agree to disagree03:20
jamielennoxalso horizon is different here03:20
ayoungNo we can't03:20
ayoungoh, wait...03:20
jamielennoxi'm talking about consumers of auth_token03:20
ayoungI HATE that expresssion03:20
ayoungI want to code to the same API inside Keystone and inside Auth Token and inside DOA.03:21
*** hilo has joined #openstack-keystone03:21
ayoungI don't want to do dictionaries unless I have to03:22
*** samuelms_ has quit IRC03:22
jamielennoxayoung: i'm not advertising dictionaries03:22
ayoungI want to use Plain old Python Objects.03:22
jamielennoxi'm not sure we want that, what's required within keystone is very different to what is outside03:23
jamielennoxauth_token is similar - but really the AccessInfo we have is covering that front reasonably well03:23
*** kobtea has quit IRC03:23
openstackgerritMerged openstack/python-keystoneclient: Correct Session docstring  https://review.openstack.org/12780503:23
openstackgerritMerged openstack/python-keystoneclient: Correct documenting constructor parameters  https://review.openstack.org/12781203:24
*** gyee has quit IRC03:25
ayoungjamielennox, not when it comes to policy and revocations03:25
*** hilo has left #openstack-keystone03:25
ayoungAnd we can deal with the V2 versus V3 issues this way too03:25
jamielennoxthe point of accessinfo is to not have v2/v3 differences - what are you missing with the current accessinfo?03:26
*** dims has quit IRC03:28
ayoungA means to build one without going to JSON first is probably the biggest thing.  But I can make sure I don';t break Accessinfo03:29
*** hilo has joined #openstack-keystone03:29
*** hilo has left #openstack-keystone03:29
jamielennoxayoung: but AccessInfo has properties for everything - what do you need from json?03:31
*** jdennis has joined #openstack-keystone03:32
ayoungI don't need JSON.  I need to be able to build the object from component parts inthe TokenProvider.  I need a single API to code to03:32
*** _cjones_ has joined #openstack-keystone03:32
*** tellesnobrega_ has quit IRC03:33
*** Hilomomo has joined #openstack-keystone03:33
ayoungjamielennox, this all started when I was trying to write an auth plugin for Keystone where I only had the username and I needed to get enough information to make a policy call.03:34
*** _cjones_ has quit IRC03:34
ayoungHaving one way to do it, and having thatway based on python objects is the simplest, least error prone approach03:34
ayoungadapting that to other places is relatively trivial03:35
ayounglook at this:03:35
*** _cjones_ has joined #openstack-keystone03:35
ayounghttps://review.openstack.org/#/c/138519/3/keystoneclient/models/access_info.py,cm  line 145 on down03:35
ayoungthat converts the base objects to a dictionary.  The same thing can be done for policy checks.03:35
ayoungThe existing AccessInfo can do the same thing, too, so that they are all working with the same canonical object03:36
ayoungwithout changing the interface03:36
jamielennoxayoung: cool so all that AuthContext stuff is great and essentially the interface i want to expose03:37
jamielennoxwhy do you need to abstract the token? not just the context?03:38
*** samuelms_ has joined #openstack-keystone03:40
openstackgerritJeremy Stanley proposed openstack/identity-api: Workflow documentation is now in infra-manual  https://review.openstack.org/13932803:41
openstackgerritJeremy Stanley proposed openstack/keystone: Workflow documentation is now in infra-manual  https://review.openstack.org/13933203:41
openstackgerritJeremy Stanley proposed openstack/keystone-specs: Workflow documentation is now in infra-manual  https://review.openstack.org/13933303:42
*** stevemar has joined #openstack-keystone03:42
openstackgerritJeremy Stanley proposed openstack/keystonemiddleware: Workflow documentation is now in infra-manual  https://review.openstack.org/13933403:42
*** ChanServ sets mode: +v stevemar03:42
*** Hilomomo has quit IRC03:44
openstackgerritJeremy Stanley proposed openstack/pycadf: Workflow documentation is now in infra-manual  https://review.openstack.org/13936703:44
openstackgerritMerged openstack/keystonemiddleware: Use real discovery object in auth_token middleware.  https://review.openstack.org/13053203:46
*** richm has quit IRC03:51
openstackgerritJeremy Stanley proposed openstack/python-keystoneclient: Workflow documentation is now in infra-manual  https://review.openstack.org/13937503:51
openstackgerritJeremy Stanley proposed openstack/python-keystoneclient-federation: Workflow documentation is now in infra-manual  https://review.openstack.org/13937603:51
openstackgerritJeremy Stanley proposed openstack/python-keystoneclient-kerberos: Workflow documentation is now in infra-manual  https://review.openstack.org/13937703:51
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Add a test to ensure the version check error  https://review.openstack.org/13951204:06
*** chrisshattuck has joined #openstack-keystone04:07
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Import _LC into auth_token middleware.  https://review.openstack.org/13951304:08
*** drjones has joined #openstack-keystone04:11
*** ncoghlan has joined #openstack-keystone04:13
*** _cjones_ has quit IRC04:13
*** drjones has quit IRC04:15
*** david-ly_ has joined #openstack-keystone04:15
*** r-daneel has joined #openstack-keystone04:15
*** david-lyle_afk has quit IRC04:17
openstackgerritJamie Lennox proposed openstack/python-keystoneclient: Pass all adapter parameters through to adapter  https://review.openstack.org/13822804:21
*** jdennis has quit IRC04:26
*** dims has joined #openstack-keystone04:29
*** lhcheng has joined #openstack-keystone04:31
*** dims has quit IRC04:34
*** chrisshattuck has quit IRC04:35
*** Sanchit has joined #openstack-keystone04:40
SanchitHi04:40
SanchitWhat is the minimum configuration required to setup a keystone server?04:40
SanchitWe have extensive usage for authentication04:41
*** r-daneel has quit IRC04:53
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Split identity server into v2 and v3  https://review.openstack.org/13053405:10
openstackgerritJamie Lennox proposed openstack/keystonemiddleware: Add a test to ensure the version check error  https://review.openstack.org/13951205:12
*** avozza is now known as zz_avozza05:30
*** lhcheng has quit IRC05:39
*** ishant has joined #openstack-keystone05:47
jamielennoxSanchit: minimum? like config options?05:53
jamielennoxmostly it's a database connection string05:54
jamielennoxhave a look at the config file generated after devstack run. It's not all required but it should give you some05:55
*** ncoghlan has quit IRC05:56
openstackgerritOpenStack Proposal Bot proposed openstack/keystone: Imported Translations from Transifex  https://review.openstack.org/13624306:04
*** ajayaa has joined #openstack-keystone06:06
*** shakamunyi has quit IRC06:07
*** ajayaa has quit IRC06:13
*** saipandi has quit IRC06:15
*** ajayaa has joined #openstack-keystone06:17
openstackgerritSamuel de Medeiros Queiroz proposed openstack/keystone-specs: Add domain roles APIs  https://review.openstack.org/13953106:17
*** zz_avozza is now known as avozza06:21
*** mfisch has quit IRC06:23
openstackgerritSamuel de Medeiros Queiroz proposed openstack/keystone-specs: Fix 'heirarchy' typo on 'Get project'  https://review.openstack.org/13953606:25
*** mfisch has joined #openstack-keystone06:27
*** mfisch is now known as Guest4508706:27
*** avozza is now known as zz_avozza06:31
*** zz_avozza is now known as avozza06:33
*** dyasny has joined #openstack-keystone06:43
dyasnyping - anyone listening in?06:47
*** openstackgerrit has quit IRC06:49
*** openstackgerrit has joined #openstack-keystone06:49
samuelms_dyasny, hi :)06:50
dyasnysamuelms_ hey, do you have a minute to help a lost soul?06:50
samuelms_dyasny, I can try :)06:50
dyasnyI've got a test lab, which I didnt build, and it looks like by default, it's using v2.006:51
dyasnyit also looks like I need v3 for some heat stuff I'm working on06:51
dyasnyquestion is, how can I figure out whether v3 is available or installed but disabled06:52
dyasnyI'm on icehouse here06:52
samuelms_do you want to setup a Openstack installation with heat? that's all?06:52
dyasnysamuelms_, already have an installation, I'm working on heat autoscaling06:52
samuelms_hmm.. how do you get a token?06:52
dyasnyhowever, when I try to run my stack, I get http://fpaste.org/156848/41776168/06:53
dyasnyI export OS_user/pass/auth_url06:53
dyasnyand my auth_url points at a v2.0 URL. I checked for v3 and v3.0 at the same location - keep getting 40406:54
samuelms_dyasny, just checked and we had v3 on icehouse06:55
dyasnysamuelms_, this is why I wonder whether I am looking in the wrong place somehow06:55
dyasnywhat's the typical 3.0 auth_url?06:56
samuelms_dyasny, try exporting OS_IDENTITY_API_VERSION=306:56
*** kobtea has joined #openstack-keystone06:56
dyasnysamuelms_, and leave the URL pointing to v2.0?06:56
samuelms_dyasny, fix that as well .. to v306:57
samuelms_export OS_IDENTITY_API_VERSION=306:59
samuelms_export OS_AUTH_URL=http://<hostname>:5000/v${OS_IDENTITY_API_VERSION}06:59
dyasnysamuelms_, curl says 404 if I try to go there06:59
samuelms_dyasny, so I dont know what's happening, sorry :/07:00
samuelms_dyasny, I dont have lots of experience deploying os07:00
*** kobtea has quit IRC07:00
dyasnysamuelms_, basically, after I change the AUTH_URL I get 404, that's an http error, simply means there is no such URL (http://server:5000/v3/)07:01
samuelms_dyasny, yes .. so you dont have /v3 running07:02
dyasnysamuelms_, any idea how I can enable it?07:03
samuelms_dyasny, thought it was enabled by default .. dont know about icehouse07:04
samuelms_dyasny, you better ask in some hours .. when people get more active07:04
dyasnysamuelms_, I see, thanks anyway, I appreciate the attempt07:04
samuelms_dyasny, you're welcome :-)07:05
samuelms_dyasny, hope you find a solution soon07:05
dyasnysamuelms_, if not, I'll just go back to ovirt, it scales well enough07:05
samuelms_dyasny, dont give up .. openstack is amazing :D07:06
samuelms_dyasny, that shouldnt be that hard07:06
samuelms_dyasny, why not use juno version? or a fresh devstack (if you're just testing something)07:06
dyasnysamuelms_, I know, this stuff works in devstack, but not in a real lab, and I find myself looking at code way too often for comfort07:07
*** mzbik has joined #openstack-keystone07:08
dyasnysamuelms_, guess it's all too fresh to google for answers07:08
samuelms_dyasny, I'll have the answers here on irc07:09
samuelms_dyasny, just need to come at time :p07:09
dyasnyyup, 2am isn't the best time07:10
*** avozza is now known as zz_avozza07:12
*** stevemar has quit IRC07:13
Sanchitjamielennox: Thanks for replying, I am concerned regarding the hardware requirements for running a highly scalable setup07:19
SanchitWhat should be the minimum RAM and all regarding07:20
openstackgerritSamuel de Medeiros Queiroz proposed openstack/keystone: Add test for changing password to blank  https://review.openstack.org/13955307:33
openstackgerritSamuel de Medeiros Queiroz proposed openstack/keystone: User password update should not accept blank  https://review.openstack.org/13955407:33
*** samuelms_ has quit IRC07:41
*** henrynash has joined #openstack-keystone07:52
*** ChanServ sets mode: +v henrynash07:52
darren-wangjamielennox,  i just read the part of starting servers in keystone-all, so if in a new installation without any v2 API, can I modify like these:07:57
darren-wangjamielennox,  1. delete the [composite: admin] in .ini,07:57
darren-wang jamielennox: comment the admin server starting part in keystone-all,07:57
darren-wangjamielennox: 3. and do not set the 'admin_bind_host', 'admin_port' and 'admin_worker_amount' in .conf07:58
jamielennoxSanchit: I can't really answer in terms of RAM and such, however at it's base keystone is just a mod_wsgi app so you scale it behind haproxy and apache as you would any other service07:58
jamielennoxdarren-wang: if you don't use them then the config options will just be ignored07:59
*** zz_avozza is now known as avozza07:59
jamielennoxdarren-wang: we've been recommending recently that people run keystone behind apache07:59
jamielennoxin which case you would just not setup the admin route and comment out the v2 route in paste07:59
darren-wangjamielennox: oh, I haven't tried that yet.08:00
jamielennoxdarren-wang: not that i said the v2 route and not just the admin app08:00
jamielennox*note08:00
jamielennoxso the admin interface typically runs on a different port08:00
jamielennoxand there is a v2 and a v3 component to both the public and the admin servcie08:00
jamielennoxjust that in v3 it's the same thing08:00
*** tellesnobrega_ has joined #openstack-keystone08:00
darren-wang... well, I'm still learning the code, so, does 35357 still necessary in pure v3?08:03
*** tellesnobrega_ has quit IRC08:04
*** bdossant has quit IRC08:07
jamielennoxdarren-wang: technically no, but most things still set it up that way08:08
darren-wangjamielennox: ok, I'll have a try.08:08
darren-wangjamielennox: we just need a consistent and easy solution, so v2 is totally unnecessary to us08:09
darren-wangjamielennox: thx jamie08:10
jamielennoxdarren-wang: np08:10
Sanchitjamielennox: Well, Thank you so much!08:25
marekdmorganfainberg: OK, no problem.08:26
Sanchitjamielennox: One more thing, If using UUID token, will the service ping keystone server every time for token validation? As far as I know, this is not the case if using PKI. Correct ?08:27
*** henrynash has quit IRC08:40
*** oomichi has quit IRC08:41
bretonSanchit: yep. But in case of pki keystone the service needs to check revocation lists periodically08:43
jamielennoxSanchit: yes, but in practice the middleware will cache the token validation so it's generally only the first time per token per service09:00
Sanchit@jami09:01
Sanchitjamielennox: first time per token per service for PKI type only.09:01
SanchitBut for each time if Using UUID? Correct me if my undestanding is wrong09:01
*** sluo_wfh has quit IRC09:02
*** erkules_ is now known as erkules09:03
*** Guest45087 has quit IRC09:11
*** sluo_wfh has joined #openstack-keystone09:14
*** jistr has joined #openstack-keystone09:14
*** mfisch has joined #openstack-keystone09:15
*** mfisch is now known as Guest321409:15
*** sluo_wfh has quit IRC09:20
*** tellesnobrega_ has joined #openstack-keystone09:35
jamielennoxSanchit: sorry, i'm in and out09:36
jamielennoxSanchit: for UUID it will cache the response that it gets from keystone09:37
jamielennoxfor PKI all it needs is like one or two requests for the certs09:37
jamielennoxthen every minute or so it gets the revocation list09:38
jamielennoxit doesn't do any work per token09:38
*** tellesnobrega_ has quit IRC10:00
Sanchitjamielennox: Thank you :)10:07
*** aix has joined #openstack-keystone10:16
openstackgerritMarek Denis proposed openstack/keystone: Identify groups by name/domain in mapping rules.  https://review.openstack.org/13901310:59
mzbikGuys I have problem with trusts11:12
mzbikwhen I create trust from admin to some member I get exception: Could not find role {role_id}11:13
mzbikI tried to create trust from admin to testUser with role _member_ to demo tenant/project11:13
*** amakarov_away is now known as amakarov11:17
*** darren-wang has quit IRC11:30
openstackgerritMerged openstack/keystone: Remove irrelative comment  https://review.openstack.org/13835511:38
*** diegows has joined #openstack-keystone11:54
*** dims has joined #openstack-keystone12:04
mzbikok, nvm I forget to add project_id12:05
*** thiagop has quit IRC12:14
*** samuelms_ has joined #openstack-keystone12:18
*** jdennis has joined #openstack-keystone12:31
openstackgerritAlexander Makarov proposed openstack/keystone: LDAP additional attribute mappings description  https://review.openstack.org/11859012:33
*** henrynash has joined #openstack-keystone12:47
*** ChanServ sets mode: +v henrynash12:47
*** mikedillion has joined #openstack-keystone12:55
*** ajayaa has quit IRC12:59
*** henrynash has quit IRC13:01
*** dyasny has quit IRC13:04
*** ajayaa has joined #openstack-keystone13:13
*** mikedillion has quit IRC13:19
*** andreaf has quit IRC13:23
*** dims has quit IRC13:29
*** dims has joined #openstack-keystone13:29
*** dyasny has joined #openstack-keystone13:32
*** dyasny has quit IRC13:32
*** kobtea has joined #openstack-keystone13:38
*** mzbik has quit IRC13:42
*** kobtea has quit IRC13:42
*** ishant has quit IRC13:54
vsilvamarekd, are you there? I spent some days away from the Mapping Enhancements spec and a lot has changed. One thing that I didn't get from the comments: Why did you move from only setting role assignments in Keystone for the IdP groups to having to add the groups apriori?13:54
amakarovbknudson, hi! I've reverted code changes leaving doc changes only. Please look at the change https://review.openstack.org/#/c/118590/13:56
*** stevemar has joined #openstack-keystone13:57
*** ChanServ sets mode: +v stevemar13:57
*** joesavak has joined #openstack-keystone14:02
*** dims has quit IRC14:05
*** dims has joined #openstack-keystone14:06
*** andreaf has joined #openstack-keystone14:07
*** radez_g0n3 is now known as radez14:07
*** bdossant has joined #openstack-keystone14:10
vsilvahey stevemar, I'm trying to figure out one thing from the mapping enhancements spec: Why did they move from only setting role assignments in Keystone for the IdP groups to having to add the groups apriori?14:13
vsilvacan't find the reason on comments and marek doesn't seem to be around14:13
*** bdossant has quit IRC14:13
vsilvarodrigods, ^14:13
*** bdossant has joined #openstack-keystone14:15
*** bdossant has quit IRC14:16
*** bdossant has joined #openstack-keystone14:17
lbragstadmorganfainberg: I realize this might be a long shot, but we don't have Release Notes for Kilo do we/14:17
openstackgerritRodrigo Duarte proposed openstack/keystone: Inherited role assignments to projects  https://review.openstack.org/13855214:18
lbragstadfollowing criteria from sdague here: https://review.openstack.org/#/c/139051/14:18
*** shakamunyi has joined #openstack-keystone14:21
*** avozza is now known as zz_avozza14:22
*** bdossant has quit IRC14:27
*** richm1 has joined #openstack-keystone14:28
*** diegows has quit IRC14:33
*** bdossant has joined #openstack-keystone14:34
lbragstadmaybe dolphm knows^14:35
lbragstad?14:35
*** mikedillion has joined #openstack-keystone14:45
ayounglbragstad, here's an idea for you.  What if we had an identifier for role assignments.  And then trusts were a form of role assignments.  AE tokens could then point to a specific role assignment for its scope14:50
lbragstadthat pretty much what jamielennox said14:50
ayounglbragstad, so...that is the point of https://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/14:51
ayoungthose are the steps we need to go through to get there14:51
ayoungdoes it make sense in that context?14:51
lbragstadlet me read it14:51
ayounglbragstad, please do14:51
lbragstadayoung: https cert expired?14:51
ayounglbragstad, on my blog?14:52
lbragstadyeah14:52
ayounglbragstad, nah, it is just signed by Dreamhosts ca14:52
lbragstadah14:53
ayoungactually, I think they do a selfsigned14:53
dstanekdoes anyone actually use x-service-token?14:53
ayoungdstanek, isn't that what is used by Auth token to validate?14:53
dstanekayoung: it's optional14:54
dstanekayoung: but i can't find anything that ever sets it14:54
*** r-daneel has joined #openstack-keystone14:55
*** zzzeek has joined #openstack-keystone14:55
ayoungdstanek, it appears you are correct14:55
bknudsondstanek: I think glance or swift wanted it for a security feature.14:56
bknudsonessentially you could have your policy.json say that this request needs to have both the user and the service user to fetch an image14:56
dstanekbknudson: interesting - i wonder if swift uses it; i don't have their code checked out14:56
ayoungthere was the "you need two tokens to do something"  discussion, but I thought that X-SERVICE-TOKEN pre-existed that14:56
dstaneknope, not in swift either14:58
bknudsonI don't know if swift uses auth-token?14:58
bknudsonthe service would have to put the service user ID in their context so that policy could access it.14:58
marekdvsilva: hey. it's mainly we don't role assignments api allowing for specyfing groups identified by name/domain. And I think this is kind of philosophical question whether we should do that or not. More! It has already been discussed as henry-nash pointed out once) and tte second approach was not implemented. So I thought that it's better to have the mapping enhancement like proposed in a spec rather than depend on such a big (and unlikely t15:01
*** gordc has joined #openstack-keystone15:01
*** Guest3214 is now known as mfisch15:01
*** mfisch has joined #openstack-keystone15:01
*** thiagop has joined #openstack-keystone15:03
vsilvaI think your last sentence was cut off there, marekd15:03
marekdno it wasn't..15:04
marekdchange: role assignment api change15:04
marekdthat's what i meant.15:04
rodrigodsayoung, https://review.openstack.org/#/c/138551/ \o/15:04
openstackgerritRodrigo Duarte proposed openstack/keystone: Adds correct checks in LDAP backend tests  https://review.openstack.org/13855115:06
marekdvsilva: makes sense?15:06
vsilvaSo I thought that it's better to have the mapping enhancement like proposed in a spec rather than depend on such a big (and unlikely t15:06
vsilvathat's how what you said ends. unlikely what?15:06
marekdvsilva: oh, strange...i can see whole sentence while you don't :-)15:07
marekdvsilva: hey. it's mainly we don't role assignments api allowing for specyfing groups identified by name/domain. And I  think this is kind of philosophical question whether we should do that or not. More! It has already been discussed as  henry-nash pointed out once) and tte second approach was not implemented. So I thought that it's better to have the15:07
marekd mapping enhncement like proposed in a spec rat her than depend on such a big (and unlikely to be quickly implemented)15:07
*** dims is now known as dimsum__15:07
marekdvsilva: that's what I had sent.15:07
vsilvaall right then15:08
ayoungrodrigods, lets get the parent on through, and then, assuming there are no changes, I'll +A that one again15:08
*** ajayaa has quit IRC15:08
marekdvsilva: if you want to start a thread/spec about changing the role assignments api15:14
marekdvsilva: but i'd rather make it a separate patch, aiming for the Kilo release date, not next week. :(15:14
vsilvamaking it a separate patch makes a lot of sense, marekd. I'll think on that along with rodrigods and maybe bring it up here to see if that change really makes sense. I fear it might not!15:18
marekdvsilva: why it might not?15:19
marekdvsilva: well, ok, 2 ways of doing the same thing may be pointless15:19
marekdvsilva: but without ephemeral groups in RAs we  are doomed.15:19
marekdvsilva: and that's exactly why i didn't want to depend on such dependency :-) I foresee lots of discussion and philosophical questions involved :-)15:20
lbragstadayoung: I read your post15:20
ayounglbragstad, I know it is dense.15:22
*** dims_ has joined #openstack-keystone15:24
*** ajayaa has joined #openstack-keystone15:26
lbragstadayoung: so why not have a token format that requires the scope in the token?15:27
ayounglbragstad, um...yes?15:27
ayoungwhy not?15:27
lbragstadI'm not saying we *can't* do that15:27
lbragstadbut with the proposed spec, we have the ability to tailor token formats to fit needs like that15:28
*** dimsum__ has quit IRC15:28
ayounglbragstad, I'm not sure that just saying "we can have multiple token formats" is sufficient15:30
lbragstadayoung: but having one token format to rule them all doesn't seem to work15:30
marekdlbragstad: ayoung AE tokens disq ?15:30
lbragstadyes15:30
ayounglbragstad, OK...so a token is a cookie...what we really care about is what is it pointing at.  And what Keystone needs to do is answer the question "what roles go along with this token that a user just handed me?"15:31
lbragstadwhy not have a format for a case that you need, where the formatter (creating the token) knows how to pack all the information required to do that specific case.15:32
lbragstadayoung: why would that be needed if you have hierarchical roles/15:33
lbragstadyou could decompose the list from the top down based on the highest role you have, right?15:33
ayounglbragstad, hierarchical roles are just a sensible way to unify all of the approaches15:33
lbragstadI assert that because I have the 'member' role I also have the 'editor' and 'reader' roles15:33
ayoungwe could keep going scatter gun, as we are, and have to support a million one-offs15:33
ayoungand I really seeAE as a one off15:33
ayoungand really, RBAC is based on the premise that a user has one role15:34
ayoungand that based on that role (Manager, boss-man, worker-bee) you determine what they can do15:34
lbragstadyeah15:35
ayoungso, if you want to say "here is a token format that points to a role for this user"  OK15:35
ayounglets do it right, and not paint ourselves into a corner15:35
lbragstadso, if every use is suppose to have only one role15:36
lbragstadand it's a hierarchical role15:36
ayoungAs written, AE can only do "here is the scope, go lookup the roles the user has for that scope"15:36
lbragstadthat I don't see the argument for requiring that a role is included in the token15:36
ayoungyeah, but we are not there yet15:36
lbragstadand until we get there we can include scope in an AE token15:37
ayoungyou can think of a trustid as a short-lived role that contains the subordinate roles...its a limited version of inheritance15:37
ayoungI'd rather not make a form of AE token that knows about trusts15:37
ayoungas I am going to be on the hook to maintain it, and I don't have the time or effort15:37
ayoungtime for the effort15:38
lbragstadayoung: what would you absolutely need in a token to know it's a trust token15:38
lbragstad?15:38
ayounglbragstad, I'd need the trust id15:38
lbragstador a token representing a trust relationship between two entities15:38
lbragstadok, so that's your delegation15:38
lbragstadright?15:38
ayounglbragstad, yes, you could do something like15:38
ayoungAE01  is standard role-based AE tokens and AE02 is trust based, and in AE01  you assume the scoped is the proejct and in AE02  you assume the scope is the trust15:39
ayoungbut you see how trusts and role assignments are really the same thing?15:40
ayoungThey are really just delegations of abilities.  Well, trusts are.  Role assignments should be.15:40
*** bdossant has quit IRC15:41
*** bdossant has joined #openstack-keystone15:42
lbragstadayoung: it's that what jamielennox meant when he said that for ae_token['role'] = trust_id?15:43
*** gordc has quit IRC15:43
lbragstadif trusts and role assignments are the same, then treat them the same in an ae token until they are technically the same mechanism in Keystone15:44
lbragstadwhich is the first point you make https://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/15:47
ayounglbragstad, how would the token validation determine that  ae_token['role'] = trust_id ?15:49
lbragstadthat's were the token version stuff comes in handy15:50
lbragstadif keystone is creating an ae token to represent a trust relationship, make the ae token version AE03 or whatever,15:50
lbragstadthat can be popped of in validation and it would know where in the token the trust_id and how to handle it15:51
ayounglbragstad, are 2 digits going to be enough?15:54
lbragstadwe would have up to 99 token formats15:54
*** thiagop has quit IRC15:54
lbragstad99 problems and a token ain't one15:54
ayoungShall we go Hex at least?15:54
ayoungFF?15:55
lbragstadif you wanted to modify the AE part you could do that too I guess15:55
lbragstadAE01 would be a generic ae token format15:55
ayoungAE0015:55
ayoungWe are computer scientists.15:56
lbragstadAT could be an authenticated encrypted trust format15:56
ayoungHeh15:56
lbragstadfor which you could have 99 authenticated encrypted trust formats15:56
ayoungWhat was the  old PKI identifier?  /me goes to look15:56
* lbragstad grabs another coffee15:57
lbragstadbrb15:57
ayoungPKI_ASN1_PREFIX = 'MII'15:58
dstaneklbragstad: more like "i got 99 problems and tokens are all of them"16:00
*** thedodd has joined #openstack-keystone16:01
openstackgerritMerged openstack/keystone: Create, update and delete hierarchical projects  https://review.openstack.org/13855016:02
ayounglbragstad, lay all of that out in the AE spec.16:03
notmynamedstanek: bknudson: swift is not yet using a service token16:07
samuelms_Hi guys .. what's your opinion on bug #1391116 ?16:11
uvirtbotLaunchpad bug 1391116 in python-keystoneclient "keystone user-password-update also accept blank password." [Medium,In progress] https://launchpad.net/bugs/139111616:11
samuelms_I'm fixing that .. but I'd like to see your thoughts before putting more effort on that16:11
*** Qlawy has quit IRC16:12
*** Qlawy has joined #openstack-keystone16:14
bknudsonsamuelms_: we have a general issue where the Keystone SQL backend doesn't do password validation.16:15
bknudsoni.e., most deployers will require a password with a certain length and special characters, not reusing etc.16:16
bknudsonand I'd prefer it if it wasn't fixed piecemeal16:16
bknudsonbut I also don't know if we want to put a lot of effort into it... use LDAP as the backend instead.16:16
bknudsonand there's also the idea that we should split user / group management out into its own service so it looks more like LDAP / federation16:17
*** thedodd has quit IRC16:17
samuelms_bknudson, hmm interesting16:18
bknudsonif we split user/group management out into its own service then I'd say go nuts adding security features like password validation.16:19
*** thedodd has joined #openstack-keystone16:19
samuelms_bknudson, for sql we could allow some kind of expressions to define constraints ..16:20
samuelms_bknudson, any entry point (spec) for splitting user/group?16:20
bknudsonsamuelms_: I haven't seen a spec for splitting user / group... it was discussed at atlanta summit16:21
samuelms_bknudson, ok .. will look for some logs on this16:25
samuelms_bknudson, maybe we could discuss about it in a meeting and then decide if we'll go on with it16:25
bknudsonsamuelms_ sounds good... there's a lot of details to work out that might make it easier or harder... for example, does it support multiple domains and how.16:27
bknudsonalso, I'm not sure how auth would work, if it would use auth_token?16:28
bknudsonbut that creates a circular dependency16:28
samuelms_bknudson, yes .. some interesting points .. I ll find some time to think about all this16:34
samuelms_bknudson, unfortunately I don't have a good knowledge on keystone auth .. tokens , federation etc16:34
samuelms_bknudson, I've put all my efforts on roles/assignments/policies16:34
samuelms_bknudson, I see that I have to have more time to study every main part of keystone :)16:35
samuelms_bknudson, and then be able to help more ... even if just having interesting ideas16:35
*** david-ly_ is now known as david-lyle16:37
*** thedodd has quit IRC16:39
*** _cjones_ has joined #openstack-keystone16:39
openstackgerritOpenStack Proposal Bot proposed openstack/python-keystoneclient: Updated from global requirements  https://review.openstack.org/13479416:39
lbragstaddstanek: :)16:40
stevemarlbragstad, go home16:42
*** dims_ is now known as dimsum__16:47
*** gordc has joined #openstack-keystone16:49
openstackgerritIlya Pekelny proposed openstack/keystone: Migrate_repo init version helper  https://review.openstack.org/13764016:52
openstackgerritIlya Pekelny proposed openstack/keystone: Share engine between migration helpers.  https://review.openstack.org/13777816:52
openstackgerritIlya Pekelny proposed openstack/keystone: Add primary key to the endpoint_group id column.  https://review.openstack.org/13763816:52
openstackgerritIlya Pekelny proposed openstack/keystone: Add index to the revocation_event.revoked_at.  https://review.openstack.org/13763916:52
openstackgerritIlya Pekelny proposed openstack/keystone: Explicit MySQL engine designation.  https://review.openstack.org/13871216:52
openstackgerritIlya Pekelny proposed openstack/keystone: Comparision of database models and migrations.  https://review.openstack.org/8063016:52
openstackgerritIlya Pekelny proposed openstack/keystone: Fix index name the assignment.actor_id table.  https://review.openstack.org/13763716:52
openstackgerritIlya Pekelny proposed openstack/keystone: Use metadata.create_all() to fill a test database  https://review.openstack.org/9355816:52
*** thedodd has joined #openstack-keystone16:53
*** bdossant has quit IRC16:53
openstackgerritayoung proposed openstack/keystone: split auth from other services in paste  https://review.openstack.org/13845216:54
lbragstadstevemar: it's not 5 yet!16:55
*** lvh has quit IRC16:57
*** lvh has joined #openstack-keystone16:59
stevemarlbragstad, close enough17:03
lbragstadstevemar: it *is* Friday17:04
marekdstevemar: why do you make him go home?17:04
*** lvh has quit IRC17:05
*** lvh has joined #openstack-keystone17:09
openstackgerritLance Bragstad proposed openstack/keystone-specs: Authenticated Encryption Tokens  https://review.openstack.org/13005017:12
lbragstadayoung: addressed ^17:12
*** Haneef_ has joined #openstack-keystone17:22
openstackgerritMarek Denis proposed openstack/keystone: Identify groups by name/domain in mapping rules.  https://review.openstack.org/13901317:22
*** marekd is now known as marekd|away17:23
*** mikedillion has quit IRC17:24
Haneef_jamielennox:  Who are the consumers of identity endpoint in catalog?. Keystoneclient relies on discovery url (from version) which can be different from catalog endpoint17:24
*** mikedillion has joined #openstack-keystone17:25
*** shakamunyi has quit IRC17:25
openstackgerritMerged openstack/keystone: Adds correct checks in LDAP backend tests  https://review.openstack.org/13855117:31
*** lhcheng has joined #openstack-keystone17:36
*** zzzeek has quit IRC17:37
*** mikedillion has quit IRC17:40
*** zz_avozza is now known as avozza17:42
*** zzzeek has joined #openstack-keystone17:44
*** ayoung has quit IRC17:44
*** jistr has quit IRC17:45
*** tellesnobrega_ has joined #openstack-keystone17:54
*** boris-42 has joined #openstack-keystone17:57
*** amakarov is now known as amakarov_away17:59
*** tellesnobrega_ has quit IRC17:59
*** rwsu has joined #openstack-keystone18:02
*** shakamunyi has joined #openstack-keystone18:07
*** _cjones_ has quit IRC18:11
*** henrynash has joined #openstack-keystone18:16
*** ChanServ sets mode: +v henrynash18:16
*** avozza is now known as zz_avozza18:17
*** zzzeek has quit IRC18:17
*** ayoung has joined #openstack-keystone18:20
*** ChanServ sets mode: +v ayoung18:20
ayoungOK,  I freaken love next-review18:22
*** zzzeek has joined #openstack-keystone18:24
*** gyee has joined #openstack-keystone18:25
*** radez is now known as radez_g0n318:29
*** harlowja_away is now known as harlowja_18:31
*** thedodd has quit IRC18:32
*** amcrn has joined #openstack-keystone18:34
*** gyee has quit IRC18:35
*** gyee has joined #openstack-keystone18:38
*** gyee has quit IRC18:38
*** _cjones_ has joined #openstack-keystone18:38
*** gyee has joined #openstack-keystone18:39
*** ChanServ sets mode: +v gyee18:39
*** shakamunyi has quit IRC18:44
vsilvaping dstanek18:45
vsilvawhat IdP are you using for your federation testing setup?18:45
dstanekvsilva: pysaml218:46
vsilvastevemar, dstanek, marekd|away, I'd love to hear from you any specific things you believe we need to test18:46
*** shakamunyi has joined #openstack-keystone18:46
dstanek1. simple authentication18:47
dstanek2. different mapping constructs18:47
dstanekother than that i'm not really sure18:48
*** shakamunyi has quit IRC18:48
*** zz_avozza is now known as avozza18:49
*** shakamunyi has joined #openstack-keystone18:52
*** _cjones_ has quit IRC18:52
vsilvaall right dstanek18:52
*** _cjones_ has joined #openstack-keystone18:53
*** avozza is now known as zz_avozza18:54
ayounghenrynash, I realize you should be asleep, but...I just tried to do the migration for the endpoint filter and it threw an exception.  I think it might have bitrotted18:55
ayoung2014-12-05 13:54:39.295 11241 TRACE keystone OperationalError: (OperationalError) (1005, "Can't create table 'keystone.project_endpoint_group' (errno: 150)") '\nCREATE TABLE project_endpoint_group (\n\tendpoint_group_id VARCHAR(64) NOT NULL, \n\tproject_id VARCHAR(64) NOT NULL, \n\tPRIMARY KEY (endpoint_group_id, project_id), \n\tFOREIGN KEY(endpoint_group_id) REFERENCES endpoint_group (id)\n)\n\n' ()18:55
*** diegows has joined #openstack-keystone19:01
openstackgerritRodrigo Duarte proposed openstack/keystone: Inherited role assignments to projects  https://review.openstack.org/13855219:01
*** thedodd has joined #openstack-keystone19:04
openstackgerritRodrigo Duarte proposed openstack/keystone: Inherited role assignments to projects  https://review.openstack.org/13855219:09
openstackgerritMerged openstack/keystone: Provide useful info when parsing policy file  https://review.openstack.org/13157419:14
*** mikedillion has joined #openstack-keystone19:17
*** stevemar2 has joined #openstack-keystone19:18
*** ChanServ sets mode: +v stevemar219:18
*** stevemar has quit IRC19:18
*** gothicmindfood has quit IRC19:19
*** lhcheng has quit IRC19:19
samuelms_henrynash, hi19:25
*** gothicmindfood has joined #openstack-keystone19:25
samuelms_henrynash, I've a first version of the domain-role api change19:25
samuelms_henrynash, https://review.openstack.org/#/c/139531/19:25
*** ayoung has quit IRC19:25
*** lhcheng has joined #openstack-keystone19:26
*** raildo has quit IRC19:28
*** afaranha has quit IRC19:28
*** samuelms has quit IRC19:28
*** htruta has quit IRC19:29
*** tellesnobrega has quit IRC19:29
*** packet has joined #openstack-keystone19:31
*** thedodd has quit IRC19:32
*** gyee has quit IRC19:34
henrynashsamuelms_: great!! Will take a look ina while19:35
samuelms_henrynash, I still need to put the other operations a role has .. like granting for domain-roles19:37
samuelms_henrynash, I've to duplicate all of those methods; if we go for not reusing the api calls we've for role19:38
samuelms_henrynash, (we've already started discussing about this)19:38
samuelms_henrynash, an example we have there is adding or removing role/domain-roles to/from a domain-role19:39
samuelms_henrynash, in which we have different calls, and could have one for delete and one for add :p19:39
*** thedodd has joined #openstack-keystone19:41
stevemar2dstanek, pm'ed you the hangout19:48
openstackgerritMerged openstack/pycadf: Workflow documentation is now in infra-manual  https://review.openstack.org/13936719:49
*** marcoemorais has joined #openstack-keystone19:49
*** shakamunyi has quit IRC19:54
*** shakamunyi has joined #openstack-keystone19:59
*** ayoung has joined #openstack-keystone19:59
*** ChanServ sets mode: +v ayoung19:59
*** shakamunyi has quit IRC20:00
*** shakamunyi has joined #openstack-keystone20:01
*** kobtea has joined #openstack-keystone20:05
*** drjones has joined #openstack-keystone20:07
*** radez_g0n3 is now known as radez20:08
*** kobtea has quit IRC20:10
*** _cjones_ has quit IRC20:10
*** drjones has quit IRC20:11
*** marcoemorais has quit IRC20:17
*** samuelms_ has quit IRC20:28
*** Haneef_ has quit IRC20:36
*** marcoemorais has joined #openstack-keystone20:36
*** marcoemorais has quit IRC20:37
*** marcoemorais has joined #openstack-keystone20:37
*** thedodd has quit IRC20:42
*** tellesnobrega_ has joined #openstack-keystone20:43
*** tellesnobrega_ has quit IRC20:43
*** saipandi has joined #openstack-keystone20:46
*** saipandi has quit IRC20:48
*** saipandi has joined #openstack-keystone20:48
*** thedodd has joined #openstack-keystone20:51
*** andreaf has quit IRC20:56
dolphmis everyone watching https://www.youtube.com/watch?v=Th61TgUVnzU ?20:56
*** shakamunyi has quit IRC20:59
*** mikedillion has quit IRC21:03
*** _cjones_ has joined #openstack-keystone21:04
*** _cjones_ has quit IRC21:05
*** _cjones_ has joined #openstack-keystone21:05
*** ajayaa has quit IRC21:05
*** shakamunyi has joined #openstack-keystone21:06
*** andreaf has joined #openstack-keystone21:07
*** saipandi has quit IRC21:08
ayoungdstanek, your workplace looks pretty ghetto.21:08
dolphmayoung: that's detroit in the background21:11
dstanekayoung: that back you were looking at was all of my shelves with raspberry pi and arduino components21:12
dstanekand my new crappy dell laptop was up there21:13
ayoungstevemar2, good job filling in21:14
stevemar2ayoung, i lol'ed at your ghetto workspace comment, poor dstanek21:15
dstanekstevemar2: me too :-)21:15
dstanekstevemar2: you did fantastical and sdague makes it feel relaxed21:16
ayoungstevemar2, it still looks more humane than the sterile THX1138 environment IBM has you working in21:16
stevemar2ayoung, i was at home21:16
Qlawydisagree21:16
Qlawymy workplace is not sterile in IBM oO21:16
openstackgerritBrant Knudson proposed openstack/keystone: Internal notifications for cleanup domain  https://review.openstack.org/12552121:16
stevemar2ayoung, but that does describe my home, so thats fair21:16
openstackgerritLance Bragstad proposed openstack/keystone-specs: Authenticated Encryption Tokens  https://review.openstack.org/13005021:17
henrynashrodigods: have added more comments to https://review.openstack.org/#/c/138552/21:17
*** marcoemorais has quit IRC21:17
*** marcoemorais has joined #openstack-keystone21:18
dstanekayoung: i should do a video cast of my home automation projects21:18
dolphmdstanek: and have sdague host?21:19
dstanekdolphm: yes!21:19
stevemar2that would be good21:19
*** stevemar2 is now known as stevemar21:19
dstaneki've been working on stuff inspired from http://lifehacker.com/build-an-entire-home-automation-system-with-a-raspberry-164084496521:20
dolphmdstanek: what have you accomplished on that front?21:24
dstanekdolphm: i have the software running on the pi and a few radios talking back to it; the only sensor i have hooked up at at is the temp one because it was easy21:25
dolphmdstanek: i'd love to tie my security system together with my nest. like if my nest thinks i'm away for a couple hours and the alarm isn't set, then arm it. or if i arm the alarm for away mode, then set the nest in away mode, etc21:25
*** jsavak has joined #openstack-keystone21:25
dstanekdolphm: that would be a neat idea21:25
openstackgerritBrant Knudson proposed openstack/keystone: Move eventlet server options to a config section  https://review.openstack.org/13096221:25
dstanekdolphm: i decided to use xbee radios instead of the ones they use in the tutorial mostly because the price to learning tradeoff made sense21:26
ayoungdstanek, I need to do something to get the music more distributed around the house21:26
dolphmayoung: i use airfoil for that21:27
dolphmayoung: although i only have two soundsystems to sync together21:27
dstanekthere is this guy in Australia that completely rewired his house with automation in mind - he has inspired me to say the least21:27
*** joesavak has quit IRC21:28
stevemarahh man i sound awful, i should have gotten closer to the mic21:28
*** joesavak has joined #openstack-keystone21:28
stevemardammit, dstanek sounds fine21:28
*** toddnni has quit IRC21:28
dolphmstevemar: you need a better mic21:28
dolphmstevemar: http://www.modmic.com/21:29
dstanekthis dude is amazing: https://www.youtube.com/watch?v=ZUEKr_48EfQ&list=UU75HTMhqVZs0sPOMTMQqI9g21:29
openstackgerritBrant Knudson proposed openstack/keystone: Correct max_project_tree_depth config help text  https://review.openstack.org/13973621:29
*** jsavak has quit IRC21:30
stevemardstanek, dolphm i still sound better than mriedeman21:30
ayoungYou spent a long time on token formats21:31
dolphmdstanek: *watching*21:32
*** toddnni has joined #openstack-keystone21:32
*** packet has quit IRC21:37
*** boris-42 has quit IRC21:37
ayounglbragstad, have you tried signing an AE token with RSA and seeing what the size difference ends up being?21:38
*** hdd has joined #openstack-keystone21:38
stevemarayoung, that was unexpected21:39
stevemarayoung, we started off on that topic, and kept going... next thing i know, i look down and it's 20 past21:40
ayoungheh21:40
ayounggood thing I wasn't there...would have gone of forever21:40
ayoungexpiration question was  interesting...21:42
*** hdd has left #openstack-keystone21:42
stevemarwell, i am outta here, see you all on the 15th21:42
morganfainbergzzzeek: I realize I have like 4 fixes for dogpile I need to respin and submit pull requests for >.<21:42
stevemarstaycation time!21:42
zzzeekmorganfainberg: OK, I’ve been super lazy about dogpile and there’s a bunch of PRs ive been sitting on21:42
morganfainbergstevemar: that isn't allowed! :P. Gonna tell uncle Topol! Have a good one dude.21:43
ayoungstevemar, enjoy.  Good work21:43
morganfainbergzzzeek: yeah, there isn't a lot "wrong". I just know some QOL stuff is still outstanding. Not critical at all.21:43
morganfainbergDogpile has been... Well... Pretty damn good.21:44
*** redcup1 has joined #openstack-keystone21:45
morganfainbergayoung: if i swing through the north east, I'm going to bug you about food / drinks in your neck of the woods.21:45
ayoungmorganfainberg, I was trying to figure out how to do a default policy file.  I figure the client should always request for a specific endpoint.  The endpoint_policy should do:  endpoint, fallback to service, fallback to default.21:46
ayoungI kindof want it all in the database, no config option21:46
morganfainbergayoung: looks like it *might* happen (have some friends in Maine I need to visit and all trips go through Boston with looooong layovers)21:46
ayoungmorganfainberg, let me know when...21:46
*** stevemar has quit IRC21:47
morganfainbergayoung: I would agree, in principle. Let me think for a moment.21:47
lbragstadayoung: I haven't21:47
lbragstadjust the AES stuff that dolphm prototyped21:48
dolphmdstanek: that guy's house runs on php21:48
ayounglbragstad, I'm not certain if it would be usable, but I'd be interested in knowing the impact21:48
morganfainbergdolphm: I hear scary words coming from you. Mostly php being in there.21:48
ayoungit would minimize our key management21:48
dstanekdolphm: when he talked about light switches POSTing to the central switch service my mouth started to water21:48
lbragstadayoung: I added a bunch of stuff around using keyCzar21:49
dolphmdstanek: that's right at about 10 minutes. i went back and watch that bit again.21:49
ayounglbragstad, I know, which is what made me think about it.21:49
dstanekdolphm: when he talked about upgrading and rebooting his house i decided that level of automation is not for me21:49
dolphmdstanek: lol21:49
morganfainbergSo, I think this can be an either-or. And the db could have a "default" rule set that is applied.21:49
morganfainbergayoung: ^^. So, either config file *or* db, but no fall through.21:50
ayoungmorganfainberg, right.  Why I said I want it in the DB is there is an oredering issue.  You need to upload the policy, which assignes the ID,  then you would ned to updatre the confoig file and restart Keystone to pick up the change21:50
morganfainbergFall through could pose "interesting" and unintentional side effects.21:50
dolphmdstanek: "honey, i'm rebooting the house because of a critical security vulnerability in the kernel! stay in one room until the lights stop flickering, okay?!"21:50
morganfainbergayoung: make the ID deployer definable.21:51
ayoungmorganfainberg, I'd like to make the ID the SHA256 hash of the file21:51
ayoungreassigning IDs is something I feel queasy about21:52
morganfainbergayoung: why? I don't disagree but step me through the logic behind sha25621:52
dstanekdolphm: that guys uses ethernet, but since i'm not planning on ripping my house apart i'm just using xbees21:52
morganfainbergI *do* have a thought, but it is an extra web request.21:52
morganfainbergdstanek: that the power line networking?21:53
dstanekmorganfainberg: no he's using real ethernet and i think PoE21:53
ayoungmorganfainberg, policy is security sensitive.  I could see a policy file being audited, and being able to run the sha256 is a valudlate "nothing has changed check"21:53
ayoungby making the ID the SHA we don't have to do a separate distribution for the sha21:54
morganfainbergayoung: ok so we would need an abstraction to make it friendly. The SHA as the ID is just not friendly to configure.21:56
morganfainbergI'm not opposed to using that for verification purposes.21:56
dstanekmorganfainberg: the opposite - sending power over ethernet21:56
morganfainbergdstanek: right. Poe.21:57
morganfainbergGot it. Misread earlier.21:57
ayoungjust a thought, but I still don't like the user setting the ID.  It seems to me that it is something that should be in the database, just strange to have a whole table for a single value21:57
dstanekmorganfainberg: i tried the do-it-yourself version and it didn't go well21:57
*** gordc has left #openstack-keystone21:57
morganfainbergHeh21:57
dstanekmorganfainberg: got a nice shock and tripped the breaker21:57
openstackgerritLance Bragstad proposed openstack/keystone-specs: Authenticated Encryption Tokens  https://review.openstack.org/13005021:58
morganfainbergayoung: maybe store the sha and history of when it changed?21:58
ayoungmorganfainberg, it seems to me that default policy if is something we should be able to deduce from the database.  Maybe it makes sense to put an ordering column on the endpoint_poicy table, and you select the lowest number that meets your criteria, with the default being a really high number and no criteria?21:59
ayoungI know that idea sucks, but there is a kernel in there somewhere21:59
morganfainbergSec. Switching to desktop from phone.22:00
morganfainbergok so..22:00
*** diegows has quit IRC22:00
morganfainbergsure, a rule ordering thing seems sane22:00
morganfainbergit doesn't suck that badly actually22:00
ayoungwould there be any real use for it besided deducing the default?22:01
*** marcoemorais has quit IRC22:01
morganfainbergnah, there really isn't i guess22:01
*** marcoemorais has joined #openstack-keystone22:01
*** marcoemorais has quit IRC22:01
ayoungI mean, we could have a "default" flag, but that seems dumb,  as only one row would ever need default22:01
ayounglooking at the table, it has22:01
*** marcoemorais has joined #openstack-keystone22:01
*** marcoemorais has quit IRC22:02
*** _cjones_ has quit IRC22:02
*** marcoemorais has joined #openstack-keystone22:02
ayoungpolicy_id endpoint_id service_id region_id22:03
*** gyee has joined #openstack-keystone22:03
*** ChanServ sets mode: +v gyee22:03
ayoungif you just had all of those values empty, you have the default policy22:04
ayoungand we should probably have a constraint saying that a combination of all those columns needs to be unique22:04
openstackgerritLance Bragstad proposed openstack/keystone-specs: Authenticated Encryption Tokens  https://review.openstack.org/13005022:04
ayoungdoes that work?  default policy is the one with only id and policy_id set?22:04
ayoungOK...need to go be a dad.  morganfainberg tell me if ^^ makes sense to you.  I think it does to me...22:05
morganfainbergayoung, hm22:12
*** zz_avozza is now known as avozza22:15
*** avozza is now known as zz_avozza22:19
dolphmmorganfainberg: dear PTL, https://review.openstack.org/#/c/131007/ or https://review.openstack.org/#/c/130013/ which would win in a fight? thanks.22:28
*** andreaf has quit IRC22:29
* morganfainberg takes a gander and gets ready to place bets.22:29
notmynamehttp://www.googlefight.com/index.php?lang=en_GB&word1=131007&word2=13001322:30
*** zz_avozza is now known as avozza22:30
morganfainbergnotmyname, hehheh22:30
morganfainbergdolphm, i'm inclined to say the discussion was deprecate the hell out of that functionality.22:32
morganfainbergdolphm, but i guess we need some kind of subst from the config?22:32
morganfainbergdolphm, ah i see what is going on.22:33
morganfainberghm.22:33
morganfainbergdolphm, also "compute_port" was something that needed to be completly removed...22:35
morganfainbergoh L release22:35
morganfainbergbah22:35
*** _cjones_ has joined #openstack-keystone22:36
morganfainbergdolphm, commented. Removal is my first choice, but didn't approve *yet*. Leaving open for comments for a bit in case there is a strong argument to keep the whitelist option around.22:39
*** avozza is now known as zz_avozza22:41
openstackgerritBrant Knudson proposed openstack/keystone: Remove endpoint_substitution_whitelist config option  https://review.openstack.org/13100722:47
*** r-daneel has quit IRC22:49
*** joesavak has quit IRC22:58
*** joesavak has joined #openstack-keystone22:58
*** shakamunyi has quit IRC23:01
openstackgerritMerged openstack/keystone-specs: Workflow documentation is now in infra-manual  https://review.openstack.org/13933323:03
openstackgerritMerged openstack/keystone-specs: Fix 'heirarchy' typo on 'Get project'  https://review.openstack.org/13953623:04
*** redcup1 has quit IRC23:13
*** joesavak has quit IRC23:19
*** boris-42 has joined #openstack-keystone23:21
*** henrynash has quit IRC23:24
*** rwsu has quit IRC23:24
*** jorge_munoz has quit IRC23:27
*** thedodd has quit IRC23:30
*** marcoemorais has quit IRC23:33
*** marcoemorais has joined #openstack-keystone23:34
*** kobtea has joined #openstack-keystone23:42
*** kobtea has quit IRC23:47
*** _cjones_ has quit IRC23:52
*** henrynash has joined #openstack-keystone23:55
*** ChanServ sets mode: +v henrynash23:55
*** _cjones_ has joined #openstack-keystone23:57

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