2014-08-01 0:22 GMT+02:00 Trey Dockendorf <[email protected]>: > > I don't have a solution regarding the removal of accounting enforcement, > but what is it your storing in LDAP that is checked by your plugin? >
We prefer using job_submit plugin which is connecting to LDAP database, because this guarantees that closing account in web interface (which is not managed by cluster administrators) affects the possibility of job submission immediately. > > We are still migrating our Torque/Maui cluster to SLURM and part of the > migration includes moving from /etc/passwd based user management to LDAP. > I've gone to considerable trouble to script the importing of our LDAP into > slurmdbd. Right now my script only queries LDAP and converts various > attributes into a sacctmgr import file. The code is a proof-of-concept and > eventually will be changed to perform regular checks that slurmdbd matches > LDAP. > We have our own code which is working the same way (however we have our own LDAP schema for accounts; honestly we are merging 2 different schemas from different sources), our backup file has more than 4k7 lines and currnetly we are unable to load it, the error message is very helpfull :) "Unspecified error". > Something similar to what I'm doing could possibly be easier than having > the SLURM code changed. > Easier solution often doesn't mean better one ;-) We want to use only QoS values allowed for every user, but we are forced to generate the dump file, load it from cron doesn't look ugly? :) cheers, marcin
