Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "NGI-VO WN tests"

From EGIWiki
Jump to navigation Jump to search
 
(14 intermediate revisions by 11 users not shown)
Line 1: Line 1:
[[Category:Grid Operations Meetings]]
The Worker Node ('''WN''') released in '''gLite 3.2''' will be supported for security updates until September 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


*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.
<br> 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:  
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
*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
*Enable the queue for the VOs supported by the NGI  
** The queue does not need to support the ops VO
**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
*Coordinate with the VO Managers, in order to have some jobs running on those WNs  
* Summarize the results in the table
*Summarize the results in the table


{| cellspacing="0" cellpadding="3" border="1" style="border-collapse: collapse; border:1px solid black; text-align:center;" class="wikitable"
{| cellspacing="0" cellpadding="3" border="1" style="border-collapse: collapse; border:1px solid black; text-align:center;" class="wikitable"
!NGI
!VOs who tested successfully the EMI-WN
!VOs who tested the EMI-WN with issues
!Comments
|-
|-
|Example
! NGI
|* Vo1
! VOs who tested successfully the EMI-WN
*vo2
! VOs who tested the EMI-WN with issues
! Comments
|-
| Example  
|  
*Vo1  
*vo2  
*vo3
*vo3
|*vo4
 
*vo5
|  
|
*vo4: Issue1
*vo5: Issue2
 
|  
|-
|-
|AsiaPacific
| AsiaPacific  
|
|  
|
|  
|
|  
|-
|-
|CERN
| CERN  
|
|  
|
|  
|
|  
|-
|-
|EGI.eu
| EGI.eu  
|
|  
|
|  
|
|  
|-
|-
|NGI_AEGIS
| NGI_AEGIS  
|
|  
|
|  
|
|  
|-
|-
|NGI_AL
| NGI_AL  
|
|  
|
|  
|
|  
|-
|-
|NGI_ARMGRID
| NGI_ARMGRID  
|
|  
|
|  
|
|  
|-
|-
|NGI_BA
| NGI_BA  
|
|  
|
|  
|
|  
|-
|-
|NGI_BG
| NGI_BG  
|
|  
|
|  
|
|  
|-
|-
|NGI_BY
| NGI_BY  
|
|  
|
|  
|
|  
|-
|-
|NGI_CH
| 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_CYGRID  
|
|  
|
|  
|
|  
|-
|-
|NGI_CZ
| NGI_CZ  
|
| ATLAS, ALICE, Auger, Belle, MPI, VOCE
|
| N/A
|
|  
|-
|-
|NGI_DE
| NGI_DE  
|
|  
|
|  
|
|  
|-
|-
|NGI_FI
| NGI_FI  
|
|  
|
NA
|
 
|  
NA
 
|  
None
 
|-
|-
|NGI_FRANCE
| NGI_FRANCE  
|
| N/A
|
| N/A
|
| None
|-
|-
|NGI_GE
| NGI_GE  
|
| N/A
|
| N/A
|
| None
|-
|-
|NGI_GRNET
| NGI_GRNET  
|
|  
|
|  
|
|  
|-
|-
|NGI_HR
| NGI_HR  
|
|  
|
|  
|
|  
|-
|-
|NGI_HU
| NGI_HU  
|
| Alice, CMS: ok on SLC5 EMI-1
|
| Alice, CMS: problems on SLC6 EMI-2
|
|  
|-
|-
|NGI_IBERGRID
| 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_IE  
|
|  
|
|  
|
|  
|-
|-
|NGI_IL
| NGI_IL  
|
|  
|
|  
|
|  
|-
|-
|NGI_IT
| NGI_IT  
|
|  
|
|  
|
|  
|-
|-
|NGI_MARGI
| NGI_MARGI  
|
|  
|
|  
|
|  
|-
|-
|NGI_MD
| NGI_MD  
|
|  
|
|  
|
|  
|-
|-
|NGI_ME
| NGI_ME  
|
|  
|
|  
|
|  
|-
|-
|NGI_NDGF
| NGI_NDGF  
|
|  
|
|  
|
|  
|-
|-
|NGI_NL
| NGI_NL  
|
| N/A
|
| N/A
|
| We plan to upgrade the site LSG-AMS to the UMD2 WN the coming month
|-
|-
|NGI_PL
| NGI_PL  
|
|  
|
|  
|
|  
|-
|-
|NGI_RO
| NGI_RO  
|
|  
|
|  
|
|  
|-
|-
|NGI_SI
| NGI_SI  
|
|  
|
|  
|
|  
|-
|-
|NGI_SK
| NGI_SK  
|
|  
|
|  
|
|  
|-
|-
|NGI_TR
| NGI_TR  
|
|  
|
|  
|
|  
|-
|-
|NGI_UA
| NGI_UA  
|
|  
|
|  
|
|  
|-
|-
|NGI_UK
| 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
| NGI_ZA  
|
|  
|
|  
|
|  
|-
|-
|ROC_Canada
| ROC_Canada  
|
|  
|
|  
|
|  
|-
|-
|ROC_IGALC
| ROC_IGALC  
|
|  
|
|  
|
|  
|-
|-
|ROC_LA
| ROC_LA  
|
|  
|
|  
|
|  
|-
|-
|Russia
| Russia  
|
|  
|
|  
|
|  
|}
|}

Latest revision as of 15:39, 16 October 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 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