Configure Grid Engine¶
A YAML cluster configuration file for a Grid Engine (Sun Grid Engine, Son of Grid Engine, Univa Grid Engine) resource manager on an HPC cluster looks like:
# /etc/ood/config/clusters.d/my_cluster.yml --- v2: metadata: title: "My Cluster" login: host: "my_cluster.my_center.edu" job: adapter: "sge" cluster: "my_cluster" bin: "/usr/lib/gridengine" conf: "/etc/default/gridengine" sge_root: "/var/lib/gridengine" libdrmaa_path: "/var/lib/gridengine/drmaa/libdrmaa.so" # bin_overrides: # qsub: "/usr/local/bin/qsub_wrapper" # qstat: "" # qhold: "" # qrls: "" # qdel: ""
with the following configuration options:
- This is set to
- The Grid Engine cluster name. Optional
- The path to the Grid Engine client installation binaries.
- The path to the root directory of the Grid Engine installation. Default:
- The path to the Grid Engine configuration file for this cluster. Optional
- The full path to libdrmaa.so. Provide this to enable use of libdrmaa for more precise job status reporting. Optional
Replacements/wrappers for Grid Engine’s job submission and control clients. Optional
Supports the following clients:
DRMAA improves OnDemand’s ability to report on the precise status of jobs. To use this feature ensure that libdrmaa.so for Grid Engine is installed or built and set the config value for
sge_root. If DRMAA is not installed then OnDemand is unable to get a precise job status for single jobs and will only return either queued or complete.