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 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. Something similar to what I'm doing could possibly be easier than having the SLURM code changed. - Trey ============================= Trey Dockendorf Systems Analyst I Texas A&M University Academy for Advanced Telecommunications and Learning Technologies Phone: (979)458-2396 Email: [email protected] Jabber: [email protected] ----- Original Message ----- > From: "Marcin Stolarek" <[email protected]> > To: "slurm-dev" <[email protected]> > Sent: Thursday, July 31, 2014 2:53:14 AM > Subject: [slurm-dev] Enforcing qos limits without associations limits > > > Hi guys, > > > In our installation we have a separate job_submit plugin which checks > the account validity directly in LDAP. We would like to disable > associations enforcement, but in current configuration we are using > qos limits which are limiting number of jobs and cores per user > (user can choose to use qos normal - with longer jobs and lower > number of jobs/cores running/allocated, or qos short which is > allowing more resources with lower walltime limit). > > I haven't yet checked in code, do you think there is an ease way to > remove accounting enforcement dependencies? > cheers, > marcin >
