230 likes | 350 Vues
This document outlines the functional design of the Domain Tool for end-to-end (E2E) monitoring, discussed during a workshop on May 15, 2003. It covers the cooperation environment, functions, interfaces, and outstanding issues. Key elements include administration, data analysis, communication frameworks, and aggregation functionalities. The tool is intended for various stakeholders, including developers and domain administrators, emphasizing interoperability with other domain tools. Insights on performance monitoring, scheduling, and data management are pivotal for enhancing network management capabilities.
E N D
Functional design of Domain Tool UCL e2e monitoring workshop May 15th, 2003 Victor Reijs victor.reijs@heanet.ie
Outline • Co-operation environment... • Environment of Domain Tool... • Functions... • Interfaces... • Issues...
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?
Outline • Co-operation environment... • Environment of Domain Tool... • Functions... • Interfaces... • Issues...
Environment of Domain Tool • man • machine • developer • administrator User representation Access interface Domain Tool... Inter-domain interface Other Domain Tools MP interface Un-Instrumented networks Instrumented networks MP
Domain Tool block Access interface Inter-domain interface Domain specific block... API interface Analyses+ aggregation Driver interface MP driver MPspecific block Domain Tool MP interface
Domain Specific block Access interface Inter-domain interface Communication AAA Scheduler Pathfinder Aggregation DBMS Administration Data analyses Domain specific API interface
Outline • Co-operation environment... • Environment of Domain Tool... • Functions... • Interfaces... • Issues...
Functions • Administration… • Communication… • AAA • Scheduler… • Pathfinder... • DBMS… • Aggregation… • Data Analysis…
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
Communication • does communication to other Domain Tools • schedules communication paths inside Domain Tool • [NIMI]
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]
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
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]
Aggregation • has domain specific aggregation functions... • aggregates test results for domain • provides aggregated results • provides aggregated exceptions/error information
Aggregation functions • Statistical functions: • mean, percentile, standard deviation, etc. [NMWG] • adding averages, concatenation, etc.
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]?
Outline • Co-operation environment... • Environment of Domain Tool... • Functions... • Interfaces... • Issues...
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
Outline • Co-operation environment... • Environment of Domain Tool... • Functions... • Interfaces... • Issues...
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!
Contact info • Part of TF-NGN (TERENA/DANTE) • Performance monitoring infrastucturehttp://www.dante.net/tf-ngn/perfmonit/Nicolas Simas: Nicolas.Simar@dante.org.uk • PERThttp://www.dante.net/tf-ngn/pert/Victor Reijs: victor.reijs@heanet.ie