Saturday, 2014-03-01

ayoungmorganfainberg, I was just looking at that.  I think the logic there is wrong00:06
ayoungit fetches the roles out of the backend, which means if the roles change between token creation and conversion, you would get different values.  It pre-supposed revoke_by_id semantics00:07
ayoungmorganfainberg, you know how you asked to see what the dictionary looks like for 'is_revoked"00:07
ayoungtoken_data dictionary00:07
morganfainbergayoung, aye00:07
ayoungits built in the Provider code...00:08
morganfainbergayoung, ah.00:08
ayoungand I don't like it00:08
morganfainbergayoung, hey this is why i ask these questions ;)00:08
ayounglink in a sec00:08
morganfainbergayoung, cool.00:08
ayounghttps://review.openstack.org/#/c/55908/63/keystone/token/provider.py  line 11800:09
ayoungfor v2 (which has a bug I found)00:09
ayoungand then line 16200:09
ayoungNow...I know what you are thinking:00:09
ayoungseems wrong to not just pass in the token....00:09
morganfainbergayoung, yeah.00:09
ayoungI would need to do "flatten"00:10
morganfainbergayoung, but if that is the way we need to do it (only good option atm), so be it...00:10
ayoungbut I really don';t like that the v2 and v3 code paths are different00:10
morganfainbergflatten would be, imo, a bit cleaner00:10
morganfainbergbut i can see where that might be icky00:10
morganfainbergayoung, ++00:10
ayoungyeah, icky00:10
morganfainbergayoung, i really want to see that "problem" go away00:10
ayoungI want to see v2 tokens go away, too00:10
morganfainbergayoung, might need to wait until K to "really" be resolved (bye bye v2)00:10
ayoungI suspect we could issue nothing be v3 tokens and be fine00:11
ayoungnothing *but*00:11
morganfainbergactually...00:11
morganfainbergmaybe that is the real fix.00:11
morganfainbergoption "only issue v3 tokens"00:11
ayoungyep00:12
morganfainbergrevocation events require that, same as PKI00:12
morganfainbergayoung, this might make things too easy ... :P00:12
ayoungnot really...this logic works...but I need to do more testing...I think I need to have a set of data, and do "v2 token is revoked " and "v3 data is revoked"00:12
ayoungdolphm, can we stop issuing v2 tokens?00:13
ayoungactually, we really can't00:13
ayoungsince the token data is what is returned from the validate call, there might be 3rd party apps using that data00:13
morganfainbergno, we can't well not unless we make it an optional thing00:13
morganfainbergcorrect00:13
ayoungok, not to be solved today00:14
ayoungI don';t think I'm going to do "flatten" here either...but I might when I port this code to the client00:14
ayoungcuz auth token is going to need it00:14
ayoungso this just needs to work.00:14
morganfainbergayoung, fair enough00:15
morganfainbergayoung, maybe in J we offer an "issue v3 only option" to help people transition more cleanly00:15
ayoung++00:15
morganfainbergeven if they still use some V2 keystone api calls00:15
morganfainbergayoung, sounds good to me00:15
ayoungmorganfainberg, we need the v2 v3 interop from the client we talked about.  Then transition should be straightforward.  Did that make it in?00:16
morganfainbergayoung, no, think thats going to be J00:16
ayoungNo the client fix is not aligned with Ice00:16
morganfainbergayoung, ooh00:16
morganfainbergayoung, uhm.00:16
morganfainbergayoung, not sure.00:16
* ayoung looks00:17
ayounghttps://review.openstack.org/#/c/75731/00:18
morganfainbergoh that change is pretty simple00:19
ayoungmorganfainberg, ^^ is the simplest hack to make it work00:19
morganfainbergyeah00:19
ayounglogic looks a touch convoluted even for a simple patch like that00:19
ayounglooks like there is a loophole in there where hasattr(self, '_management_url'):  is true but _management_url is None00:20
ayoungneeds to and those two checks together00:21
*** krsna has quit IRC00:30
*** gokrokve_ has quit IRC00:32
*** david-lyle has joined #openstack-keystone00:41
*** gokrokve has joined #openstack-keystone00:41
*** browne1 has quit IRC00:52
*** richm has quit IRC00:55
*** gokrokve has quit IRC00:56
*** ayoung has quit IRC01:01
*** ayoung has joined #openstack-keystone01:08
*** devlaps1 has joined #openstack-keystone01:20
*** devlaps has quit IRC01:21
*** devlaps1 has quit IRC01:22
*** devlaps has joined #openstack-keystone01:23
*** devlaps has quit IRC01:23
*** ChanServ sets mode: +o dolphm01:33
*** achampion has joined #openstack-keystone01:43
*** gokrokve has joined #openstack-keystone01:46
*** lnxnut has joined #openstack-keystone02:10
*** lnxnut has quit IRC02:52
*** lnxnut has joined #openstack-keystone02:55
*** marcoemorais has quit IRC03:00
*** dolphm is now known as dolphm_50303:00
*** devlaps has joined #openstack-keystone03:03
*** devlaps has quit IRC03:28
*** amcrn has quit IRC03:29
*** lbragstad has joined #openstack-keystone03:31
*** dolphm_503 is now known as dolphm03:39
*** dolphm is now known as dolphm_50303:52
*** lnxnut has quit IRC04:18
*** lnxnut has joined #openstack-keystone04:22
*** harlowja is now known as harlowja_away04:31
*** dolphm_503 is now known as dolphm04:43
*** chandan_kumar has joined #openstack-keystone04:48
*** wchrisj has quit IRC04:49
ayoungmorganfainberg, any chance you are around and can help me with a dogpile question?  I need to use it to syncronize the revoke tree04:51
morganfainbergayoung, hehe sure04:51
ayoungso...04:51
ayounghttps://review.openstack.org/#/c/55908/63/keystone/contrib/revoke/core.py04:52
ayoungline 17904:52
* morganfainberg is unfortunately not out having a drink yet, but fortunately able to help04:52
* ayoung had scotch hours ago...04:52
morganfainbergi might pour some of the cognac here that is on my desk04:52
ayoungI think this is last thing before I can repost.04:52
morganfainbergbut i'm debugging some sql migrate issues *production*04:52
morganfainbergand.04:53
ayoungNoice!04:53
morganfainbergi might need a new phone now04:53
morganfainbergsigh04:53
ayoungouch04:53
morganfainbergjust poured coffee all over my desk and phone04:53
morganfainberg*sigh*04:53
ayounganyway...if I want to use dogpile to syncronize the built Revoke Tree between greenthreads,  what should I look at as an example04:54
morganfainberghmm04:54
morganfainbergkvs is sufficient yes?04:54
morganfainbergin-mem that is04:54
morganfainbergbrb getting towel04:55
*** dolphm is now known as dolphm_50304:55
morganfainbergok back04:57
ayoungOoh, that just happend?  I thought you were talking about something that happened earlier tonight.04:57
ayoungSorry04:57
ayoungkvs...sufficient to start.04:57
morganfainbergno i mean i went to type and poured coffee on myself.04:58
ayoungprobably should be memcached also in the future04:58
morganfainbergyou could probably just use the same backend you're using for the events04:58
ayoungnope04:58
morganfainbergjust use another key04:58
morganfainbergwrap in a lock04:58
morganfainbergno?04:58
ayoungthey might be stored in sql04:58
morganfainbergoh oh04:59
morganfainbergright04:59
morganfainberghmm.04:59
morganfainbergsame mechanics as you're doing now, probably not configurable to begin with04:59
ayoungnot sure how cleanly they are going to serialize....04:59
morganfainbergjust hard set openstack.kvs.memory as the driver04:59
morganfainbergthis is a case where i wish we could toggle off the copy mechanism in that backend05:00
ayoungwith kvs, it just stores python objects, right?  No serialization?05:00
morganfainbergcorrect05:00
ayounghmmm05:00
morganfainbergit's an in-memory dict05:00
morganfainbergbut get/set does a copy.deepcopy05:00
morganfainberglet me check something05:00
ayoungOK...I can do that...probably will wait until tomorrow05:00
morganfainbergyou should eb able to use dogpile.memory.MemoryBackend05:01
morganfainbergit wont do copy/deepcopy so changes will affect the cached values05:01
morganfainbergbut you can still use the locking semantics i added to the keystone kvs stuff05:02
morganfainbergit _should_ work, but i haven't tested it extensively with greenthreads/threading05:02
morganfainbergit relies on threading.lock which iirc is patched05:03
ayoungI'll write it up and post...its pretty simple, I think05:05
ayoungOooh...I need to be able to overide the backing store for Event storage...any reason not do open it up to storage other than In Memory?05:06
morganfainbergayoung, hm. nah. it's just for syncronization between greenthreads05:07
morganfainbergi don't think it'll make a huge difference/benefit to share outside / across processes05:07
ayoungfor events, it will be the actual backing store...I would like to get persistance05:07
morganfainbergayoung, right. which you will get with Redis or mongo or whatever05:08
morganfainbergand yes that should be configurable05:08
ayoungfor the tree...I'll leave that to later, but I might make it a config option as well.  It might be useful for Apache based, to not have to rebuild the tree everytime05:08
morganfainbergbut i don't see a need to make the tree part more than in-mem05:08
ayoungso memcached too05:08
morganfainbergaye memcached is... ok05:08
morganfainberg:P05:08
*** wchrisj__ has joined #openstack-keystone05:16
ayoungdagnabit...just using the cache buys me nothing unless I copy05:20
ayoungOk..headed to bed...I need to think about this.05:20
*** stevemar has joined #openstack-keystone05:42
*** ChanServ sets mode: +v stevemar05:42
*** dolphm_503 is now known as dolphm05:46
*** dolphm is now known as dolphm_50305:56
*** chandan_kumar has quit IRC06:01
*** chandan_kumar has joined #openstack-keystone06:13
*** marcoemorais has joined #openstack-keystone06:19
*** wchrisj__ has quit IRC06:22
*** chandan_kumar has quit IRC06:28
*** chandan_kumar has joined #openstack-keystone06:40
*** dstanek has quit IRC06:46
*** dolphm_503 is now known as dolphm06:47
*** chandan_kumar has quit IRC06:48
*** dolphm is now known as dolphm_50306:56
*** chandan_kumar has joined #openstack-keystone06:58
*** stevemar has quit IRC06:59
*** chandan_kumar has quit IRC07:22
*** dolphm_503 is now known as dolphm07:47
*** marcoemorais1 has joined #openstack-keystone07:50
*** marcoemorais has quit IRC07:50
*** dolphm is now known as dolphm_50307:57
*** marcoemorais1 has quit IRC08:00
*** morganfainberg is now known as morganfainberg_Z08:33
*** gokrokve has quit IRC08:38
*** gokrokve_ has joined #openstack-keystone08:41
*** gokrokv__ has joined #openstack-keystone08:43
*** gokrokve_ has quit IRC08:45
*** dolphm_503 is now known as dolphm08:48
*** dolphm is now known as dolphm_50308:58
*** david_lyle_ has joined #openstack-keystone09:10
*** david-lyle has quit IRC09:13
*** david-lyle has joined #openstack-keystone09:13
*** david_lyle_ has quit IRC09:15
*** gokrokv__ has quit IRC09:17
*** gokrokve has joined #openstack-keystone09:48
*** dolphm_503 is now known as dolphm09:49
*** gokrokve_ has joined #openstack-keystone09:49
*** chandan_kumar has joined #openstack-keystone09:50
*** gokrokve has quit IRC09:52
*** dolphm is now known as dolphm_50309:59
*** chandan_kumar has quit IRC10:02
*** david_lyle_ has joined #openstack-keystone10:19
*** david-lyle has quit IRC10:23
*** chandan_kumar has joined #openstack-keystone10:24
*** dolphm_503 is now known as dolphm10:50
*** dolphm is now known as dolphm_50311:00
*** chandan_kumar has quit IRC11:36
*** dolphm_503 is now known as dolphm11:50
*** chandan_kumar has joined #openstack-keystone11:53
*** dolphm is now known as dolphm_50312:00
*** chandan_kumar has quit IRC12:38
*** dolphm_503 is now known as dolphm12:51
*** dolphm is now known as dolphm_50313:01
*** dstanek has joined #openstack-keystone13:33
*** ChanServ sets mode: +v dstanek13:33
*** dolphm_503 is now known as dolphm13:35
*** dolphm is now known as dolphm_50314:17
*** dstanek has quit IRC14:22
*** dstanek has joined #openstack-keystone14:36
*** ChanServ sets mode: +v dstanek14:36
*** dolphm_503 is now known as dolphm14:36
*** lnxnut has quit IRC14:58
*** lnxnut has joined #openstack-keystone15:04
*** dolphm is now known as dolphm_50315:05
*** dolphm_503 is now known as dolphm15:25
*** lnxnut has quit IRC15:27
*** dstanek has quit IRC15:28
*** lnxnut has joined #openstack-keystone15:35
*** dolphm is now known as dolphm_50315:37
*** lnxnut has quit IRC15:39
*** dolphm_503 is now known as dolphm15:56
*** dstanek has joined #openstack-keystone16:28
*** ChanServ sets mode: +v dstanek16:28
*** lnxnut has joined #openstack-keystone16:35
*** lnxnut has quit IRC16:40
*** dolphm is now known as dolphm_50316:40
*** lnxnut has joined #openstack-keystone17:00
*** wchrisj has joined #openstack-keystone17:22
*** wchrisj has quit IRC17:26
*** nkinder has quit IRC17:26
*** wchrisj has joined #openstack-keystone17:28
*** wchrisj has quit IRC17:31
*** dolphm_503 is now known as dolphm17:35
*** marcoemorais has joined #openstack-keystone17:35
*** marcoemorais has quit IRC17:39
*** gokrokve_ has quit IRC17:43
*** gokrokve has joined #openstack-keystone17:43
*** thedodd has joined #openstack-keystone17:49
*** lnxnut has quit IRC17:52
*** lnxnut has joined #openstack-keystone17:53
*** lnxnut has quit IRC18:20
*** lnxnut has joined #openstack-keystone18:21
*** lnxnut has quit IRC18:21
*** lnxnut has joined #openstack-keystone18:22
*** lnxnut has quit IRC18:26
*** wchrisj has joined #openstack-keystone18:39
*** wchrisj has quit IRC18:48
*** leseb has joined #openstack-keystone18:50
*** wchrisj has joined #openstack-keystone18:56
*** ayoung has quit IRC18:59
*** dolphm is now known as dolphm_50319:00
*** wchrisj has quit IRC19:06
*** leseb has quit IRC19:08
*** dolphm_503 is now known as dolphm19:20
*** lnxnut has joined #openstack-keystone19:23
*** leseb has joined #openstack-keystone19:24
*** leseb has quit IRC19:24
*** lnxnut has quit IRC19:27
*** dolphm is now known as dolphm_50319:29
*** lnxnut has joined #openstack-keystone19:35
*** lnxnut has quit IRC19:40
*** topol has joined #openstack-keystone20:04
*** topol_ has joined #openstack-keystone20:06
*** topol has quit IRC20:09
*** topol_ is now known as topol20:09
*** topol has quit IRC20:20
*** dolphm_503 is now known as dolphm20:20
*** leseb has joined #openstack-keystone20:22
*** lnxnut has joined #openstack-keystone20:35
*** rwsu has quit IRC20:40
*** lnxnut has quit IRC20:40
*** ayoung has joined #openstack-keystone20:45
*** leseb has quit IRC20:51
*** dolphm is now known as dolphm_50320:58
*** thedodd has quit IRC21:05
*** leseb has joined #openstack-keystone21:18
*** wchrisj has joined #openstack-keystone21:34
*** lnxnut has joined #openstack-keystone21:35
*** lnxnut has quit IRC21:40
*** leseb has quit IRC21:43
*** leseb has joined #openstack-keystone21:44
*** leseb has quit IRC21:48
*** dolphm_503 is now known as dolphm21:49
*** wchrisj has quit IRC21:54
*** dolphm is now known as dolphm_50321:58
*** leseb has joined #openstack-keystone22:09
*** dolphm_503 is now known as dolphm22:14
*** dolphm is now known as dolphm_50322:17
*** ayoung has quit IRC22:20
*** dolphm_503 is now known as dolphm22:27
*** ayoung has joined #openstack-keystone22:33
*** lnxnut has joined #openstack-keystone22:35
*** lnxnut has quit IRC22:40
*** dolphm is now known as dolphm_50323:29
*** dolphm_503 is now known as dolphm23:30
*** lnxnut has joined #openstack-keystone23:35
*** leseb has quit IRC23:39
*** dolphm is now known as dolphm_50323:39
*** leseb has joined #openstack-keystone23:39
*** lnxnut has quit IRC23:40
*** leseb has quit IRC23:44
*** leseb has joined #openstack-keystone23:44
*** dolphm_503 is now known as dolphm23:49
*** dolphm is now known as dolphm_50323:59
*** leseb has quit IRC23:59

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