Changes between Version 20 and Version 21 of GIMIv2tasks


Ignore:
Timestamp:
04/29/13 17:17:26 (6 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GIMIv2tasks

    v20 v21  
    8383 042913;  4pm EDT;  discuss planning meeting 5/2- 5/3 for GIMI Portal;  discuss interop status;  discuss GSAS status
    8484
     85 050213 - 050313;  define GIMI Portal configuration
     86
    8587 051313;  2-4pm EDT;  demo
    8688
     89 052013 - 052213;  design GIMI Portal
     90
    8791 052713;  4pm EDT
    8892
     
    96100
    97101
    98 == 4)  Tasks ==
    99 
    100 GIMI Tasks Through GEC17
     102== 4)  GIMI Tasks Through GEC17 ==
    101103
    102104 * Started 032013
     
    106108 * Revised after 041513 and 042213 calls, and discussions with Mike.
    107109
    108 1)  Meet biweekly starting 4/1, with 3 demo sessions: 5/13, 6/10 and 7/8  [[BR]]
    109 
    110 2)  By 4/15:  /cleanup/checkin/test/document current code [[BR]]
     110
     1111)  By 4/15:  /cleanup/checkin/test/document current code [[BR]]
    111112        What needs work? [[BR]]
    112113
    113 3)  Agree on goals: [[BR]]
     1142)  Agree on goals: [[BR]]
    114115        a)  GIMI (also GEMINI) to work with both ExoGENI and InstaGENI  [[BR]]
    115116        b)  Consistent user experience, both racks, both sets of I&M tools [[BR]]
     
    127128        i)  Stay consistent with Spiral 5 GIMI SOW [[BR]]
    128129
    129 4)  Build workflow for GEMINI to work on both InstaGENI and ExoGENI [[BR]]
     1303)  Build workflow for GEMINI to work on both InstaGENI and ExoGENI [[BR]]
    130131    a)  Start with browser, GENI Desktop, FLACK and OMNI, for InstaGENI [[BR]]
    131132    b)  Start with User Workspace, Flukes and OMNI for ExoGENI [[BR]]
     
    140141                4/16:  Sub-team has met, made plan;  see http://groups.geni.net/geni/wiki/IMInteroperability  [[BR]]
    141142       
    142 5)  Decide on configuration of GIMI Portal service. [[BR]]
     1434)  Define configuration of GIMI Portal service. [[BR]]
    143144        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]]
    144145        b)  Continue to include OML Server and Lab wiki (for orchestration, results, and documentation) [[BR]]
     
    164165                 5)  All captured in descriptive text, drawings, and a detailed workflow  [[BR]]
    165166
    166 6)  Plan to develop GIMI Portal service  [[br]]
    167          a) On 4/19, Mike agrees to have small group (Mike, Cong, Divya, Max, Jeanne and Harry) meet in Cambridge 5/20 - 5/21 (also 5/22?) to define multi-session GIMI Portal. Suggest:  have Tom/Aaron present to represent GENI CH Portal  [[BR]]
     1675)  Design GIMI Portal service  [[br]]
     168         a)  Who?
     169             On 4/19, Mike agrees to have small group (Mike, Cong, Divya, Max, Jeanne and Harry) meet in Cambridge 5/20 - 5/21 (also 5/22?) 
     170             Suggest:  have Tom/Aaron present to represent GENI CH Portal  [[BR]]
    168171         b)  Follows:  definition defined 5/2 - 5/3 [[BR]]
    169172         c)  Includes: [[BR]]
    170               Apache server [[BR]]
     173              Thin server [[BR]]
    171174              OML Server [[BR]]
    172175              User DB [[BR]]
     
    175178           
    176179
    177 7)  Add features to iRODS [[BR]]
     1806)  Add features to iRODS [[BR]]
    178181        a)  Add rules to process incoming descriptors in XML files, ans store info in iCAT [[BR]]
    179182        b)  Add rules to move object to public archive directory, and manage any changes [[BR]]
     
    198201            On 040413, put off discussion of this topic, until other topics are understood;  may have BBN summer interns work on some of these topics. [[BR]]
    199202       
    200 8)  Overall schedule: [[BR]]
    201         a)  By 6/10:  We need to have the bulk of the work done on GIMI Portal no later than 6/10 [[BR]]
    202         b)  By 7/8:  v2 ready for testing [[BR]]
    203         c)  On 7/21 - 7/23  at GEC17:  v2 software released after testing;  integrated tutorials presented  [[BR]]
    204 
    205 == 5)  Key Task List ==
     203
     204
     2058)  Key task list:   [[br]]
    206206
    207207|| '''ID''' || '''Description''' || '''Assignee''' || '''Due'''  || '''Status''' || '''Notes''' ||