GridPP5 Tier2 plans

From GridPP Wiki
Jump to: navigation, search

Other links

Sites batch system status

This page has been setup to collect information from GridPP sites regarding their batch systems in February 2014. The information will help with wider considerations and strategy. The table seeks the following:

  1. Site name
  2. Batch/CE system (the main batch system and CE you are intending to use in GridPP5. This might be one that you are testing as a replacement for, say, Torque/CREAM)
  3. Shared, non-CE? (Is the batch system shared with users who don’t access it through the grid CE?)
  4. Shared filesystem? (Do users rely on a shared filesystem? e.g. Lustre. i.e. that couldn’t be replaced with local filesystems on worker nodes.)
  5. Non-LHC, non GridPP DIRAC VOs? (Do you support VOs, e.g. from EGI, that aren’t LHC experiments or use the GridPP DIRAC service. Please list the top 3.)
  6. Non-LHC storage? (Do you provide storage to non-LHC projects? Please list the top 3.)
Site Batch/CE system Shared, non-CE? Shared filesystem? Non-LHC, non GridPP DIRAC VOs? Non-LHC storage? Notes Notes Notes
UKI-LT2-Brunel Arc/Condor ArcCE info system Spark cluster in test Arc Yes Yes Yes -
UKI-LT2-IC-HEP Gridengine (local) None No reason CREAM, ARC Yes No Yes -


UKI-LT2-QMUL Gridengine / SLURM SLURM does support MaxCPUTime for queues but it's complicated SLURM CREAM Yes Yes (SLURM)/ No (Gridengine) Yes -
UKI-LT2-RHUL Torque/Maui (local) Torque/Maui support non-existent Will follow the consensus CREAM Yes No Yes -


UKI-NORTHGRID-LANCS-HEP Son of Gridengine (HEC) Torque/Maui clusterDecommissioned, for for grid and local (tier 3) Sticking with grid engine CREAM, moving to ARC eventually Yes No Yes -
UKI-NORTHGRID-LIV-HEP (Single core cluster) Torque Maui (local) Poor Support, Maui intrinsically broken Cream Yes No No -
UKI-NORTHGRID-LIV-HEP (Multi core cluster) HTCondor (local) None ARC Yes Loooking into it Yes Warn


UKI-NORTHGRID-MAN-HEP Torque/Maui (local) Maui is unsupported. It had memory leaks. Robert wrote a patch and there was nowhere to feed it back into. HTCondor Currently CREAM, testing ARC-CE/HTCondor Yes Looking into it Yes Pass


UKI-NORTHGRID-SHEF-HEP Torque/Maui (local) Torque/Maui support non-existent HTCondor is in testing mode CREAM CE, ACR CE is in test Yes No Yes -


UKI-SCOTGRID-DURHAM SLURM (local) No reason ARC CE Yes Yes -


UKI-SCOTGRID-ECDF Gridengine None No reason Cream CE for standard production, ARC CE for exploratory HPC work No Yes -


UKI-SCOTGRID-GLASGOW HTcondor (local), Torque/Maui (local) Becomes unresponsive at times of high load or nodes being un-contactable. Investigating HTCondor/SoGE/SLURM as a replacement. ARC, Cream Yes Yes -
UKI-SOUTHGRID-BHAM-HEP Torque/Maui Maui sometimes fails to see new jobs and so nothing is scheduled HTCondor CREAM No No -


UKI-SOUTHGRID-BRIS HTCondor (shared) None No reason ARC-CE, abandoned plan to move to HTCondor CE(no accounting) On roadmap No No -


UKI-SOUTHGRID-CAM-HEP Torque/Maui (local) Torque/Maui support non-existent Will follow the consensus CREAM CE Yes No Yes Pass
UKI-SOUTHGRID-OX-HEP HTCondor (local) None No reason ARC CE in production Yes Yes Yes -


UKI-SOUTHGRID-RALPP HTCondor None No reason ARC CE Yes Yes Yes Warn


UKI-SOUTHGRID-SUSX (Shared) Gridengine - (Univa Grid Engine) None No reason CREAMCE Looking into it Yes -