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 || || |
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 || || |
277 | 277 | || T3.10 || Acting as User, using OMNI, get [7] sliver_manifest_rspecs from AMs || Cong, Jeanne, Keleigh, Tom/Aaron || GEC17 || || S2 || || |
278 | 278 | || 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?|| |
279 | 279 | || 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 || |
282 | 282 | || T3.15 || Acting as User, using iclient, push [7] sliver_manifest_rspecs and [8] descriptors to iRODS || Cong, Jeanne, Keleigh, Shu || GEC17 || || S3 || || |
283 | 283 | || 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|| |
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 || || |
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|| |
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? || |
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 || |