| 170 | Conclusions: |
| 171 | |
| 172 | 1) Be flexible in use of tools; don't kill innovation |
| 173 | |
| 174 | 2) Push towards single-sign-on |
| 175 | |
| 176 | 3) To make it easier to mix and match tools. pass info from tool to tool, using iRODS as a repository |
| 177 | |
| 178 | Issues: |
| 179 | |
| 180 | Team to continue discussion: |
| 181 | |
| 182 | Tom Mitchell (GPO); Hussam Nasir (Univ Kentucky); Mike Zink (UMass Amherst); Jeanne Ohren (GPO) [[BR]] |
| 183 | |
| 184 | |
| 185 | == 4) Introduction of OMF to config/orchestrate I&M and experimenter's application services == |
| 186 | 9:35am |
| 187 | |
| 188 | === Introduction === |
| 189 | Harry Mussman (GPO) [[BR]] |
| 190 | |
| 191 | Step 5: Run/orchestrate I&M and experimenter's application services |
| 192 | * Now: GEMINI uses portal to GUI, to config/orchestrate |
| 193 | * Now: GIMI uses OMF EC with Ruby script to config/orchestrate |
| 194 | * Gap: no common way to config/orchestrate exp apps |
| 195 | |
| 196 | * Next: Integrate orchestration of all services, including GIMI, GEMINI and experimenter's application services, to better unify experiment environment |
| 197 | * Suggest: Introduce OMF for config/orchestration of all I&M tools and experimenter's application services; later, add optional graphical interface |
| 198 | |
| 199 | === Summary of OMF capabilities === |
| 200 | Max Ott (NICTA) [[BR]] |
| 201 | 10min |
| 202 | |
| 203 | [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/omf-gec16-mar-2013.pdf slides]: current config; current capabilities and issues; future possibilities [[BR]] |
| 204 | |
| 205 | === Roundtable discussion === |
| 206 | Max Ott (NICTA); Marshall Brinn (GPO); Martin Swany (Indiana Univ); Fraida Fund (NYU Poly) [[BR]] |
| 207 | 15min |
| 208 | |
| 209 | Should we introduce OMF into GENI for config/orchestration of all I&M tools and experimenter's application services? [[BR]] |
| 210 | |
| 211 | What are advantages? [[BR]] |
| 212 | |
| 213 | What are current limitations that need to be fixed? [[BR]] |
| 214 | |
| 215 | Could we add a graphical interface? [[BR]] |
| 216 | |
168 | | == 4) Introduction of OMF to config/orchestrate I&M and experimenter's application services == |
169 | | 9:35am |
170 | | |
171 | | === Introduction === |
172 | | Harry Mussman (GPO) [[BR]] |
173 | | |
174 | | Step 5: Run/orchestrate I&M and experimenter's application services |
175 | | * Now: GEMINI uses portal to GUI, to config/orchestrate |
176 | | * Now: GIMI uses OMF EC with Ruby script to config/orchestrate |
177 | | * Gap: no common way to config/orchestrate exp apps |
178 | | |
179 | | * Next: Integrate orchestration of all services, including GIMI, GEMINI and experimenter's application services, to better unify experiment environment |
180 | | * Suggest: Introduce OMF for config/orchestration of all I&M tools and experimenter's application services; later, add optional graphical interface |
181 | | |
182 | | === Summary of OMF capabilities === |
183 | | Max Ott (NICTA) [[BR]] |
184 | | 10min |
185 | | |
186 | | [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/omf-gec16-mar-2013.pdf slides]: current config; current capabilities and issues; future possibilities [[BR]] |
187 | | |
188 | | === Roundtable discussion === |
189 | | Max Ott (NICTA); Marshall Brinn (GPO); Martin Swany (Indiana Univ); Fraida Fund (NYU Poly) [[BR]] |
190 | | 15min |
191 | | |
192 | | Should we introduce OMF into GENI for config/orchestration of all I&M tools and experimenter's application services? [[BR]] |
193 | | |
194 | | What are advantages? [[BR]] |
195 | | |
196 | | What are current limitations that need to be fixed? [[BR]] |
197 | | |
198 | | Could we add a graphical interface? [[BR]] |
199 | | |
200 | | [Any additional topics, suggestions and issues suggested by members of roundtable?] [[BR]] |
201 | | |
202 | | At the end: |
203 | | * List of conclusions |
204 | | * List of issues |
205 | | * Team to continue discussion |
206 | | |
207 | | |