PerfSONAR: Development Status

1. PerfSONAR: Development Status Jeff W. Boote Internet2 Feb-7-06

2. Project Goals • Enable end-users & network operators to: • determine E2E performance capabilities • locate E2E problems • contact the right person to get an E2E problem resolved. • Enable remote initiation of partial path performance tests • Make partial path performance data publicly available • Be interoperable with other performance measurement frameworks • Encompass needs of next generation infrastructures

3. Decouple 3 components of a Measurement Infrastructure

4. Our strategy has been to focus effort in the middle tier We are well leveraged to help build the measurement community needed to make this work (ESnet and Geant as well) Allows a common interface for measurement tools to be built Allows a common interface for analysis tools to be built Enables researchers who are better positioned to do the “sexy” analysis or tool development to concentrate efforts on those portions of the problem Strategy

5. PerfSONAR Overview • Joint effort of ESnet, GÉANT2 JRA1 and Internet2 (and more) • Webservices network performance framework • Network measurement tools • Network measurement archives • Distributed scheduling/authorization • Multi-domain policy • Control communication via SOAP messages containing GGF NMWG schema

6. Services (Data) • Measurement Archive • Storage of passive/active measurement results • Measurement Point • Request collection for passive • Request execution for active • Interacts with MA for storage • Transformation Service • Transform the data (aggregation, concatenation, correlation, translation, etc) • Example: ongoing analysis of data stream for NOC alarm, etc…

7. Services (Discovery) • Lookup Service • Allows the client to find existing services and other LS services. • Dynamic: services can register/de-register/timeout • LS within a “domain” will have detailed knowledge of services within the domain • Inter-domain LS accomplished by sharing aggregated/summary information about what kinds of services are available along with a reference to the LS that hold detailed knowledge • Topology Service • Make the network topology information available to the framework. • Find the closest MP, provide topology information for visualisation tools • Algorithmic entity: Data is still held by Measurement Archives

8. Services (AuthN/Z) • Authentication Service • Internet2 MAT, GN2-JRA5 • Authentication functionality for the framework • Users can have several roles, the authorization is done based on the user role • Basically, this is the interface between perfSONAR applications and services and “real” federated authentication systems • Resource protector • Arbitrate the consumption of limited resources. • Centralize the policy as much/little as wanted

9. Inter-domain perfSONAR example interaction Useful graph Client Token MA Here is who I am, I’d like to access MA B Here is who I am, I’d like to access MA A Token MB a,b,c : Network A, MA A, AA A Where Link utilisation along - Path a,b,c? AA A Here you go Get Link utilisation a,b,c Get link utilisation c,d,e,f AA B Here you go a,b,c: Network A – LS A, c,d,e,f : Network B, MA B, AA B Where Link utilisation along - Path a,b,c,d,e,f? LS A LS B MA B MA A a b f e c d Network A Network B

10. Community Design Implementation Deployments Status

11. perfSONAR is a joint effort Major Partners: ESnet, GEANT2 JRA1, and Internet2. RNP recent activity Internet2 includes: Internet2 staff University of Delaware My apologies if I have overlooked someone (still working on the credits process) GEANT2 JRA1 includes: Arnes Belnet Carnet Cesnet DANTE DFN FCCN GRNet ISTF PSNC Nordunet (Uninett) Renater RedIRIS Surfnet SWITCH Community

12. Design • Architecture document (Fall ’04) • Detailed Design document (Spring ’05) • Workshops in Brussels (09/04), Zurich (04/05), Ann Arbor (05/05), Poznan (08/05), Cambridge (01/06) • Communications: • E2EMON submission (03/05) • TNC05 paper / presentation (06/05) • ICSOC05 paper (12/05)

13. Design (Next Tasks) • Multi-domain LS (Target: SC paper) • Hierarchical/P2P aspects • Trade-off between privacy/utility • Topology • Major effort of Geant JRA-3 • Integration with LS for topological discovery • Authentication • JRA-5 eduGAIN (Rosetta stone for authN)

14. Implementation • MA RRD data stores (base) • MP ping/bwctl/SNMP* (base) • LS single domain (base) • MA RRD (python) • MP ping (python) • MA IPPM (perl) • MP bwctl (perl) • MP looking glass (Java) (BELNET) • Sample UI (Java) (Bulgarians) • Sample UI for path utilization (web cgi/perl) ESnet

15. Implementation (Next steps) • Integration • Ease of deployment • More tools (types of tools) • Analysis • Discovery* • Authentication*

16. Deployments (Demos) • Participants who have deployed service infrastructure over RRD files: • Abilene • ESnet • Geant • Other NRENs (GRnet, PSNC, SWITCH) • University of Delaware • GGF, EGEE, Supercomputing demos (10-11/05) • https://performance.es.net/cgi-bin/perfsonar-trace.cgi

17. Conclusions • Many tools are becoming interoperable using the common GGF schema language (and specifically the perfSONAR dialect). • Good working relationships with the principles across multiple continents (Brazil is even becoming involved!) • The pace of development is increasing. • Real tools (i.e. analysis tools building on the minimal framework) are already in development now.