1 / 23

JRA4 Update

JRA4 Update. Ratnadeep Abrol EPCC, The University of Edinburgh, UK. Contents. Network Performance Monitoring What is NPM? Architecture and Interface Bandwidth Allocation Reservation What is a BAR service ? Architecture & Interface for BAR Issues. Network Performance Monitoring (NPM).

luann
Télécharger la présentation

JRA4 Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JRA4 Update Ratnadeep Abrol EPCC, The University of Edinburgh, UK

  2. Contents • Network Performance Monitoring • What is NPM? • Architecture and Interface • Bandwidth Allocation Reservation • What is a BAR service ? • Architecture & Interface for BAR • Issues 2nd EGEE Conference. PTF meeting.

  3. Network Performance Monitoring (NPM) 2nd EGEE Conference. PTF meeting.

  4. What is NPM? • Main function • Provides network performance data • to high level middleware (JRA1) • available bandwidth between end sites (CEs and SEs) • allows for calculation of equivalent of Network Cost Function in EDG • to NOCs and GOCs • end site and backbone statistics • e.g. round trip time, one way delay, available bandwidth... • to end users • end site statistics • allows simple examination of network problems 2nd EGEE Conference. PTF meeting.

  5. What is NPM? • Additional functions • Running on demand network tests • for NOCs and GOCs • useful for diagnosing faults • Alarms • for NOCs and GOCs • useful for diagnosing faults 2nd EGEE Conference. PTF meeting.

  6. Architecture and Interface 2nd EGEE Conference. PTF meeting.

  7. High Level Overview • Provides access to Network Monitoring Frameworks • End to End Frameworks • e.g. PingER, EDG WP7, GridMon, IEPM-BW, home grown • Backbone Frameworks • e.g. perfmonit, GN2’s own, Internet2, piPEs, home grown 2nd EGEE Conference. PTF meeting.

  8. NPM Glue High Level Overview Middleware GOC/NOC End Site NPM request End Site or Backbone NPM request End Site EDG WP7 End Site Home grown Backbone GN2 Backbone Perfmonit Backbone piPEs 2nd EGEE Conference. PTF meeting.

  9. Framework Interfaces • Problem: Each framework exposes own interface • NM-WG • piPES, perfmonit • R-GMA • EDG WP7 • Flat file • GridMon • Solution: Require that frameworks support NM-WG • NM-WG is GGF working group • “NMWG will determine with of the network characteristics are relevant to Grid applications and pursue standardization of the attributes to describe these characteristics.” • Define a request/report schema to gather network monitoring statistics. 2nd EGEE Conference. PTF meeting.

  10. NPM Glue NM-WG End Site Home grown NM-WG NM-WG NM-WG Backbone GN2 Backbone Perfmonit Backbone piPEs High Level Architecture Middleware GOC/NOC NM-WG End Site EDG WP7 2nd EGEE Conference. PTF meeting.

  11. Interaction with NPM • High Level Middleware • Similar to interaction with WP7 in EDG • End site information published to a Grid Information System (GIS) • HLM retrieves information from GIS • NOC/COG • Interacts with diagnostic client • Allows measurement to be built up from along a route • Require backbone as well as end site information • Will talk directly to NPM Glue • End users • Interacts with simple client • Provides information on current state of the network • Will talk directly to NPM Glue 2nd EGEE Conference. PTF meeting.

  12. Grid Information System NM-WG NPM Glue NM-WG End Site Home grown NM-WG NM-WG NM-WG Backbone GN2 Backbone Perfmonit Backbone piPEs High Level Architecture – take 2 GOC/NOC Middleware Diagnostic Client NM-WG End Site EDG WP7 2nd EGEE Conference. PTF meeting.

  13. Bandwidth Allocation and Reservation (BAR) 2nd EGEE Conference. PTF meeting.

  14. What is a BAR service ? • The BAR service will allow (JRA1) Higher Level Middleware (HLM) to reserve network services between two end points. • Middleware, for example, can use this service to request reservations on guaranteed bandwidth between two end-points during a certain period of time. • Or it can use this service to reserve a transfer of given volume of data within a given period of time between two end-points. 2nd EGEE Conference. PTF meeting.

  15. BAR Requirements • Time-windowed bulk transport • Guarantee of average bandwidth, B, starting at time S and ending at time E. • ‘Guaranteed and Configurable Bandwidth’ requirement from the joint document. • Time-windowed bandwidth guaranteed transport • Fixed guaranteed bandwidth, B, starting at time S and ending at time E. • ‘Guaranteed Delivery Time’ requirement from the joint document. • Time-windowed high reliability transport • Option to guarantee a very high reliability. In other words, an option that provides better Mean Time Between Failures (MTBF). • ‘Restoration after Failure’ requirement from the joint document. 2nd EGEE Conference. PTF meeting.

  16. BAR Requirements • Confidential transport • Implement a high confidentiality connection option. • ‘Encryption During Transmission’ requirement from the joint document. • Long term mission critical transport • Minimum possible latency and very high reliability over a long period. • ‘Long Term Low Latency Low Bandwidth QoS’ requirement from the joint document • Time-windowed delay/jitter sensitive transport. • Low latency and jitter, starting at time S and ending at time E. • ‘Long Term Low Latency Low Bandwidth QoS’ requirement from the joint document 2nd EGEE Conference. PTF meeting.

  17. Architecture and Interface 2nd EGEE Conference. PTF meeting.

  18. An architecture for BAR • An overview of how BAR fits into rest of the architecture 2nd EGEE Conference. PTF meeting.

  19. Interface to BAR • The document DJRA4.1, “Specification of Interfaces For Bandwidth Reservation Service”, shows the current view on the BAR interface. • Absolutely not cast in stone • https://edms.cern.ch/document/501154/1 • The document gives detailed explanation of types of reservation services offered by BAR • Please send comments to: project-eu-egee-jra4@cern.ch 2nd EGEE Conference. PTF meeting.

  20. BAR Web Services • JRA4 BAR translates HLM to NSAP and vice versa • It assumes the HLM (JRA1) and the NSAP (GN2) functionality. • As a result, some of the requirements may not be possible to be catered for, as the necessary Network facilities may not be available within the EGEE timeframe 2nd EGEE Conference. PTF meeting.

  21. Port Types • RequestService makes initial request • E.g., to reserve a guaranteed bandwidth between two end points. • ModifyService • Complex task we need to understand better • Prototype due Feb ’05 will help • CancelService • QueryService • Notification • Start/end times • Failure of request 2nd EGEE Conference. PTF meeting.

  22. Issues 2nd EGEE Conference. PTF meeting.

  23. Issues • Requirements clarification and prioritisation • Collaboration with GN2, EGEE::SA2 and EGEE::JRA1 mainly • Authorisation and Authentication • JRA1 will use VOMS • Network is likely to use Shibboleth or PERMIS • WS-Agreement • To integrate or not to integrate? • BAR and NPM should share AAA architecture, perhaps implementation • Do they really have anything else in common? 2nd EGEE Conference. PTF meeting.

More Related