Download - Functional design of Domain Tool
Functional design of Domain Tool
UCL e2e monitoring workshop
May 15th, 2003
Victor Reijs
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
Userrepresentation
DomainTool...
MPUn-Instrumentednetworks
Instrumentednetworks
• man• machine• developer• administrator
Other Domain Tools
Access interface
MP interface
Inter-domain interface
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
Domain Specific block
Communication
AAA Scheduler
Ad
min
istr
atio
n
DB
MS
Pathfinder Aggregation
Access interface
Inter-domain interface
API interface
Data analyses
Domain specific
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 infrastucture
http://www.dante.net/tf-ngn/perfmonit/Nicolas Simas: [email protected]
PERThttp://www.dante.net/tf-ngn/pert/Victor Reijs: [email protected]