Pete Clarke– GridPP 6 – 31 Jan n° 1 EGEE EGEE - The Network Sector

Pete Clarke– GridPP 6 – 31 Jan n° 2 EGEE EGEE - The Network Sector WHY ? u Operation of EGEE relies upon Geant and NRENs u A priori EGEE will make demanding requirements: s Topology of Traffic loads s Value added services over and above best efforts IP u …etc….. u Inconceivable that HEP should not influence EGEE u Inconceivable that UK would not wish to be a partner u EU mandates close co-operation with Geant u Is one of the things everyone is happy for the UK to coordinate (at present)

Pete Clarke– GridPP 6 – 31 Jan n° 3 EGEE GeantEGEE First task is to define what fits legitimately in scope of EGEE

Pete Clarke– GridPP 6 – 31 Jan n° 4 EGEE Geant Policy Committee NRENUKERNA …………….. DFN DANTE TERENA NL UKIT ……………..

Pete Clarke– GridPP 6 – 31 Jan n° 5 EGEE u Additional capacity requirements: n It is possible that upgrades to INTERNATIONAL links are required specifically for the Grid infrastructure. Case will have to be made from EGEE. u Requirements capture and modelling u Performance monitoring & Diagnostics n Need integrated End-to-end performance monitoring and diagnostic services ( Instrumentation throughout network (core and edges), Diagnostic engines) n GOPS (Grid Ops centre) will need access to comprehensive tools in addition to the above

Pete Clarke– GridPP 6 – 31 Jan n° 6 EGEE u Production services for control and allocation of network resources (i.e. Bandwidth, Qos, Secure Virtual Networks, Extended VLANs….) n User interface to scheduling and reservation services n e2e control plane n provisioning mechanisms n Interface to Grid middleware n Scalability n..of course AAA u Data Transport: n Key to Grid operations. n Must ensure results of current projects to achieve > Gbit/s transport become usable by Grid centres.

Pete Clarke– GridPP 6 – 31 Jan n° 7 EGEE u Convene working group which represents stakeholders u Define scope (Ensure boundaries and relation between Geant infrastructure and EGEE infrastructure funding are agreed and clear) u Start to prepare a work package for proposal…… u Hold meetings Next steps

Pete Clarke– GridPP 6 – 31 Jan n° 8 Intermission

Pete Clarke– GridPP 6 – 31 Jan n° 9 GridPP-2 Middleware DEVELOPMENT & SUPPORT

Pete Clarke– GridPP 6 – 31 Jan n° 10 Suggested policies u Dont try to cover everything (a la EDG) Support a limited number of middleware areas properly Support those which are Mission critical to HEP (e.g. Data Management) Support areas where we have a clear leadership role

Pete Clarke– GridPP 6 – 31 Jan n° 11 Suggested policies u GridPP-2 should deal with logical centres Not sensible to deal with many individual institutes at the level of 0.5 posts..etc.. (this puts the onus on coordinating a sector on GridPP-2 resource management which is silly) Instead a logical centre agrees to deliver on a specific area – against several posts. Logical centre = { critical mass, credibility, expertise…} Can be grouping of institutes. But this is invisble to GridPP-2 at the level of resource management. Perhaps should have inter disciplinary / industry agle

Pete Clarke– GridPP 6 – 31 Jan n° 12 u Taper down of effort in middleware GridPP should move from development to exploitation Should take progressively more from external suppliers u Much of current middleware R&D in work packages will evolve to operations and support

Pete Clarke– GridPP 6 – 31 Jan n° 13 Status of deliberations u SLOW u Document just drafted with first thoughts => PMB u Next it goes to TB : axiomatic that people involved in work say what they think are logical next steps in middleware form HEP point of view EB: What experiments want of GridPP-2 must shape this sector u Middleware Workshop to be organised Day 1: present in detail what we have all done Evening 1: Stitch up in pub Day 2: Discuss where we should go (to justify prior step)