Changes between Version 2 and Version 3 of GEMINIv1.1Definition


Ignore:
Timestamp:
09/27/12 14:46:20 (12 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GEMINIv1.1Definition

    v2 v3  
    1313 e)  Include NewUNIS operational service (IU) for use with BLiPP and MS modules;  retain OldUNIS operational service (IU) to support legacy modules;  modify instrumentation script to push configuration data to both OldUNIS and NewUNIS.
    1414
    15  f)  Introduce flexible authentication and authorization
     15 f)  Introduce flexible Authentication and Authorization (AA) modules between new modules (BLiPP and MS) and NewUNIS.
     16
     17 g)  Modify GEMINI Portal to display data from all modules, and to utilize NewUNIS for storing configuration data.
     18
     19 h)  Support these operational services:  NewUNIS (IU);  OldUNIS (IU);  ProxyCertGenerator (IU);  LAMP CA  (IU);  GEMINI Portal (UK);  iRODS (UK)
     20
    1621
    1722 c)  Focus on target aggregates including protoGENI sites (e.g., Utah) and InstaGENI racks.
    … …  
    2126 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”.
    2227
    23  f)  Include these operational services:  Old UNIS (Delaware to IU);  LAMP CA  (Delaware to IU);  Portal (UK);  iRODS (UK)
    24 
     28 f) 
    2529 g)  Integrate tools so that user can ask for active network and/or passive host measurements, in  a unified manner.
    2630