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.
Top-BDII list for NGI
Revision as of 09:26, 14 October 2011 by Tferrari (talk | contribs) (→Top-BDIIs considered for NGIs core services availability computation)
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Top-BDIIs operated by the NGIs
The following table 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 report.
Availability figures are extracted from MyEGI (ROC profile, OPS VO).
Notes:
- 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.
- 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.
- 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.
| Operations Centre | Top-BDII host(s) | Notes |
|---|---|---|
| AsiaPacific | bdii.grid.sinica.edu.tw | |
| CERN | lcg-bdii.cern.ch | |
| Serbia | bdii.ipb.ac.rs | |
| Albania | ||
| Armenia | bdii.grid.am | |
| Austria | grid-bdii.uibk.ac.at | |
| Bosnia Herzegovina | c15.grid.etfbl.net | |
| Bulgaria | bdii.ipp.acad.bg | |
| Belarus | topbdii.glite.basnet.by | |
| Switzerland | bdii-fzk.gridka.de | |
| Cyprus | bdii101.grid.ucy.ac.cy | |
| Czech Republic | bdii1.egee.cesnet.cz | |
| Germany | bdii-fzk.gridka.de | |
| Denmark | ||
| Spain | gridii01.ifca.es, bdii.pic.es, topbdii01.ncg.ingrid.pt | Spanish sites also point to the Portuguese TopBDII |
| Finland | No Top-BDII currently in use | |
| France | cclcgtopbdii01.in2p3.fr,topbdii.grif.fr | |
| Georgia | s2.ngi.grena.ge | |
| Greece | bdii.marie.hellasgrid.gr,bdii01.afroditi.hellasgrid.gr,bdii.ariagni.hellasgrid.gr,bdii.athena.hellasgrid.gr,bdii.isabella.grnet.gr | |
| Croatia | bdii-egee.srce.hr | |
| Hungary | grid152.kfki.hu | |
| Ireland | All sites use the CERN top-bdii | |
| Israel | wipp-bdii.weizmann.ac.il | |
| Italy | egee-bdii.cnaf.infn.it | five instances under dns round robin |
| Lithuania | bdii.mif.vu.lt | |
| Latvia | bdii.grid.etf.rtu.lv | |
| FYR Macedonia | grid-bdii.ii.edu.mk | |
| Moldova | ||
| Montenegro | bdii.grid.ac.me | |
| Netherlands | kraal.nikhef.nl,bdii03.nikhef.nl,bdii.grid.sara.nl,bdii2.grid.sara.nl | |
| Norway | No Top-BDII currently in use | |
| Poland | bdii-top.reef.man.poznan.pl, zeus60.cyf-kr.edu.pl, topbdii.polgrid.pl | All 3 working under DNS pool bdii.cyf-kr.edu.pl |
| Portugal | topbdii01.ncg.ingrid.pt, gridii01.ifca.es, bdii.pic.es | Portuguese sites also point to the Spanish TopBDIIs |
| Romania | bdii.grid.ici.ro, bdii.nipne.ro | |
| Slovenia | bdii.sling.si | |
| Slovakia | bdii.ui.savba.sk | |
| Sweden | ||
| Turkey | bdii.ulakbim.gov.tr | |
| UK | lcgbdii.gridpp.rl.ac.uk | |
| SAGrid | srvslngrd001.uct.ac.za | |
| IGALC | is.igalc.org | |
| ROC_LA | top-bdii.roc-la.org | |
| Russia | lcg15.sinp.msu.ru |
Computation algorithm
A brief description of the algorithm used for the availability calculation.
There could be two different scenarios:
- The NGI reports only one Top-BDII. It could be a single top-bdii instance, or an alias for a DNS pool, but it has to be monitored by the NGI Nagios. If the alias is used by the sites but only the single instances in the pool are monitored, the NGI should enter the list of the instances. In this case the Availability and Reliability statistics are calculated asking directly the monthly values for the service to MyEGI.
- The NGI reports a list of Top-BDII that are used by the sites to configure failover at client side. In this case the steps are the following
- Query MyEGI to get the hourly A/R values for every top-BDII listed
- Select, for every hour, the best availability/reliability performance of the top-BDIIs
- Calculate the average of this selected values: (sum of the best performance selected)/(number of hours where the status was known)