[[PageOutline]] = Service Developers Roundtable = Tuesday, March 19, 8:30am - 10am [[BR]] Room: [[BR]] Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]] == Description == This I&M session will focus on the key issues of interest to both the GIMI and GEMINI projects, as they continue to work towards a comprehensive set of I&M tools for GENI experimenters and for infrastructure measurement. In particular, we will consider the services and functions that can be used by both the GIMI and GEMINI projects.[[BR]] We will form teams that can resolve these issues. [[BR]] Finally, we will discuss the I&M goals for the next 4 months, particularly how to best support experimenters and those doing infrastructure measurement. [[BR]] == Pre-Requisites == None [[BR]] == Agenda == This is a tentative agenda, which may change. [[BR]] == 1) Introductions == 8:30am [[BR]] == 2) Topics for this meeting == === T9) GENI Storage and Archive Service (based on iRODS) === 8:35am [[BR]] Shu Huang (RENCI) [[BR]] Tasks * Design and deploy GENI Storage and Archive Service for use by all GENI services. * Provide functions similar to the Measurement Data Archive (MDA) service prototype, designed by CNRI. * Use to store all types of experiment artifacts (not just measurement data), and identify objects to be moved to a long-term archive. * Implement using the iRODS data grid service, by defining rules (interfaces) to provide the necessary GENI functions. [[BR]] Design goals and approach * [wiki:InstMeasTopic_4.9ArchiveService status at GEC13] [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides at GEC13] [[BR]] * iRODS service has been established at RENCI [[BR]] * iRODS service has been established at Univ of Kentucky [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx iRODS configuration at GEC14] [[BR]] * Proposed configuration? [[BR]] * Operations plan? [[BR]] Current implementation and next steps * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/iRODS%20GENI%20plan.docx iRODS GENI Plan] [[BR]] Open issues * Who is lead? [[BR]] * Will all iRODS services be federated, for redundancy? * How to move data to service: move file; move SQL DB; or? [[BR]] * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] * How are partitions for different users managed? [[BR]] * How is authorization for a user done? [[BR]] * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] * How will the GEMINI project use the iRODS service? [[BR]] * Will other parts of GENI want to use the iRODS service? [[BR]] * Do we need a breakout session for further discussion? when? [[BR]] Team * Shu Huang (RENCI), GIMI project, Lead * ? , GEMINI project * Giridhar Manepalli (CNRI) * Harry Mussman and Jeanne Ohren (GPO) === S5) Unified Network Information Service (UNIS) === 9:45am [[BR]] Ahmed El-Hassany (IU) [[BR]] Tasks [[BR]] * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set. Summary * [wiki:InstMeasTopic_4.7LookupService status at GEC13] [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf UNIS configuration at GEC14; proposed configuration] [[BR]] Discussion * Who is lead? [[BR]] * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] * What additional features are under consideration? [[BR]] * What new interfaces are under consideration? [[BR]] * Will the GIMI project want to use the UNIS service? [[BR]] * Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] * Do we need a breakout session for further discussion? when? [[BR]] == 2) Meeting Introduction == 8:35am [[BR]] Harry Mussman (GENI Project Office) [[BR]] Goals and Approach * Work towards a "unified experiment environment". * Help groups prepare responses to Sol 4 Current overall experiment configuration Summary of current experiment steps Possible next steps towards a “unified experiment environment”. Today’s discussion topics: * Common graphical resource assignment tool * Rationalization of all graphical portals, and all graphical tools * Introduction of OMF to configure/orchestrate I&M and ExpApp services == 3) Common graphical resource assignment tool == 8:45am [[BR]] === Overview === Harry Mussman S3: Obtain slice, install software Now: GIMI using ExoGENI, Flukes; loads images/pkgs Now: GEMINI using InstaGENI, FLACK; loads images/pkgs Next: move towards common graphical resource assignment tool for both ExoGENI and InstaGENI racks Suggest: discuss common graphical resource assignment tool, and relationship to portals, at Roundtable session * Current Flukes tool (Ilia Baldine) 5min 3 slides: current config; current capabilities and issues; future possibilities * Current FLACK tool (Rob Ricci) 5min 3 slides: current config; current capabilities and issues; future possibilities * Roundtable discussion 15min (Ilia Baldine); (Rob Ricci); (Tom Mitchell or Aaron Helsinger); Niky Riga [Any topics, suggestions and issues suggested AHEAD OF TIME by members of roundtable] [At the end: any conclusions, list of issues, team to continue discussion] == 4) Rationalization of all graphical portals, and all graphical tools == 9:10am [[BR]] * Overview Harry Mussman S2: Establish exper mgmt environment Next: GENI CH Portal, to establish credentials, and enter GENI S3: Obtain slice, install software Now: GIMI using ExoGENI, Flukes; loads images/pkgs Now: GEMINI using InstaGENI, FLACK; loads images/pkgs Next: move towards common graphical resource assignment tool for both ExoGENI and InstaGENI racks S5: Run/orchestrate I&M and exp app Now: GEMINI uses portal to GUI, to config/orchestrate Now: GEMINI uses portal to GUI, to configure and present graphs Now: GIMI uses portal incl GUI, to configure and present graphs S6: Analyze Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects) Next: Need to rationalize all graphical portals, and all graphical tools, to better unify experiment environment Suggest: Consider single sign-on at GENI CH portal, then link to GEMINI Portal (GENI Desktop) for entry into I&M tools, then link to I&M GUIs (including the GIMI portal/GUI and the iRODS portal/GUI); discuss at Rountable * Current GENI CH Portal (Tom Mitchell or Aaron Helsinger) 5min 3 slides: current config; current capabilities and issues; future possibilities * Current GEMINI Portal (GENI Desktop) (Charles Carpenter or Jim Griffioen) 5min 3 slides: current config; current capabilities and issues; future possibilities * Current GIMI Portal/GUI (Jeanne Ohren or Divya) 5min 3 slides: current config; current capabilities and issues; future possibilities * Roundtable discussion 15min (Tom Mitchell or Aaron Helsinger); (Charles Carpenter or Jim Griffioen); (Jeanne Ohren or Divya); Niky Riga [Any topics, suggestions and issues suggested AHEAD OF TIME by members of roundtable] [At the end: any conclusions, list of issues, team to continue discussion] == 5) Introduction of OMF to config/orchestrate I&M and ExpApp services == * Overview Harry Mussman S5: Run/orchestrate I&M and exp app 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: Need to rationalize orchestration of all services, including GIMI, GEMINI and Exp Apps, to better unify experiment environment Suggest: Introduce OMF for config/orchestration of all I&M tools and Exp Apps; later, add optional graphical interface; discuss at Roundtable * Summarize OMF capabilities Max Ott 5min 3 slides: current config; current capabilities and issues; future possibilities * Roundtable discussion 10min Max Ott; Marshall Brinn; Martin Swany; Fraida Fund [Any topics, suggestions and issues suggested AHEAD OF TIME by members of roundtable] [At the end: any conclusions, list of issues, team to continue discussion] == 4) Adjourn == 10:00am [[BR]] = I&M References = == GENI I&M Architecture and Tools: Goals, Overview and Status == * GIMI I&M tool set design [[BR]] * Based on OML, provides basic host and active network measurements [[BR]] * Ready for use on ExoGENI racks; successful tutorial [[BR]] * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service; use by others? iRODS by GEMINI [[BR]] * Spiral 5 goals: also work with InstaGENI racks, WiMAX sites [[BR]] * GEMINI I&M tool set design [[BR]] * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]] * Ready for use on InstaGENI/protoGENI racks ; successful tutorial [[BR]] * Introduces portal to GUIs service, UNIS unified ntwk info service; use by others? [[BR]] * Spiral 5 goals: also work with ExoGENI racks [[BR]] * Need simplified MDOD measurement data object descriptor schema [[BR]] * Also service for creation and editing of MDOD [[BR]] * Possible extensions to other GENI objects, events [[BR]] [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt slides] [[BR]]