Changes between Version 9 and Version 10 of GEC12InstMeasWorkingSession

Timestamp:

10/27/11 12:17:59 (13 years ago)

Author:

hmussman@bbn.com

Comment:

--

GEC12InstMeasWorkingSession

@@ -33 +33 @@
 
 First focus on I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
-First supported aggregates:  ORCA servers/VMs/racks  [[BR]]
+First supported aggregates:  ORCA servers/VMs and RENCI racks  [[BR]]
 First utilized experiment control tools:  GUSH, with additions  [[BR]]
 First utilized interfaces:  GENI AM API for resources;  ns3 for topology;  ssh;  add OMF for orchestration  [[BR]]
@@ -39 +39 @@
 Requires XML messaging service, with pub/sub, in public IP space    [[BR]]
 
-Introduces portal service, with: OML Server, for collection; Results Service, for presentation; measurement orchestration service using OMF;  documentation service to create and edit MDOD.  Can this be shared with GEMINI?  [[BR]]
+Introduces portal service, with: OML Server, for collection; Results Service, for presentation; measurement orchestration service using OMF;  documentation service to create and edit MDOD.  Can this be shared with GEMINI project?  [[BR]]
 
 Introduces iRODS service for user workspace and archive.  Start with CNRI prototype?  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
 
 Begin:  support for WiMAX sites  [[BR]]
-
+Consider:  adding OML server with perfSONAR interface, for sharing data [[BR]]
 Later:  add sensor measurement data, carried in data network  [[BR]]
 
@@ -50 +50 @@
 PI:  Martin Swany (Indiana U) [[BR]]
 Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]]
-Starts with INSTOOLS and LAMP/perfSONAR [[BR]]
+
+Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment  [[BR]]
+Consider:  how to gather customized data from application  [[BR]]
+
+First focus on I&M use cases for experiments [[BR]]
+First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
+First utilized experiment control tools:  FLACK, with additions  [[BR]]
+First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
+
+Continues portal to presentation service;  need to add documentation service to create and edit MDOD.  Can portal be shared with GIMI project?  [[BR]]
+
+Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
+
+Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
+Continue to setup within resources assigned by slice mechanism [[BR]]
+Consider:  monitoring of clusters/racks [[BR]]
+Consider:  measurements of Layer 2 and OpenFlow paths [[BR]]
+
+First focus on I&M use cases for infrastructure measurement [[BR]]
+First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
+First utilized experiment control tools:  FLACK, with additions  [[BR]]
+First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
+
+Continues local and global Lookup Services [[BR]]
+Need to map MDOD into metadata that is registered [[BR]]
+
+Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
+
+Consider how INSTOOLS and LAMP/perfSONAR tools might be shared   [[BR]]
+