Changes between Version 34 and Version 35 of GEC16Agenda/ServiceDevelopersRoundtable


Ignore:
Timestamp:
03/28/13 10:44:02 (11 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GEC16Agenda/ServiceDevelopersRoundtable

    v34 v35  
    787815min  [[BR]]
    7979 
    80 
    81 Conclusions on how do we move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks?  [[BR]]
     80How do we move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks?  [[BR]]
     81
     82Conclusions:
    8283
    83841)  FLACK works with InstaGENI, now using AM API
    … …  
    130131[http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/TMitchell-GEC16-SDR%20%20portal.pptx  slides]:  current config;  current capabilities and issues;  future possibilities
    131132
     133Now:  have embedded FLACK
     134
    132135=== Current GEMINI Portal (GENI Desktop) ===
    133136Hussam Nasir  (Univ Kentucky) [[BR]]
    … …  
    136139[http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/Gemini%20Portal.pptx   slides]:  current config;  current capabilities and issues;  future possibilities
    137140
     141Now:  login using emulab or protoGENI account [[BR]]
     142Now:  provides access to your slice [[BR]]
     143Now:  auto login to FLACK to create slice [[BR]]
     144Now:  built as HTML5 web page with plug-ins [[BR]]
     145
     146
     147
    138148=== Current GIMI Portal/GUI ===
    139149Mike Zink (UMass Amherst) [[BR]]
    … …  
    143153
    144154[http://emmy9.casa.umass.edu:5021/labwiki  link to GIMI portal]  [[BR]]
     155
     156Now:  based on Lab wiki, with 3 windows for plan, script, results
    145157
    146158=== Roundtable discussion ===
    … …  
    149161
    150162How to we move towards integration of portals and all tools with graphical interfaces, to better unify experiment environment?  [[BR]]
    151 
    152 What features are required?  desirable? [[BR]]
    153163
    154164Strawman:
    … …  
    158168 * then link to I&M GUIs (including the GEMINI GUI, GIMI portal/GUI and the iRODS portal/GUI)
    159169
     170Conclusions:
     171
     1721)  Be flexible in use of tools;  don't kill innovation
     173
     1742)  Push towards single-sign-on
     175
     1763)  To make it easier to mix and match tools. pass info from tool to tool, using iRODS as a repository
     177
     178Issues:
     179
     180Team to continue discussion:
     181
     182Tom 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  ==
     1869:35am
     187
     188=== Introduction ===
     189Harry Mussman (GPO)  [[BR]]
     190
     191Step 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 ===
     200Max Ott (NICTA) [[BR]]
     20110min
     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 ===
     206Max Ott (NICTA);  Marshall Brinn (GPO);  Martin Swany (Indiana Univ);  Fraida Fund (NYU Poly) [[BR]]
     20715min
     208
     209Should we introduce OMF into GENI for config/orchestration of all I&M tools and experimenter's application services? [[BR]]
     210
     211What are advantages?   [[BR]]
     212
     213What are current limitations that need to be fixed? [[BR]]
     214
     215Could we add a graphical interface? [[BR]]
     216
    160217[Any additional topics, suggestions and issues suggested by members of roundtable?] [[BR]]
    161218
    … …  
    166223
    167224
    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 
    208225
    209226== 5)  Adjourn ==