Changes between Version 37 and Version 38 of GSAS
- Timestamp:
- 05/07/13 14:20:11 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSAS
v37 v38 106 106 This 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]] 107 107 108 [http://groups.geni.net/geni/attachment/wiki/GSAS/0 42913_iRODS_Figures.vsd GSAS Configuration and Use Cases Figure (visio)] [[br]]109 [http://groups.geni.net/geni/attachment/wiki/GSAS/Visio-0 42913_iRODS_Figures.pdf GSAS Configuration and Use Cases Figure (pdf)] [[br]]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]] 110 110 111 111 Versions of document: … … 113 113 114 114 [http://groups.geni.net/geni/attachment/wiki/GSAS/042913%20%20v1.2_GENIObjectDescriptor%20Schema.docx 042913 v1.2 GENI ObjectDescriptor Schema] [[br]] 115 116 [http://groups.geni.net/geni/attachment/wiki/GSAS/042913b%20%20v1.2_GENIObjectDescriptor%20Schema.docx 042913 v1.2 GENI ObjectDescriptor Schema] [[br]] 115 117 116 118 Task list: [[br]] … … 120 122 || 2a || Review v1.1 || Group || 4/29/13 || completed || || || 121 123 || 2b || Draft v1.2 || Harry || 5/1/13 || completed || || || 122 || 2c || Review with GPO || Harry/Jeanne || ? || || || || 123 || 2d || Review with GEMINI || Harry/Jeanne || ? || || || || 124 || 2e || Review with GIMI || Harry/Jeanne || ? || || || || 125 || 2f || || || || || || || 124 || 2c || Review v1.2 || Group || 5/8/13 || || || || 125 || 2d || Review with GPO || Harry/Jeanne || ? || || || || 126 || 2e || Review with GEMINI || Harry/Jeanne || ? || || || || 127 || 2f || Review with GIMI || Harry/Jeanne || ? || || || || 128 || 2g || || || || || || || 126 129 || 3 || Resolve design issues || || || || || || 127 || 3a || Issue 2.1: How are persistent accounts established for each user in iRODSs? || Shu, Jeanne || || || ||||130 || 3a || Issue 2.1: How are persistent accounts established for each user in iRODSs? || Shu, Jeanne, Tom || || || || Per GIMI workflow discussion || 128 131 || 3b || Issue 2.2: How are storage capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || 129 132 || 3c || Issue 2.3: How are archive capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || 130 || 3d || Issue 5.1: Where is the proxy certificate created? How is the proxy certificate transferred to the service? || Ezra || || || || ||133 || 3d || Issue 5.1: Where is the proxy certificate created? How is the proxy certificate transferred to the GEMINI Measurement Store service? || Ezra || || || || || 131 134 || 3e || Issue 5.2: What happens if the proxy certificate expires? Is the user notified? How can they load an updated proxy certificate? || Ezra || || || || || 132 135 || 3f || Issue 5.3: How is the target information transferred to the service? || Ezra || || || || || 133 || 3g || Issue 5.4: How is the iticket transferred to the service? || Cong || || || ||||136 || 3g || Issue 5.4: How is the iticket transferred to the GIMI portal service? || Cong || || || || Per GIMI workflow discussion || 134 137 || 3h || Issue 5.5: What happens if the iticket certificate expires? Is the user notified? How can they load an updated proxy certificate? || Cong || || || || || 135 || 3i || Issue 5.6: How is all of th is target information transferred to the service agent? || Cong || || || ||||138 || 3i || Issue 5.6: How is all of the target information transferred to the service agent? || Cong || || || || Per GIMI workflow discussion || 136 139 || 3j || Issue 6.1: Need to establish rules if there is a discrepancy in descriptors. || Shu || || || || || 137 140 || 3k || Issue 6.2: Need to establish rules for changing or removing metadata.xml files. || Shu || || || || || … … 215 218 || 5b || Establish persistent accounts for each user, use icommands to store and retrieve measurement data objects for each user in a storage service || Shu and Cong || GEC14 || completed || || || 216 219 || 5c || Establish authentication for each user based on certificates, and also proxy (delegated) certificates. || Shu and Jeanne || GEC15 || completed || || || 217 || 5d || Establish directory structure in storage service for each user to accommodate multiple experiments, and directory structure for each experiment (consider "bag") to include all objects (artifacts) associated with that experiment, including one or more descriptors (metadata) within XML files (following the GENI descriptor schema) || Shu, Harry and Giridhar || GEC15 || in progress|| || ||218 || 5e || Provide multiple interfaces (including icommand, restful http, and web) to allow authenticated user to view, search and curate their objects (artifacts) || Shu || GEC15 || in progress|| || restful http can come later||220 || 5d || Establish directory structure in storage service for each user to accommodate multiple experiments, and directory structure for each experiment (consider "bag") to include all objects (artifacts) associated with that experiment, including one or more descriptors (metadata) within XML files (following the GENI descriptor schema) || Shu, Harry and Giridhar || GEC15 || completed || || || 221 || 5e || Provide multiple interfaces (including icommand, restful http, and web) to allow authenticated user to view, search and curate their objects (artifacts) || Shu || GEC15 || completed || || restful http can come later|| 219 222 || 5f || Provide interface to allow user to define an object to be archived (where the object may range from a large directory to a single file), include a descriptor (following the GENI descriptor schema), assign a persistent Digital Object Identifier (DOI, or "handle"), and decide when to push it to archive service. || Shu || GEC16 || in progress || || || 220 223 || 5g || Establish an archive service that provides long-term and reliable storage, with access via a DOI from the global handle service, with access following a local policy included in archived object. (Include at least two policies: give the object to anyone, or give the object only to its owner.) || Shu || GEC17 || in progress || || || 221 || 5h || "iRODS" || Shu|| || || || ||222 || 5i || "iRODS" || Shu|| || || || ||223 || 5j || "iRODS" || Shu|| || || || ||224 || 5k || "iRODS" || Shu|| || || || ||224 || 5h || Add rules to process incoming descriptors in xml files, and store info in iCAT (3-4 weeks) || Shu, Antoine || || || || || 225 || 5i || Add rules to move object to public archive service, and make any changes (3-5 weeks) || Shu, Antoine || || || || || 226 || 5j || Integrate archive service into handle service (1 week) || Shu, Antoine || || || || || 227 || 5k || Provide interface to iRODS to allow GENI Experimenter Portal to create iRODS user accounts || Shu, Antoine || || || || || 225 228 || 5l || "iRODS" || Shu || || || || || 226 229 || 5m || "iRODS" || Shu || || || || || … … 305 308 || '''ID''' || '''Description''' || '''Who''' || '''Due''' || '''Status''' || '''Demos''' || '''Notes''' || 306 309 || 9 || "Integration of tools/agents with GSAS" || || || || || || 307 || 9a || || Cong|| || || || ||310 || 9a || || Jeanne || || || || || 308 311 || 9b || || || || || || || 309 312 || 9c || || || || || || ||