wiki:GEC15Agenda/IMDesignTopics

Version 5 (modified by hmussman@bbn.com, 12 years ago) (diff)

--

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.

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

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

Summary

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?

T5) Digital Objects, Identifiers and Descriptors

9:05am

Giridhar Manepalli (CNRI)

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

9:25am

Ezra Kissel (IU)

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:

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

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

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

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

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?

Attachments (3)

Download all attachments as: .zip