[torquedev] [Bug 67] New: Support for counted resources on nodes

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Wed Jun 30 08:58:46 MDT 2010


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

           Summary: Support for counted resources on nodes
           Product: TORQUE
           Version: 2.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: pbs_server
        AssignedTo: glen.beane at gmail.com
        ReportedBy: SimonT at mail.muni.cz
                CC: torquedev at supercluster.org
   Estimated Hours: 0.0


I finally managed to reserve some time to tear this patch from my development
branch.

The feature itself is stable, but I'm not sure that the patch is entirely
complete (some tiny bugfix might have run past me).

What it does:

support on nodes:
  resources_total.resource = value (read-write, can be taken from node)
  resources_used.resource = value (read-only, counted on server)

There are two server attributes that control what resources should be taken
from the node reports.

resources_to_store: list of resources that should be stored
resources_mappings: list of mappings for resources (old=new)

For example, if you want to store reported memory (physmem) and store it as
pmem resource, you could do this:

resources_to-store = physmem
resources_mappings = physmem=pmem

Resources set manually (using qmgr or nodes file) are never overwritten. For
that resources have to be unset.

Server calculates used resources.

The server does not currently prevent jobs requesting more resources then
available from running. This is something that I need to implement on server (I
handle it only on schedulers side now). I will post the patch as soon as it is
done. Should just require patching hasprop() function.

-- 
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