[[PageOutline]] == GIMI v1.0 Architecture for GEC 14 Tutorial == This document gives an overview of the GIMI v1.0 architecture as it is planned to be in place for the tutorial at GEC 14. [[BR]] After review on 5/23/12. [[BR]] General [[BR]] The tutorial is limited to a maximum of 30 attendants. Two attendees will be working as a team during the tutorial. Like the DICloud tutorial, there will be several members of the GIMI team there to allow us to pay sufficient attention to each individual. To do: [[BR]] • Confirm that the GIMI tutorial will be preceded by an ORCA/ExoGENI tutorial. • What will be exact date and time of the ORCA/ExoGENI tutorial? (Mon, 7/9, ~10:30am) Of the GIMI tutorial? (Mon, 7/9, ~1pm) • We need 15 accounts. To make things easy we should have the same account and PW across all GIMI tools. Proposal: gimitut1-15, gec$14 • Prepare tutorial script, and put on GENI wiki • Consider ongoing support for tutorial, to provide a “GENI at home course”. Timetable Tutorial length: 1 1/2 hours [[BR]] Topic Duration iRODS Intro 15 minutes IREEL Intro 15 minutes Measurement Tutorial 60 minutes ExoGENI [[BR]] • For the tutorial users will be given a pre-defined ExoGENI topology. Some of these topologies (approximately 3-4) will be inter rack slices (two aggregates), the others will be intra rack slices (one aggregate). • We will give a short (approximately 30 minutes) introduction on how resources can be obtained with either Flukes or Omni. This will be canceled if an ExoGENI tutorial precedes our tutorial at GEC14. • Due to time limit we will use per-configured ExoGENI machine images. Users will have to learn otherwise how to generate and configure images. • The pre-configured images will include (5/25): o OML 2.7.0 o OMF 2.7.0 o OML-ified Iperf o iRODS 3.1 client o web server (small apache) o r (for visualization) o also EC? To do: [[BR]] • Review GEC 13 ExoGENI tutorial slides. • Coordinate with GEC14 ExoGENI tutorial. • Create accounts that can be used to access ExoGENI resources (6/15) • Pre-configure 15 ExoGENI slices on aggregates (define rspecs) (6/15) OMF/OML [[BR]] • Run OML server on one of the ExoGENI nodes (5/25). • Use OML-ified Iperf for throughput measurements between ExoGENI nodes (5/25) • Use nmetrics to monitor condition of single node (5/25) • OMF EC to execute measurement (5/25) • Collect data on MC (5/25) To do: [[BR]] • How to bring up desired services on selected nodes? (6/1) • Decide on what XMPP server to use. NICTA, Rutgers, UMass? (5/25) • Decide how to load info into XMPP server. (6/1) • Provide for visualization on MC (6/1) How? iRODS [[BR]] • Persistent iRODS servers are already setup at UMass and RENCI (with RENCI running iCAT). • Measurement data collected at MC will be transferred to iRODS (6/1). • Users will be able to use IREEL to analyze and present data stored in iRODS (6/15). To Do: [[BR]] • Create iRODS accounts for tutorial users (6/1) • We should give a short (approximately 30 minutes) iRODS intro during the tutorial. MZ: Still possible with in 90 minutes time slot? IREEL [[BR]] • Use IREEL as measurement portal (6/1) • Persistent portal will be set up at UMass Amherst (6/15) To Do: [[BR]] • Implement Flukes/Omni interface (TBD) MZ: Do we want to do this for tutorial? • Implement iRODS interface (6/15) • Can GENI credential mechanism be used? – Most likely not for tutorial! VirtualBox [[BR]] • It would be great if we could have an independent (of other tutorials) VirtualBox image; on 5/23, it appears that only GIMI and GEMINI require VirtualBox, so perhaps have one image for both. • VirtualBox image for testing (6/1, Jeanne) • Required SW: o Flukes o Omni o iRODS client o Web browser o EC To Do: [[BR]] • Is there a way to pre-install all required credentials? • What Java version does Flukes require? Applications [[BR]] • Time-series radar data: measure throughput of time-series data? • Video: measure jitter of video data? • TCP/UDP experiment from IREEL, Guillaume? • Multi-path TCP? • Energy consumption? To Do: [[BR]] • Pick a good application, or “reference experiment” (6/1) • Prepare a reference use case (6/1)