1. INFSO-RI-508833 Enabling Grids for E-sciencE www.eu-egee.org Network Services Development Network Resource Provision 3 rd EGEE Conference, Athens, 20 th April 2005 K. Kavoussanakis, EPCC, The University of Edinburgh J-P. Gautier, CNRS

2. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 2 Activities SA2 –Operational Interface EGEE  Network (Geant + NRENs) –SLAs EGEE  Network (Geant + NRENs) –Technical Network Liaison Committee JRA4 –Network Performance Monitoring –Bandwidth Allocation and Reservation –IPv6 These activities are by design building an important working relation between EGEE and the network providers (GÉANT + NRENs)

3. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 3 SA2: Network Resource Provision

4. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 4 TNLC Network Operational Interface between EGEE-NRENs –Agreement with NRENs will be sought –TNLC approved proposed Operational Interface, discussed in MSA2.3 SLAs are new to the NREN community and for EGEE –Plan for institution of SLAs described in DSA2.2 –The QoS experiment will help validate the proposed process Agreed to limit BAR pilot to 2, perhaps 3 NRENs –That’s as many have agreed in principle to deploy software –Buy in from other NRENs can be achieved based on the success of the pilot

5. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 5 Network Operational Interface: The aim of the work Operational model Operational entities – Actors – Roles – Responsibilities Operational procedures – Detection – Troubleshooting – Maintenance The main purpose of the work (MSA2.3) is to design an operational support environment for EGEE as network customer of the GEANT/NREN community.

6. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 6 Network Operational Interface: The model Assumptions –GEANT/NRENs agree to signal their network problems to EGEE; –EGEE can signal network problems to GÉANT/NRENs. To keep the model simple –Use of Global Grid User Support (GGUS) –Setting up an EGEE Network Operation Support (ENOC) –Minimal extra work for the NREN NOCs

7. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 7 Network Operational Interface: Trouble ticket system workflow 1 2 3 4 4 4

8. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 8 Network Operational Interface: Future Work Deployment: –Organization of an “operational test-bed” during Summer 2005  2 organisations: DANTE, Renater  SA2 people with SA1 collaboration. Ticket processing Integration: –Compliance of ENOC operational model with SA1/Support_Unit workflow scenarios.

9. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 9 SLA institution (DSA2.2): Model The GÉANT/NREN community can currently offer two types of border-to-border services: –Best-Effort IP service –Premium IP service

10. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 10 SLA institution (DSA2.2): Services All domains involved in network services provisioning to EGEE as part of the existing network infrastructure hierarchy have to be categorized as: –Compliant with the Premium IP service –Supportive of the Premium IP service –Indifferent to the Premium IP service

11. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 11 SLA institution (DSA2.2): Establishment of SLAs An end-to-end EGEE SLA is a collection of per domain SLAs.

12. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 12 JRA4: Network Services Development

13. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 13 Network Performance Monitoring Standardising access to NPM across different domains. –GGF NM-WG recommendation is the selected basis for standardisation End Site EDG WP7 NM-WG Backbone Perfmonit NM-WG End Site Home grown NM-WG Backbone PiPEs NM-WG Backbone GN2 NM-WG Some Client

14. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 14 NPM Architecture End Site EDG WP7 NM-WG Backbone Perfmonit NM-WG End Site Home grown NM-WG Backbone PiPEs NM-WG Backbone GN2 NM-WG JRA4 NPM Mediator NM-WG GOC/NOC Diagnostic Client JRA1::WMS JRA1::DMS

15. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 15 MJRA4.3: NPM Prototype Prototype implementation of NPM for NOC/GOC use Provides access to: –End site data (WP7/R-GMA) –Backbone data (Perfmonit) Data exposed through web services implementing a single interface –Including transport layer security as per JRA3 Requests are made using schema defined by GGF’s Network Measurements Working Group –NPM Prototype demoed as part of NM-WG GGF session Demonstrates aggregation of data along a hop list

16. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 16 NPM Prototype Deployment

17. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 17 NPM Prototype Setup

18. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 18 NPM Future Plans NPM getting into gLite CVS –Including EDG::WP7 tools A Diagnostic Tool with a graphical interface for use by NOCs and GOCs will be developed by September 2005 The Mediator will be separated into a stand-alone web service and the NM-WG interfaces will be updated to match the current standard Working with SA1 on network monitoring deployment

19. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 19 Bandwidth Allocation and Reservation (BAR) To allow reservation of a network service between two endpoints –Assuming underlying functionality from the network providers For EGEE-1 the network service will be “IP-Premium” Goal is to show first programmatic interface between EGEE and GÉANT

20. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 20 BAR Architecture Network 1Network 2Network 3

21. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 21 BAR Status First prototype produced end of February –Interface implementations –2 different webservices for BAR and NSAP –Dummy client and NSAP –Not dealing with LNSAP problem Working on security architecture with JRA3 Migration of code to gLite CVS

22. Enabling Grids for E-sciencE INFSO-RI-508833 EGEE-3, Athens; Network Service Development & Resource Provision 22 BAR Future Plans Working on improved prototype for end of June (MJRA4.4) and the overall design (MJRA4.5) –Rewriting prototype code –Adding security –Still not dealing with LNSAP –3 NRENs provisionally agreed to deploy NSAP software for EGEE pilot (GRNET, GARR, UKERNA) EGEE cannot write NSAP and timescales with GN2 not coinciding –Important part is the interface and the webservice –Interface designed together with partners DANTE