Scheduler Plugins

The RADICAL-Pilot UnitManager class is responsible for assigning and enacting submitted Units on the respectively available Pilots. The specific placement algorithm is encapsulated in scheduler plugins, to support research and experiments on different scheduling strategies.

The scheduler plugin interface is rather simple:

• Scheduler components must be installed under troy/plugins/scheduler/troy_unit_scheduler_[name].py, where name should be a short and descriptive string like round-robin, etc.
• the scheduler module must include two structures:
  • a description dictionary like this one:

PLUGIN_DESCRIPTION = {
    'name'        : 'round_robin', 
    'version'     : '0.1',
    'type'        : 'unit_scheduler', 
    'description' : 'simple scheduler, assigns CUs to pilots in round-robin fashion.'
}

* the scheduler class, similar to this stub:

class PLUGIN_CLASS (object) :
    def __init__ (self, unit_manager) :
        ...
    def run (self) :
        ...

The scheduler's responsibility is to move Units, which are submitted to the UnitManager and thus registered in the data store as:

/sinon/v1/users/<username>/<sid>/um.1/u.1
/sinon/v1/users/<username>/<sid>/um.1/u.2
/sinon/v1/users/<username>/<sid>/um.1/u.3
/sinon/v1/users/<username>/<sid>/um.1/p.1/
/sinon/v1/users/<username>/<sid>/um.1/p.1/

into the respective Pilots, like:

/sinon/v1/users/<username>/<sid>/um.1/p.1/u.1
/sinon/v1/users/<username>/<sid>/um.1/p.1/u.3
/sinon/v1/users/<username>/<sid>/um.1/p.2/u.2

That is the location where the pilot agents will pick the units up to execute them.