I&M Design Topics

Schedule

Tuesday, 10:30am - noon

Session Leaders

Harry Mussman. GENI Project Office

Agenda / Details

Pre-Requisites

Instrumentation and Measurement (I&M): GIMI and GEMINI Design Topics at GEC15

Tuesday, October 23, 8:30am - 10am
Room:
Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies)

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.

We will form teams that can resolve these issues.

Finally, we will discuss the I&M goals for the next 4 months, particularly how to best support experimenters and those doing infrastructure measurement.

Agenda

This is a tentative agenda, which may change.

1) Introductions

8:30am

2) Topics for this meeting

T9) GENI Storage and Archive Service (based on iRODS)

8:35am

Shu Huang (RENCI)

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.
  

Design goals and approach

• status at GEC13
  
• ​slides at GEC13
  
• iRODS service has been established at RENCI
  
• iRODS service has been established at Univ of Kentucky
  
• ​iRODS configuration at GEC14
  
• Proposed configuration?
  
• Operations plan?
  

Current implementation and next steps

• ​iRODS GENI Plan
  

Open issues

• Who is lead?
  
• Will all iRODS services be federated, for redundancy?
• How to move data to service: move file; move SQL DB; or?
  
• How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.
  
• How are partitions for different users managed?
  
• How is authorization for a user done?
  
• How is data in MDOD used to set archive sharing policy? what is required in MDOD?
  
• How will the GEMINI project use the iRODS service?
  
• Will other parts of GENI want to use the iRODS service?
  
• Do we need a breakout session for further discussion? when?
  

Team

• Shu Huang (RENCI), GIMI project, Lead
• ? , GEMINI project
• Giridhar Manepalli (CNRI)
• Harry Mussman and Jeanne Ohren (GPO)

a) Introductions 5min

b) Meeting Introduction Harry Mussman 5min

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, and possible next steps towards a “unified experiment environment”.

Today’s discussion topics:

Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks Use instrumentize script, driven by rspec extension, to configure/init I&M tools Options for further measurement data analysis and presentation

c) Support GIMI and GEMINI I&M tools on both ExoGENI and InstaGENI racks 25min

• 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: 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; discuss at I&M session

• Lessons learned from using GIMI tools on ExoGENI racks

Cong Wang 10min 4 slides: current config; current capabilities and issues; future possibilities

• Lessons learned from using GEMINI tools on InstaGENI racks

Hussam Nasir 10min 4 slides: current config; current capabilities and issues; future possibilities

• Discussion

15min Cong Wang; Hussam Nasir; (Ilia Baldine); (Rob Ricci); Louisa Nevers; Jeanne Ohren

[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]

d) Use instrumentize script, driven by rspec extension, to configure/init I&M tools

• Overview

Harry Mussman S4: 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 5min 2 slides: current config; current capabilities and issues; future possibilities

• Current GEMINI use of instrumentize script, to configure/init services

Hussam Nasir 5min 2 slides: current config; current capabilities and issues; future possibilities

• Discussion

10min Cong Wang; Hussam Nasir; Aaron Helsinger; Jeanne Ohren

[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]

e) Options for further measurement data analysis and presentation

• Overview

Harry Mussman S6: 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. Both: Many options for further analysis and presentation, not being developed as part of tools.

Next: Consider possible ways to unify data formats, analysis and presentation Suggest: Discuss what might be possible, and potential approaches at I&M session

• Current GIMI measurement data object schema

(Christoph Dwertmann) 10min

• Current GEMINI measurement data object schema

Ezra Kissel 10min

• Discussion

10min (Christoph Dwertmann); Ezra Kissel; Marshall Brinn; 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]

T5) Digital Objects, Identifiers and Descriptors

9:05am

Giridhar Manepalli (CNRI)

Tasks

• Define a comprehensive system for identifying and describing a wide range of digital objects, including all types of experiment artifacts (e.g., rspecs, scripts, measurement data).
• Show how to group objects into one combined object (e.g., all artifacts associated with one experiment), and then identify, describe adn archive this combined object

Design goals

Approach and next steps

• ​Archive, DOI (handle), Descriptors
  

Open issues

Team

• Giridhar Manepalli and Larry Lannom (CNRI)
• Harry Mussman and Jeanne Ohren (GPO)
• ?, GIMI project
• ?, GEMINI project

T10) I&M Service-to-Service Authentication and Authorization

9:25am

Ezra Kissel (IU)

Tasks

• Establish a approach for providing authentication and authorization between GENI I&M service when they are required.
• Note: One approach included in LAMP tools from IU
• Note: Most authentication and authorization work in GENI has been focused on resource assignment, between an experimenter's tolls and an aggregate manager

Design goals and approach

Current implementation and next steps

​GEMINI AA Workflow Configuration
​GEMINI AA Workflow Process
​Status
​AA Reference Configurations
​I&M A&A Considerations (slides)

Open issues

Team

• Ezra Kissel (IU), GEMINI project, Lead
• ?, GIMI project
• Harry Mussman and Jeanne Ohren (GPO)

3) Goals for the next 4 months

9:45am

Harry Mussman (GPO)

Goals

• Both GIMI and GEMINI tools should be available to Users during this period
  
  • Acceptance testing continued by the GPO (Jeanne Ohren)
    
  • Bug tracking system, plus periodic bug fixes, continued (who are leads?)
    
  • How can we facilitate feedback from Users, after EVERY use?
    

• Both GIMI and GEMINI must provide a high level of support to Users
  
  • Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?)
    
  • Instructions must be continuously refined, to make the tools easier to use. (who are leads?)
    
  • Requested tool extensions must be gathered from users, based upon their experience. (who are leads?)
    
  • Users with advanced requirements must be found, better identify gaps in the tools. How? (who are leads?)
    
  • Tool extensions must be proposed by the teams, and reviewed with the users. How? (who are leads?)
    
  • A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?)
    

• Persistent multi-user services must be reliably available to all Users
  
  • User Worksapce (Jeanne Ohren)
    
  • XML messaging service (who is lead?)
    
  • iRODS archive service (who is lead?)
    
  • IREEL analysis and presentation service (who is lead?)
    
  • INSTOOLS portal-to-GUIs service (who is lead?)
    
  • Unified Network Information Service (UNIS) (who is lead?)
    

Discussion

• Do we have leads identified for all items?
  

4) Adjourn

10:00am

I&M References

GENI I&M Architecture and Tools: Goals, Overview and Status

• GIMI I&M tool set design
  
  • Based on OML, provides basic host and active network measurements
    
  • Ready for use on ExoGENI racks; successful tutorial
    
  • Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service; use by others? iRODS by GEMINI
    
  • Spiral 5 goals: also work with InstaGENI racks, WiMAX sites
    

• GEMINI I&M tool set design
  
  • Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements
    
  • Ready for use on InstaGENI/protoGENI racks ; successful tutorial
    
  • Introduces portal to GUIs service, UNIS unified ntwk info service; use by others?
    
  • Spiral 5 goals: also work with ExoGENI racks
    

• Need simplified MDOD measurement data object descriptor schema
  
  • Also service for creation and editing of MDOD
    
  • Possible extensions to other GENI objects, events
    

​slides

GIMI I&M Tools: Goals, Overview and Status

PI Michael Zink, University of Massachusetts at Amherst (​mailto:zink@ecs.umass.edu)
Co-PI Max Ott, NICTA (​mailto:max.ott@nicta.com.au)
Key personnel Ilia Baldine, RENCI (mailto:ibaldin@renci.org)

GIMI wiki
​GIMI website at UMass Amherst

Goals

• Starts with OML, and provides easy-to-use tools for GENI environment
  

• 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
  
• Second focus: I&M use cases for infrastructure measurement
  
• Later focus: add sensor measurement data, carried in data network
  

• Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks
  
• Later, support: WiMAX sites
  
• Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks
  

• Introduces XML messaging service, with pub/sub, in public IP space
  
• Introduces iRODS service, as a measurement data archive.
  
• Introduces IREEL portal service, for measurement data analysys and presentation.
  

Summary:

• ​GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5
  
• For more information, attend or audit ​GIMI v1.0 tutorial
  

GEMINI I&M Tools: Goals, Overview and Status

PI Martin Swany, Indiana University (​mailto:swany@iu.edu)
Co-PI Chris Small, Indiana University (​mailto:chsmall@indiana.edu)
Co-PI James Griffioen, University of Kentucky (​mailto:griff@netlab.uky.edu)
Co-PI Zongming Fei, University of Kentucky (​mailto:fei@netlab.uky.edu)

GEMINI wiki

Goals

• Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements
  
• Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements
  
• Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools.
  

• First focus: I&M use cases for infrastructure measurement
  
• Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential
  
• Show how to monitor clusters/racks
  
• Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project)
  

• Second focus: I&M use cases for experiments
  
• Gather basic host measurements (as was done by INSTOOLS using SNMP)
  
• Show how to gather customized data from applications (as provided by OML Client)
  

• Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks
  
• Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks
  

• Continues INSTOOLS portal service, to find GUIs
  
• Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology
  

Summary

• ​GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5
  
• For more information, attend or audit ​GEMINI v1.0 tutorial
  

Persistent Multi-user I&M Services

Goals

• Use by both GIMI and GEMINI tools sets
  
• Use by other parts of GENI
  
• Identify need for further reviews and discussions
  

S1) GENI (XML) Messaging Service

S2) GENI Storage and Archive Service (based on iRODS)

9:15am

Shu Huang (RENCI)

Tasks

• Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions.
  

Summary

• status at GEC13
  
• ​slides at GEC13
  
• iRODS service has been established at RENCI
  
• iRODS service has been established at Univ of Kentucky
  
• ​iRODS configuration at GEC14
  
• Proposed configuration?
  
• Operations plan?
  

Discussion

• Who is lead?
  
• Will all iRODS services be federated, for redundancy?
• How to move data to service: move file; move SQL DB; or?
  
• How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.
  
• How are partitions for different users managed?
  
• How is authorization for a user done?
  
• How is data in MDOD used to set archive sharing policy? what is required in MDOD?
  
• How will the GEMINI project use the iRODS service?
  
• Will other parts of GENI want to use the iRODS service?
  
• Do we need a breakout session for further discussion? when?
  

S3) GIMI Portal Service

9:30am

Max Ott and Christoph Dwertmann (NICTA); Mike Zink and Cong Wang (UMass Amherst)

Tasks

• Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project
  
• Extend/change to become Lab wiki service
  

Summary

• IREEL service has been established at NICTA
  
• IREEL service has been established at UMassAmherst
  
• Current configuration [ slides]
  
• Proposed configuration [ slides]
  
• Operations plan [ slides]
  

Discussion

• Who is lead?
  
• How are partitions for different users managed?
  
• How is authorization for a user done?
  
• Can IREEL be used to provide other functions, e.g., experiment meangement? if so, how?
  
• Will the GEMINI project want to use the IREEL service?
  
• Will other parts of GENI want to use the IREEL service?
  
• Do we need a breakout session for further discussion? when?
  

S4) GEMINI Portal Service

9:40am

Charles Carpenter (U Kentucky)

Tasks:

• Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools
  

Summary

• ​current GEMINI portal service configuration
  

Discussion

• Who is lead?
  
• How are partitions for different users managed?
  
• How is authorization for a user done?
  
• What additional features are under consideration?
  
• Will the GIMI project want to use the INSTOOLS portal-to-GUIs service?
  
• Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service?
  
• Do we need a breakout session for further discussion? when?
  

S5) Unified Network Information Service (UNIS)

9:45am

Ahmed El-Hassany (IU)

Tasks

• Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set.

Summary

• status at GEC13
  
• ​UNIS configuration at GEC14; proposed configuration
  

Discussion

• Who is lead?
  
• Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances?
  
• What additional features are under consideration?
  
• What new interfaces are under consideration?
  
• Will the GIMI project want to use the UNIS service?
  
• Will other parts of GENI want to use the UNIS service, e.g., stitching?
  
• Do we need a breakout session for further discussion? when?