Thanks, Ahmet, in the settings it mentions servername and servertype so it seemed at first glance that some relatively elaborate communication with a license server was involved. I'll try if with some scripting around the options you mentioned I can find a suitable solution.
Greetings, Pim On Tue, Jun 25, 2019 at 2:53 PM mercan <ahmet.mer...@uhem.itu.edu.tr> wrote: > Hi; > > As far as I know, the slurm is not able to work (communicate) with > reprise license manager or any other license manager. Slurm just sums > the used licenses according to the -L parameter of the jobs, and > subtracts this sum from the total license count which given by using > "sacctmgr add/modify resource", and the result is used as free license > count. That's all. No more calculation, communication, testing, > monitoring etc. with both license managers and jobs. > > If you want to share a license with non-cluster users, you should check > and update license using a script that detects global/free license count > changes. > > Regards, > > Ahmet M. > > > On 25.06.2019 14:00, pim schravendijk wrote: > > Hi all, > > > > We use a piece of software that works with reprise license management > > via the cloud > http://www.reprisesoftware.com./products/cloud-licensing.php > > > > According to https://slurm.schedmd.com/licenses.html slurm is able to > > work with reprise license manager, though the examples at schedmd seem > > to aim at the on-premise rlm version. Instead of a useful pool of > > licenses we seem to be stuck with per-user licenses. > > > > Does anyone have experience with rlmcloud and slurm? Maybe some sample > > configuration or just some hints on whether this will work at all. > > > > Greetings, Pim >
