Changes between Version 20 and Version 21 of GIMIv2tasks

Timestamp:

04/29/13 17:17:26 (11 years ago)

Author:

hmussman@bbn.com

Comment:

--

GIMIv2tasks

@@ -83 +83 @@
  042913;  4pm EDT;  discuss planning meeting 5/2- 5/3 for GIMI Portal;  discuss interop status;  discuss GSAS status
 
+ 050213 - 050313;  define GIMI Portal configuration
+
  051313;  2-4pm EDT;  demo
 
+ 052013 - 052213;  design GIMI Portal
+
  052713;  4pm EDT
 
@@ -96 +100 @@
 
 
-== 4)  Tasks ==
-
-GIMI Tasks Through GEC17
+== 4)  GIMI Tasks Through GEC17 ==
 
  * Started 032013
@@ -106 +108 @@
  * Revised after 041513 and 042213 calls, and discussions with Mike.
 
-1)  Meet biweekly starting 4/1, with 3 demo sessions: 5/13, 6/10 and 7/8  [[BR]]
-
-2)  By 4/15:  /cleanup/checkin/test/document current code [[BR]]
+
+1)  By 4/15:  /cleanup/checkin/test/document current code [[BR]]
         What needs work? [[BR]]
 
-3)  Agree on goals: [[BR]]
+2)  Agree on goals: [[BR]]
         a)  GIMI (also GEMINI) to work with both ExoGENI and InstaGENI  [[BR]]
         b)  Consistent user experience, both racks, both sets of I&M tools [[BR]]
@@ -127 +128 @@
         i)  Stay consistent with Spiral 5 GIMI SOW [[BR]]
 
-4)  Build workflow for GEMINI to work on both InstaGENI and ExoGENI [[BR]]
+3)  Build workflow for GEMINI to work on both InstaGENI and ExoGENI [[BR]]
     a)  Start with browser, GENI Desktop, FLACK and OMNI, for InstaGENI [[BR]]
     b)  Start with User Workspace, Flukes and OMNI for ExoGENI [[BR]]
@@ -140 +141 @@
                 4/16:  Sub-team has met, made plan;  see http://groups.geni.net/geni/wiki/IMInteroperability  [[BR]]
         
-5)  Decide on configuration of GIMI Portal service. [[BR]]
+4)  Define configuration of GIMI Portal service. [[BR]]
         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]]
         b)  Continue to include OML Server and Lab wiki (for orchestration, results, and documentation) [[BR]]
@@ -164 +165 @@
                  5)  All captured in descriptive text, drawings, and a detailed workflow  [[BR]]
 
-6)  Plan to develop GIMI Portal service  [[br]]
-         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]]
+5)  Design GIMI Portal service  [[br]]
+         a)  Who?
+             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?)  
+             Suggest:  have Tom/Aaron present to represent GENI CH Portal  [[BR]]
          b)  Follows:  definition defined 5/2 - 5/3 [[BR]]
          c)  Includes: [[BR]]
-              Apache server [[BR]]
+              Thin server [[BR]]
               OML Server [[BR]]
               User DB [[BR]]
@@ -175 +178 @@
             
 
-7)  Add features to iRODS [[BR]]
+6)  Add features to iRODS [[BR]]
         a)  Add rules to process incoming descriptors in XML files, ans store info in iCAT [[BR]]
         b)  Add rules to move object to public archive directory, and manage any changes [[BR]]
@@ -198 +201 @@
             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]]
         
-8)  Overall schedule: [[BR]]
-        a)  By 6/10:  We need to have the bulk of the work done on GIMI Portal no later than 6/10 [[BR]]
-        b)  By 7/8:  v2 ready for testing [[BR]]
-        c)  On 7/21 - 7/23  at GEC17:  v2 software released after testing;  integrated tutorials presented  [[BR]]
-
-== 5)  Key Task List ==
+
+
+8)  Key task list:   [[br]]
 
 || '''ID''' || '''Description''' || '''Assignee''' || '''Due'''  || '''Status''' || '''Notes''' ||