[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grid-engine-dev
Subject:    Re: Implementing User Based QoS Scheduler
From:       Andreas Haas <Andreas.Haas () Sun ! COM>
Date:       2003-06-05 8:48:42
Message-ID: Pine.GSO.4.53.0306051047560.11860 () sr-ergb01-01
[Download RAW message or body]

All,

(thanks a lot for clarifying, Ron)

I continue here at dev@ mailing list because this is undoubtedly a
development related topic. The DRMAA API does not target
on implementing customized scheduling algorithms. The purpose
of DRMAA is best described in the charter of the DRMAA-WG
(www.drmaa.org):

   "Develop an API specification for the submission
    and control of jobs to one or more Distributed
    Resource Management (DRM) systems. The scope of
    this specification is all the high level functionality
    which is necessary for an application to consign a
    job to a DRM system including common operations on jobs
    like termination or suspension."

if you wish to plug your own scheduling algorithm into SGE
technically two approaches are possible in principle:

(1) The first one is to use the existing SGE schedd trunk and
    add a new scheduling algorithm. The overall idea how this
    would work is described in the developer documentation about
    the Schedd under


http://gridengine.sunsource.net/unbranded-source/browse/%7Echeckout%7E/gridengine/source/daemons/sched
d/schedd.html?content-type=text/html

   note that there are two models how this could work (Layer 2 only or
   Layer 1 + 2) in principle.

(2) The second approach was used for the Maui integration. In this
    case only those SGE sub-modules are used that are required to
    interconnect with SGE qmaster (receive events + send scheduling).
    I'm not sure about the best source for information about it. Maybe
    it's the best to simply download it and play around with it.

Note that apart from the question how your algorithm can techically be
plugged into SGE the question in which category your scheduler shall
fall semantic-wise is at least of the same importance. This question is
shortly discussed also in the Schedd developer documentation page
mentioned above ("Classifying Alternative Schedulers").

  Andreas


[prev in list] [next in list] [prev in thread] [next in thread]