Access to UConn-OSG resources is provided via GUMS/VOMS authorization
software and is restricted to OSG member VOs. Users are mapped to VO group
accounts exclusively when they obtain VOMS proxy credentials for their
session. No individual accounts are permitted.
Any planned event that would impact the regular operation of processing
at our site will by preceded by public notices on
the UConn cluster message
board at least 96 hours in advance. Unplanned outages will be
reported on the same message board as soon as the issue is detected,
together with an estimate for the time when normal operations are expected
to resume.
Processing Policies:
UConn-OSG consists primarily of AMD x86 and Opteron processors and
Intel Xeons shared among local users and OSG VO group accounts, with priority
given to local users. There are 420 job slots on the UConn site currently. The
Condor scheduler configuration allows 120 processors to be allocated to
OSG Gluex jobs, with opportunistic access to 248 more. These resources
are also made available to non-Gluex OSG VO users on an opportunistic
basis.
All jobs are limited to a maximum of 72 hours of runtime. Jobs exceeding
this limit may be terminated without warning and removed from the queue of
executable jobs.
All access to processing resources by OSG users is opportunistic.
Jobs submitted by local users have priority over those submitted by
non-local VO members. Any jobs that are preempted to allow a local user's
job to run will be requeued and eventually restarted. Any previously
executed work performed by such jobs will be lost, and the job will be
restarted from the beginning.
UConn-OSG may suspend or ban DNs, VOs, Roles and/or CAs as necessary to
assure operations. Under normal running conditions, we will attempt to
contact the affected VOs and/or users through the OSG Operations Center
and attempt to provide up to 4 hours of warning before taking these
actions. During some running conditions we may be forced to take this
action without warning.
VOs and VO members that desire to use UConn-OSG grid resources must
initialize their credentials using:
$VDT_LOCATION/voms/bin/voms-proxy-init
Those VOs and VO members that fail to use voms-proxy-init may be blocked
from accessing UConn-OSG grid resources.
UConn-OSG requests that VOs submit using Condor Grid Monitor. VOs unable
to submit through grid monitor may be limited in the number of active
processes allowed. UConn-OSG requires that VO's submitting multi user pilot
jobs use the glexec package to validate the grid credentials of the actual
user who has submitted the job.
Storage Policies:
Remote access to UConn-OSG storage should use either dCache or SRM.
The following three canonical storage areas are provided.
$APP is an area for software installation shared across all
worker nodes. It is read/write from the head node via the jobmanager-fork
queue, and read-only from worker nodes. Default quotas are 30 GB for
all the users in a VO. VO's that have more than one user may request that
only a single privileged user be allowed quota to write files. By default,
the directory is mode 1777.
$DATA is a NFS-mounted area which is accessible read-write from the
head node and all the workers. By default the directory is mode 1777.
OSG also defines $SITE_READ and $SITE_WRITE which are URL's that point
to a local storage element accessible by SRM and dCache for reading, and
by SRM for writing. This is volatile storage with a total available space
of 5TB. Files are deleted, if necessary, on a least recently used basis
and there are no quotas. This space is not backed up to tape.
$WN_TMP is a read/write area for temporary files local to each worker
node. We may delete or purge files in any of the above storage areas
as necessary to assure operations. Under normal running conditions, we will
attempt to contact the affected VOs and/or users through the OSG Operations
Center and attempt to provide up to 4 hours of warning before deleting or
purging files. During some running conditions we may be forced to delete
or purge files without warning.