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 || || S1 || || |
250 | | || 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 || || |
| 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 || || |
253 | 252 | || T3.5 || Make init script interactive, to allow selection by User at run time; how? || Cong, Jeanne, Keleigh || GEC17 || || S2 || || |
254 | 253 | || T3.6 || Provide options with init script for a new experiment, or an update. || Cong, Jeanne, Keleigh || GEC17 || || S2 || Could this be automatic?|| |
255 | 254 | || 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 5) for OML Results Isolation || |
256 | 255 | || T3.8 || Get [9] project_id from CH (how?), or enter || Cong, Jeanne, Keleigh, Tom/Aaron || GEC17 || || S2 || || |
259 | | || 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?|| |
260 | | || T3.12 || Register slice, nodes to XMPP server (if needed) || Cong, Jeanne, Keleigh || GEC17 || || S1 || || |
| 258 | || 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 || |
263 | | || T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS || Cong, Jeanne, Keleigh, Shu || GEC17 || || S3 || || |
264 | | || 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|| |
| 262 | || T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS || Cong, Jeanne, Keleigh, Shu || GEC17 || || S1 || || |
| 263 | || 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 available|| |
283 | | || 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; See Fog 2a) and 3) || |
284 | | || T4.2 || Define RESTful config interface, and integrate with interface in EME used by init script || Max, Jack, Cong || GEC17 || || S1 || || |
285 | | || 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 || || |
286 | | || 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 || || |
287 | | || || || || || || || || |
| 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 || || S1 || See Fig 2a) and 3) || |
| 284 | || T4.2 || Define RESTful config interface/API , and integrate with interface in EME used by init script || Cong, Jeanne || GEC17 || || S1 || || |
| 285 | || 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 || || S1, S2, S3 || || |
| 286 | || T4.4 || Define Exper Registry interface/API to LabWiki || GEC17 || Cong, Max, Jack || || S1 || || |
319 | | || T6.2 || Provide navigation from GENI CH Portal to GUI User Interface, identifying User, forwarding other information (what?). and allowing SSO; 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? || |
| 318 | || T6.2 || Provide navigation from GENI CH Portal to GUI User Interface, identifying User, forwarding other information (what?). and allowing SSO; then login User, and then verify against User entry in Exper Registry || Max, Jack, Tom/Aaron || GEC17 || || S2 || Need to be able to select GIMI Portal from GENI CH Portal; how? || |
321 | | || 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? || |
322 | | || 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? || |
| 320 | || 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 || || S1, S2, S3 || How can we link from [4] node names, or other info in silver_manifest? || |
| 321 | || T6.5 || On LabWiki page, allow User to add parameters to scripts || Max, Jack || GEC17 || || S1 || How can we link from [4] node names, or other info in silver_manifest? || |
325 | | || T6.8 || On LabWiki page, allow User to pull meas data from postgreSQL DB for this experiment and this meas_task, format as a table, add a descriptor; then use iclient to push artifact and descriptor files from GIMI Portal Agent to iRODS, using iRODS target and ticket from Exper Registry; GIMI Portal Agent is a registered iRODS user, is authenticated with cert/priv key, and can access the GENI User directories with the iticket. || Max, Jack, Shu || GEC17 || || S2, S3 || See Fig ? on use of iticket || |
326 | | || 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 || || |
327 | | || 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 || || |
| 324 | || T6.8 || On LabWiki page, allow User to pull, on demand, meas data from postgreSQL DB for this experiment and this meas_task, format as a table, add a descriptor; then use iclient to push artifact and descriptor files from GIMI Portal Agent to iRODS, using iRODS target and ticket from Exper Registry; GIMI Portal Agent is a registered iRODS user, is authenticated with cert/priv key, and can access the GENI User directories with the iticket. || Max, Jack, Shu || GEC17 || || S2, S3 || See Fig 7b) on use of iticket || |
| 325 | || T6.9 || On LabWiki page, allow User to push to iRODS scripts and other info for this experiment, meas_task, as stored in Experiment Registry || Max, Jack, Shu || GEC17 || || S3 || || |
| 326 | || T6.10 || On LabWiki page, allow user to select available or define new measurement task for new page, without stopping current tasks || Max, Jack || GEC17 || || S3 || || |
| 327 | || T6.11 || On LabWiki page, allow User to select, on demand, a particular experiment and meas_task, and stop them, without erasing measurement data in the DB || Max, Jack || GEC17 || || S2 || || |
| 328 | || T6.12 || On LabWiki page, allow User to select, on demand, a particular experiment and meas_task, that have been stopped, and erase measurement data in the DB || Max, Jack || GEC17 || || S3 || || |