[[PageOutline]] = Instrumentation and Measurement (I&M) Design Topics at GEC14 = Monday, July 9, 8am - 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]] Since the I&M projects continuing from Solicitation 2 are ending, it will focus on the two large Solicitation 3 I&M D&P projects, GIMI and GEMINI, starting with a review their design and status. [[BR]] Next, we will review the current status of three ongoing I&M design topics, and five operational I&M services that are being introduced by the GIMI and GEMINI projects. [[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 == == Agenda == This is a tentative agenda, which may change. [[BR]] == 1) Introductions == 8:00am [[BR]] == 2) Goals for this meeting == 8:05am [[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 three ongoing 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 and status == 8:10am [[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]] * Current architecture, design and status. [[BR]] * Plan for GEC-14 tutorial [[BR]] * 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 and plans == 8:25am [[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]] * Current architecture, design and status. [[BR]] * Plan for GEC-14 tutorial [[BR]] * 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 == 8:40m [[BR]] === T4) GENI I&M Tool Testing Environment === 8:40am [[BR]] Harry Mussman (GPO) [[BR]] Goals [[BR]] * Define a step-by-step process for the GEMINI and GIMI tools sets over Spirals 4, 5 and 6 such that: [[BR]] * They deliver useful tools in each spiral [[BR]] * They eventually provide tools that can be included in slices built with any type of GENI hosts [[BR]] * GENI hosts should include those provided by ExoGENI and InstaGENI racks, as soon as they are available [[BR]] * Include: [[BR]] * User tools for experiment and measurement setup and orchestration [[BR]] * Interfaces/protocols between user tools and GENI aggregates [[BR]] * Supported GENI aggregates [[BR]] [[Image(Visio-070512_UseCases_Projects_Figures_Page_01.jpg, 110%)]] [[BR]] * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.4GENIEnvironment status at GEC13] [[BR]] Goals for Spiral 4: * By the end of Spiral 4, GIMI tools will test/operate in slices built in ORCA/ExoGENI environment [[BR]] * By the end of Spiral 4, GEMINI tools will test/operate in slices built in Emulab/protoGENI/InstaGENI environment [[BR]] * As much as possible, the two groups will use common user tools and common interfaces/protocols/APIs [[BR]] * As much as possible, the two groups will avoid arrangements customized to one environment [[BR]] * Both groups will be ready to provide tutorials on their capabilities starting at GEC-14. [[BR]] * Not yet defined: support for PlanetLab/InstaGENI environment [[BR]] [[Image(Visio-070512_UseCases_Projects_Figures_Page_02.jpg, 110%)]] [[BR]] Goals for Spiral 5: * By the end of Spiral 5, GIMI tools will test/operate in slices built in both the Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments (but not together in one slice) [[BR]] * By the end of Spiral 5, GIMI tools will also support measurements at WiMAX sites. [[BR]] * By the end of Spiral 5, GEMINI tools will test/operate in slices built in both the Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments (but not together in one slice) [[BR]] * Not yet defined: support for PlanetLab/InstaGENI environment [[BR]] [[Image(Visio-070512_UseCases_Projects_Figures_Page_03.jpg, 110%)]] [[BR]] Goals for later: [[BR]] * Both GEMINI and GIMI tools will test/operate in slices built with both Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments. However, this requires stitching functions that are not currently available. [[BR]] === T8) GENI User Tools and Services === 8:45am [[BR]] Jeanne Ohren (GPO)[[BR]] Goals [[BR]] * Work towards Max Ott's vision for experiment support [[BR]] * Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user. Those user services with a GUI (web) interface are often called "portal services".[[BR]] * Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present their measurement data. [[BR]] * These services should work together via APIs, etc., to streamline the experiment process. [[BR]] Tasks [[BR]] * Based upon the configuration defined below, the implementation is split into: [[BR]] 1) A GENI User Workspace, which is a persistent Linux OS environment dedicated to the user, that serves as a container for multiple user tools [[BR]] 2) Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]] * Define, prototype, deploy and operate a GENI User Workspace. [[BR]] * Gather the various "user tools" that have been implemented to date, and fit them into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]] * So that the GENI User Workspacet can be hosted on a server dedicated to the user (even the user's laptop), provide on a Virtual Box "portable VM". [[BR]] * Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials. [[BR]] Summary [[BR]] * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.8PortalService status at GEC13] [[BR]] * Current configuration (Spiral 4) [[BR]] * Next configuration (Spiral 5) [[BR]] Discussion [[BR]] * Should the GENI User Workspace be supported on a server hosting multiple user workspaces for multiple users? [[BR]] * Which tools should be added to the GENI User Workspace? [[BR]] * How can we best optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators). [[BR]] === T5) Descriptors, Objects and Registries === 8:50am [[BR]] Harry Mussman (GPO) [[BR]] [[BR]] Summary [[BR]] * Current v0.2 design [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD references] [[BR]] * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService status at GEC13] [[BR]] * v0.2 design reviewed at GEC13 Summary of current status (Giridhar Manepalli): [[BR]] [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx slides] [[BR]] Conclusions: [[BR]] Good things: [[BR]] Excellent start [[BR]] Collaborative Specification [[BR]] Great Coverage [[BR]] Nicely broken down into elements [[BR]] Mandatory vs. optional elements identified [[BR]] Genuine Use Cases: Gathering, transferring, and sharing [[BR]] Jensen's proposal (NetKarma): [[BR]] Current: Identifiers, Descriptors, Holders [[BR]] Proposed: Identification, Lineage/Provenance, Constraints/Security, MDO Description [[BR]] Zurawski's comments: [[BR]] Too many secondary identifiers [[BR]] Descriptors should be contextualized [[BR]] Variations based on the type of object [[BR]] GENI specific descriptions should be clearly marked and separated [[BR]] Slight changes to names & enclosing elements recommended [[BR]] Comments/suggestions based on metadata practices: [[BR]] Too many optional elements [[BR]] Too many choices given to users [[BR]] Users bound to take the path of least resistance [[BR]] Keep the scope restricted to only mandatory elements – at least in the beginning [[BR]] Try those out. Implement them. [[BR]] One size fits all ---- No! [[BR]] Capturing descriptions, formats, policies, transactions, etc. in a monolithic fashion [[BR]] Register individual components separately [[BR]] E.g., Capture legal formats & interpretations in their own records, and reference them here [[BR]] E.g., Same with accepted policies [[BR]] Identifiers cannot be semantic [[BR]] Domain, sub-domain, and object-type are part of an ID [[BR]] World view changes frequently [[BR]] Non-semantic Ids are worth every penny [[BR]] Search engines & registries mask the opaqueness [[BR]] After all, IDs are just entities behind the scenes [[BR]] Object Type controlled vocabulary enumerates apples and oranges [[BR]] Collection, flow, directory, file, database, gui are not mutually exclusive [[BR]] Doesn’t help the recipient make any decision looking at the descriptor [[BR]] Bundle type & format into format interpretation method [[BR]] Covers too many corner cases, e.g., flow-rate [[BR]] Expects too many details, e.g., locator (type, access method, etc.) [[BR]] Tasks [[BR]] * Need to DRAFT simplified v0.4 MDOD schema, for XML file; then review and finalize. (who can help?) [[BR]] * Optional: extend MDOD to cover all types of objects, i.e., software images. [[BR]] * Optional: extend MDOD schema to define Event Record schema. [[BR]] * Do we need MDOD registry? Include in iRODS? [[BR]] * Need MDOD creation and editing service. [[BR]] * Need Measurement Data Object identifiers (names); sometimes need a persistent, public reference; consider DataCite approach, which uses handle [[BR]] Discussion * Who will help DRAFT simplified v0.2 MDOD schema, for XML file? Shall we have a breakout meeting on Wed, 7/11? [[BR]] * Who will implement MDOD creation and editing service? [[BR]] * How will MDOD be included in iRODS? [[BR]] == 6) Reports on persistent multi-user I&M services, being introduced by GIMI and GEMINI projects == 9:00am [[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 === 9:00am [[BR]] Anirban Mandal (RENCI) [[BR]] Tasks [[BR]] * Define, prototype, demonstrate and operate a GENI XML Messaging service, starting at GEC13. [[BR]] * Support use in GENI by many tools, starting with GIMI I&M tools, who will use it to exchange OMF messages. [[BR]] * Define operations plan for XML Messaging service. [[BR]] Summary [[BR]] * [wiki:InstMeasTopic_4.6MessagingService work in progress] [[BR]] * An XMPP server is operational at Rutgers WINLAB (and other GENI wireless sites) for OMF messages. [[BR]] * An XML messaging service has been prototyped by the IMF project. [ slides] [[BR]] * An XMPP server has been setup at UMass Amherst. [[BR]] * Current configuration [ slides] [[BR]] * Proposed configuration [ slides] [[BR]] * Operations plan [ slides] [[BR]] Discussion [[BR]] * Who is lead? [[BR]] * Where will XMPP servers be located? will they be fully federated? [[BR]] * How do we set "topics" in XMPP servers to support OMF messages? [[BR]] * Will these XMPP servers provide a generalized GENI XML messaging service? If so, what functions will be included? * What authorization mechanisms will be required? [[BR]] * Will the GEMINI project want to use the XML messaging service? [[BR]] * Will other parts of GENI (e.g., monitoring) want to use the XML messaging service? [[BR]] * Do we need a breakout session for further discussion? when? [[BR]] === S2) iRODS Service === 9:10am [[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 Work in Progress] [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides] [[BR]] * iRODS service has been established at RENCI [[BR]] * iRODS service has been established at Univ of Kentucky [[BR]] * Current configuration [ slides] [[BR]] * Proposed configuration [ slides] [[BR]] * Operations plan [ slides] [[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) IREEL Portal Service === 9:20am [[BR]] Christoph Dwertmann (NICTA) and Cong Wang (UMass Amherst) [[BR]] Tasks * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project [[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) INSTOOLS portal-to-GUIs Service === 9:30am [[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 * 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]] * 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:40am [[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 Work in Progress] [[BR]] * Current configuration [ slides] [[BR]] * Proposed configuration [ slides] [[BR]] * Operations plan [ slides] [[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:50am [[BR]] Harry Mussman (GPO) [[BR]] Goals * Both GIMI and GEMINI tools should be available to Users during this period [[BR]] * Acceptance testing by the GPO (Jeanne Ohren) [[BR]] * Bug tracking system, plus periodic bug fixes (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]]