Changes between Version 71 and Version 72 of 020513_GEMINI_Demo


Ignore:
Timestamp:
02/07/13 12:01:44 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 020513_GEMINI_Demo

    v71 v72  
    5858[[Image(Gemini_instrumentize_passive.png, 80%)]] [[BR]]
    5959
    60  * Instrumentize script runs in Use Workspace  [[BR]]
    61 
    6260 * Both version of the instrumentation code will talk to the GENIDESKTOP Parser Service to obtain User information, Slice/Slice  Credential Information and Manifest information thus making the instrumentation process somewhat independent of the Control Frameworks.
    6361
     
    6664 * A Detailed list of the Parser API and its return values is provided in this document [attachment:ParserAPI.pdf]. [[BR]]
    6765
    68 Issue:  where does Parser service run?  in User Workspace, where it has access to certs/credentials? 
     66Issue:  where does Parser service run?  in User Workspace, where it has access to certs/credentials?  somewhere else, with a copy of credentials?  (but, trying to avoid this) 
    6967
    7068 * But then, how can GN get access to Parser service, since the UW is not necessarily reachable?
     
    9492
    9593==== Current interfaces ====
    96 * Uses proxy certs generated during the instrumentize process and copied onto the GN Node. [[BR]]
    97 Only interface available as of today is a command line to be run when logged into the GN Node to archive data.To view the data archived the user can use the icommands from the GN Node or can go to the irods Server's webinterface to view the data. [[BR]]
     94 * Uses proxy certs generated during the instrumentize process and copied onto the GN Node. [[BR]]
     95 * Only interface available as of today is a command line to be run when logged into the GN Node to archive data.
     96 * To view the data archived the user can use the icommands from the User Workspace, or can go to the irods Server's web interface to view the data. [[BR]]
    9897
    9998==== Features available now (2/5) ====
    100 * Current version on archives passive measurement data and metadata.[[BR]]
    101 * There is no web-interface for the user to run this archive process[[BR]]
    102 * I am  not sure if the web-interface supports GSI authentication to view the data and metadata. If this feature is not available, then it would be a really huge task for the user to view the data and metadata since the icommands are complicated form a user's viewpoint.[[BR]]
    103 * Irods account creation is outside the scope of the GEMINI Instrumentize  process. The user is expected to have this account before hand.[[BR]]
     99 * Current version archives (stores) passive measurement data (INSTOOLS) and associated metadata, from RRD on GN
     100 * Does the web-interface on iRODS support GSI authentication to view the data and metadata?
     101 * Irods account creation is outside the scope of the GEMINI Instrumentize  process. The user is expected to have this account before hand.[[BR]]
    104102
    105103==== Features expected to be available by GEC16 (3/19) ====
    106 * Web-interface to initiate the archive process [[BR]]
     104 * Script for GN, to archive data from MS and metadata from UNIS
     105 * Web-interface to initiate the archive script on GN [[BR]]
    107106
    108107==== Issues that need to be resolved before GEC16 (3/19) ====
    109 * If there are plans for archiving Active measurement data, then that itself is a huge amount of work.[[BR]]
    110 
     108 * Need to define naming conventions, et.c, for storing measurement data and associated metadata, into iRODS, incluidng full path, and decide how to load path into GN from UW.
    111109
    112110=== 4)  GENI Desktop, initing global node, displaying topology, instrumentize,  displaying measurements ===