[[PageOutline]] = Service Developers Roundtable at GEC16 = Tuesday, March 19, 8:30am - 10am [[BR]] Room: City Creek [[BR]] Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]] == Description == This session will focus on the evolution of tools and services to allow GENI to work towards a "unified experiment environment". [[BR]] The discussion topics are: * Future of graphical resource assignment tools * Integration of portals and all tools with graphical interfaces * Introduction of the OMF to configure and orchestrate Instrumentation and Measurement (I&M) services and the experimenter's application services In each case, we will start with a review of current tools and services, and then have a round-table discussion of possible next steps towards a “unified experiment environment”. [[BR]] It is hoped that the discussions at this session may inspire proposals that will be submitted to GENI Solicitation 4. Finally, we will form teams to continue the discussions. [[BR]] == Pre-Requisites == None [[BR]] == Agenda == This is a tentative agenda, which may change. [[BR]] == 1) Introductions == 8:30am [[BR]] == 2) Future of graphical resource assignment tools == 8:35am [[BR]] === Introduction === Harry Mussman (GPO) [[BR]] GENI experiment management Step 3: Obtain slice, install software * Now: ExoGENI experimenter typically using Flukes to obtain slice, load images/pkgs * Now: InstaGENI experimneter typically using FLACK to obtain slice, load images/pkgs * Next: move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks === Current GENI CH Portal === Tom Mitchell (GPO) [[BR]] 5min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/TMitchell-GEC16-SDR%20%20graphical%20resources.pptx slides]: current config; current capabilities and issues; future possibilities Now: good introductory tool, for inexperienced experimenter === Current FLACK tool === Matt Strum and Rob Ricci (Univ Utah) [[BR]] 5min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/gec16-flack.pptx slides]: current config; current capabilities and issues; future possibilities New: other tools can include FLACK [[BR]] New: plug-in to add GEMINI tools [[BR]] New: better error handling [[BR]] Soon: AM API v3 [[BR]] === Current Flukes tool === Victor Orlikowski (Duke) [[BR]] 5min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/GEC16-ExoGENI-Flukes.pptx slides]: current config; current capabilities and issues; future possibilities Now: used with ExoGENI, with ndl [[BR]] New: extend duration of a slice [[BR]] New: save manifest and request into iRODS [[BR]] === Roundtable discussion === Tom Mitchell (GPO); Victor Orlikowski (Duke); Rob Ricci (or Matt Strum) (Univ Utah); Niky Riga (GPO) [[BR]] 15min [[BR]] How do we move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks? [[BR]] Conclusions: 1) FLACK works with InstaGENI, now using AM API 2) Need to test FLACK with ExoGENI using AM API; may have issue with accepting certificate 3) FLUKES has been designed for ORCA API, and would be difficult to adapt to AM API (for use with InstaGENI) 4) However, could use FLUKES to setup slice in ExoGENI rack using ORCA API, and then retrieve manifest rspec following AM API Issues: [[BR]] 5) Can draw a bigger topology than can be realized; not sure this can be fixed at drawing time, only after first submission of request; however, could consider "beginner's mode", which would limit drawing topology Team to continue discussion: Tom Mitchell (GPO); Victor Orlikowski (Duke); Ilia Baldine (RENCI); Rob Ricci and Matt Strum (Univ Utah); Niky Riga (GPO) == 3) Integration of portals and all tools with graphical interfaces == 9:05am [[BR]] === Introduction === Harry Mussman (GPO) [[BR]] GENI experiment management Step 2: Establish exper mgmt environment * Next: GENI CH Portal, to establish credentials, and enter GENI GENI experiment management Step 3: Obtain slice, install software * Now: ExoGENI typically using Flukes to obtain slice, load images/pkgs * Now: InstaGENI typically using FLACK to obtain slice, load images/pkgs * Next: move towards common graphical resource assignment tool for both ExoGENI and InstaGENI racks GENI experiment management Step 5: Run/orchestrate Instrumentation and Measurement (I&M) services and the experimenter's application services * Now: GEMINI I&M tools use portal to GUI, to config/orchestrate and present graphs * Now: GIMI I&M tools use portal to GUI, to config/orchestrate and present graphs GENI experiment management Step 6: Analyze * Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects) Next: Integration of portals and all tools with graphical interfaces, to better unify experiment environment [[BR]] === Current GENI CH Portal === Tom Mitchell (GPO) [[BR]] 5min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/TMitchell-GEC16-SDR%20%20portal.pptx slides]: current config; current capabilities and issues; future possibilities Now: have embedded FLACK === Current GEMINI Portal (GENI Desktop) === Hussam Nasir (Univ Kentucky) [[BR]] 5min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/Gemini%20Portal.pptx slides]: current config; current capabilities and issues; future possibilities Now: login using emulab or protoGENI account [[BR]] Now: provides access to your slice [[BR]] Now: auto login to FLACK to create slice [[BR]] Now: built as HTML5 web page with plug-ins [[BR]] === Current GIMI Portal/GUI === Mike Zink (UMass Amherst) [[BR]] 5min Current config; current capabilities and issues; future possibilities [http://emmy9.casa.umass.edu:5021/labwiki link to GIMI portal] [[BR]] Now: based on Lab wiki, with 3 windows for plan, script, results === Roundtable discussion === Tom Mitchell (GPO); Hussam Nasir (Univ Kentucky); Mike Zink (UMass Amherst); Jeanne Ohren (GPO) [[BR]] 15min [[BR]] How to we move towards integration of portals and all tools with graphical interfaces, to better unify experiment environment? [[BR]] Strawman: * Consider single sign-on at GENI CH portal, * link to common graphical resource assignment tool(s), ot obtain slice * then link to GEMINI Portal (GENI Desktop) for entry into I&M tools, * then link to I&M GUIs (including the GEMINI GUI, GIMI portal/GUI and the iRODS portal/GUI) Conclusions: 1) Be flexible in use of tools; don't kill innovation 2) Push towards single-sign-on 3) To make it easier to mix and match tools. pass info from tool to tool, using iRODS as a repository Issues: Team to continue discussion: Tom Mitchell (GPO); Hussam Nasir (Univ Kentucky); Mike Zink (UMass Amherst); Jeanne Ohren (GPO) [[BR]] == 4) Introduction of OMF to config/orchestrate I&M and experimenter's application services == 9:35am === Introduction === Harry Mussman (GPO) [[BR]] Step 5: Run/orchestrate I&M and experimenter's application services * Now: GEMINI uses portal to GUI, to config/orchestrate * Now: GIMI uses OMF EC with Ruby script to config/orchestrate * Gap: no common way to config/orchestrate exp apps * Next: Integrate orchestration of all services, including GIMI, GEMINI and experimenter's application services, to better unify experiment environment * Suggest: Introduce OMF for config/orchestration of all I&M tools and experimenter's application services; later, add optional graphical interface === Summary of OMF capabilities === Max Ott (NICTA) [[BR]] 10min [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/ServiceDevelopersRoundtable/omf-gec16-mar-2013.pdf slides]: current config; current capabilities and issues; future possibilities [[BR]] === Roundtable discussion === Max Ott (NICTA); Marshall Brinn (GPO); Martin Swany (Indiana Univ); Fraida Fund (NYU Poly) [[BR]] 15min Should we introduce OMF into GENI for config/orchestration of all I&M tools and experimenter's application services? [[BR]] What are advantages? [[BR]] What are current limitations that need to be fixed? [[BR]] Could we add a graphical interface? [[BR]] [Any additional topics, suggestions and issues suggested by members of roundtable?] [[BR]] At the end: * List of conclusions * List of issues * Team to continue discussion == 5) Adjourn == 10am