Allow/deny-listing execute sites¶
The IGWN Grid configuration enables allow/deny-listing execute points using the name of the computing centre.
Only use as a last resort, use requirements instead.
The configuration below should not be relied upon in general, and should only be used for testing sites (allowlist) or in exceptional/urgent circumstances when specific sites are known to be problematic (denylist).
It is much better to use feature attributes (e.g. via requirements expressions) to match your job with execute points that provide what is needed.
Allowlist (DESIRED_Sites)¶
The DESIRED_Sites job attribute may be set as a quoted, comma-separated list of site names to allow as a match for your job.
This is a non-standard attribute, so should be set in your submit description using the MY. prefix.
DESIRED_Sites
To force your job to only match with nodes at LIGO-Caltech or LIGO-Livingston:
MY.DESIRED_Sites = "LIGO-CIT,LIGO-LA"
Denylist (UNDESIRED_Sites)¶
The UNDESIRED_Sites job attribute may be set as a quoted, comma-separated list of site names to deny (forbid) as a match for your job.
This is a non-standard attribute, so should be set in your submit description using the MY. prefix.
UNDESIRED_Sites
To force your job to not match with nodes at LIGO-Caltech or LIGO-Livingston:
MY.UNDESIRED_Sites = "LIGO-CIT,LIGO-LA"
Do not use both DESIRED_Sites and UNDESIRED_Sites at the same time.
You should not use both DESIRED_Sites and UNDESIRED_Sites at the same time. Doing so will prevent your job from running.
Valid site names¶
To see a current list of valid site names, you can query the IGWN Grid status:
condor_status -pool condor.igwn.org -af GLIDEIN_Site | sort -u
This list is dynamic
Computing centres contribute resources to the IGWN Grid dynamically, based on current demand. The above command only shows sites that are currently contributing, so will return, in general, an incomplete list.