Mon 14 Nov
GridPP project in github used to host documents and scripts to audit work done accounts independently of APEL.
So far, methods exist for ARC CE, and Torque batch system. Method for VAC still rough and being worked out by (e.g.)
next week. To get the material:
git clone https://sjones-hep-ph-liv-ac-uk@github.com/gridpp/audit.git
Substituting you own github username. Or go to:
https://github.com/gridpp/audit
For write access, ask Andrew McNab.
- Changes to CMS resource requirements
Note: The 'Resources' entries apply per core. CMS usually sends 8-core pilots.
Jobs require an address space larger than the memory size specified above. Sites should allow processes to use at least one aditional GB of virtual address space more per core than memory to accomodate the large amount of shared libraries used by jobs. (For a typical 8-core pilot that would translate into a VZSIZE limit of at least 24GB.)
Cloud resources should provision 8-core VMs to match standard 8-core pilots.
Input I/O requirement is an average 2.5 MB/s per thread from MSS.
All jobs need to have outbound connectivity.
Sites must not use pool accounts for the FQAN cms:/cms/Role=lcgadmin . For any other CMS job, sites need to use pool accounts so that at any time every grid credential is mapped to an independent local account.
National VOMS groups: In CMS national VOMS groups, e.g. /cms/becms or /cms/dcms, are used. Those proxies must be "supported" at all sites in the following way:
glexec must not fail
should be treated like /cms (base group), in case no special treated is wanted by the site
proxies with such national groups must be able to write to /store/user/temp (the PFN associated to this LFN)
Tue 1 Nov
Publishing tutorial updated to use new wording for various measurements.
https://www.gridpp.ac.uk/wiki/Publishing_tutorial#Accounting_transmissions
Tue 20th Sept
GridPP Approved VOs now has link to RPM versions of the VOMS records. They are available for now via the VOMS RPMS Yum Repository. The latest version, which is consistent with the Yaim records in the Approved VOs doc, is 1.0-1. Plan is that when VO records change, Approved VOs doc version will be incremented, and RPMs of changed VOs (only those) will be released carrying the same version stamp as the document. Thus a site that upgrades to "latest" will get the records compatible with the newest version of the GridPP Approved VOs document.
Note: A typical RPM contains as so:
[sjones@hep169]$ rpm -qlp gridpp-voms-dteam-1.0-1.noarch.rpm
/etc/grid-security/vomsdir/dteam
/etc/grid-security/vomsdir/dteam/voms.hellasgrid.gr.lsc
/etc/grid-security/vomsdir/dteam/voms2.hellasgrid.gr.lsc
/etc/vomses/dteam-voms.hellasgrid.gr
/etc/vomses/dteam-voms2.hellasgrid.gr
/root/vo_xml/dteam.xml
The vomsdir (lsc) files (which list the DNs and CA DNs of acceptable certificates) and the vomses files (which give the coordinates of VOMS servers of various VOs) are provided, as if they were created by YAIM in the normal locations. No other features of YAIM are facilitaed by these RPMs. Thus they are useful for migrating from YAIM, but do not provide all the functions of YAIM such as setting SW dirs or other ENV vars etc.
Tue 6th Sept
Benchmarking procedure. Contains instructions for ARC/Condor, CREAM/Torque, VAC. Needs to be updated for use with other systems.
https://www.gridpp.ac.uk/wiki/Benchmarking_procedure
Mon 1st Aug
LZ VO now up to date in portal, and will be updated in Approved VOs automatically from now on. Sites supporting LZ are advised to read LZ VOMS settings section of https://www.gridpp.ac.uk/wiki/GridPP_approved_VOs (which is between LSST and MAGIC!)
Tue 26th July
Elena has provided VOMS info for DUNE. I'm maintaining it by hand, at present, similarly for LZ.
Both should be present and correct in the Operations Portal, but are not.
https://www.gridpp.ac.uk/wiki/GridPP_approved_VOs
General note
See the worst KeyDocs list for documents needing review now and the names of the responsible people.
|