Changes between Version 55 and Version 56 of GEC12InstMeasWorkingSession


Ignore:
Timestamp:
11/11/11 16:24:15 (8 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC12InstMeasWorkingSession

    v55 v56  
    7575==== GEMINI ==== 
    7676PI:  Martin Swany (Indiana U) [[BR]]
    77 Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]];  Hussamuddin Nasir (U Kentucky)
     77Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]];  Hussamuddin Nasir (U Kentucky) [[BR]]
    7878
    7979Goals:  [[BR]]
    8080
    81 **Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment  [[BR]]
     81**Starts with INSTOOLS, which provide easy-to-use tools in GENI environment for experimenters [[BR]]
     82++Fold features into LAMP to form GEMINI tools, and then discontinue [[BR]]
     83
     84Focus:  I&M use cases for experiments [[BR]]
     85Supported aggregates:  protoGENI servers/VMs? [[BR]]
     86Utilized experiment control tools:  FLACK, with additions  [[BR]]
     87Utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh for image loading;  vnc for server login;  [[BR]]
     88
     89Portal to find presentation services in each Measurement Collector;  includes vnc for login to server  [[BR]]
     90
     91Can use Kentucky and CNRI archive services  [[BR]]
     92
     93
     94**Starts with LAMP [[BR]]
     95First focus on providing easy-to-use tools in GENI environment for experimenters [[BR]]
     96Setup within an experimenters slice [[BR]]
     97Basic user node image contains suite of perfSONAR tools;  application loaded next;  provides perfSONAR data interface [[BR]]
     98Measurement Collector image contains UNIS registry (lookup and toplogy) and Periscope portal services [[BR]]
     99MC uses protogENI credential to pull data from perfSONAR data interface on each user node [[BR]]
     100MC and user nodes can be anywhere in GENI [[BR]]
     101
     102Supported aggregates:  protoGENI servers/VMs?  [[BR]]
     103Utilized experiment control tools:  ?? [[BR]]
     104Utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh for image loading;  [[BR]]
     105
     106Move to:  ORCA aggregate/rack, or ? [[BR]]
     107Move to:  GUSH experiment control tools, with OMNI, or ? [[BR]]
     108Move to:  GENI AM API for resources;  ns3 for topology;  ssh for image laoding; or ? [[BR]]
     109
     110Continue to setup within resources assigned by slice mechanism, but modify request rspec to add I&M features before submitting;  how to pass manifest to UNIS?;  how to create and edit MDOD?[[BR]]
     111
     112Extend with LAMP features: [[BR]]
     113Consider how to load tools on top of basic image [[BR]]
     114Consider how to extend Periscope to include druple content management service [[BR]]
     115Consider how to add xserver to basic node image, to login from portal using vnc protocol [[BR]]
     116 
    82117Consider:  how to gather customized data from application  [[BR]]
    83118
    84 First focus:  I&M use cases for experiments [[BR]]
    85 First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
    86 First utilized experiment control tools:  FLACK, with additions  [[BR]]
    87 First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
    88 
    89 *Continues portal to presentation service;  need to add documentation service to create and edit MDOD.  Can portal be shared with GIMI project?  [[BR]]
    90 
    91 *Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
    92 
    93 **Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
    94 Continue to setup within resources assigned by slice mechanism [[BR]]
     119Consider how to add interface to archive service, e.g., iRODs [[BR]]
     120
     121Second focus on I&M use cases for infrastructure measurement  [[BR]]
     122*Continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
     123*Continues compatibility with perfSONAR services   [[BR]]
     124*Continues home and global Lookup Services [[BR]]
     125
     126Show how to setup slice that provides perfSONAR data interface, and registers it with globalLookupService [[BR]]
     127Show how to setup slice with Periscope service and gather data from perfSONAR data interface on another slice [[BR]]
     128
    95129Consider:  monitoring of clusters/racks [[BR]]
    96130Consider:  measurements of Layer 2 and OpenFlow paths [[BR]]
    97 
    98 First focus on I&M use cases for infrastructure measurement [[BR]]
    99 First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
    100 First utilized experiment control tools:  FLACK, with additions  [[BR]]
    101 First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
    102 
    103 *Continues home and global Lookup Services [[BR]]
    104 Create and map MDOD into metadata that is registered [[BR]]
    105 
    106 *Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
    107 
    108 **Consider how INSTOOLS and LAMP/perfSONAR tools might be merged   [[BR]]
    109131
    110132