Changes between Version 43 and Version 44 of GSAS


Ignore:
Timestamp:
05/22/13 18:03:07 (6 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSAS

    v43 v44  
    106106This document is based on the early Measurement Data Archive (MDA) service prototype developed by CNRI, and many discussions within the GENI I&M community.  [[BR]]
    107107
    108  [http://groups.geni.net/geni/attachment/wiki/GSAS/050713_iRODS_Figures.vsd  GSAS Structure and Use Cases figure (visio)]  [[br]]
    109  [http://groups.geni.net/geni/attachment/wiki/GSAS/Visio-050713_iRODS_Figures.pdf  GSAS Structure and Use Cases figure (pdf)]  [[br]]
     108 [http://groups.geni.net/geni/attachment/wiki/GSAS/051613_iRODS_Figures.vsd  GSAS Structure and Use Cases figure (visio)]  [[br]]
     109
     110 [http://groups.geni.net/geni/attachment/wiki/GSAS/Visio-051613_iRODS_Figures.pdf  GSAS Structure and Use Cases figure (pdf)]  [[br]]
    110111
    111112Versions of document:
     
    128129|| 2g ||   ||   ||  ||   ||  || ||
    129130|| 3 || Resolve design issues  ||   ||  ||   ||  || ||
    130 || 3a || Issue 2.1:  How are persistent accounts established for each user in iRODSs?  || Shu, Jeanne, Tom  ||  ||   ||  || Per GIMI workflow discussion;  use POST to restful interface? ||
     131|| 3a || Issue 2.1:  How are persistent accounts established for each user in iRODSs?  || Shu, Jeanne, Tom  ||  || completed  ||  || Per GIMI workflow discussion:  use POST to restful interface on iRODS ||
    131132|| 3b || Issue 2.2:  How are storage capacity limits established and enforced for each IRODS user?  Are older objects (artifacts) flagged for removal?  || Shu  ||  ||   ||  || ||
    132133|| 3c || Issue 2.3:  How are archive capacity limits established and enforced for each IRODS user?  Are older objects (artifacts) flagged for removal?  || Shu  ||  ||   ||  || ||
     
    134135|| 3e || Issue 5.2:  What happens if the proxy certificate expires?  Is the user notified?  How can they load an updated proxy certificate?      || Ezra  ||  ||   ||  || ||
    135136|| 3f ||  Issue 5.3:  How is the target information transferred to the service?  || Ezra  ||  ||   ||  || ||
    136 || 3g || Issue 5.4:  How is the iticket transferred to the GIMI portal service?  || Cong  ||  ||   ||  || Per GIMI workflow discussion ||
     137|| 3g || Issue 5.4:  How is the iticket transferred to the GIMI portal service?  || Cong  ||  || completed  ||  || Per GIMI workflow discussion:  init script gets, pushes ||
    137138|| 3h || Issue 5.5:  What happens if the iticket certificate expires?  Is the user notified?  How can they load an updated proxy certificate?     || Cong  ||  ||   ||  || ||
    138 || 3i || Issue 5.6:  How is all of the target information transferred to the service agent? || Cong  ||  ||   ||  || Per GIMI workflow discussion ||
     139|| 3i || Issue 5.6:  How is all of the target information transferred to the service agent? || Cong  ||  ||  completed  ||  || Per GIMI workflow discussion:  init script gets, pushes ||
    139140|| 3j || Issue 6.1:  Need to establish rules if there is a discrepancy in descriptors.  || Shu  ||  ||   ||  || ||
    140141|| 3k ||  Issue 6.2:  Need to establish rules for changing or removing metadata.xml files. || Shu  ||  ||   ||  || ||