Changes between Version 41 and Version 42 of Gec7InstMeasWGAgenda

Timestamp:

03/24/10 18:13:34 (14 years ago)

Author:

hmussman@bbn.com

Comment:

--

Gec7InstMeasWGAgenda

@@ -325 +325 @@
 v0.1 DRAFT includes proposed I&M services and proposed configuration [[BR]]
 
+
+Purpose:
+Provide a comprehensive and ordered list of topics that must be addressed for a complete architecture
+Identify the priority topics that the WG needs to address first
+Pull together contributions by the WG though Spiral 2
+
+
+Plan:
+Now :  v0.1 DRAFT completed, by GPO;  see http://groups.geni.net/geni/wiki/GeniInstrumentationandMeasurementsArchitecture 
+By GEC8:  v0.5 draft, by GPO, with contributions from WG
+By GEC9:  v1.0 draft, reviewed by WG
+
+Document outline:
+Document Scope
+2.  Introduction
+3.  Definition and configuration of I&M services
+4.  Interfaces, protocols and schema for Measurement Data (MD)
+5.  Ownership of MD and privacy of owners
+6.  Interfaces, protocols and APIs for using I&M services
+7.  Basic GENI I&M use cases
+8.  MD transport via the GENI Measurement Plane
+9.  Discovery, authorization, assignment and binding of GENI I&M services
+10.  Measurement Orchestration (MO) service
+11.  Measurement Point (MP)
+12.  Time-stamping MD
+13. Measurement Collection (MC) service
+14.  Measurement Analysis and Presentation (MAP) service
+15.  Measurement Data Archive (MDA) service
+16.  Additional GENI I&M use cases
+
+Based on GENI I&M Capabilities Catalog (v0.1), these GENI projects have comprehensive, end-to-end capabilities:
+OML (ORBIT Measure Library) in OMF (ORBIT Mgmt Framework)  
+        (Ott, NICTA  and Gruteser, WINLAB/Rutgers, 1660)
+Instrumentation Tools 
+        (Griffioen, Univ Kentucky, 1642)
+perfSONAR for network measurements  
+         (Zekauskas, I2 and Swany, Univ Delaware, 1788)
+Scalable Sensing Service 
+        (Fahmy, Purdue and Sharma, HP Labs, 1723)
+OnTimeMeasure 
+        (Calyam, Ohio Super Ctr, 1764)
+
+After considering projects with comprehensive, end-to-end capabilities, here are five services they have in common:
+
+Measurement Orchestration (MO) service 
+(p/o Experiment Control service, uses a language to orchestrate I&M services)
+Measurement Point (MP) service  
+(instrumentation that taps into a network and/or systems, links and/or nodes, to capture measurement data and format it using a standardized schema)
+Measurement Collection (MC) service  
+(programmable systems that collect, combine, transform and cache measurement data)
+Measurement Analysis and Presentation (MAP) service  
+(programmable systems that analyze and then present measurement data)
+Measurement Data Archive (MDA) service  
+(measurement data repository, index and portal)
+
+Expected range of implementations:  
+
+Small-scale implementations might put all I&M services within one aggregate, and even in one server
+interfaces between services would be internal to the aggregate, or even internal to the server
+
+Large-scale implementations might have I&M services distributed over many aggregates
+with measurement data flowing between services
+with orchestration mechanisms based upon message exchanges
+
+
+
+
+
 Priority topics: [[BR]]
 +  Common terminology;  best granularity of functions  [[BR]]