Changes between Version 48 and Version 49 of GIMIv2tasks


Ignore:
Timestamp:
05/28/13 11:01:23 (6 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GIMIv2tasks

    v48 v49  
    193193=== 4.6)  Add features to iRODS ===
    194194
    195         a)  Add rules to process incoming descriptors in XML files, ans store info in iCAT [[BR]]
     195        a)  Add rules to process incoming descriptors in XML files, and store info in iCAT [[BR]]
    196196        b)  Add rules to move object to public archive directory, and manage any changes [[BR]]
    197197        c)  Integrate archive service with handle service [[BR]]
     
    203203            On 4/29, Shu agrees to provide latest task list, and schedule. [[BR]]
    204204       
    205 === 4.6) Include easy way to configure measurements, for all types of experiments (small, medium and large) ===
     205=== 4.7) Include easy way to configure measurements, for all types of experiments (small, medium and large) ===
    206206
    207207
     
    267267|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    268268|| 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 ||   || S1 || ||
    269 || T3.2 || Use script to install [2] user_cred's, so can use iclient to access iRODS || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
    270 || T3.3 || Use iinit with username/password to access iRODS  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
     269|| T3.2 || Use script to install [2] user_cred's, so can use iclient to access iRODS (option 1 of 2) || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
     270|| T3.3 || Use iinit with username/password to access iRODS  (option 2 of 2)  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
    271271|| T3.4 || Build v2 Init Script for User, to run in EME  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
    272 || T3.5 || Make init script interactive, to allow selection at run time  how?  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || ||
     272|| T3.5 || Make init script interactive, to allow selection by User at run time;  how?  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || ||
    273273|| T3.6 || Provide options with init script for a new experiment, or an update.  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || Could this be automatic?||
    274 || T3.7 || Enter exp_name, derive [10] exper_id = user_name-exper_name-unix_timestamp, at start of experiment  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
    275 || T3.8 || Get [9] project_id   (from CH?  how?)  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||   || S2 || ||
    276 || T3.9 || Acting as User, get list of slice_id's from CH SA, select [3] slice_id for this experiment  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||   || S2 || ||
     274|| T3.7 || Enter exp_name, derive [10] exper_id = user_name-exper_name-unix_timestamp, at start of experiment  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || See Fig for OML Results Isolation ||
     275|| T3.8 || Get [9] project_id from CH (how?, or enter  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||   || S2 || ||
     276|| 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 ||   || S2 || ||
    277277|| T3.10 || Acting as User, using OMNI, get [7] sliver_manifest_rspecs from AMs  || Cong, Jeanne, Keleigh, Tom/Aaron  || GEC17 ||   || S2 || ||
    278278|| T3.11 || Parse [7] to get [4] slice_node_names  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 || 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?||
    279279|| T3.12 || Register slice, nodes to XMPP server (if needed)  || Cong, Jeanne, Keleigh  || GEC17 ||   || S1 || ||
    280 || T3.13 || Select default GIMI Portal, or override  | Cong, Jeanne, Keleigh  || GEC17 ||   || S2 ||  ||
    281 || 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 ||   || S2 || Need summary of IRODS structure;  see figure for use of iticket ||
     280|| T3.13 || Select default GIMI Portal, or override  || Cong, Jeanne, Keleigh  || GEC17 ||   || S2 ||  ||
     281|| 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 ||   || S2 || Need summary of IRODS structure;  see Fig for use of iticket ||
    282282|| T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS  || Cong, Jeanne, Keleigh, Shu  || GEC17 ||   || S3 || ||
    283283|| 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 ||   || S1, S2, S3 || Start with default values, and then replace with gathered values as avaialble||
     
    300300
    301301|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    302 || T4.1 || Include Experiment Registry in GIMI Portal, with RESTful config interface, and underlying tuple-store (based on "OMF_SFA AM")  || Max, Jack  || GEC17 ||   || S1 || ||
     302|| T4.1 || Include Experiment Registry in GIMI Portal, with RESTful config interface, and underlying tuple-store   || Max, Jack  || GEC17 ||   || S1 || Start with "OMF_SFA AM", per Max. ||
    303303|| T4.2 || Define RESTful config interface, and integrate with interface in EME used by init script  || Max, Jack, Cong  || GEC17 ||   || S1 || ||
    304 || T4.3 || On first config message from Init Script in EME, use presented GENI cred's to register user in Exper Registry   || Max, Jack  || GEC17 ||   || S1 || ||
    305 || T4.4 || On first and subsequent config messages from init script in EME, put all exper info into Exper Registry  || Max, Jack || GEC17 ||   || S1, S2, S3 || ||
     304|| T4.3 || On first config message from Init Script in EME, use presented GENI cred's to register User in Exper Registry   || Max, Jack  || GEC17 ||   || S1 || ||
     305|| T4.4 || On first and subsequent config messages from init script in EME, put experiment info into Exper Registry  || Max, Jack || GEC17 ||   || S1, S2, S3 || ||
    306306||  ||  ||   ||  ||   ||  || ||
    307307||  ||  ||   ||  ||   ||  || ||
     
    318318
    319319|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    320 || T5.1 || Include OML Server in GIMI Portal, with inbound interface, and underlying postgreSQL DB  || Olivier  || GEC17 ||   || S1 || ||
    321 || T5.2 || Accept OML measurements into OML server, identified by exper_id and oml_id, and put into postgreSQL DB  || Olivier  || GEC17 ||   || S1 || ||
     320|| T5.1 || Include OML Server in GIMI Portal, with inbound OML Interface, and underlying postgreSQL DB  || Olivier  || GEC17 ||   || S1 || Use OML ver ? ||
     321|| 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 ? on OML Results Isolation||
    322322||  ||  ||   ||  ||   ||  || ||
    323323||  ||  ||   ||  ||   ||  || ||
     
    335335
    336336|| '''ID''' || '''Description''' || '''Who''' || '''Due'''  || '''Status''' || '''Demos''' || '''Notes''' ||
    337 || T6.1 || Include LabWiki in GIMI Portal, with EC, with GUI (web) User interface based on OMF web service, and underlying state machines   || Max, Jack  || GEC17 ||   || S1, S2, S3 || ||
    338 || T6.2 || Provide navigation from GENI CH Portal to GUI User interface, identifying User, login, and then verify against Exper Registry  || Max, Jack, Tom/Aaron  || GEC17 ||   || S3 ||  Need to be able to select GIMI Portal from GENI CH Portal ||
     337|| T6.1 || Include LabWiki in GIMI Portal, with EC, with GUI (web) User interface based on OMF web service, and underlying state machines   || Max, Jack  || GEC17 ||   || S1, S2, S3 ||  Start with LabWiki ver ?, based on OMF ver 5.4, and OMF Web ver ? ||
     338|| T6.2 || Provide navigation from GENI CH Portal to GUI User Interface, identifying User, and forwarding other information (what?);  then login User, and then verify against User entry in Exper Registry  || Max, Jack, Tom/Aaron  || GEC17 ||   || S3 ||  Need to be able to select GIMI Portal from GENI CH Portal;  how? ||
    339339|| T6.3 || On login to GUI User Interface, present LabWiki page, and allow User to select from available experiments, as listed in Exper Registry  || Max, Jack  || GEC17 ||   || S1 || ||
    340 || T6.4 || On LabWiki page, for a given exper, allow user to select available or define new measurement_task, add descriptor, and then load template/stored script from iRODS, and then edit || Max, Jack  || GEC17 ||   || S2, S3 || ||
    341 || T6.5 || On LabWiki page, allow User to add parameters to scripts || Max, Jack  || GEC17 ||   || S2, S3 || How can we link from [4] node names, or other info in silver_manifest ?||
    342 || T6.6 || On LabWiki page, execute script to configure OML Clients, pushing IP address of this GIMI Portal OML server, exper-id and oml_id   || Max, Jack  || GEC17 ||   || S1 || ||
    343 || T6.7 || On LabWiki page, execute script to orchestrate measurement_task, then pull data from postgreSQL DB, and provide graphs  || Max, Jack, Olivier  || GEC17 ||   || S1, S2, S3 || ||
    344 || T6.8 || On LabWiki page, allow User to pull meas data from postgreSQL DB for this experiment and this meas_task, and push to iRODS as table, adding a descriptor;  use iRODS target and ticket from Exper Registry  || Max, Jack, Shu  || GEC17 ||   || S2, S3 || ||
     340|| T6.4 || On LabWiki page, for a given exper, allow User to select available or define new measurement_task, add descriptor, and then load template/stored script from iRODS, and then edit script || Max, Jack  || GEC17 ||   || S2, S3 || How can we link from [4] node names, or other info in silver_manifest? ||
     341|| T6.5 || On LabWiki page, allow User to add parameters to scripts || Max, Jack  || GEC17 ||   || S2, S3 || How can we link from [4] node names, or other info in silver_manifest? ||
     342|| T6.6 || On LabWiki page, allow User to execute script to configure OML Clients, pushing IP address of this GIMI Portal OML server, exper-id and oml_id   || Max, Jack  || GEC17 ||   || S1 || ||
     343|| T6.7 || On LabWiki page, allow User to execute script to orchestrate measurement_task, then pull data from postgreSQL DB, and provide graphs  || Max, Jack, Olivier  || GEC17 ||   || S1, S2, S3 || ||
     344|| T6.8 || On LabWiki page, allow User to pull meas data from postgreSQL DB for this experiment and this meas_task, and push to iRODS as table, adding a descriptor;  use iRODS target and ticket from Exper Registry;  GIMI Portal/Lab Wiki has agent with credentials that is a registered iRODS user, and can access the GENI User directories given the iticket.  || Max, Jack, Shu  || GEC17 ||   || S2, S3 ||  See Fig ? on use of iticket ||
    345345|| T6.9 || On LabWiki page, allow User to push to iRODS scripts and other info for this experiment, meas_task  || Max, Jack, Shu  || GEC17 ||   || S3 || ||
    346346|| T6.10 || On LabWiki page, allow user to select available or define new measurement task for new page, without stopping current tasks   || Max  || GEC17 ||   || S3 || ||
    347347||  ||  ||   ||  ||   ||  || ||
    348348||  ||  ||   ||  ||   ||  || ||
    349 ||  || ||   ||  ||   ||  || ||
     349||  ||  Consider best way to drive OMF script (on a medium experiment) from the slice information, e.g., number of nodes, names of nodes, topology of nodes. ||   ||  ||   ||  || ||
    350350||  || On LabWiki page, create new scripts, and then edit  || Max, Jack  ||  ||   ||  || ||
    351351||  || On LabWiki page, drag and drop scripts, and then edit || Max, Jack  ||  ||   || || ||