EGEE data access

From GEANT2-JRA1 Wiki

EGEE JRA4 (Network Performance Measurement) need to have access to some monitoring information from the NRENs. This page aims at (i) providing information about the timeline for which EGEE needs the data, (ii) at describing what EGEE intend to do with those data and (iii) who will have access to those data from the EGEE community. An outline about the status of the access provided by the NRENs is also provided. (EGEE JRA4)

Contents 1 Purpose 2 NREN Data Accessibility Status 3 EGEE user access 4 EGEE preferred sites 5 Timeline

Purpose

EGEE is requesting access to link utilisation and link capacity from the backbone circuits as well as form the access circuit whenever available. Their aims is to have access to available bandwidth information.

EGEE JRA4 is developing a diagnostic tool for the GOCs (Grid Operations Centres) and ROCs (Regional Operations Centres) which presents the data from end-sites and backbones networks. The ROC and GOC will have access to the data provided by the NRENs. A general (non-ROC) EGEE user, e.g. an end user, can only access coarse utilisation data - i.e. utilisation between ". <30%", "30 < . <50%", ". >50%".
The data will be used by EGEE (i) for demonstration purpose (end of September, they would wish to have access to the data from three different networks), (ii) to provide information about the network, and (iii) gather feedback from their community of users over the next months. For this, they wish thus to cover the network between all the LHC Tier1 centers (#EGEE preferred sites - from October onwards).

The data will be made available to EGEE JRA4 trough the NM-WG v2 interface. This will implies that the NREN will have to deploy the perfSONAR MA service and modify the service engine to access to the data stored on their measurement archives (for example, the prototype MA has a RRDTypeMAServiceEngine which is in charge of accessing a RRDB) Another way is to develop your own script in e.g. python (this requires knowledge about web-services). If you wish to have secure communication with EGEE you will need to have a certificate and use ssl.

NREN Data Accessibility Status

NREN	Link Utilisation	Capacity	ROC access	EGEE User Access	Deployment status
Abilene	Yes	Yes	Yes	Yes	tbc
ESnet	Yes	Yes	Yes	Yes	tbc
GARR	Bakcbone, access to be confirmed	Backbone, access to be confirmed	Yes	tbc	tbc. Note: data stored in mrtg log files
GRNet	tbc	tbc	Yes	tbc	tbc - note: Are using MRTG files
GEANT	Backbone and access	Backbones and access	Yes	Yes	Access link utilisation up and running, backbone data and capacity available mid-September
Hungarnet	tbc	tbc	tbc	tbc	tbc
PSNC	tbc	tbc	tbc	tbc	tbc
REDIris	Backbone, access tbc	Backbones, acceses tbc	Yes	tbc	Tbc: are using their own format, but will provide the interface.
Uninett	Backbone	tbc	Yes	Yes	tbc

• The network "backbone data" are the information retrieved from or between equipment from the network itself (single administrative authority).
• The network "access data" are the information retrieved from the links inter-connecting two different network (two administrative authority, e.g. between GEANT and a NREN, between a NREN and a university, between a NREN and it's global connectivity provider).
• It is expected that it will take more time to offer the information for the NRENs who are not using the RRD from cricket as they have to develop their own service engine.

EGEE user access

• The ROC and GOC will have access to the data provided by the NRENs
• A general (non-ROC) EGEE user, e.g. an end user, can only access coarse utilisation data - i.e. utilisation between ". < 30%", "30 < . < 50%", ". < 50%".

This restriction will be enforced within EGEE by appropriate use of VOMS roles. It will be enforced in the (JRA4) perfSonar Translation Layer by limiting the results users without the ROC role receive, until security is in place in perfSonar. Once perfSonar security is in place, the Translation Layer will map EGEE users with the ROC role to a perfSonar user with appropriate access rights, and EGEE users without the ROC role to another perfSonar user that can only access the coarse utilisation data.

Since the restriction relies on EGEE VOs appropriately assigning roles and a Translation Layer that can be trusted to uphold the requirements, there is a need to have a data disclosure agreement between the EGEE and the GN2 projects and/or Abilene and/or ESnet at some level.

EGEE preferred sites

Below the list of sites of importance for the EGEE project between which they would wish to get access to monitoring information.

• ASCC (Taiwan, ASnet)
• CNAF (Italy, GARR)
• PIC (Spain, redIRIS)
• CC-IN2P3 (France, Renater)
• GridKA (Germany, X-WIN)
• RAL (UK, SuperJANET)
• BNL (NY, USA, ESnet)
• FNAL (IL, USA, ESnet)
• TRIUMF (Canada, Ca*Net 4, Netherlight)
• NIKHEF/SARA (Netherlands, Surfnet 6)
• Nordic data grid (Distributed, Nordic countries)

The prefered places with which EGEE would like to start with are SuperJANET, GARR, redIRIS, Renater, X-WIN, Surfnet 6.

Timeline

1. September 2005 : link utilisation and link capacity provided by at least three networks: GEANT (candidates: ESnet, Abilene, PSNC, Uninett)
2. October 2005 onwards: link utilisation and link capacity provided by more NRENs willing to do so.