Changes between Initial Version and Version 1 of GEMINI_v1.0_Definition


Ignore:
Timestamp:
05/22/12 15:37:50 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEMINI_v1.0_Definition

    v1 v1  
     1=  GEMINI v1.0 Definition =
     2
     3Based on GEMINI design review on 5/7 and 5/8, the GEMINI plan to produce v1.0 between now and GEC14 is this:
     4
     5 a)  Focus on GEMINI  tools that include primarily existing LAMP and INSTOOLS modules, to provide (respectively) active network and passive host measurements.
     6
     7 b)  Postpone the testing and integration of the new GEMINI architecture until after GEC14 (since there is no chance that it could be useful by GEC14);  complete and integrate it later,  at a time TBD.
     8
     9 c)  Focus on target aggregates including protoGENI sites (e.g., Utah) and InstaGENI racks.
     10
     11 d)  Use the GENI AM API and ssh as the principal interfaces to the aggregates
     12
     13 e)  Use OMNI to drive the GENI AM API, and write scripts to install software packages and configure the tools, where the scripts will run in the defined “user workspace”.
     14
     15 f)  Include these operational services:  Old UNIS (Delaware to IU);  LAMP CA  (Delaware to IU);  Portal (UK);  iRODS (UK)
     16
     17 g)  Integrate tools so that user can ask for active network and/or passive host measurements, in  a unified manner.
     18
     19 h)  Aim for “providing usable tools” to users, to be presented in a tutorial at GEC14.  (content of tutorial TBD)