[[PageOutline]] = Instrumentation and Measurement (I&M): GIMI and GEMINI Design Topics at GEC15 = Tuesday, October 23, 8:30am - 10am [[BR]] Room: [[BR]] Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]] == Description == This I&M session will review progress towards a comprehensive set of I&M tools for GENI experimenters and for infrastructure measurement. [[BR]] It will focus on the two large Solicitation 3 I&M D&P projects, GIMI and GEMINI, starting with a review their design goals for Spiral 5 and current status. [[BR]] Next, we will review the current status of outstanding I&M design topics, and the operational I&M services that are being introduced by the GIMI and GEMINI projects. We will consider how GIMI might be able to use the GEMINI services, and vice-versa. [[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]] == Summary == * 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]] == Agenda == This is a tentative agenda, which may change. [[BR]] == 1) Introductions == 8:30am [[BR]] == 2) Goals for this meeting == 8:35am [[BR]] Harry Mussman (GPO) [[BR]] Goals * Review the progress of the GIMI and GEMINI I&M projects towards providing a comprehensive set of I&M tools for GENI experimenters and for infrastructure measurement. [[BR]] * Review the current status of outstanding I&M design topics. [[BR]] * Review five persistent multi-user I&M services that are being introduced by the GIMI and GEMINI projects, to see which can be used by both projects and/or by other parts of GENI. [[BR]] * Discuss the I&M goals for the next 4 months, particularly how to best support experimenters and those doing infrastructure measurement. [[BR]] == 3) Summary of GIMI design goals for Spiral 5, and current status == 8:40am [[BR]] '''PI''' Michael Zink, University of Massachusetts at Amherst (mailto:zink@ecs.umass.edu) [[BR]] '''Co-PI''' Max Ott, NICTA (mailto:max.ott@nicta.com.au) [[BR]] '''Key personnel''' Ilia Baldine, RENCI (mailto:ibaldin@renci.org) [[BR]] [wiki:GIMI GIMI wiki] [[BR]] [http://gimi.ecs.umass.edu/ GIMI website at UMass Amherst] [[BR]] Goals [[BR]] * Starts with OML, and provides easy-to-use tools for GENI environment [[BR]] * First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf [[BR]] * Second focus: I&M use cases for infrastructure measurement [[BR]] * Later focus: add sensor measurement data, carried in data network [[BR]] * Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] * Later, support: WiMAX sites [[BR]] * Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] * Introduces XML messaging service, with pub/sub, in public IP space [[BR]] * Introduces iRODS service, as a measurement data archive. [[BR]] * Introduces IREEL portal service, for measurement data analysys and presentation. [[BR]] Summary: [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GIMI%20GEC%2014%20I%26M%20Session.pptx GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial GIMI v1.0 tutorial] [[BR]] == 4) Summary of GEMINI design goals for Spiral 5, and current status == 8:50am [[BR]] '''PI''' Martin Swany, Indiana University (mailto:swany@iu.edu) [[BR]] '''Co-PI''' Chris Small, Indiana University (mailto:chsmall@indiana.edu) [[BR]] '''Co-PI''' James Griffioen, University of Kentucky (mailto:griff@netlab.uky.edu) [[BR]] '''Co-PI''' Zongming Fei, University of Kentucky (mailto:fei@netlab.uky.edu) [[BR]] [wiki:GEMINI GEMINI wiki] [[BR]] Goals [[BR]] * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] * First focus: I&M use cases for infrastructure measurement [[BR]] * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] * Show how to monitor clusters/racks [[BR]] * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] * Second focus: I&M use cases for experiments [[BR]] * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] * Show how to gather customized data from applications (as provided by OML Client) [[BR]] * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] * Continues INSTOOLS portal service, to find GUIs [[BR]] * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] Summary [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Overview%20and%20Direction-GEC14.pptx GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial GEMINI v1.0 tutorial] [[BR]] == 5) Reports on I&M design topics == 9:00am [[BR]] === T5) Descriptors, Objects and Registries === 9:00am [[BR]] Harry Mussman (GPO) and Giridhar Manepalli (CNRI) [[BR]] [[BR]] == 6) Reports on persistent multi-user I&M services, being introduced by GIMI and GEMINI projects == 9:15am [[BR]] Goals [[BR]] * Use by both GIMI and GEMINI tools sets [[BR]] * Use by other parts of GENI [[BR]] * Identify need for further reviews and discussions, in breakout meetings on Wed, 7/11 [[BR]] === S1) XML Messaging Service === === S2) iRODS Service === 9:15am [[BR]] Shu Huang (RENCI) [[BR]] Tasks * Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions. [[BR]] Summary * [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]] Discussion * 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]] === S3) GIMI Portal Service === 9:30am [[BR]] Max Ott and Christoph Dwertmann (NICTA); Mike Zink and Cong Wang (UMass Amherst) [[BR]] Tasks * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project [[BR]] * Extend/change to become Lab wiki service [[BR]] Summary * IREEL service has been established at NICTA [[BR]] * IREEL service has been established at UMassAmherst [[BR]] * Current configuration [ slides] [[BR]] * Proposed configuration [ slides] [[BR]] * Operations plan [ slides] [[BR]] Discussion * Who is lead? [[BR]] * How are partitions for different users managed? [[BR]] * How is authorization for a user done? [[BR]] * Can IREEL be used to provide other functions, e.g., experiment meangement? if so, how? [[BR]] * Will the GEMINI project want to use the IREEL service? [[BR]] * Will other parts of GENI want to use the IREEL service? [[BR]] * Do we need a breakout session for further discussion? when? [[BR]] === S4) GEMINI portal-to-GUIs Service === 9:40am [[BR]] Charles Carpenter (U Kentucky) [[BR]] Tasks: * Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]] Summary * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Portal.ppt current GEMINI portal service configuration] [[BR]] Discussion * Who is lead? [[BR]] * How are partitions for different users managed? [[BR]] * How is authorization for a user done? [[BR]] * What additional features are under consideration? [[BR]] * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] * Do we need a breakout session for further discussion? when? [[BR]] === S5) UNIS Service === 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]] == 7) Goals for the next 4 months == 9:55am [[BR]] Harry Mussman (GPO) [[BR]] Goals * Both GIMI and GEMINI tools should be available to Users during this period [[BR]] * Acceptance testing continued by the GPO (Jeanne Ohren) [[BR]] * Bug tracking system, plus periodic bug fixes, continued (who are leads?) [[BR]] * How can we facilitate feedback from Users, after EVERY use? [[BR]] * Both GIMI and GEMINI must provide a high level of support to Users [[BR]] * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?) [[BR]] * Instructions must be continuously refined, to make the tools easier to use. (who are leads?) [[BR]] * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?) [[BR]] * Users with advanced requirements must be found, better identify gaps in the tools. How? (who are leads?) [[BR]] * Tool extensions must be proposed by the teams, and reviewed with the users. How? (who are leads?) [[BR]] * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?) [[BR]] * Persistent multi-user services must be reliably available to all Users [[BR]] * User Worksapce (Jeanne Ohren) [[BR]] * XML messaging service (who is lead?) [[BR]] * iRODS archive service (who is lead?) [[BR]] * IREEL analysis and presentation service (who is lead?) [[BR]] * INSTOOLS portal-to-GUIs service (who is lead?) [[BR]] * Unified Network Information Service (UNIS) (who is lead?) [[BR]] Discussion * Do we have leads identified for all items? [[BR]] == 8) Adjourn == 10:00am [[BR]]