Grid Laboratories of Wisconsin CMS-T2 Site Policies#

GLOW-CMS T2 has a few policies concerning the use of the site’s resources. These policies are intended to provide reasonably fair access to users of our resources, and indicate the level of service we can provide. Users who violate the policies listed below may find their access curtailed as is deemed appropriate.#

General Site Policies#

GLOW-CMS T2 resources are primarily intended for use with the US-CMS VO at this time. If you would like to use GLOW-CMS T2 resources for another VO, please contact our site admins.#

Any planned event that would impact the regular operation of processing at our site will by preceeded by public notice visible on the OSG site maintenance page for the GLOW site.#

Unplanned outages will be acknowledged in a similar way within the first 6 hours of downtime, and again when normal operation resumes.#

Processing Policies#

  • All access to processing resources is opportunistic unless otherwise arranged.
  • All jobs are limited to a maximum of 1 day of runtime.
  • In extreme cases, we may be forced to remove running jobs. Should this happen, we will attempt to requeue submitted work, rather than remove it entirely.
  • If we need to affect running jobs, we will notify the affected VO. While not all system events may allow it, we will attempt to provide up to four hours advance notice.
  • Both dedicated and opportunistic resources (GLOW+CHTC) are available to CMS through the standard Condor jobmanager on and
  • Preempted jobs will eventually be restarted. Any previously executed work will be lost, and the job will be completely re-run.

Storage Policies#

  • Remote access to GLOW-CMS T2 storage should use SRM (
  • Data in the T2 storage cluster will not be backed up.
  • We may, at our discretion, remove files older than 31 days.
  • CMS users should limit their usage to 1TB unless special arrangements have been made.
  • All GRAM Job directories residing in $HOME older than a week will be purged.