Context Navigation

Changes between Version 4 and Version 5 of _GIMI_NextSteps

Timestamp:: 04/27/12 12:05:56 (12 years ago)
Author:: hmussman@bbn.com
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

_GIMI_NextSteps

-                      v4
+                      v5
 a)  (Mike)  need to arrive at nominal configuration ASAP
  on 4/18:  good discussion (see below);  still need a clear and complete description soon;  when?
  on 4/25:  discussion as noted below;  still need a clear and complete description soon, and a full design review;  when?
+ - on 4/18:  good discussion (see below);  still need a clear and complete description soon;  when?
+ - on 4/25:  discussion as noted below;  still need a clear and complete description soon, and a full design review;  when?
 a')  on 4/20:  issue:  how to configure MPs/MCs?  from EC to RC in  MP/MC?
 a!'')  on 4/20:  issue:  is there a MAP on common node?  at least to preview data?  is there a MAP in user workspace?  what?
  on 4/25:  for 1st, no MAP on common node
+ - on 4/25:  for 1st, no MAP on common node
 b)  MPs with multiple possible measurements:  host info;  basic network performance with iperf, ping;  data from app
  on 4/25:  need to list baseline measurements, and configurable parameters
+ - on 4/25:  need to list baseline measurements, and configurable parameters
 c)  MC (OML server) in common node (node n+1)
 d)  where is MAP service installed?  in common node?    in user workspace?    what is planned for this service?  how can analysis/presentation be configured?  is there an r script?  is there a GUI?  how is GUI accessed?
  on 4/25:  for 1st, expect MAP only bin user workspace
  on 4/25:  what is 1st MAP service?  what functions are provided?  can these be done using iREEL and r?
+ - on 4/25:  for 1st, expect MAP only bin user workspace
+ - on 4/25:  what is 1st MAP service?  what functions are provided?  can these be done using iREEL and r?
 e)  movement of data from MC (OML server) to MAP service:   direct?   how?   via iRODS, i.e., MC to iRODS to MAP?  how?
  on 4/18,  per Shu, and discussion:  could login to MC node;  establish first transfer from iRODS client on MC to to iRODS with iput;  use  iinit, so iRODS client remembers password;  then periodic transfers with no human intervention;  another push protocol, from MC to iRODS.
  on 4/18,  per Shu, and discussion: next, can install iRODS client on user workspace, then pull data back to user workspace for analysis and presentation, and then push back to iRODS for archive
+ - on 4/18,  per Shu, and discussion:  could login to MC node;  establish first transfer from iRODS client on MC to to iRODS with iput;  use  iinit, so iRODS client remembers password;  then periodic transfers with no human intervention;  another push protocol, from MC to iRODS.
+ - on 4/18,  per Shu, and discussion: next, can install iRODS client on user workspace, then pull data back to user workspace for analysis and presentation, and then push back to iRODS for archive
 f)  1st:  common node in slice;  2nd:  common node in user workspace (out of slice)  (is this beyond GEC14?)
  on 4/25:  for 1st, do common node in slice, but plan one per aggregate
+ - on 4/25:  for 1st, do common node in slice, but plan one per aggregate
 g)  1st:  nodes on VMs, one aggregate;  2nd:  nodes on VMs, multiple aggregates
 h)  1st:  Load image for common node, MP nodes;  2nd:  load MP code as package before/after app
  on 4/25:  what is test app?  need to have something visible, e.g., video to a web page?
+ - on 4/25:  what is test app?  need to have something visible, e.g., video to a web page?
 i)  Is there authentication/authorization when data pushed fom MP to MC?  1st:  none;  considered OK  2nd:  add ssl?
 j)  Is there authentication/authorization when accessing GUI (MAP) on common node?  how?   does this use portal to GUIs?
  on 4/25:  not in 1st
+ - on 4/25:  not in 1st
 == 4)  *** Introduce XML messaging service:  required for OMF messages, used to orchestrate services ==
 …
 b)  (Max, Christoph)  signed OMF messages:  need summary of arrangement from NICTA.    what are names?  who configures pub/sub nodes?    what is structure?    how to generate and distribute keys?  is a public key registry required?    how would it be done?
  on 4/18:  Max explains plan to use OMF6.0 approach;  limited messages;  can use XMPP or another transport;  signed messages;  can start with no authentication/authorization, and then turn it on later;
  on 4/18:  need clear and complete description soon, particularly naming and establsihment of XMPP nodes. so that others can consider for use and Jeanne can begin testing.
  on 4/18:  expect release of first OMF6.0 by mid-May, with firm RC and skeleton EC;  expect updated EC by mid-June;  is this too late for GEC14?
   on 4/25:  need to start with an earlier version of OMF, e.g., OMF 5.3
+ - on 4/18:  Max explains plan to use OMF6.0 approach;  limited messages;  can use XMPP or another transport;  signed messages;  can start with no authentication/authorization, and then turn it on later;
+ - on 4/18:  need clear and complete description soon, particularly naming and establsihment of XMPP nodes. so that others can consider for use and Jeanne can begin testing.
+ - on 4/18:  expect release of first OMF6.0 by mid-May, with firm RC and skeleton EC;  expect updated EC by mid-June;  is this too late for GEC14?
+  - on 4/25:  need to start with an earlier version of OMF, e.g., OMF 5.3
 == 5)  Tools in user workspace  ==
 …
 f)  (Christoph)  Add iREEL (experimenter portal service);
  on 4/25:  what can this do?  can it provide MAP functions?  can it drive scripts?  (need copy to run locally)
+ - on 4/25:  what can this do?  can it provide MAP functions?  can it drive scripts?  (need copy to run locally)
 g)  (From GEMINI;  under discussion)  Include portal service to find other GUIs?
  on 4/25:  for 1st, not necessary
+ - on 4/25:  for 1st, not necessary
 h)  (Giridhar, Jeanne, Shu)  Include Directory Archive (DA) service ,which can push data to DOA service, using OI service  (all from CNRI, also GPO )
  on 4/25:  now replaced with iRODS client
+ - on 4/25:  now replaced with iRODS client
 i)   (Giridhar, Jeanne, Shu) Include MDOD creator/editor  How does this interface with iRODS, ot push MDOD to iRODS?
   on 4/18:  who on GIMI project will help define final MDOD schema?  Shu.
   on 4/25:  need to get group together, to revise MDOD schema, and consider implementation of creator/editor
+  - on 4/18:  who on GIMI project will help define final MDOD schema?  Shu.
+  - on 4/25:  need to get group together, to revise MDOD schema, and consider implementation of creator/editor
 …
 d) (Shu)  define use case for:  moving data from MC to iRODS, then from iRODS to user workspace
 use iRODS cleint in MC to push to iRODS?  how is authentication/authorization handled?
 use iRODS client in user workspace to pull to user workspace?  how is authentication/authorization handled?
+ - use iRODS cleint in MC to push to iRODS?  how is authentication/authorization handled?
+ - use iRODS client in user workspace to pull to user workspace?  how is authentication/authorization handled?
 On 4/18:  use cases received:
 …
 c)  (Mike)  What is first configuration of tools code?  when?  who?
  on 4/18:  plan to forward all code and plans for GEC13 to Jeanne
  on 4/18:  code leads are David and Delip;  will join future calls
+ - on 4/18:  plan to forward all code and plans for GEC13 to Jeanne
+ - on 4/18:  code leads are David and Delip;  will join future calls
 d)  (Jeanne)  What are first test scripts?  when?
  on 4/25:  need to outline process for using tools in user workspace
  on 4/25:  need to provide first test plan
+ - on 4/25:  need to outline process for using tools in user workspace
+ - on 4/25:  need to provide first test plan
 e)  (Jeanne)  When are first tests?
 …
 a)  (Mike, Cong)  Can we do something by GEC14?  what?
  on 4/25:  agree UMass Amherst WiMAX site should be up by GEC14
  on 4/25:  agree should have plan to integrate GIMI with WiMAX by GEC14, but does not need to be done
+ - on 4/25:  agree UMass Amherst WiMAX site should be up by GEC14
+ - on 4/25:  agree should have plan to integrate GIMI with WiMAX by GEC14, but does not need to be done