Changes between Version 9 and Version 10 of GIMIv2tasks
- Timestamp:
- 04/22/13 15:43:11 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GIMIv2tasks
v9 v10 92 92 g) Current InstaGENI configuration per attached figure; changes? [[BR]] 93 93 h) Current ExoGENI configuration? [[BR]] 94 95 i) By 4/15: Jeanne will have met with team, and provide report of DRAFT plan [[BR]] 94 i) By 4/15: Jeanne will have met with team, and provide report of DRAFT plan [[BR]] 96 95 97 96 5) Decide on configuration of GIMI Portal service, and complete development. [[BR]] 98 97 a) On 4/2: Reconfirm that will continue as a multi-user persistent service, with account for each user, to retain advantages of a persistent sink for measurement data. However, encourage users to move completed measurements to iRODS, so that we do not end up with long-term storage of measurement data within GIMI Portal Service. [[BR]] 99 100 98 b) Continue to include OML Server and Lab wiki (for orchestration, results, and documentation) [[BR]] 101 99 c) Separate OML results, by experiment and user, per the defined method [[BR]] … … 105 103 g) Realize workable authentication/authorization to iRODS; start with current proxycert arrangement [[BR]] 106 104 h) Do we want to support link from GENI Desktop? or somehow include Lab wiki as a plug-in in the GENI Desktop? These could be a step towards a "consistent user interface". [[BR]] 107 108 105 i) On 4/4: We need a workable solution, not the “best” solution. We can’t wait for future authentication/authorization mechanisms. [[BR]] 109 110 106 j) On 4/4: We need to have the bulk of the work done in 6-8 weeks (no later than 6/11), then cleanup towards GEC17. [[BR]] 111 112 107 k) On 4/4: A small team will be organized to work on the problem, define multiple solutions, and pick the best we can do in the time allotted: Jeanne, Cong, Mike (lead), Shu, (also web services expert from RENCI?), Max. [[BR]] 113 114 108 l) By 4/15, Mike will have met with team, and will provide a report, including: evaluation of current Lab wiki code; available options for authentication of user to iRODS (starting with current proxycert arrangement); overview of current structure, and early view of possible options [[BR]] 115 109 … … 118 112 b) Add rules to move object to public archive directory, and manage any changes [[BR]] 119 113 c) Integrate archive service with handle service [[BR]] 120 121 114 d) By 4/15, Shu needs to summarize planned extensions, per his earlier document. [[BR]] 122 115