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.
|