Changes between Version 57 and Version 58 of GIMIv2tasks


Ignore:
Timestamp:
06/07/13 11:46:43 (6 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GIMIv2tasks

    v57 v58  
    247247
    248248|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    249 || T3.1 || Download [2] user_creds (cert + priv key)from GENI CH Portal (which interface?), store locally in EME, verify can act as User  || Cong, Jeanne, Keleigh  || GEC17 || Completed  || S1 || ||
    250 || T3.3 || Use iinit with username/password to access iRODS  (option 2 of 2)  || Cong, Jeanne, Keleigh  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/5 #5]  || S1 || ||
     249|| T3.1 || Download [2] user_creds (cert + priv key)from GENI CH Portal (web interface), store locally in EME, verify can act as User  || Cong, Jeanne, Keleigh  || GEC17 || Completed  || S1 || ||
     250|| T3.3 || Use iinit with username/password to access iRODS, and setup iRODS env file  (option 2 of 2)  || Cong, Shu  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/5 #5]  || S1 || ||
    251251|| T3.4 || Build GIMI v2 Init Script for User, to run in EME  || Cong, Jeanne, Keleigh  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/4 #4]  || S1, S2, S3 || See Fig 2a) and 2b) ||
    252 || T3.5 || Make init script interactive, to allow selection by User at run time;  how?  || Cong, Jeanne, Keleigh  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/4 #4]  || S2 || ||
     252|| T3.5 || Make init script interactive, to allow selection by User at run time;  how?  || Cong, Jeanne, Keleigh  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/4 #4]  || S1 || ||
    253253|| T3.6 || Provide options with init script for a new experiment, or an update.  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || Could this be automatic?||
    254254|| T3.7 || Enter exp_name, derive [10] exper_id = user_name-exper_name-unix_timestamp, at start of experiment  || Cong, Jeanne, Keleigh  || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/4 #4] || S1 || See Fig 5) for OML Results Isolation ||
    255255|| T3.8 || Get [9] project_id from CH (how?), or enter  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||   || S2 || ||
    256256|| T3.9 || Acting as User, get list of slice_id's from CH SA, then select [3] slice_id for this experiment  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/7 #7]  || S1 || ||
    257 || T3.10 || Acting as User, using OMNI, get [7] sliver_manifest_rspecs from AMs  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/8 ticket #8] || S2 || ||
     257|| T3.10 || Acting as User, using OMNI, get [7] sliver_manifest_rspecs from AMs  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/8 ticket #8] || S1 || ||
    258258|| T3.11 || Parse [7] to get [4] slice_node_names  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || Do we want to parse [7] and get many more parameters?  like GENI Desktop parser is doing?  and then push them to Experiment Registry in GIMI Portal?||
    259 || T3.12 || Register slice, nodes to XMPP server (if needed)  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || Move to OMF ver 5.4 ||
    260 || T3.13 || Select default GIMI Portal, or override  ||  Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || ||
    261 || T3.14 || Acting as User, using iclient, setup GSAS (iRODS) structure for this experiment, derive defaults for [12] user_irods_home_directory and [13] user_irods_target_directory, or override;  derive and load [11] proj_exper_step_descriptors;  load template OMF scripts (where are these?);  get iticket for experiment, assigned to selected GIMI Portal Agent    || Cong, Jeanne, Keleigh, Shu  || GEC17 || tickets [http://groups.geni.net/gimi/ticket/9 #9],  [http://groups.geni.net/gimi/ticket/10 #10], [http://groups.geni.net/gimi/ticket/11 #11]|| S2 || Need summary of IRODS structure;  see Fig 7b) for use of iticket ||
    262 || T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS  || Cong, Jeanne, Keleigh, Shu  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/12 #12]  || S1 || ||
     259|| T3.12 || Register slice, nodes to XMPP server (if needed)  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || Not needed if using OMF ver 5.4.2 ||
     260|| T3.13 || Select default GIMI Portal, or override  ||  Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || Now using default ||
     261|| T3.14 || Acting as User, using iclient, setup GSAS (iRODS) structure for this experiment, derive defaults for [12] user_irods_home_directory and [13] user_irods_target_directory, or override;  derive and load [11] proj_exper_step_descriptors;  load template OMF scripts (where are these?);  get iticket for experiment, assigned to selected GIMI Portal Agent    || Cong, Jeanne, Keleigh, Shu, Antoine  || GEC17 || tickets [http://groups.geni.net/gimi/ticket/9 #9],  [http://groups.geni.net/gimi/ticket/10 #10], [http://groups.geni.net/gimi/ticket/11 #11]|| S1, S2 || Need summary of IRODS structure;  see Fig 7b) for use of iticket ||
     262|| T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS  || Cong, Keleigh  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/12 #12]  || S1 || ||
    263263|| T3.16 || Acting as User, using RESTful client, push configs to GIMI Portal, including:  [1]  user_identity  (from [2]), [10]  experiment_id,  [9] project_id, [3] slice_id, [4]  slice_node_names, [7]  sliver_manifest_rspecs, [12]  user_irods_home_directory, [13]  user_irods_target(exper)_directory,    [14]  user_irods_target(exper)_iticket  || Cong, Jeanne, Keleigh, Max, Jack  || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/13 #13] || S1, S2, S3 || Start with default values, and then replace with gathered values as available||
    264264|| T3.17 || Build v2 release script  || Cong, Jeanne, Keleigh  || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/6 #6] || S3 || See Fig 2b) ||
     
    281281
    282282|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    283 || T4.1 || Include Experiment Registry in GIMI Portal, with RESTful config interface, and underlying tuple-store, starting with current  "OMF_SFA AM" code  || Cong, Max, Jack  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/14 #14]  || S1 || See Fig 2a) and 3)  ||
     283|| T4.1 || Include Experiment Registry in GIMI Portal, with RESTful config interface, and underlying tuple-store, starting with current  "OMF_SFA AM" code  || Cong, Max, Jack  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/14 #14]  || S1 || See Fig 2a) and 3)   Need to get latest code from Max. ||
    284284|| T4.2 || Define RESTful config interface/API , and integrate with interface in EME used by init script  || Cong, Jeanne  || GEC17 || ticket [http://groups.geni.net/gimi/ticket/15 #15]  || S1 || ||
    285285|| T4.3 || On receipt of config messages from init script in EME, put user and experiment info (tuple) into Exper Registry  || Cong, Max, Jack || GEC17 ||  ticket [http://groups.geni.net/gimi/ticket/16 #16] || S1, S2, S3 || ||
     
    298298
    299299|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    300 || T5.1 || Include OML Server in GIMI Portal, with inbound OML Interface, and underlying postgreSQL DB  || Olivier  || GEC17 ||   || S1 || Use OML ver 2.8 ||
    301 || T5.2 || Accept OML measurements into OML server, into inbound OML Interface, identified by exper_id and oml_id, and put into postgreSQL DB  || Olivier  || GEC17 ||   || S1 || See Fig 5) on OML Results Isolation||
     300|| T5.1 || Include OML Server in GIMI Portal, with inbound OML Interface, and underlying postgreSQL DB  || Steve, Olivier  || GEC17 ||   || S1 || Now OML ver 2.9;  consider 2.10? ||
     301|| T5.2 || Accept OML measurements into OML server, into inbound OML Interface, identified by exper_id and oml_id, and put into postgreSQL DB  || Steve, Olivier  || GEC17 ||   || S1 || See Fig 5) on OML Results Isolation||
    302302||  ||  ||   ||  ||   ||  || ||
    303303||  ||  ||   ||  ||   ||  || ||