1. Functional design of Domain Tool UCL e2e monitoring workshop May 15 th, 2003 Victor Reijs victor.reijs@heanet.ie

2. Outline Co-operation environment... Environment of Domain Tool... Functions... Interfaces... Issues...

3. Co-operation environment I2: 4 years ago talk on e2e problem:  NLM-HEAnet and VidiNet: Chariot TF-NGN:  PERT  Performance infrastructure NIMI GGF/OGSA E2E piPEs Monalisa, others?

4. Outline Co-operation environment... Environment of Domain Tool... Functions... Interfaces... Issues...

5. Environment of Domain Tool User representation Domain Tool... MP Un-Instrumented networks Instrumented networks man machine developer administrator Other Domain Tools Access interface MP interface Inter-domain interface

6. Domain Tool block Domain specific block... Analyses+ aggregation MP driver MP specific block Domain Tool Inter-domain interface API interface Access interface MP interface Driver interface

7. Domain Specific block Communication AAA Scheduler Administration DBMS Pathfinder Aggregation Access interface Inter-domain interface API interface Data analyses Domain specific

8. Outline Co-operation environment... Environment of Domain Tool... Functions... Interfaces... Issues...

9. Functions Administration… Communication… AAA Scheduler… Pathfinder... DBMS… Aggregation… Data Analysis…

10. Administration knows what Domain Tool can do knows about the feature set of connected MP’s keeps track of test functionalities available [NMWG] keeps track of other Domain Tools (JINI?) keeps track of users and AAA keeps track of aggregation functions keeps domain policies

11. Communication does communication to other Domain Tools schedules communication paths inside Domain Tool [NIMI]

12. Scheduler accepts information requests asks for path (using Pathfinder) does resource management of Domain Tool and MP’s determines if test is needed (could be in Database) uses AAA towards MP specific block does test management (start, stop, abort, etc.) provides database exceptions/error information [E2E piPEs]

13. Pathfinder determines MP’s in the e2e path determines the IP path for own domain: finds MP’s on path determines neighbor Domain Tool un-instrumented domain exists

14. DataBase Management System has (distributed) Domain Database knows if MP’s have Local Database(s) uses AAA determines if data is available [Test Arbiter] [OGSA]

15. Aggregation has domain specific aggregation functions... aggregates test results for domain provides aggregated results provides aggregated exceptions/error information

16. Aggregation functions Statistical functions:  mean, percentile, standard deviation, etc. [NMWG]  adding averages, concatenation, etc.

17. Data Analyses knows how to analyze the test results of MP’s uses MP specific aggregation functions... anonymizes data provides MP results provides MP exceptions/error information [test engine, E2E piPEs]?

18. Outline Co-operation environment... Environment of Domain Tool... Functions... Interfaces... Issues...

19. Interfaces Access interface (XML, SOAP)  user (man or machine)  domain administrator  MP developer Inter-domain interface (XML) Driver interface MP interface [PMP, E2EpiPEs?] (proprietary) API interface (XML?)  data analyses  aggregation functions

20. Outline Co-operation environment... Environment of Domain Tool... Functions... Interfaces... Issues...

21. Issues Chaining and/or referral (resilience)?  Data and AAA 3 levels: multi-domain, domain, MP  Aggregation, Data Analyses, Scheduler Agree common/defined naming Work together!

22. Contact info Part of TF-NGN (TERENA/DANTE) Performance monitoring infrastucture http://www.dante.net/tf-ngn/perfmonit/ Nicolas Simas: Nicolas.Simar@dante.org.uk PERT http://www.dante.net/tf-ngn/pert/ Victor Reijs: victor.reijs@heanet.ie