| 53 | == 3) Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks == |
| 54 | 8:40am |
| 55 | |
| 56 | === Overview === |
| 57 | Harry Mussman [[BR]] |
| 58 | 2min |
| 59 | |
| 60 | Step 3: Obtain slice, install software |
| 61 | * Now: GIMI using ExoGENI, Flukes; loads images/pkgs |
| 62 | * Now: GEMINI using InstaGENI, FLACK; loads images/pkgs |
| 63 | |
| 64 | Next: be able to use GEMINI on ExoGENI, and GIMI on InstaGENI |
| 65 | |
| 66 | Suggest: set goal to begin testing all combinations starting 5/1; good support by GEC17 |
| 67 | |
| 68 | === Lessons learned from using GIMI tools on ExoGENI racks === |
| 69 | Cong Wang [[BR]] |
| 70 | 8min |
| 71 | |
| 72 | 4 slides: current config; current capabilities and issues; future possibilities |
| 73 | |
| 74 | === Lessons learned from using GEMINI tools on InstaGENI racks === |
| 75 | Hussam Nasir [[BR]] |
| 76 | 8min |
| 77 | |
| 78 | 4 slides: current config; current capabilities and issues; future possibilities |
| 79 | |
| 80 | === Discussion === |
| 81 | 15min |
| 82 | Cong Wang; Hussam Nasir; (Ilia Baldine); (Rob Ricci); Louisa Nevers; Jeanne Ohren |
| 83 | |
| 84 | Discuss: |
| 85 | * Goal to begin testing all combinations starting 5/1; good support by GEC17 |
| 86 | * Likely roadblocks |
| 87 | * Suggested approaches |
| 88 | |
| 89 | Any topics, suggestions and issues suggested AHEAD OF TIME by members of roundtable? |
| 90 | |
| 91 | At the end: any conclusions, list of issues, team to continue discussion] |
53 | | a) Introductions |
| 98 | === Overview === |
| 99 | Harry Mussman [[BR]] |
| 100 | 2min |
| 101 | |
| 102 | Step 4: Configure/init I&M and exp app |
| 103 | * Now: GIMI using post boot scripts, OMF |
| 104 | * Now: GEMINI using instrumentize script, choices based on rspec extension; also used to add GN |
| 105 | |
| 106 | Next: move towards common approach, to better unify experiment environment |
| 107 | |
| 108 | Suggest: both move towards script, driven by rspec ext; discuss at I&M session |
| 109 | |
| 110 | === Current GIMI use of post boot scripts, OMF, to configure/inti services === |
| 111 | Cong Wang [[BR]] |
64 | | Current overall experiment configuration |
65 | | |
66 | | Summary of current experiment steps, and possible next steps towards a “unified experiment environment”. |
67 | | |
68 | | Today’s discussion topics: |
69 | | Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks |
70 | | Use instrumentize script, driven by rspec extension, to configure/init I&M tools |
71 | | Options for further measurement data analysis and presentation |
72 | | |
73 | | |
74 | | c) Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks |
75 | | 25min |
76 | | |
77 | | * Overview |
78 | | Harry Mussman |
79 | | S3: Obtain slice, install software |
80 | | Now: GIMI using ExoGENI, Flukes; loads images/pkgs |
81 | | Now: GEMINI using InstaGENI, FLACK; loads images/pkgs |
82 | | |
83 | | Next: be able to use GEMINI on ExoGENI, and GIMI on InstaGENI |
84 | | Suggest: set goal to begin testing all combinations starting 5/1; good support by GEC17; discuss at I&M session |
85 | | |
86 | | * Lessons learned from using GIMI tools on ExoGENI racks |
87 | | Cong Wang |
| 122 | === Discussion === |
108 | | * Overview |
109 | | Harry Mussman |
110 | | S4: Configure/init I&M and exp app |
111 | | Now: GIMI using post boot scripts, OMF |
112 | | Now: GEMINI using instrumentize script, choices based on rspec extension; also used to add GN |
| 138 | Step 6: Analyze |
| 139 | * Now: Both GEMINI and GIMI push measurement data objects (files) to GENI Storage Service (iRODS) |
| 140 | * Now: GEMINI provides dump of mongo DB, plus separate file of metadata |
| 141 | * Now: GIMI (will) provide SQLdump of PostgreSQL DB, which includes metadata |
114 | | Next: move towards common approach, to better unify experiment environment |
115 | | Suggest: both move towards script, driven by rspec ext; discuss at I&M session |
116 | | |
117 | | * Current GIMI use of post boot scripts, OMF, to configure/inti services |
118 | | Cong Wang |
119 | | 5min |
120 | | 2 slides: current config; current capabilities and issues; future possibilities |
121 | | |
122 | | * Current GEMINI use of instrumentize script, to configure/init services |
123 | | Hussam Nasir |
124 | | 5min |
125 | | 2 slides: current config; current capabilities and issues; future possibilities |
126 | | |
127 | | * Discussion |
128 | | 10min |
129 | | Cong Wang; Hussam Nasir; Aaron Helsinger; Jeanne Ohren |
130 | | |
131 | | [Any topics, suggestions and issues suggested AHEAD OF TIME by members of roundtable] |
132 | | |
133 | | [At the end: any conclusions, list of issues, team to continue discussion] |
134 | | |
135 | | |
136 | | e) Options for further measurement data analysis and presentation |
137 | | |
138 | | * Overview |
139 | | Harry Mussman |
140 | | S6: Analyze |
141 | | Now: Both GEMINI and GIMI push measurement data objects (files) to GENI Storage Service (iRODS) |
142 | | Now: GEMINI provides dump of mongo DB, plus separate file of metadata |
143 | | Now: GIMI (will) provide SQLdump of PostgreSQL DB, which includes metadata |
144 | | |
145 | | Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects) |
| 143 | * Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects) |