[[PageOutline]] = I&M Design Topics at GEC16 = Tuesday, March 19, 10:30am - 12noon [[BR]] Room: City Creek [[BR]] Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]] == Description == This I&M session will focus on three 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. [[BR]] We will first review the overall goal to move towards a "unified experiment environment". [[BR]] Then, we will discuss these topics: * Support for GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks * Use of an instrumentize script, driven by rspec extension, to configure/init all I&M tools * Options for further measurement data analysis and presentation For each topic, we will have a review of current practice, and a discussion of how to move forward. [[BR]] Finally, we will form teams for continued discussion. [[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) Towards a Unified Experiment Environemnt == 8:35am [[BR]] Marshall Brinn (GPO) [[BR]] 10min What does it mean to move towards a "unified experiment environment"? [[BR]] == 3) Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks == 8:45am === Introduction === Harry Mussman (GPO) [[BR]] GENI experiment management Step 3: Obtain slice, install software * Now: GIMI loaded (and tested) on ExoGENI * Now: GEMINI loaded (and tested) on InstaGENI, FLACK * Next: be able to use GEMINI on ExoGENI, and GIMI on InstaGENI * Suggest: set goal to begin testing all combinations starting 5/1; good support by GEC17 === Lessons learned from using GIMI tools on ExoGENI racks === Cong Wang (UMass Amherst) [[BR]] 5min 3 slides: current config; key techniques; known challenges [[BR]] === Lessons learned from using GEMINI tools on InstaGENI racks === Hussam Nasir (Univ Kentucky) [[BR]] 5min 3 slides: current config; key techniques; known challenges [[BR]] === Discussion === Cong Wang (Umass Amherst; Hussam Nasir (Univ Kentucky); (Ilia Baldine) (RENCI); (Rob Ricci); Louisa Nevers (GPO); Jeanne Ohren (GPO) [[BR]] 15min How do we move towards using GEMINI on ExoGENI, and GIMI on InstaGENI? [[BR]] Discuss: * Suggested approaches * Key techniques * Likely challenges * Goal to begin testing all combinations starting 5/1; good support by GEC17; are there any roadblocks? Any topics, suggestions and issues suggested by members of roundtable? At the end: * List of conclusions * List of issues * Team to continue discussion == 4) Use of instrumentize script, driven by rspec extension, to configure/initialize I&M tools == 9:10am === Overview === Harry Mussman (GPO) [[BR]] GENI experiment management Step 4: Configure/init I&M and exp app * Now: GIMI using post boot scripts, OMF * Now: GEMINI using instrumentize script, choices based on rspec extension; also used to add GN * Next: move towards common approach, to better unify experiment environment * Suggest: both move towards script, driven by rspec ext; discuss at I&M session === Current GIMI use of post boot scripts, OMF, to configure/inti services === Cong Wang (UMass Amherst) [[BR]] 5min 3 slides: key techniques; known challenges [[BR]] === Current GEMINI use of instrumentize script, to configure/init services === Hussam Nasir (Univ Kentucky) [[BR]] 5min 3 slides: key techniques; known challenges [[BR]] === Discussion === Cong Wang (Umass Amherst) ; Hussam Nasir (Univ Kentucky); Marshall Brinn (GPO); Jeanne Ohren (GPO) [[BR]] 15min [[BR]] How do we move towards a common approach to configure and initialize I&M tools, to better unify experiment environment? [[BR]] Strawman: * move towards instrumentize script, driven by rspec ext * or is there a better solution? [Any topics, suggestions and issues suggested by members of roundtable] At the end: * List of conclusions * List of issues * Team to continue discussion == 5) Options for further measurement data analysis and presentation == 9:35am === Introduction === Harry Mussman (GPO) [[BR]] GENI experiment management Step 6: Analyze * Now: Both GEMINI and GIMI push measurement data objects (files) to GENI Storage Service (iRODS) * Now: GEMINI provides dump of mongo DB, plus separate file of metadata * Now: GIMI (will) provide SQLdump of PostgreSQL DB, which includes metadata * Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects) Both: Pull measurement data files from GENI Storage Service (iRODS) back to user workspace, where DBs can be reconstituted, and data pulled for further analysis and presentation. [[BR]] Both: Many options for further analysis and presentation, not being developed as part of tools. [[BR]] Next: Consider possible ways to unify data formats, analysis and presentation; what commonly available tools might be useful? [[BR]] === Current GIMI measurement data object schema === Charles Glass (NICTA) [[BR]] 10min === Current GEMINI measurement data object schema === Ezra Kissel (Indiana Univ) [[BR]] 10min === Discussion === Charles Glass (NICTA); Ezra Kissel (Indiana Univ); Marshall Brinn (GPO); Fraida Fund (NYU Poly) [[BR]] 10min What are possible ways to unify data formats? [[BR]] How could we unify further analysis and presentation? [[BR]] What commonly available tools might be useful? [[BR]] [Any topics, suggestions and issues suggested by members of roundtable] At the end: * List of conclusions * List of issues * Team to continue discussion == 6) Adjourn == 12noon [[BR]] Please join us for I&M BoF dinner on Wednesday evening. Please indicate on this poll, if you will be attending