18:00:19 #startmeeting keystone-meeting 18:00:20 Meeting started Tue Feb 14 18:00:19 2012 UTC. The chair is jsavak. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:35 anyone else here for keystone meeting? 18:00:53 #link agenda and meeting notes: http://wiki.openstack.org/Meetings/KeystoneMeeting 18:01:18 #link essex 4 bp and bugs: https://launchpad.net/keystone/+milestone/essex-4 18:01:47 #topic Status and Progress 18:02:17 All looks ok on https://launchpad.net/keystone/+milestone/essex-4 but I admit I've been out of the loop recently... 18:03:08 hey 18:03:13 hi termie 18:03:17 jsavak, I've only been working on LDAP support. My current code is on https://github.com/admiyo/keystone/tree/ldap2 18:03:34 we're currently trying to finish the merge across, we ran into jenkins bugs last night that have resolved into some new bug 18:03:35 I'm feeling pretty good about it, have something ready for code review shortly 18:03:56 #link ldap support being worked on by ayoung https://github.com/admiyo/keystone/tree/ldap2 18:03:57 but the outstanding code in merge proposals is the required stuff for us to merge across legacy 18:05:01 ok cool. Quick convo with a few people resulted in the abandon of #link https://review.openstack.org/#change,3985 which was a 401/403 disabled-user change 18:05:18 the review has a few links to explain why the change was abandoned 18:05:57 termie - so the merge will still happen ok by end of e4? 18:06:10 jsavak: the merge should happen today 18:06:19 termie thanks! 18:06:48 any other status updates? 18:07:10 looks like we covered some of #topic Keystone Light Progress (redux branch) 18:07:19 #topic Keystone Light Progress (redux branch) 18:07:25 anything else for KSL progress? 18:08:10 #topic Open-Discussion 18:08:31 any issues, questions, complaints, asks? 18:08:47 i've been -2ing anything aimed at master and asking them to use redux instead 18:09:00 who's been pushing against master? 18:09:14 jsavak: various code reviews come in 18:09:44 they'll be able to push to master again post merge though (tomorrow), right? 18:10:35 jsavak: yes, though not with any of the existing reviews, obviously, since the code base is radically different 18:10:53 jsavak: my statement was only meant to say i am preventing work being done before the erge 18:11:11 so if somebody has a large problem with that they should probably let me know 18:11:39 termie: ok. Maybe an email out to the mailing list may help? 18:13:22 anything else for the open discussion? 18:14:09 taking that as a no. :) 18:14:14 thanks y'all 18:14:19 #endmeeting