https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Koubat&feedformat=atomEGIWiki - User contributions [en]2024-03-28T13:46:45ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=NGI-VO_WN_tests&diff=38987NGI-VO WN tests2012-07-30T13:18:39Z<p>Koubat: </p>
<hr />
<div>The Worker Node ('''WN''') released in '''gLite 3.2''' will be supported for security updates until September 2012. <br />
* 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)<br />
* 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.<br />
* 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<br />
<br />
<br />
NGIs are strongly suggested to provide to the supported VOs the possibility to run their code on EMI-WNs.<br />
If no sites have EMI-WN in production a possible solution could be:<br />
* 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<br />
* Enable the queue for the VOs supported by the NGI<br />
** The queue does not need to support the ops VO<br />
* Coordinate with the VO Managers, in order to have some jobs running on those WNs<br />
* Summarize the results in the table<br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border-collapse: collapse; border:1px solid black; text-align:center;" class="wikitable"<br />
!NGI<br />
!VOs who tested successfully the EMI-WN<br />
!VOs who tested the EMI-WN with issues<br />
!Comments<br />
|-<br />
|Example<br />
|<br />
* Vo1<br />
*vo2<br />
*vo3<br />
|<br />
*vo4: Issue1<br />
*vo5: Issue2<br />
|<br />
|-<br />
|AsiaPacific<br />
|<br />
|<br />
|<br />
|-<br />
|CERN<br />
|<br />
|<br />
|<br />
|-<br />
|EGI.eu<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_AEGIS<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_AL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ARMGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BA<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BG<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BY<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CH<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CYGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CZ<br />
| ATLAS, ALICE, Auger, Belle, MPI, VOCE<br />
| N/A<br />
|<br />
|-<br />
|NGI_DE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_FI<br />
|<br />
NA<br />
|<br />
NA<br />
|<br />
None<br />
|-<br />
|NGI_FRANCE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_GE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_GRNET<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_HR<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_HU<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IBERGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IT<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_MARGI<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_MD<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ME<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_NDGF<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_NL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_PL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_RO<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_SI<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_SK<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_TR<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_UA<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_UK<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ZA<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_Canada<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_IGALC<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_LA<br />
|<br />
|<br />
|<br />
|-<br />
|Russia<br />
|<br />
|<br />
|<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=NGI-VO_WN_tests&diff=38986NGI-VO WN tests2012-07-30T13:18:03Z<p>Koubat: </p>
<hr />
<div>The Worker Node ('''WN''') released in '''gLite 3.2''' will be supported for security updates until September 2012. <br />
* 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)<br />
* 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.<br />
* 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<br />
<br />
<br />
NGIs are strongly suggested to provide to the supported VOs the possibility to run their code on EMI-WNs.<br />
If no sites have EMI-WN in production a possible solution could be:<br />
* 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<br />
* Enable the queue for the VOs supported by the NGI<br />
** The queue does not need to support the ops VO<br />
* Coordinate with the VO Managers, in order to have some jobs running on those WNs<br />
* Summarize the results in the table<br />
<br />
{| cellspacing="0" cellpadding="3" border="1" style="border-collapse: collapse; border:1px solid black; text-align:center;" class="wikitable"<br />
!NGI<br />
!VOs who tested successfully the EMI-WN<br />
!VOs who tested the EMI-WN with issues<br />
!Comments<br />
|-<br />
|Example<br />
|<br />
* Vo1<br />
*vo2<br />
*vo3<br />
|<br />
*vo4: Issue1<br />
*vo5: Issue2<br />
|<br />
|-<br />
|AsiaPacific<br />
|<br />
|<br />
|<br />
|-<br />
|CERN<br />
|<br />
|<br />
|<br />
|-<br />
|EGI.eu<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_AEGIS<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_AL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ARMGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BA<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BG<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_BY<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CH<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CYGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_CZ<br />
| ATLAS, ALICE, Auger, VOCE, MPI<br />
| N/A<br />
|<br />
|-<br />
|NGI_DE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_FI<br />
|<br />
NA<br />
|<br />
NA<br />
|<br />
None<br />
|-<br />
|NGI_FRANCE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_GE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_GRNET<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_HR<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_HU<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IBERGRID<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IE<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_IT<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_MARGI<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_MD<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ME<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_NDGF<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_NL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_PL<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_RO<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_SI<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_SK<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_TR<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_UA<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_UK<br />
|<br />
|<br />
|<br />
|-<br />
|NGI_ZA<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_Canada<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_IGALC<br />
|<br />
|<br />
|<br />
|-<br />
|ROC_LA<br />
|<br />
|<br />
|<br />
|-<br />
|Russia<br />
|<br />
|<br />
|<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=36858IPv6Testbed2012-05-18T14:05:29Z<p>Koubat: </p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
| GLITE UI & GridFTP server<br />
|<br />
|-<br />
|'''GARR'''<br />
| pilot.dir.garr.it <br />
|<br />
|<br />
| 193.206.106.34<br />
|<br />
| GLITE CREAM CE<br />
|<br />
|-<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| dpmhead.ipv6.farm.particle.cz<br />
| dpmhead-v4.ipv6.farm.particle.cz<br />
| dpmhead-v6.ipv6.farm.particle.cz<br />
| 147.231.25.71<br />
| 2001:718:1e01:1725::71<br />
| emi_dpm_mysql<br />
| ..<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| ui.ipv6.farm.particle.cz<br />
| ui-v4.ipv6.farm.particle.cz<br />
| ui-v6.ipv6.farm.particle.cz<br />
| 147.231.25.65<br />
| 2001:718:1e01:1725:5054:ff:fe3f:6545<br />
| gridftp server<br />
| ..<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| voms.ipv6.farm.particle.cz<br />
| voms-v4.ipv6.farm.particle.cz<br />
| voms-v6.ipv6.farm.particle.cz<br />
| 147.231.25.74<br />
| 2001:718:1e01:1725::6:91<br />
| VOMS server<br />
| VO ipv6.hepix.org - mirror of voms2.cnaf.infn.it<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| lb.ipv6.farm.particle.cz<br />
| lb-v4.ipv6.farm.particle.cz<br />
| lb-v6.ipv6.farm.particle.cz<br />
| 147.231.25.73<br />
| 2001:718:1e01:1725::73<br />
| LB (UMD repo)<br />
| ...<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
|109.127.252.39<br />
|2001:1470:8000:403::39<br />
| ARC CE<br />
|<br />
|-<br />
|'''GRNET '''<br />
| repository.egi.eu<br />
| repository.egi.eu<br />
| repository.egi.eu<br />
| 195.251.55.113, 195.251.53.182<br />
| 2001:648:2030:3000:216:3eff:fefb:3771<br />
| UMD Repository Service<br />
| ..<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=36857IPv6Testbed2012-05-18T13:57:46Z<p>Koubat: </p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
| GLITE UI & GridFTP server<br />
|<br />
|-<br />
|'''GARR'''<br />
| pilot.dir.garr.it <br />
|<br />
|<br />
| 193.206.106.34<br />
|<br />
| GLITE CREAM CE<br />
|<br />
|-<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| dpmhead.ipv6.farm.particle.cz<br />
| dpmhead-v4.ipv6.farm.particle.cz<br />
| dpmhead-v6.ipv6.farm.particle.cz<br />
| 147.231.25.71<br />
| 2001:718:1e01:1725::71<br />
| emi_dpm_mysql<br />
| ..<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| ui.ipv6.farm.particle.cz<br />
| ui-v4.ipv6.farm.particle.cz<br />
| ui-v6.ipv6.farm.particle.cz<br />
| 147.231.25.65<br />
| 2001:718:1e01:1725:5054:ff:fe3f:6545<br />
| gridftp server<br />
| ..<br />
|-<br />
|'''NGI_CZ/FZU '''<br />
| voms.ipv6.farm.particle.cz<br />
| voms-v4.ipv6.farm.particle.cz<br />
| voms-v6.ipv6.farm.particle.cz<br />
| 147.231.25.74<br />
| 2001:718:1e01:1725::6:91<br />
| gridftp server<br />
| VO ipv6.hepix.org - mirror of voms2.cnaf.infn.it<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
|109.127.252.39<br />
|2001:1470:8000:403::39<br />
| ARC CE<br />
|<br />
|-<br />
|'''GRNET '''<br />
| repository.egi.eu<br />
| repository.egi.eu<br />
| repository.egi.eu<br />
| 195.251.55.113, 195.251.53.182<br />
| 2001:648:2030:3000:216:3eff:fefb:3771<br />
| UMD Repository Service<br />
| ..<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=Top-BDII_list_for_NGI&diff=26595Top-BDII list for NGI2011-10-27T09:04:43Z<p>Koubat: /* Top-BDIIs operated by the NGIs */</p>
<hr />
<div>{{Template:Op menubar}} <br />
__TOC__<br />
= top-BDII Availability and Reliability =<br />
This page contains the list of the Top-BDII instances that are operated by the NGIs. Starting from October 2011, these instances will be considered for the generation of the '''monthly NGI Availability and Reliability report'''. <br />
<br />
Availability and Reliability figures are extracted from [https://grid-monitoring.cern.ch/myegi/sa/ MyEGI] (ROC profile, OPS VO).<br />
<br />
'''Notes''': <br />
<br />
* if you think that a wrong top-BDII entry is mentioned in the table below, please send a GGUS ticket to the Operations support unit indicating the entry to replace and the new service end-point.<br />
<br />
* the same top-BDII instance can be reported for more than one NGI. This is the case if two ore more NGIs are sharing this service, this is typically the case when they are operated by the same Operations Centre.<br />
<br />
* several top-BDII instances can be reported for one NGI. This is the case one a NGI deploys failover at client side using multiple top-BDII instances as alternative contact points ([[MAN05]]). In this case the NGI overall top-BDII hourly availability is calculated by OR-ing the hourly availability of the individual top-BDIIs.<br />
<br />
= Top-BDIIs operated by the NGIs =<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Operations Centre <br />
! Top-BDII host(s) <br />
! Notes<br />
|-<br />
| AsiaPacific <br />
| bdii.grid.sinica.edu.tw <br />
| <br><br />
|-<br />
| CERN <br />
| lcg-bdii.cern.ch <br />
| <br><br />
|-<br />
| Serbia <br />
| bdii.ipb.ac.rs <br />
| <br><br />
|-<br />
| Albania <br />
| <br />
| <br><br />
|-<br />
| Armenia <br />
| bdii.grid.am <br />
| <br><br />
|-<br />
| Austria<br />
| grid-bdii.uibk.ac.at <br />
| <br><br />
|-<br />
| Bosnia Herzegovina<br />
| c15.grid.etfbl.net <br />
| <br><br />
|-<br />
| Bulgaria <br />
| bdii.ipp.acad.bg <br />
| <br><br />
|-<br />
| Belarus <br />
| topbdii.glite.basnet.by <br />
| <br><br />
|-<br />
| Switzerland<br />
| bdii-fzk.gridka.de <br />
| <br><br />
|-<br />
| Cyprus<br />
| bdii101.grid.ucy.ac.cy <br />
| <br><br />
|-<br />
| Czech Republic <br />
| bdii1rr.farm.particle.cz<br />
| DNS alias for two instances running at different sites.<br />
|-<br />
| Germany<br />
| bdii-fzk.gridka.de <br />
| <br><br />
|-<br />
| Denmark <br />
| <br> <br />
| <br><br />
|-<br />
| Spain<br />
| gridii01.ifca.es, bdii.pic.es, topbdii01.ncg.ingrid.pt <br />
| Spanish sites also point to the Portuguese TopBDII<br />
|-<br />
| Finland <br />
| <br />
| No Top-BDII currently in use<br />
|-<br />
| France <br />
| cclcgtopbdii01.in2p3.fr,topbdii.grif.fr <br />
| <br><br />
|-<br />
| Georgia <br />
| s2.ngi.grena.ge <br />
| <br><br />
|-<br />
| Greece <br />
| bdii.marie.hellasgrid.gr,bdii01.afroditi.hellasgrid.gr,bdii.ariagni.hellasgrid.gr,bdii.athena.hellasgrid.gr,bdii.isabella.grnet.gr <br />
| <br><br />
|-<br />
| Croatia <br />
| bdii-egee.srce.hr <br />
| <br><br />
|-<br />
| Hungary<br />
| grid152.kfki.hu <br />
| <br><br />
|-<br />
| Ireland<br />
| <br />
| All sites use the CERN top-bdii<br />
|-<br />
| Israel<br />
| wipp-bdii.weizmann.ac.il <br />
| <br><br />
|-<br />
| Italy <br />
| egee-bdii.cnaf.infn.it <br />
| five instances under dns round robin<br />
|-<br />
| Lithuania <br />
| bdii.mif.vu.lt <br />
| <br><br />
|-<br />
| Latvia<br />
| bdii.grid.etf.rtu.lv <br />
| <br><br />
|-<br />
| FYR Macedonia <br />
| grid-bdii.ii.edu.mk <br />
| <br><br />
|-<br />
| Moldova <br />
| <br />
| <br><br />
|-<br />
| Montenegro<br />
| bdii.grid.ac.me <br />
| <br><br />
|-<br />
| Netherlands<br />
| kraal.nikhef.nl,bdii03.nikhef.nl,bdii.grid.sara.nl,bdii2.grid.sara.nl <br />
| <br><br />
|-<br />
| Norway<br />
| <br />
| No Top-BDII currently in use<br />
|-<br />
| Poland <br />
| bdii-top.reef.man.poznan.pl, zeus60.cyf-kr.edu.pl, topbdii.polgrid.pl <br />
| All 3 working under DNS pool bdii.cyf-kr.edu.pl<br />
|-<br />
| Portugal <br />
| topbdii01.ncg.ingrid.pt, gridii01.ifca.es, bdii.pic.es <br />
| Portuguese sites also point to the Spanish TopBDIIs<br />
|-<br />
| Romania<br />
| bdii.grid.ici.ro, bdii.nipne.ro <br />
| <br><br />
|-<br />
| Slovenia <br />
| bdii.sling.si <br />
| <br><br />
|-<br />
| Slovakia<br />
| bdii.ui.savba.sk <br />
| <br><br />
|-<br />
| Sweden <br />
| <br />
| <br><br />
|-<br />
| Turkey <br />
| bdii.ulakbim.gov.tr <br />
| <br><br />
|-<br />
| UK <br />
| lcgbdii.gridpp.rl.ac.uk,topbdii.grid.hep.ph.ic.ac.uk<br />
| <br><br />
|-<br />
| SAGrid <br />
| srvslngrd001.uct.ac.za <br />
| <br><br />
|-<br />
| IGALC <br />
| is.igalc.org <br />
| <br><br />
|-<br />
| ROC_LA <br />
| top-bdii.roc-la.org <br />
| <br><br />
|-<br />
| Russia <br />
| lcg15.sinp.msu.ru <br />
| <br><br />
|}<br />
<br />
=Algorithm =<br />
top-BDII availability/reliability statistics are based on availability/reliability data that is published by MyEGI through the SAM Programmatic Interface (SAM PI). [https://grid-monitoring.cern.ch/myegi/sa/ MyEGI] is the authoritative source of availability/reliability data (GridView is now decommissioned).<br />
<br />
A brief description of the algorithm adopted to compute top-BDII availbility and reliability statistics follows.<br />
<br />
Different schenarios are possible.<br />
<br />
== Scenario 1. Single top-BDII ==<br />
The NGI reports only one Top-BDII. It could be a single top-bdii instance, or alternatively a DNS alias for a pool of top-BDII instances (the DNS alias MUST BE monitored by the NGI Nagios). In this case Availability and Reliability are the ''monthly'' Availability and Reliability reported directly by the MyEGI Programmatic Interface.<br />
<br />
'''Note''': If the alias is used by the sites but only the single instances in the pool are monitored by Nagios, then in the table above the list of instances per NGI has to be reported. In this case Availability and Reliability are <br />
computed according to Scenario 2.<br />
<br />
== Scenario 2. List of top-BDIIs ==<br />
The NGI reports a list of top-BDIIs. These are all used by the sites to configure failover at client side. <br />
In this case the algorithm steps are the following:<br />
#Query MyEGI to get the '''hourly''' A/R values for every top-BDII instance in the list. ([[SAM_PI_examples|Example of query]])<br />
#Hourly Availability and Reliability: given the list of Availability/Reliability figures for the top-BDII in the list, the maximum Availability/Reliability figures are computed. These are selected to be the hourly Availability/Reliability. ([[SAM_PI_examples|Example of query]])<br />
#Monthly Availability and Reliability: the monthly Availability/Reliability is the arithmetic mean of the hourly Availability/Reliability figures in the reference month:<br />
::'''Monthly A/R''': (sum of the '''Hourly A/R''' figures)/(number of hours when the status was known).<br />
[[Category:Service_Level_Management]]</div>Koubathttps://wiki.egi.eu/w/index.php?title=Top-BDII_list_for_NGI&diff=26594Top-BDII list for NGI2011-10-27T09:03:21Z<p>Koubat: /* Top-BDIIs operated by the NGIs */</p>
<hr />
<div>{{Template:Op menubar}} <br />
__TOC__<br />
= top-BDII Availability and Reliability =<br />
This page contains the list of the Top-BDII instances that are operated by the NGIs. Starting from October 2011, these instances will be considered for the generation of the '''monthly NGI Availability and Reliability report'''. <br />
<br />
Availability and Reliability figures are extracted from [https://grid-monitoring.cern.ch/myegi/sa/ MyEGI] (ROC profile, OPS VO).<br />
<br />
'''Notes''': <br />
<br />
* if you think that a wrong top-BDII entry is mentioned in the table below, please send a GGUS ticket to the Operations support unit indicating the entry to replace and the new service end-point.<br />
<br />
* the same top-BDII instance can be reported for more than one NGI. This is the case if two ore more NGIs are sharing this service, this is typically the case when they are operated by the same Operations Centre.<br />
<br />
* several top-BDII instances can be reported for one NGI. This is the case one a NGI deploys failover at client side using multiple top-BDII instances as alternative contact points ([[MAN05]]). In this case the NGI overall top-BDII hourly availability is calculated by OR-ing the hourly availability of the individual top-BDIIs.<br />
<br />
= Top-BDIIs operated by the NGIs =<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Operations Centre <br />
! Top-BDII host(s) <br />
! Notes<br />
|-<br />
| AsiaPacific <br />
| bdii.grid.sinica.edu.tw <br />
| <br><br />
|-<br />
| CERN <br />
| lcg-bdii.cern.ch <br />
| <br><br />
|-<br />
| Serbia <br />
| bdii.ipb.ac.rs <br />
| <br><br />
|-<br />
| Albania <br />
| <br />
| <br><br />
|-<br />
| Armenia <br />
| bdii.grid.am <br />
| <br><br />
|-<br />
| Austria<br />
| grid-bdii.uibk.ac.at <br />
| <br><br />
|-<br />
| Bosnia Herzegovina<br />
| c15.grid.etfbl.net <br />
| <br><br />
|-<br />
| Bulgaria <br />
| bdii.ipp.acad.bg <br />
| <br><br />
|-<br />
| Belarus <br />
| topbdii.glite.basnet.by <br />
| <br><br />
|-<br />
| Switzerland<br />
| bdii-fzk.gridka.de <br />
| <br><br />
|-<br />
| Cyprus<br />
| bdii101.grid.ucy.ac.cy <br />
| <br><br />
|-<br />
| Czech Republic <br />
| bdii1rr.farm.particle.cz<br />
| <br><br />
|-<br />
| Germany<br />
| bdii-fzk.gridka.de <br />
| <br><br />
|-<br />
| Denmark <br />
| <br> <br />
| <br><br />
|-<br />
| Spain<br />
| gridii01.ifca.es, bdii.pic.es, topbdii01.ncg.ingrid.pt <br />
| Spanish sites also point to the Portuguese TopBDII<br />
|-<br />
| Finland <br />
| <br />
| No Top-BDII currently in use<br />
|-<br />
| France <br />
| cclcgtopbdii01.in2p3.fr,topbdii.grif.fr <br />
| <br><br />
|-<br />
| Georgia <br />
| s2.ngi.grena.ge <br />
| <br><br />
|-<br />
| Greece <br />
| bdii.marie.hellasgrid.gr,bdii01.afroditi.hellasgrid.gr,bdii.ariagni.hellasgrid.gr,bdii.athena.hellasgrid.gr,bdii.isabella.grnet.gr <br />
| <br><br />
|-<br />
| Croatia <br />
| bdii-egee.srce.hr <br />
| <br><br />
|-<br />
| Hungary<br />
| grid152.kfki.hu <br />
| <br><br />
|-<br />
| Ireland<br />
| <br />
| All sites use the CERN top-bdii<br />
|-<br />
| Israel<br />
| wipp-bdii.weizmann.ac.il <br />
| <br><br />
|-<br />
| Italy <br />
| egee-bdii.cnaf.infn.it <br />
| five instances under dns round robin<br />
|-<br />
| Lithuania <br />
| bdii.mif.vu.lt <br />
| <br><br />
|-<br />
| Latvia<br />
| bdii.grid.etf.rtu.lv <br />
| <br><br />
|-<br />
| FYR Macedonia <br />
| grid-bdii.ii.edu.mk <br />
| <br><br />
|-<br />
| Moldova <br />
| <br />
| <br><br />
|-<br />
| Montenegro<br />
| bdii.grid.ac.me <br />
| <br><br />
|-<br />
| Netherlands<br />
| kraal.nikhef.nl,bdii03.nikhef.nl,bdii.grid.sara.nl,bdii2.grid.sara.nl <br />
| <br><br />
|-<br />
| Norway<br />
| <br />
| No Top-BDII currently in use<br />
|-<br />
| Poland <br />
| bdii-top.reef.man.poznan.pl, zeus60.cyf-kr.edu.pl, topbdii.polgrid.pl <br />
| All 3 working under DNS pool bdii.cyf-kr.edu.pl<br />
|-<br />
| Portugal <br />
| topbdii01.ncg.ingrid.pt, gridii01.ifca.es, bdii.pic.es <br />
| Portuguese sites also point to the Spanish TopBDIIs<br />
|-<br />
| Romania<br />
| bdii.grid.ici.ro, bdii.nipne.ro <br />
| <br><br />
|-<br />
| Slovenia <br />
| bdii.sling.si <br />
| <br><br />
|-<br />
| Slovakia<br />
| bdii.ui.savba.sk <br />
| <br><br />
|-<br />
| Sweden <br />
| <br />
| <br><br />
|-<br />
| Turkey <br />
| bdii.ulakbim.gov.tr <br />
| <br><br />
|-<br />
| UK <br />
| lcgbdii.gridpp.rl.ac.uk,topbdii.grid.hep.ph.ic.ac.uk<br />
| <br><br />
|-<br />
| SAGrid <br />
| srvslngrd001.uct.ac.za <br />
| <br><br />
|-<br />
| IGALC <br />
| is.igalc.org <br />
| <br><br />
|-<br />
| ROC_LA <br />
| top-bdii.roc-la.org <br />
| <br><br />
|-<br />
| Russia <br />
| lcg15.sinp.msu.ru <br />
| <br><br />
|}<br />
<br />
=Algorithm =<br />
top-BDII availability/reliability statistics are based on availability/reliability data that is published by MyEGI through the SAM Programmatic Interface (SAM PI). [https://grid-monitoring.cern.ch/myegi/sa/ MyEGI] is the authoritative source of availability/reliability data (GridView is now decommissioned).<br />
<br />
A brief description of the algorithm adopted to compute top-BDII availbility and reliability statistics follows.<br />
<br />
Different schenarios are possible.<br />
<br />
== Scenario 1. Single top-BDII ==<br />
The NGI reports only one Top-BDII. It could be a single top-bdii instance, or alternatively a DNS alias for a pool of top-BDII instances (the DNS alias MUST BE monitored by the NGI Nagios). In this case Availability and Reliability are the ''monthly'' Availability and Reliability reported directly by the MyEGI Programmatic Interface.<br />
<br />
'''Note''': If the alias is used by the sites but only the single instances in the pool are monitored by Nagios, then in the table above the list of instances per NGI has to be reported. In this case Availability and Reliability are <br />
computed according to Scenario 2.<br />
<br />
== Scenario 2. List of top-BDIIs ==<br />
The NGI reports a list of top-BDIIs. These are all used by the sites to configure failover at client side. <br />
In this case the algorithm steps are the following:<br />
#Query MyEGI to get the '''hourly''' A/R values for every top-BDII instance in the list. ([[SAM_PI_examples|Example of query]])<br />
#Hourly Availability and Reliability: given the list of Availability/Reliability figures for the top-BDII in the list, the maximum Availability/Reliability figures are computed. These are selected to be the hourly Availability/Reliability. ([[SAM_PI_examples|Example of query]])<br />
#Monthly Availability and Reliability: the monthly Availability/Reliability is the arithmetic mean of the hourly Availability/Reliability figures in the reference month:<br />
::'''Monthly A/R''': (sum of the '''Hourly A/R''' figures)/(number of hours when the status was known).<br />
[[Category:Service_Level_Management]]</div>Koubathttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Czech_Rep.-CESNET_Metrics&diff=22154EGI-InSPIRE:Czech Rep.-CESNET Metrics2011-07-26T14:10:52Z<p>Koubat: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||20,397,856||20,488,260||25,312,840||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||2992||2992||3086||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||24658||24658||25077||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.38||1.38||1.38||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||1||1||1||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||1||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Czech_Rep.-CESNET_Metrics&diff=22150EGI-InSPIRE:Czech Rep.-CESNET Metrics2011-07-26T14:07:51Z<p>Koubat: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||20,397,856||20,488,260||25,312,840||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||2992||2992||3086||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||24658||24658||24658||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.38||1.38||1.38||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||1||1||1||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||1||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Czech_Rep.-CESNET_Metrics&diff=22144EGI-InSPIRE:Czech Rep.-CESNET Metrics2011-07-26T13:26:00Z<p>Koubat: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||20,397,856||20,488,260||25,312,840||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||2992||2992||3085||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||24658||24658||24658||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.38||1.38||1.38||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||1||1||1||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||1||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Czech_Rep.-CESNET_Metrics&diff=22142EGI-InSPIRE:Czech Rep.-CESNET Metrics2011-07-26T13:02:42Z<p>Koubat: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||20,397,856||20,488,260||25,312,840||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||2992||2992||2992||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||24658||24658||24658||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.38||1.38||1.38||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||1||1||1||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||1||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Czech_Rep.-CESNET_Metrics&diff=16598EGI-InSPIRE:Czech Rep.-CESNET Metrics2011-05-02T12:53:13Z<p>Koubat: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||20,397,856||20,488,260||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||2992||2992||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||24658||24658||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.38||1.38||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||2||2||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||1||1||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||0||0||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||1||2||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>Koubathttps://wiki.egi.eu/w/index.php?title=Agenda-14-03-2011&diff=13114Agenda-14-03-20112011-03-14T12:45:31Z<p>Koubat: /* 3.2 NGI wide WMS and top-level BDII used by Nagios */</p>
<hr />
<div>=Detailed Agenda=<br />
<br />
==1 - Information (Mario)==<br />
<br />
===1.1 - Update on status of the EMI 1.0 release===<br />
C. Aiftimiei (EMI release manager) will update the operations community about the current status of the EMI 1.0 release.<br />
<br />
===1.2 - Transition from lcg-CE to CREAM-CE===<br />
<br />
Mail from Gergely Sipos March 1 (snippet):<br />
<br />
''LCG-CE hosts are gradually being replaced by CREAM-CEs within EGI the gLite developer consortium has decided to focus its effort on the CREAM-CE and terminate support for the LCG-CE software. The exact schedule is still<br />
under discussion, but the LCG-CE software will likely reach its end of support during the summer of 2011.''<br />
<br />
''In order to help EGI user communities prepare to work with CREAM-CEs, the Operations and User Support teams of EGI.eu have prepared an information page about the CREAM-CE software and about the transfer of applications from LCG-CE to CREAM-CE:''<br />
<br />
https://wiki.egi.eu/wiki/FAQ:_lcg-ce_to_cream-ce, <br />
Support team: ucst@egi.eu<br />
<br />
===1.3 - gLite 3.1 CREAM reached end of life and DPM===<br />
<br />
Mail from Tiziana March 1 for the CREAM in glite 3.1<br />
<br />
For DPM in glite 3.1, the following NGI's showed interest: Italy, UK, Greece, Geórgia.<br />
In order for us to make any request to the developers to produce new rpm with the dependencies <br />
in voms-api version that have the mem leak fixed, we need to have early adopter sites for the test. Currently there is only one EA from the UK.<br />
<br />
===1.4 - phasing out of EGEE Grid name===<br />
<br />
Mail from Tiziana March 3<br />
<br />
Instructions are available at:<br />
https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information<br />
<br />
As of March 10: 168 sites still publish EGEE (http://gstat.egi.eu/gstat/summary/GRID/EGEE/)<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
===1.5 - Decomissioning of the old SAM infrastructure===<br />
<br />
EGI Broadcast March 7<br />
<br />
''Decommission the old SAM infrastructure by the end of June 2011.''<br />
<br />
''Document which describes the new programmatic interface:''<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/Migration+to+the+new+SAM+portal+and+programmatic+interface <br />
<br />
List of machines which are contacting old SAM (Nagioses excluded):<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/List+of+hosts+using+the+old+system<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
<br />
==2 - Staged Rollout (Mario)==<br />
<br />
===2.1 - gLite 3.1===<br />
* FTS/FTM/FTA 2.2.5: are in certification.<br />
* Torque_Utils: in staged rollout<br />
<br />
===2.2 - gLite 3.2===<br />
* Ready for Certification, in Certification - Upcoming in the next few days to staged rollout:<br />
** L&B 2.1.11<br />
** Torque_utils: re certification because of configuration issues<br />
** FTS/A/M 2.2.5<br />
* In staged rollout<br />
** TopBDII 5.1.22: under test - '''Contains the updated GOCDB url'''.<br />
** SiteBDII 5.1.22: under test<br />
** VOBOX 3.2.11: in staged rollout<br />
** UI 3.2.9: in staged rollout<br />
** Torque clients/server: The Torque utils has configuration issues, and are being solved by the developer.<br />
<br />
===2.3 - Operational Tools===<br />
* Staged rollout of SAM update 9 https://rt.egi.eu/rt/Ticket/Display.html?id=1281<br />
** SAM-U9 successfully released on 08/03/2011<br />
<br />
==3 - Operational Issues (all)==<br />
<br />
===3.1 [https://wiki.egi.eu/wiki/Jobs_work_directory_and_temportary_directory Jobs work directory and temportary directory]===<br />
We would like to discuss and finalize a long-standing issue which affects the LRMS administrators, concerning the management of the job work directory and the usage of temporary directories. A proposal is presented for discussion.<br />
<br />
===3.2 NGI wide WMS and top-level BDII used by Nagios===<br />
I would like to discuss setup of NGI Nagios services in terms of WMS/BDII used. Is there a recommended way what WMS should be used for good performance and reliability of nagios tests?<br />
Is it a good practice to set up a dedicated WMS for nagios tests with BDII limited to NGI resources?<br />
My concern comes from the fact that our CEs are sometimes marked as having problem because of non-responsive BDII/WMS.<br />
See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=67631 (-- Tomas Kouba (NGI_CZ))<br />
<br />
==4 - AOB==<br />
<br />
Next Grid Operations Meeting:<br />
<br />
28 March 2011, 14h00 Amsterdam time</div>Koubathttps://wiki.egi.eu/w/index.php?title=Agenda-14-03-2011&diff=13113Agenda-14-03-20112011-03-14T12:45:09Z<p>Koubat: /* 3 - Operational Issues (all) */</p>
<hr />
<div>=Detailed Agenda=<br />
<br />
==1 - Information (Mario)==<br />
<br />
===1.1 - Update on status of the EMI 1.0 release===<br />
C. Aiftimiei (EMI release manager) will update the operations community about the current status of the EMI 1.0 release.<br />
<br />
===1.2 - Transition from lcg-CE to CREAM-CE===<br />
<br />
Mail from Gergely Sipos March 1 (snippet):<br />
<br />
''LCG-CE hosts are gradually being replaced by CREAM-CEs within EGI the gLite developer consortium has decided to focus its effort on the CREAM-CE and terminate support for the LCG-CE software. The exact schedule is still<br />
under discussion, but the LCG-CE software will likely reach its end of support during the summer of 2011.''<br />
<br />
''In order to help EGI user communities prepare to work with CREAM-CEs, the Operations and User Support teams of EGI.eu have prepared an information page about the CREAM-CE software and about the transfer of applications from LCG-CE to CREAM-CE:''<br />
<br />
https://wiki.egi.eu/wiki/FAQ:_lcg-ce_to_cream-ce, <br />
Support team: ucst@egi.eu<br />
<br />
===1.3 - gLite 3.1 CREAM reached end of life and DPM===<br />
<br />
Mail from Tiziana March 1 for the CREAM in glite 3.1<br />
<br />
For DPM in glite 3.1, the following NGI's showed interest: Italy, UK, Greece, Geórgia.<br />
In order for us to make any request to the developers to produce new rpm with the dependencies <br />
in voms-api version that have the mem leak fixed, we need to have early adopter sites for the test. Currently there is only one EA from the UK.<br />
<br />
===1.4 - phasing out of EGEE Grid name===<br />
<br />
Mail from Tiziana March 3<br />
<br />
Instructions are available at:<br />
https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information<br />
<br />
As of March 10: 168 sites still publish EGEE (http://gstat.egi.eu/gstat/summary/GRID/EGEE/)<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
===1.5 - Decomissioning of the old SAM infrastructure===<br />
<br />
EGI Broadcast March 7<br />
<br />
''Decommission the old SAM infrastructure by the end of June 2011.''<br />
<br />
''Document which describes the new programmatic interface:''<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/Migration+to+the+new+SAM+portal+and+programmatic+interface <br />
<br />
List of machines which are contacting old SAM (Nagioses excluded):<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/List+of+hosts+using+the+old+system<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
<br />
==2 - Staged Rollout (Mario)==<br />
<br />
===2.1 - gLite 3.1===<br />
* FTS/FTM/FTA 2.2.5: are in certification.<br />
* Torque_Utils: in staged rollout<br />
<br />
===2.2 - gLite 3.2===<br />
* Ready for Certification, in Certification - Upcoming in the next few days to staged rollout:<br />
** L&B 2.1.11<br />
** Torque_utils: re certification because of configuration issues<br />
** FTS/A/M 2.2.5<br />
* In staged rollout<br />
** TopBDII 5.1.22: under test - '''Contains the updated GOCDB url'''.<br />
** SiteBDII 5.1.22: under test<br />
** VOBOX 3.2.11: in staged rollout<br />
** UI 3.2.9: in staged rollout<br />
** Torque clients/server: The Torque utils has configuration issues, and are being solved by the developer.<br />
<br />
===2.3 - Operational Tools===<br />
* Staged rollout of SAM update 9 https://rt.egi.eu/rt/Ticket/Display.html?id=1281<br />
** SAM-U9 successfully released on 08/03/2011<br />
<br />
==3 - Operational Issues (all)==<br />
<br />
===3.1 [https://wiki.egi.eu/wiki/Jobs_work_directory_and_temportary_directory Jobs work directory and temportary directory]===<br />
We would like to discuss and finalize a long-standing issue which affects the LRMS administrators, concerning the management of the job work directory and the usage of temporary directories. A proposal is presented for discussion.<br />
<br />
===3.2 NGI wide WMS and top-level BDII used by Nagios===<br />
I would like to discuss setup of NGI Nagios services in terms of WMS/BDII used. Is there a recommended way what WMS should be used for good performance and reliability of nagios tests?<br />
Is it a good practice to set up a dedicated WMS for nagios tests with BDII limited to NGI resources?<br />
My concern comes from the fact that our CEs are sometimes marked as having problem because of non-responsive BDII/WMS.<br />
See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=67631<br />
<br />
-- Tomas Kouba (NGI_CZ)<br />
<br />
==4 - AOB==<br />
<br />
Next Grid Operations Meeting:<br />
<br />
28 March 2011, 14h00 Amsterdam time</div>Koubathttps://wiki.egi.eu/w/index.php?title=Agenda-14-03-2011&diff=13112Agenda-14-03-20112011-03-14T12:44:53Z<p>Koubat: /* 3 - Operational Issues (all) */</p>
<hr />
<div>=Detailed Agenda=<br />
<br />
==1 - Information (Mario)==<br />
<br />
===1.1 - Update on status of the EMI 1.0 release===<br />
C. Aiftimiei (EMI release manager) will update the operations community about the current status of the EMI 1.0 release.<br />
<br />
===1.2 - Transition from lcg-CE to CREAM-CE===<br />
<br />
Mail from Gergely Sipos March 1 (snippet):<br />
<br />
''LCG-CE hosts are gradually being replaced by CREAM-CEs within EGI the gLite developer consortium has decided to focus its effort on the CREAM-CE and terminate support for the LCG-CE software. The exact schedule is still<br />
under discussion, but the LCG-CE software will likely reach its end of support during the summer of 2011.''<br />
<br />
''In order to help EGI user communities prepare to work with CREAM-CEs, the Operations and User Support teams of EGI.eu have prepared an information page about the CREAM-CE software and about the transfer of applications from LCG-CE to CREAM-CE:''<br />
<br />
https://wiki.egi.eu/wiki/FAQ:_lcg-ce_to_cream-ce, <br />
Support team: ucst@egi.eu<br />
<br />
===1.3 - gLite 3.1 CREAM reached end of life and DPM===<br />
<br />
Mail from Tiziana March 1 for the CREAM in glite 3.1<br />
<br />
For DPM in glite 3.1, the following NGI's showed interest: Italy, UK, Greece, Geórgia.<br />
In order for us to make any request to the developers to produce new rpm with the dependencies <br />
in voms-api version that have the mem leak fixed, we need to have early adopter sites for the test. Currently there is only one EA from the UK.<br />
<br />
===1.4 - phasing out of EGEE Grid name===<br />
<br />
Mail from Tiziana March 3<br />
<br />
Instructions are available at:<br />
https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information<br />
<br />
As of March 10: 168 sites still publish EGEE (http://gstat.egi.eu/gstat/summary/GRID/EGEE/)<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
===1.5 - Decomissioning of the old SAM infrastructure===<br />
<br />
EGI Broadcast March 7<br />
<br />
''Decommission the old SAM infrastructure by the end of June 2011.''<br />
<br />
''Document which describes the new programmatic interface:''<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/Migration+to+the+new+SAM+portal+and+programmatic+interface <br />
<br />
List of machines which are contacting old SAM (Nagioses excluded):<br />
<br />
https://tomtools.cern.ch/confluence/display/SAM/List+of+hosts+using+the+old+system<br />
<br />
Every NGI is requested to follow-up this issue internally with the respective sites.<br />
<br />
<br />
==2 - Staged Rollout (Mario)==<br />
<br />
===2.1 - gLite 3.1===<br />
* FTS/FTM/FTA 2.2.5: are in certification.<br />
* Torque_Utils: in staged rollout<br />
<br />
===2.2 - gLite 3.2===<br />
* Ready for Certification, in Certification - Upcoming in the next few days to staged rollout:<br />
** L&B 2.1.11<br />
** Torque_utils: re certification because of configuration issues<br />
** FTS/A/M 2.2.5<br />
* In staged rollout<br />
** TopBDII 5.1.22: under test - '''Contains the updated GOCDB url'''.<br />
** SiteBDII 5.1.22: under test<br />
** VOBOX 3.2.11: in staged rollout<br />
** UI 3.2.9: in staged rollout<br />
** Torque clients/server: The Torque utils has configuration issues, and are being solved by the developer.<br />
<br />
===2.3 - Operational Tools===<br />
* Staged rollout of SAM update 9 https://rt.egi.eu/rt/Ticket/Display.html?id=1281<br />
** SAM-U9 successfully released on 08/03/2011<br />
<br />
==3 - Operational Issues (all)==<br />
<br />
===3.1 [https://wiki.egi.eu/wiki/Jobs_work_directory_and_temportary_directory Jobs work directory and temportary directory]===<br />
We would like to discuss and finalize a long-standing issue which affects the LRMS administrators, concerning the management of the job work directory and the usage of temporary directories. A proposal is presented for discussion.<br />
<br />
===3.2 NGI wide WMS and top-level BDII used by Nagios<br />
I would like to discuss setup of NGI Nagios services in terms of WMS/BDII used. Is there a recommended way what WMS should be used for good performance and reliability of nagios tests?<br />
Is it a good practice to set up a dedicated WMS for nagios tests with BDII limited to NGI resources?<br />
My concern comes from the fact that our CEs are sometimes marked as having problem because of non-responsive BDII/WMS.<br />
See ticket https://gus.fzk.de/dmsu/dmsu_ticket.php?ticket=67631<br />
<br />
-- Tomas Kouba (NGI_CZ)<br />
<br />
==4 - AOB==<br />
<br />
Next Grid Operations Meeting:<br />
<br />
28 March 2011, 14h00 Amsterdam time</div>Koubat