Dear All
In early December both LHCb and ATLAS requested (changes to the) pilot
roles to be enabled at sites. The original request is forwarded below.
Since December only a few sites have enabled these pilot roles. The
matter is now becoming more urgent as LHCb and ATLAS need these to be in
place to advance their testing. Please can all LHCb and ATLAS supporting
sites enable these roles as a priority over the coming weeks? We will
review the status and any arising issues at the next UKI deployment
meeting which is currently scheduled for Thursday 21st May. After that
meeting we will raise GGUS tickets against sites to track the
deployment.
If there are any immediate questions please respond to this mail!
Many thanks,
Jeremy
-------- Original Message --------
Subject: Site admins - please note LHCb and ATLAS pilot role requests
Date: Thu, 4 Dec 2008 16:38:08 +0000
From: Coles, J (Jeremy) <[log in to unmask]>
Reply-To: Testbed Support for GridPP member institutes
<[log in to unmask]>
To: <[log in to unmask]>
Dear All
In case you have missed the announcements, both LHCb and ATLAS are
currently requesting changes to their roles enabled at sites.
For LHCb all the details are in their VO card. The request is to enable
role = pilot. The reason for this request is that within LHCb it has
been decided that sites supporting the pilot role will be used to steer
multi-user (generic) pilot jobs. A JDL requirement on the Software tag
would target these special pilots. Sites not enabling this will continue
to be used in the way LHCb has been operating until now - private user
pilots are submitted for each user task. Generic pilots allows LHCb much
greater control over the prioritisation of jobs. For more details see
the slides here:
http://indico.cern.ch/materialDisplay.py?sessionId=4&materialId=0&confId
=20230.
For ATLAS Graeme had the following request. Please could sites enable
/atlas/Role=pilot with the following percentages for the ATLAS share:
50% /atlas/Role=production
25% /atlas/Role=pilot
25% /atlas
Alessandra indicates that the process to be followed is:
"sites with YAIM should insert in groups.conf this line
"/VO=atlas/GROUP=/atlas/ROLE=pilot":::pilot:
and in users.conf the unix accounts lines should be something like
UID:pilatl001:atlpilGID,atlasGID:atlpil,atlas:atlas:pilot:
and then rerun the full configuration on all the nodes."
I'm sure there will be further discussion via this list - please do keep
us informed of progress and problems.
Many thanks,
Jeremy
--
Scanned by iCritical.
--
Scanned by iCritical.
|