| |
| |
| |
|
Page: 1 2 3 4 5
<podzap> yep
<SuperPhly> podzap: production quality?
<podzap> well, who can state that? :-)
<podzap> penrose provides an LDAP interface to data pulled in from various sources, LDAP, and nearly all major database systems
<podzap> I just found out about it a few days ago, and I played with it the other night.
<podzap> it is pretty cool
<podzap> you could pull in entries from the university offices, and merge in attributes from your own LDAP server, for example
<SuperPhly> hmm, too bad the site is down
<podzap> works for me right now
<podzap> you could try the ip address in your browser: 64.34.170.108
<hyc> the translucent overlay in OpenLDAP is designed for this purpose as well.
<podzap> hi hyc
<hyc> howdy podzap
<podzap> i have been out of work for two weeks now (on sick leave)
<SuperPhly> hyc: what does that mean?
<hyc> brb
<podzap> hyc: that translucent overlay doesn't support RDBMS, though, does it?
<hyc> hm, how/why would it support an RDBMS?
<podzap> just as a data aggregation engine
<hyc> you'd use back-sql for that
<podzap> right, but could you combine data from another LDAP and RDBMS into a single entry?
<hyc> if you put back-sql over the RDBMS then why not?
<hyc> once you put the data into an LDAP-friendly form it's the same as anything else.
<podzap> ok, so you can use multiple backends to compose a single entry?
<podzap> that's basically my question
<hyc> to a limited degree, that is what the translucent overlay does.
<hyc> it treats one backend as a master, and creates a private slave backend. Entries can only be created in the master, but once an entry exists, you can add local data to it using the slave backend.
<hyc> so when you search on the backend, you get the combined data of the master and the private backend merged into one entry.
<podzap> sounds pretty neat
<hyc> yes, it comes in handy. The obvious use case is where you have a central master directory that contains info about all users, and you want a small application-specific directory; you can load a private schema into the app directory and attach whatever info you want to users, without having to change anything on the master dir.
<podzap> so can you create e.g. multiple branches on the master directory, and attach a seperate slave backend to each seperate branch?
<podzap> or a translucent overlay for each branch, each pointing to a different directory server?
<podzap> hi JoBbZ
<hyc> podzap - sure
<JoBbZ> heya all
<hyc> hey JoBbZ. settled in?
<JoBbZ> my life is in boxes, but I have internet, and my PS2 is hooked up to my HDTV, so life is good :P
<podzap> lol
<hyc> lol
<SimonRaven> hehe
<podzap> where did you move from to?
<JoBbZ> I bought a 802.11g wireless router (the new 108Mbps ones) to hook up to my dedicated ethernet connection, so now I've got a nice wireless network too
<JoBbZ> from an apartment in downtown palo alto to Stanford's apartment complex
<hyc> I still have boxes I haven't unpacked in 15 years
<JoBbZ> hyc: heh
<JoBbZ> generally an indication you can just toss them :P
<hyc> lol
<podzap> i was in germany last week, and i tripped coming out of a pizza place and hit my head on the ground really hard. i woke up in the hospital some 4 hours later.
<JoBbZ> ouch!
<podzap> spent 3 days in the hospital
<hyc> nasty
<JoBbZ> sounds very nasty
<podzap> and all this week on doctor-ordered rest
<SimonRaven> ow :(
<hyc> at least you guys have decent medical care. do that around Los Angeles and they'd probably leave you lying on the street.
<podzap> yeah, now i got a nasty scar on my forehead and headaches that just won't stop.
<SimonRaven> well, i hope you heal well, and are getting enough rest
<JoBbZ> probably a good time to look at moving to OpenLDAP, podzap :P
<JoBbZ> a whole week to just play!
<podzap> :-)
<hyc> lol
<SimonRaven> heh
<podzap> I have been studying the NSPR and NSS APIs
<hyc> that doesn't sound like fun.
<podzap> ever think about porting OL to use NSPR? Then perhaps it could be run on many platforms without code changes...
<hyc> trying to work with mozilla code is pretty confusing, there are a lot of nspr routines that are deprecated and you're just supposed to use the regular libc instead.
<hyc> OpenLDAP already runs on everything from my old Atari TT to IBM z/OS.
<podzap> cool :-)
<SimonRaven> wow
<hyc> it is pretty vanilla C code after all.
<SimonRaven> that's a strength IMO. makes it easy (easier) to manage, debug, etc.
<hyc> the areas that present the most trouble in a port are very rarely in the code itself, almost always in the build environment.
<SimonRaven> ok
<hyc> linker flags, dependent libraries, etc.
<hyc> have you run HEAD on your test systems?
<JoBbZ> not yet
<JoBbZ> probably should do that first :P
<JoBbZ> i saw that BDB cursor commit
<JoBbZ> what is that about?
<JoBbZ> :)
<hyc> yeah, it would be a good idea.... :P
<hyc> that cursor commit... sigh..... that is about reading a tiny footnote in the BDB documentation and suddenly realizing there was a better solution to a deadlock problem than what we were using.
<JoBbZ> heh
<JoBbZ> that sounds like a good thing ;)
<podzap> how does the deadlock problem manifest itself?
<hyc> yes, ultimately it's a very good thing. it also means that BDB patch we maintain isn't needed any more.
<SimonRaven> oh cool
<JoBbZ> sweet
<JoBbZ> so no special patches to 4.2.52 at all?
<JoBbZ> just the sleepycat ones ;P
<hyc> right
<JoBbZ> that'll make life easier
<JoBbZ> maybe 4.3 will even work :P
<hyc> podzap: in general we only touch one BDB file at a time. there were two cases where we needed to have two BDB files accessed at once.
<hyc> when inside a transaction, there was no problem, but for read operations we didn't use transactions.
<SimonRaven> JoBbZ: it works, but rather poorly. at least here
<podzap> hyc: so it would cause a read to hang forever, or what?
<hyc> I created a long-lived read transaction to get around one of the problem cases.
<hyc> with the latest commit we don't need the read transaction any more.
<JoBbZ> simonraven: poor performance? low stability? what issues? :)
<SimonRaven> slapd hanging around during the start of a request, usually
<JoBbZ> eww
<JoBbZ> what version of BDB 4.3?
<SimonRaven> yeh
<SimonRaven> sec
<SimonRaven> ii libdb4.3 4.3.29-1
<hyc> I just downloaded the BDB 4.4 alpha the other day, haven't built it yet.
<JoBbZ> hm, 4.3.29 is the latest
<JoBbZ> that's scary
<JoBbZ> hyc: Yeah, 4.4 should finally get rid of the damn 4GB limit on memory sections
<JoBbZ> can you test that first? :P
<hyc> that's the claim.
<JoBbZ> we can then bonk sleepycat on the head if they "forgot" again like in 4.3
<JoBbZ> hehe
<hyc> I only have 2GB of memory on my test machine :P
<JoBbZ> oh
<JoBbZ> well
<JoBbZ> once head works with 4.4 I suppose I can test it :P
<SimonRaven> also, mem usage goes up and up. it'll start at ~50 MB, and soar to over 200 in a few hours
<SimonRaven> (not a big db)
<hyc> that sounds like a leak.
<SimonRaven> and i patched it for the mem leak too. must've missed one
<podzap> if slapd deadlocks on multiple bdb access, do you have to use kill -9 ?
<hyc> podzap - if it deadlocks, yes.
<JoBbZ> hm... I'm thinking I'm probably just going to go from 4.2 to 4.4 if 4.4 turns out stable enough :P
<SimonRaven> i've had to do that
<SimonRaven> :(
<JoBbZ> 4.3 seemed kind of a dud release :P
<SimonRaven> almost as bad as 4.1
<SimonRaven> *shrug*
<podzap> during deadlock on read, would e.g. write operations still succeed?
<hyc> but the main reason for deadlocks was the bogus syncrepl provider code in 2.2, which I deleted from 2.3.
<hyc> podzap: no - you can only get a deadlock because of conflicting locks, which means a writer and a reader are waiting for each other.
<hyc> depending on which data pages are being locked, other read or write operations may go thru or get stuck.
<podzap> ok
<podzap> i think i have been experiencing a similar situation lately as well
<hyc> what situation?
<podzap> deadlocking
<podzap> in NDS 6.21 (which uses a multiple BDB backend)
<hyc> sounds like one for dboreham or richm
<podzap> yeah
<podzap> well, it has to go first through HP
<hyc> you get your directory service from HP?
<podzap> hp-ux is our system platform, and with the hp-ux support contract, we get NDS and support for free
<hyc> ahhh
<JoBbZ> gee, you should get CDS through HP instead :P
<hyc> I believe new HP customers will...
<podzap> we are moving away from HP-UX ASAP, but will make one more release (which is going out soon)
<hyc> though that may only be for their Linux side...
<podzap> RHEL will be the new system platform...
Return to ldap
or
Go to some related
logs:
unixboard
politics
|
|