JRA 4 F 2 F CERN 1415 OCt

JRA 4 -F 2 F CERN 14/15 OCt 2004 www. eu-egee. org Pete playing devils advocate EGEE is a project funded by the European Union under contract IST-2003 -508833

Critique of Subactivity: NPM • What are we trying to achieve ? § See TA high level description <BAR Survey, Cambridge> <8 September 2004> - 2

Critique of Subactivity: NPM • • What is it primarily about § Standardising meaning of NP information § Deploying standardised access to NP information for a range of consumers § First opportunity for coherent scheme including EGEE sites and GNs domains § Recasting existing work into web services framework § Getting agreement form all sites and domains to deploy a standard framework (regardless of its initial content) § Developing diagnostic tools for GOC and ROC § Making the information useful to Higher Layer Middleware (HLM) in EGEE What is it NOT about § Developing yet another implementation with no context (enough of these exist: WP 7, IEPM, Pipes, Grid. Mon, Perfmonit, Mona. Lisa). These are all potential backends/frontends. § Deploying an arbitrary implementation at EGEE and other sites (we could have just used WP 7 for this). § Monitoring tool development (IPerf, Ping…. ) (this is secondary) § Worrying unduly about what measurements mean (at least in first instance) <BAR Survey, Cambridge> <8 September 2004> - 3

Strawman architecture (not rpoperly designed yet) EGEE Resource Information System JRA 4 code to publish (& interpolate ? ) Interface based on GGF-NMWG Imp 1 Imp 3 NREN Imp 3 Geant Inet-2 <BAR Survey, Cambridge> <8 September 2004> - 4

Strawman architecture (not rpoperly designed yet) GRM JRA 4 code to query for GRM Interface based on GGF-NMWG Imp 1 Imp 3 NREN Imp 3 Geant Inet-2 <BAR Survey, Cambridge> <8 September 2004> - 5

Strawman architecture (not rpoperly designed yet) Diagnostic Services for GOCs JRA 4 code For network diagnostics Interface based on GGF-NMWG Imp 1 Imp 3 NREN Imp 3 Geant Inet-2 <BAR Survey, Cambridge> <8 September 2004> - 6

Where might existing work fit in this ? EGEE Resource Information System WP 7 R-GMA work ? ? WP 7 Imp 3 NREN Perfmonit Geant Inet-2 <BAR Survey, Cambridge> <8 September 2004> - 7

GN 2 code Interface based on GGF-NMWG Imp 1 (WP 7? ) Imp 3 NREN Imp 3 Geant Inet-2 <BAR Survey, Cambridge> <8 September 2004> - 8

Critique of Subactivity: NPM • How to plan § Develop a project plan based upon what we need to achieve by when § Look at bigger picture than simply the “ titles of the deliverables” § Realise this is first opportunity for coherent scheme including EGEE sites and GNs domains, and just getting a basic framework deployed will be a major achievement. Getting the content perfect is a secondary goal. • • § Re assign effort to achieve (i) consolidation i. e. no 0. 5 PM here and there (ii) use strengths § Put in place a much more formal project mangement structure so that every one knows what they are meant to do Milestones and deliverables § Merely a punctuation of project plan – not a definitive receipe for success § These DO NOT define a complete project plan. Current WBS § Only a first iteration § Fine up to PM 6 in most places (requirements, surveys) § Inadequate in terms of getting a framework deployed in a timely fashion • Not enough understanding of time needed to get first iteration of architecture & interfaces defined • No explicit planning for a long and resource intensive software development cycle to get prototype framework on ground by PM 9 (this is a fault of the TA) <BAR Survey, Cambridge> <8 September 2004> - 9

Critique of Subactivity: NPM • Key omissions in WBS § Understanding that prototype work is needed to define interfaces • § You don’t just write them down and assume they work Understanding that web services framework development is needed for any of this to mean anything, and that this needs § • a proper canonical software development approach, • a long lead time • This has nothing to do with measurement implementation, which is a back end to the framework • Should have started much earlier Understanding that defining an AA solution requires serious effort <BAR Survey, Cambridge> <8 September 2004> - 10

In my opinion Q 1 Q 2 Q 3 Q 4 Q 5 Q 6 Q 7 Q 8 Requirements… Target: Something Surveys… working Prototype WS based standard which is a interface framework deployedstep towards overall goals Arch 1 by ~ PM 10 Interface 1 Why: AA 1 WS-Framework 1 Arch 2 WP 7 exists NMWG exists Why take longer ? Interface 2 AA 2 WS-Framework 2 Backend for EGEE sites Simple Client <BAR Survey, Cambridge> <8 September 2004> - 11

Performance Monitoring Project Month Deliverable or Milestone Item M 6 Milestone MJRA 4. 1 Requirements and use cases for monitoring and diagnostics tools for users, middleware and operations. M 6 Milestone MJRA 4. 2 Definition of initial network performance metrics and composite measurements required. M 9 Deliverable DJRA 4. 2 Definition of standardised network measurement query/response interfaces, with adequate authorization. M 12 Milestone MJRA 4. 3 Prototype tool to access network performance metrics from a limited set of measurement points. M 18 Milestone MJRA 4. 6 Specification high-level monitoring and diagnostics tools. Revision of network performance metrics. M 21 Deliverable DJRA 4. 5 Service to supply network performance information to resource brokering middleware. M 24 Deliverable DJRA 4. 7 Report on network monitoring within EGEE. <BAR Survey, Cambridge> <8 September 2004> - 12

Bandwidth on Demand Project Month Deliverable or Milestone Item M 6 Deliverable DJRA 4. 1 Specification of interfaces I) to network control plane, II) to global resource reservation middleware for bandwidth allocation and reservation. M 15 Milestone MJRA 4. 4 Prototype Implementation of bandwidth allocation and reservation service at specific network ingress points using static network configuration. M 15 Milestone MJRA 4. 5 Specification of end-to-end bandwidth reservation system. M 18 Milestone MJRA 4. 7 Dynamic re-configuration of key ingress points in response to reservations. M 21 Deliverable DJRA 4. 4 Implementation of pilot single-domain bandwidth allocation and reservation service in the network core (GEANT and NRENs). M 24 Deliverable DJRA 4. 6 Report on bandwidth allocation and reservation in EGEE. <BAR Survey, Cambridge> <8 September 2004> - 13

Network Resource Allocation and Reservation Source Dest EGEE Middelware Site Broker Net Broker Site Broker Configure Configure Site NRE N-A Geant NREN -B Site <BAR Survey, Cambridge> <8 September 2004> - 14

DJRA 4. 1 EGEE Middleware Resource Provider EGEE-Network Liaison AAA Configure Site Configure NRE N-A Static SLA Geant NREN -B Static SLA Site Static SLA [Note: For example, GRS project of S. Bhatti, UCL] <BAR Survey, Cambridge> <8 September 2004> - 15

IPv 6 Proj ect Mon th Deliver able or Milesto ne Item M 18 Deliver able DJRA 4. 3 Report on implications of IPv 6 usage for the EGEE Grid. <BAR Survey, Cambridge> <8 September 2004> - 16

JRA 4 IPv 6 Policy Statement q EGEE agreed with 6 NET at the time of the original proposal to work with 6 NET to § promote IPv 6, § make EGEE software developers aware of IPv 6 coding practice, § investigate the possibility of trying some EGEE code on a limited IPv 6 testbed q This agreement is codified in the relevant deliverable DJRA 4. 3 q This has not been critical path in comparison to initial requirements gathering deliverables an milestones, and hence it was natural and timely to leave this until after PM 6 q JRA 4 has now started on this. We have § held a preliminary meeting with Piers O'Hanlon from 6 NET § spoken at high level with senior 6 NET personnel (Kirstein, Butler) to re-affirm intentions q We remain as committed as ever to work with 6 NET, and our intentions are to § hold sessions on IPv 6 awareness raising (Ne. SC training) § promote good practice for writing code independent of IPv 4/6 (Ne. SC training § Investigate whether some joint IPv 6 testbed work is feasible. q We now plan to hold a telecon soon in October to take this forward I <BAR Survey, Cambridge> <8 September 2004> - 17

Middleware service Site 1 Site 2 Domain 3 Domain 1 Domain 2 <BAR Survey, Cambridge> <8 September 2004> - 18

Suggestion 1: Hierarchical Middleware Transport Service Data Volume V transferred from A to B in time T LOGICAL User Service Network oriented service requestor Min/Max bandwidth over time T from a to B Site LOGICAL Service Physical Service IP Premium width DSCP C in this domain for bandwidth B in a period T LOGICAL Service Physical Service Domain A Site Domain B Domain C MPLS-VPN tunnel in this domain for bandwidth B in a period T <BAR Survey, Cambridge> <8 September 2004> - 19

Suggestion 2: Sequential Middleware Transport Service LOGICAL Service Network Oriented Service requestor Site LOGICAL Service Physical Service Domain A LOGICAL Service Domain B Domain C <BAR Survey, Cambridge> <8 September 2004> - 20

Network Performance Architecture R-GMA SP Middleware NM-WG Tool X Domain A NM-WG Tool Y Tool Z Domain B Domain C <BAR Survey, Cambridge> <8 September 2004> - 21

Authorisation Auditing Grid Access Service Grid Middleware Information and Monitoring Accounting Data Management Site Gatekeeper Workload Management Monitoring Authentication Network Performance Interfaces with Grid Middleware Bandwidth Allocation and Reservation <BAR Survey, Cambridge> <8 September 2004> - 22

• Review WBS [P. Clarke] • Review and assign effort allocation to this task, a sit needs both § Network experts § Experienced software developers <BAR Survey, Cambridge> <8 September 2004> - 23

Components and Requirements Consumer (User Application) Operations Interface End-user Interface Operations Grid Middleware Interface Computer Element NE-A NE-B Network Element Storage Element NE-X Network (GEANT+NRENs) <BAR Survey, Cambridge> <8 September 2004> - 24

Bandwidth Allocation & Reservation 5. - Resource Management 4. - Path Discovery 3. - Can Allocate Resource ? 2. - Topology Discovery 1. - Authentication Authorization BB C BB-C NREN C Resource Management Path Discovery END Can Allocate Resource ? Topology Discovery Authentication Authorization BB-A NOW !!! A NREN A BB-B GEANT NREN B BB ie. : One flow from A to B Bandwidth Broker Traffic flows Signalling between BB Provisioning devices B <BAR Survey, Cambridge> <8 September 2004> - 25

Bandwidth Allocation & Reservation 2. - Path Discovery 1. - Authentication Authorization Multi. Domain-BB C BB-C NOW !!! BB NREN C 4. - Resource Management 3. - Can Allocate Resource ? 2. - Topology Discovery 1. - Authentication Authorization BB-A A NREN A BB-B GEANT NREN B BB ie. : One flow from A to B Bandwidth Broker Traffic flows Signalling between BB Provisioning devices B <BAR Survey, Cambridge> <8 September 2004> - 26

Network Performance Monitoring • Grid Performance closely linked to Network Performance • Network Performance? , what for? : § Problem diagnostic and rectification § Facilitate resources allocation § Performance monitoring and SLA adherence Grid Middleware NOC: Network Operation Center GOC: Grid Operation Center GOCs NOCs Operations Information Service (R-GMA) Common Interface (OGSA) Domain_A Grid Users Domain_B . . Network (GEANT+NRENs) Domain_X <BAR Survey, Cambridge> <8 September 2004> - 27

Net. Perf. Monitoring: Use case example ie. OWD from point A to B ? DM 1 DM 2 DM 3 We. We got. DON’T that already yet A PMS 1 NREN A PMS 2 PMS 3 GEANT B NREN B OWD=OWD 1+OWD 2+OWD 3 • • PMSx and DMx § Are independent implementation for the measurements Features § Multiple domains, AAA, OGSA/OGSI DM Domain Manager PMS Performance Monitoring System Signalling between DM Request of Measurement <BAR Survey, Cambridge> <8 September 2004> - 28

Thank you Questions? <BAR Survey, Cambridge> <8 September 2004> - 29