Changes between Version 9 and Version 10 of GEC12InstMeasWorkingSession


Ignore:
Timestamp:
10/27/11 12:17:59 (8 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC12InstMeasWorkingSession

    v9 v10  
    3333
    3434First focus on I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
    35 First supported aggregates:  ORCA servers/VMs/racks  [[BR]]
     35First supported aggregates:  ORCA servers/VMs and RENCI racks  [[BR]]
    3636First utilized experiment control tools:  GUSH, with additions  [[BR]]
    3737First utilized interfaces:  GENI AM API for resources;  ns3 for topology;  ssh;  add OMF for orchestration  [[BR]]
     
    3939Requires XML messaging service, with pub/sub, in public IP space    [[BR]]
    4040
    41 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]]
     41Introduces 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]]
    4242
    4343Introduces iRODS service for user workspace and archive.  Start with CNRI prototype?  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
    4444
    4545Begin:  support for WiMAX sites  [[BR]]
    46 
     46Consider:  adding OML server with perfSONAR interface, for sharing data [[BR]]
    4747Later:  add sensor measurement data, carried in data network  [[BR]]
    4848
     
    5050PI:  Martin Swany (Indiana U) [[BR]]
    5151Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]]
    52 Starts with INSTOOLS and LAMP/perfSONAR [[BR]]
     52
     53Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment  [[BR]]
     54Consider:  how to gather customized data from application  [[BR]]
     55
     56First focus on I&M use cases for experiments [[BR]]
     57First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
     58First utilized experiment control tools:  FLACK, with additions  [[BR]]
     59First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
     60
     61Continues portal to presentation service;  need to add documentation service to create and edit MDOD.  Can portal be shared with GIMI project?  [[BR]]
     62
     63Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
     64
     65Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
     66Continue to setup within resources assigned by slice mechanism [[BR]]
     67Consider:  monitoring of clusters/racks [[BR]]
     68Consider:  measurements of Layer 2 and OpenFlow paths [[BR]]
     69
     70First focus on I&M use cases for infrastructure measurement [[BR]]
     71First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
     72First utilized experiment control tools:  FLACK, with additions  [[BR]]
     73First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
     74
     75Continues local and global Lookup Services [[BR]]
     76Need to map MDOD into metadata that is registered [[BR]]
     77
     78Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
     79
     80Consider how INSTOOLS and LAMP/perfSONAR tools might be shared   [[BR]]
     81
    5382
    5483