18:01:57 #startmeeting 18:01:58 Meeting started Tue Jun 26 18:01:57 2012 UTC. The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:09 ola all - 18:02:16 #topic milestone progress 18:02:27 (even if all is rafael) 18:02:53 We're coming up on the milestone 2 release 18:02:56 #link https://launchpad.net/keystone/+milestone/folsom-2 18:03:16 There's a pile of pending code reviews. dolphm, termie - could use some time getting reviews in please 18:03:50 https://review.openstack.org/#/c/6875/ this really needs to be reviewed, it's holding up a loooong list of bugs 18:04:06 #link https://review.openstack.org/#/q/status:open+keystone,n,z 18:04:06 not to mention all the ones i've closed as dupes :( 18:04:28 dolphm: I've pinged termie since he commented on it earlier. Are you nearby to him? 18:04:39 nope 18:04:40 (i.e. can you throw something at him to review it) 18:04:50 Ok - I'll get some others in on the review 18:06:30 dolphm: I think https://review.openstack.org/#/c/8272/ could use your eyes, which appears to be dependent so that https://review.openstack.org/#/c/8170/ can flow thru after 18:06:31 o/ 18:06:40 ola lzyeval 18:07:02 ayoung isn't going to be able to make it, but wanted to share status update on the PKI work too 18:07:09 #link ayoung's progress report: https://gist.github.com/2997212 18:07:43 Any new/hot/burning/oh-shit-it's-breaking issues come up recently or hitting anyone's plate? 18:07:57 (other than Dolph's change, which is just pending another +2) 18:08:21 I hope the import ordering is clear with everyone 18:08:30 * heckj notes that github changed their formatting again 18:08:38 lzyeval: I think it's all good to go now 18:09:07 formatting for what? 18:09:31 dolphm: ordering of imports 18:09:44 github formatting? 18:10:00 (what does github have to do with import statements?) 18:10:06 lzyeval: github just changed their UI again - always leaves me slightly uneasy when they do it. 18:10:17 non-sequiter 18:10:25 * heckj is guilty of confusing 18:10:42 heckj: i don't see anything significantly different 18:11:24 dolphm: irrelevant to keystone, but look at the pull requests today. They're notably different, showing commit messages in the discussion view 18:11:47 heckj: ah, ok 18:14:01 Er, well - that's all I really had right now. 18:14:12 #topic open questions 18:14:19 heckj: swift keystone middleware 18:14:24 status? 18:14:35 chmouel has a pull request/git review in flow for you now. 18:14:38 I think chmouel may have started working on it on the swift side 18:14:48 I added you as a specific reviewer to it 18:14:53 notmyname ^ 18:15:10 ya, I've been a little behind on reviews lately 18:15:32 anything needed from us on your side? 18:15:43 are you waiting for it to land in swift before pulling it from keystone? 18:15:46 notmyname: found it: https://review.openstack.org/#/c/8748/ 18:15:47 (that would make senes) 18:15:47 #link https://review.openstack.org/#/c/8748/ 18:15:55 notmyname: yes 18:16:04 heckj: ok 18:16:06 (waiting for it to land before removing it) 18:16:16 tentative date for next swift release is july 16 18:16:34 notmyname: reviews for https://review.openstack.org/#/c/8748/ is what we need current help with 18:16:34 so we'll try to get it merged in the next week and a half to make it for QA testing 18:16:41 excellent, thank you 18:18:14 after some time off, I'm working again on the bp improve-keystone-security 18:18:27 # link https://blueprints.launchpad.net/keystone/+spec/improve-keystone-security 18:18:56 i'm focusing on just the rate limiting, since work so far was useless 18:19:54 can we rename that blueprint to something more specific? 18:20:09 yeah, no problem 18:20:09 it's a pretty broad title as-is 18:20:52 what about just "keystone-rate-limiting"? 18:21:22 rafaduran: trying to recall.. are you doing it in middleware? 18:21:53 dolphm: yes, an extension and a middleware 18:22:29 cool (and yeah, that's a much better title) 18:22:38 ++ 18:22:41 dolphm: the extension just provides a method to check current limits for a user and the middleware does the heavy work 18:23:08 rafaduran: are you doing the feature work in a branch somewhere that's public? 18:23:28 I've been helping everett w/ an extension to enable quota data in keystone - wanted to see how you were approaching it as well. 18:23:46 trying to write dev docs on "how to make an extension and/or plugin to Keystone" 18:24:07 heckj: not yet, I've just starting, since as I said I couldn't work on this last weeks 18:24:44 no worries - as you get into it, let me know. 18:25:23 heckj: the monitoring middleware thing i wrote might be a good example of that 18:25:31 I will push changes to github until I've got something to review 18:25:38 #link https://github.com/rafaduran/keystone/tree/bp/improve-keystone-security 18:25:51 dolphm: thanks 18:25:55 thought, I will rename the branch 18:25:55 rafaduran: thanks 18:26:02 no worries, I'll keep an eye 18:26:04 heckj: keystone.contrib.stats 18:28:02 dolphm: is that in master 18:28:50 heckj: ah, sorry https://review.openstack.org/#/c/8550/ 18:29:16 Ah - I recall seeing that now. Not in yet? 18:29:36 Another to add to the list to get others reviewing 18:29:42 heckj: I've written an extension for my company too, you might want check it too 18:29:48 #link https://github.com/bvox/keystone-bvox-extension 18:30:11 heckj: it got some good feedback, but nothing that i think should prevent a merge -- mostly suggestions for additional features / backends 18:31:36 Anything else for keystone? 18:31:48 (if it's all good for you guys, I'll end this meeting - as I need to run) 18:33:08 cool me too lol 18:35:05 #endmeeting