...
The format of the input parameters for jobs and hosts are standard Perl hash structures.
$job = {“id”
"id" => 1000,“pid”
"pid" => 1,“pgrp”
"pgrp" => 1000,“priority”
"priority"=> 2,“user”
"user" =>“username”, “status” => “pending”, “name” => “my job’s name”, “label” => “qube1”, “cluster” => “
"username", "status" => "pending", "name" => "my job’s name", "label" => "qube1", "cluster" => "/my/cluster/”, “cpus”
", "cpus" => 2,“prototype”
"prototype" =>“cmdline”, “requirements” => “”, “reservations” => “”, “restrictions” => “”, “account” => “shotname”
"cmdline", "requirements" => "", "reservations" => "", "restrictions" => "", "account" => "shotname",
};“name”
$host = {
"name" =>“host’s name ”,
“state” => “active”,
“cluster” => “/my/cluster”, “resources” => ”host.processors=10”, “restrictions” => “”,
“address” => “192.168.10.22” };
"host’s name ",
"state" => "active",
"cluster" => "/my/cluster", "resources" => "host.processors=10", "restrictions" => "",
"address" => "192.168.10.22" };
Important: If you implement this routine in a custom algorithm and mix passive and aggressive preemptions, make sure that the qb_supervisor_preempt_policy is set to "mixed".
See supervisor_preempt_policy for details.