NGI-VO WN tests

From EGIWiki
Jump to: navigation, search

The Worker Node (WN) released in gLite 3.2 will be supported for security updates until September 2012.


NGIs are strongly suggested to provide to the supported VOs the possibility to run their code on EMI-WNs. If no sites have EMI-WN in production a possible solution could be:

NGI VOs who tested successfully the EMI-WN VOs who tested the EMI-WN with issues Comments
Example
  • Vo1
  • vo2
  • vo3
  • vo4: Issue1
  • vo5: Issue2
AsiaPacific
CERN
EGI.eu
NGI_AEGIS
NGI_AL
NGI_ARMGRID
NGI_BA
NGI_BG
NGI_BY
NGI_CH ATLAS, CMS, LHCb, HONE, OPS EMI UMD 1 WN (emi-wn-1.0.0-0.sl5) installed as regular WN with no jobs failing. No extra queues for this host.
NGI_CYGRID
NGI_CZ ATLAS, ALICE, Auger, Belle, MPI, VOCE N/A
NGI_DE
NGI_FI

NA

NA

None

NGI_FRANCE N/A N/A None
NGI_GE N/A N/A None
NGI_GRNET
NGI_HR
NGI_HU Alice, CMS: ok on SLC5 EMI-1 Alice, CMS: problems on SLC6 EMI-2
NGI_IBERGRID Report from major PT sites: One WN as been deployed using emi-wn-2.0.0-1.sl5 (SL5), and it is currently supporting CMS, ATLAS and other generic VOs. No problems have been reported up to now.
NGI_IE
NGI_IL
NGI_IT
NGI_MARGI
NGI_MD
NGI_ME
NGI_NDGF
NGI_NL N/A N/A We plan to upgrade the site LSG-AMS to the UMD2 WN the coming month
NGI_PL
NGI_RO
NGI_SI
NGI_SK
NGI_TR
NGI_UA
NGI_UK ATLAS: Able to use EMI-1 and EMI-2 on SL5 ATLAS: Unable to use EMI-1 WN

Conflicting reports; down to the storage access libs

NGI_ZA
ROC_Canada
ROC_IGALC
ROC_LA
Russia
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export