[torquedev] [Bug 92] Enhancement to enable dynamic tokens

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Sat Oct 16 03:31:12 MDT 2010


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=92

Simon Toth <SimonT at mail.muni.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |SimonT at mail.muni.cz

--- Comment #1 from Simon Toth <SimonT at mail.muni.cz> 2010-10-16 03:31:11 MDT ---
(In reply to comment #0)
> Created an attachment (id=59)
 --> (http://www.clusterresources.com/bugzilla/attachment.cgi?id=59) [details]
> Dynamic token patches
> 
> These patches enable the C FIFO scheduler properly schedule jobs which require
> network based licenses, such as flexlm, which may also be used by software not
> running under the control of Torque.
> 
> This was implemented using the existing tokens capability in the server and C
> FIFO scheduler.  This has been in production on one cluster for 18 months with
> Torque 2.3.6.  I recently updated the patches for 2.5.2.
> 
> There are three patches.  The first changes the token limit to 1000000 using a
> #defined value in pbs_server.  The second contains all of the necessary changes
> to the scheduler.  The third adds documentation for the tokens resource and
> server attribute to the man pages.
> 
> Ideally this should probably be re-written to enable the C FIFO scheduler to
> understand generic resources; however, since the token capability was already
> there, I just extended it.

This is interesting. We have a fully resource-aware server and scheduler.
Server part is in bugzilla here:
http://www.clusterresources.com/bugzilla/show_bug.cgi?id=67

But we also have a separate external daemon for dynamic resources like
licences. You store licenses dirrectly on server? How do you handle the delay?

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list