Difference between revisions of "NGI-VO WN tests"

From EGIWiki
Jump to: navigation, search
Line 85: Line 85:
 
|-
 
|-
 
|NGI_CZ
 
|NGI_CZ
|
+
| ATLAS, ALICE, Auger, VOCE, MPI
|
+
| N/A
 
|
 
|
 
|-
 
|-

Revision as of 15:18, 30 July 2012

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

  • During the coming months the gLite WNs will need to be updated to the EMI-WN released in UMD1, or UMD2 (expected for the UMD2.1 update)
  • The main changes in the upgrade are the path to the client libraries. The EMI-WN aligned the libraries path to the linux standard locations, if the job's code has the library path hard coded needs to be corrected.
  • Changes in the execution environment of user's payload may affect the code executed by the job, and in general for VOs is useful to have their code tested vs more recent releases of the WN


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:

  • Choose one or more site and ask the Site Managers to install a couple of EMI-WN, set up a new queue in the CE to submit jobs to those WN
  • Enable the queue for the VOs supported by the NGI
    • The queue does not need to support the ops VO
  • Coordinate with the VO Managers, in order to have some jobs running on those WNs
  • Summarize the results in the table
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
NGI_CYGRID
NGI_CZ ATLAS, ALICE, Auger, VOCE, MPI N/A
NGI_DE
NGI_FI

NA

NA

None

NGI_FRANCE
NGI_GE
NGI_GRNET
NGI_HR
NGI_HU
NGI_IBERGRID
NGI_IE
NGI_IL
NGI_IT
NGI_MARGI
NGI_MD
NGI_ME
NGI_NDGF
NGI_NL
NGI_PL
NGI_RO
NGI_SI
NGI_SK
NGI_TR
NGI_UA
NGI_UK
NGI_ZA
ROC_Canada
ROC_IGALC
ROC_LA
Russia