Instrumentation and Measurement (I&M) Working Session for GEC12

Wednesday, November 2, 2011, 8:30am - 12noon
Room:
Session Leader: Harry Mussman, (GPO, Raytheon BBN Technologies)

Description

This session will review the GENI I&M design and prototyping projects planned for Spiral 4 (this year), including the two large Solicitation 3 I&M D&P projects and those projects continuing from Solicitation 2. Then, it will define and discuss the priority topics that must be resolved between now and GEC13.

Summary

Agenda

This is a tentative agenda, which may change.

1) Introductions

8:30am

2) GENI I&M D&P Projects for Spiral 4

8:35am
Harry Mussman

Goals:
**Provide broad data gathering, analysis and archival capability that is sufficient for scientific mission, operations, and success of the infrastructure.

**Remove the burden on researcher to become a system and network measurement infrastructure expert so that researcher can better focus on the science in the experiments

**Follow defined I&M architecture
Approach:
** Two large I&M projects (GIMI and GEMINI) approved from Sol 3, which include groups that have provided OML, INSTOOLS and LAMP/perfSONAR tools

**SOWs for remaining Year 3 of Sol 2 I&M projects focused on key topics that need to be resolved

Architecture:

Figure 1 GENI I&M Services and Messages

Figure 2 I&M Services in Experiment Slice

Figure 3 I&M Services in Infrastructure Measurement Slice

2.1) New Sol 3 Projects

GIMI

PI: Mike Zink (UMass Amherst)
Co-PI/Key: Max Ott (NICTA); Ilia Baldine (RENCI); David Irwin (UMass Amherst); Thanasis Korakis (NYU Poly)

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
First supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks
First utilized experiment control tools: GUSH, with additions
First utilized interfaces: GENI AM API for resources; ns3 for topology; ssh; OMF for orchestration

How are OML Client and Exp App loaded into nodes?

*Requires XML messaging service, with pub/sub, in public IP space

*Introduces portal service, with: OML Server, for collection; Results Service, for presentation; measurement orchestration service using OMF; documentation service to create and edit MDOD. Can portal be shared with GEMINI project?

*Introduces iRODS service for user workspace and archive. Can GEMINI use iRODS? Can iRODS serve as registry for MDOD?

Begin effort: support for WiMAX sites
Consider: adding OML server with perfSONAR interface, for sharing data with GEMINI tools
Later: add sensor measurement data, carried in data network

*Second focus on I&M use cases for infrastructure measurement

GEMINI

PI: Martin Swany (Indiana U)
Co-PI/Key: Chris Small (Indiana U); Eric Boyd (Internet2); Jim Griffioen (U Kentucky); Zongming Fei (U Kentucky)
; Hussamuddin Nasir (U Kentucky)

Goals:

**Starts with INSTOOLS, which provide easy-to-use tools in GENI environment for experimenters
++Fold INSTOOLS features into LAMP to form GEMINI tools, and then discontinue INSTOOLS

Focus: I&M use cases for experiments
Supported aggregates: protoGENI servers
Utilized experiment control tools: FLACK, with additions
Utilized interfaces: protoGENI API for resources; ns3 for topology; ssh for image loading; vnc for server login;

Portal to find presentation services in each Measurement Collector; includes vnc for login to server

Can use Kentucky and CNRI archive services

**Starts with LAMP
First focus on providing easy-to-use tools in GENI environment for experimenters
Setup within an experimenters slice
Basic user node image contains suite of perfSONAR tools; provides perfSONAR data interface; application loaded last
Measurement Collector (MC) (taking MC name from INSTOOLS) image contains UNIS registry (lookup and toplogy) and Periscope portal services
MC uses protoGENI credential to pull data from perfSONAR data interface on each user node
MC and user nodes can be anywhere in GENI

Supported aggregates: protoGENI servers?
Utilized experiment control tools: ?
Utilized interfaces: protoGENI API for resources?; ns3 for topology?; ssh for image loading?;
Check report from Ali Sydney (Aug 19, 2011) on experience using LAMP to monitor OF slice.

Move to: ORCA aggregate/ExoGENIrack, and then ?
Move to: GUSH experiment control tools, with OMNI, or ?
Move to: GENI AM API for resources; GENI rspec v3; ssh for node configure; or ?

Continue to setup within resources assigned by slice mechanism, but modify request rspec to add I&M features before submitting; how to pass manifest to UNIS?; how to create and edit MDOD?

Extend with INSTOOLS features:
Consider how to load tools on top of basic image
Consider how to extend Periscope to include druple content management service
Consider how to add xserver to basic node image, to login from portal using vnc protocol
Continue separate portal service, which is really a gateway service, within a user workspace service
Consider how to add interface to archive service, e.g., iRODs

Consider how to gather customized data from applications (as provided by OML Client)

Second focus on I&M use cases for infrastructure measurement
*Continues to provide for infrastructure measurement, and for sharing of data
*Continues compatibility with perfSONAR services
*Continues home and global Lookup Services

Show how to setup slice that provides perfSONAR data interface, and registers it with globalLookupService
Show how to setup slice that includes Periscope service, and gathers data from perfSONAR data interface on another slice
Show how to use GENI credentials to authorize sharing of data at perfSONAR data interface; move to ABAC?

Show how to monitor clusters/racks
Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project)

2.2) Continuing Sol 2 Projects

LAMP/perfSONAR

PI: Martin Swany (Indiana U)
Co-PI/Key: Eric Boyd (Internet2); Jason Zurawski (Internet 2); Guilherme Fernandes (U Delaware); Ezra Kissel (U Delaware); Mathew Jaffee (U Delaware)

Goals:

**Demonstrate and/or help others to demonstrate “infrastructure measurement slices” in both protoGENI and ORCA environments, with the data available at the perfSONAR MP is registered with the operational Lookup Service.

*Provide operational home and global Lookup Services
*Creates and maps MDOD into metadata that is registered in Lookup Service

*Expand authorization at interface where data is shared; introduce use of GENI credentials

OnTimeMeasure

PI: Prasad Calyam (Ohio Supercomputer Center/OARnet)
Co-PI: Paul Schopis (OARnet)

Goals:

**Work with the LAMP project to understand the LAMP/perfSONAR tools, and demonstrate using them to implement “infrastructure measurement slices” in today’s GENI backbone and access networks.

*Assuming LAMP/perfSONAR tools, develop a plan to evaluate the performance of today’s GENI IP backbone and access networks, using persistent or temporary “infrastructure measurement slices”, and utilizing existing perSONAR nodes in I2 and/or other networks.

*Define a procedure for evaluating the performance of GENI’s backbone and access networks when carrying L2 VLANs; start with the existing IP measurement tools including in the LAMP/perfSONAR tools, but consider tools that are specialized for evaluating the performance of L2 networks.

*Define a procedure for evaluating the performance of GENI’s backbone and access networks when using OpenFlow (e.g., “Tango GENI”); consider how to monitor the performance of OF networks, and introducing new specialized tools.

NetKarma

PI: Beth Plale (Indiana U)
Co-PI/Key: Chris Small (Indiana U); Scott Jensen (Indiana U); Mehmet Aktas (Indiana U)

Goals:

**Participate in defining the schema for the “measurement data object descriptor”, and uses of “descriptors” in tracking provenance.

*Work with the GENI community to define extensions to the “descriptor” that would locate and describe objects beyond “measurement data objects” associated with an experiment, such as scripts, images, etc.

*Modify your tools to create, gather and forward “descriptors”, that could locate and describe all objects associated with an experiment; demonstrate how “descriptors” can be automatically created.

*Work with the GENI I&M community to define a modified “descriptor” that would provide a standardized GENI “resource event record”; these records could describe events such as assignments, faults or errors.

*Add modules to your tools to create, gather and forward “resource event records”, that when logged could fully describe the sequence of an experiment.
*Work towards fitting your provenance tools into the “experimenter’s portal”.

IMF

PI: Rudra Dutta (NCSU)
Co-PI/Key: George Rouskas (NCSU); Ilia Baldine (RENCI); Keren Bergman (Columbia U)

Goals:

**Prototype and operate a GENI XML messaging service, with pub/sub, based on an XMPP server and XCP-0060.

*Prototype and demonstrate a GENI I&M “measurement orchestration service”, based on the ORBIT Management Framework (OMF) software modules provided by NICTA, including the Experiment Controller (EC) and the Resource Controller (RC).

*Prototype and demonstrate using your pub/sub capability to transport and distribute standardized GENI “resource event records”, as defined by the NetKarma project.

DOR

PI: Larry Lannom (CNRI)
Co-PI/Key: Giridhar Manepalli (CNRI); Jim French (CNRI); Christophe Blanchi (CNRI)

Goals:

Continue to deploy a prototype Measurement Data Archive (MDA) service.

**Participate in the GENI I&M effort, particularly in the MDA specification effort that includes defining metadata model for archived entities, defining access-control layer, and integrating control framework authorization scheme with the MDA.

*Enforce metadata schema on archived objects, and enable access control rights as defined by the MDA specification.

*Evangelize and demonstrate how the MDA/DOR service can be used to archive published data.

2.3 GIMI Project Overview

8:45am
PI: Mike Zink (UMass Amherst)
Co-PI/Key: Max Ott (NICTA); Ilia Baldine (RENCI); David Irwin (UMass Amherst); Thanasis Korakis (NYU Poly)

Goals
Configuration
Issues to be resolved

 slides

Figure 1 GIMI Tools Configuration

Figure 2 WiMAX Site Tools Configuration

Figure 3 OMF/OML Services and Messages

2.4 GEMINI Project Overview

9:05am
PI: Martin Swany (Indiana U)
Co-PI/Key: Chris Small (Indiana U); Eric Boyd (Internet2); Jim Griffioen (U Kentucky); Zongming Fei (U Kentucky)
; Hussamuddin Nasir (U Kentucky)

Goals
Configuration
Issues to be resolved

 GEMINI overview slides, Martin Swany

 From INSTOOLS to GEMINI slides, Jim Griffioen

Figure 1 GEMINI Tools Configuration

Figure 2 INSTOOLS Services and Messages

Figure 3 perfSONAR Services and Messages

2.4 LAMP/perfSONAR Project Overview

9:25am
PI: Martin Swany (Indiana U)
Co-PI/Key: Eric Boyd (Internet2); Jason Zurawski (Internet 2); Guilherme Fernandes (U Delaware); Ezra Kissel (U Delaware); Mathew Jaffee (U Delaware)

Goals
Configuration
Issues to be resolved

(see GEMINI slides)

2.6 OnTimeMeasure Project Overview

9:30am
PI: Prasad Calyam (Ohio Supercomputer Center/OARnet)
Co-PI: Paul Schopis (OARnet)

Goals
Configuration
Issues to be resolved

 slides

2.7 NetKarma Project Overview

9:35am
PI: Beth Plale (Indiana U)
Co-PI/Key: Chris Small (Indiana U); Scott Jensen (Indiana U); Mehmet Aktas (Indiana U)

Goals
Configuration
Issues to be resolved

 slides, by Scott Jensen

2.8 IMF Project Overview

9:40am
PI: Rudra Dutta (NCSU)
Co-PI/Key: George Rouskas (NCSU); Ilia Baldine (RENCI); Keren Bergman (Columbia U)

Goals
Configuration
Issues to be resolved

Slides Download

2.9 DOR Project Overview

9:45am
PI: Larry Lannom (CNRI)
Co-PI/Key: Giridhar Manepalli (CNRI); Jim French (CNRI); Christophe Blanchi (CNRI)

Goals
Configuration
Issues to be resolved

 slides

2.10 Discussion: Use of IF-MAP and IF-MAP in GENI

9:50am PI: Deniz Gurken

MDOD can be stored in IF-MAP server, acting as a registry

 MDOD Implementation Using IF-MAP, slides
 Standards-based Registry Service for GENI, poster

3) Break

10:00am

4) GENI I&M Priority Topics

10:30am

Goals:

Resolve between now (GEC12) and GEC13.

Simplify where possible!

Approach:

Form teams for each topic.

4.1) Overview

10:35am

I&M Use Cases for Experiments

I&M Use Cases for Infrastructure Measurement

Platform Targets

Experiment and Measurement Orchestration Tools

Interfaces/Protocols? Between Tools and Services

Descriptor Schema and Registry Service

Object Names and Registry Service

XML Messaging Service

Lookup Service

Portal Service

User Workspace and Archive Services

Operational Services

Services Shared by GIMI and GEMINI

Support for Experimenters

Support for Operators

4.2) I&M Use Cases for Experiments, and Support for Experimenters

10:40am
I&M Use Cases for Experiments
Support for Experimenters

a) How do we work towards Max Ott's vision for experiment support?  slides

b) Nominal experiment use case:

1) Setup and run experiment using Experiment Control Tools, Experiment Orchestration Service and Lab Portal.
2) Setup and run measurements using services within slice, and persistent services. Option: get measurement data from persistent MP.
3) Gather MD, and observe during experiment; formulate MDOD.
4) Archive MD with MDOD.
5) Share archived MD with others, per policy included within MDOD.
6) Pull MD out of archive, to analyze and/or visualize.

c) What support must be provided for Experimenters? how?

d) Who: Max Ott (NICTA); Jim Griffioen (U Kentucky); Prasad Calyam (Ohio Super Center); Mike Zink (UMass Amherst)

4.3) I&M Use Cases for Infrastructure Measurement, and Support for Operators

10:50am
I&M Use Cases for Infrastructure Measurement
Support for Operators

a) Delineate what infrastructure monitoring is and is not covered by this approach.

1) Yes: monitoring of clusters/racks
2) Yes: passive measurements of transport switches, etc.
3) Yes: active measurements of IP networks, of Layer 2 and OpenFlow paths

b) Nominal infrastructure measurement process:

1) Setup persistent or on-demand infrastructure measurement slice.
2) Make passive measurements or make active measurements.
3) Gather MD, and observe as it is gathered; formulate MDOD.
4) Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared.
5) Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD.
6) Pull MD out of collector, analyze and visualize.
7) Archive MD with MDOD.
8) Share archived MD with others, per policy included within MDOD.
9) Pull MD out of archive, to analyze and/or visualize.

c) What support must be provided for Operator? how?

d) Who: Martin Swany (Indiana U); Eric Boyd (Internet2); Jason Zurawski (Internet2); Chris Small (Indiana U); Ilia Baldine, for ExoGENI racks (RENCI); ?, for InstaGENI racks (?)

4.4) GENI Environment

11:00am
Platform Targets
Experiment and Measurement Orchestration Tools
Interfaces/Protocols? Between Tools and Services

a) Platform targets:

1) protoGENI servers/VMs
2) ORCA servers/VMs
3) WiMAX sites
4) ExoGENI (RENCI) racks; like ORCA
5) TransCloud? (HP) racks; like protoGENI?
6) PlanetLab

b) Experiment and Measurement Orchestration tools:

1) FLACK
2) GUSH (with Omni)
3) SFACE + RAVEN

c) Interfaces/protocols between tools and services:

1) protoGENI API, with protoGENI RSpec v2, for resource assignment
2) GENI AM API, with protoGENI RSpec v2, for resource assignment
3) ns for topology
4) ssh for image loading
5) OMF messages for orchestration

d) Who: Martin Swany (IU); Jim Griffioen (U Kentucky); Ilia Baldine, for ExoGENI racks (RENCI); ?, for InstaGENI racks (?); David Irwin (UMass Amherst); Mike Zink (UMass Amherst); Christoph Dwertmann (NICTA); Tom Mitchell (GPO); Aaron Helsinger (GPO)

4.5) Descriptors, Objects and Registries, and Lookup Service

11:10am
Descriptor Schema and Registry Service
Object Names and Registry Service
Lookup Service

a) MDOD schema, for XML file.  References

b) MDOD registry. Use DOR registry? Include in iRODS? Consider IF-MAP server?

c) Object (e.g., I&M service) names.

d) Object registry, with names and public key.

e) Home and global Lookup Service, as defined by perfSONAR

f) Map MDOD into metadata that is registered

g) Can Lookup Service be used for finding portals?

h) Also Topology Service? following UNIS?

e) Who: Jason Zurawski (Internet2); Ezra Kissel (U Delaware); Eric Boyd (Internet2); Scott Jensen (Indiana U); Larry Lannom (CNRI); LEAD Giridhar Manepalli (CNRI); Deniz Gurken (UH); Aaron Helsinger (GPO)

4.6) Messaging Service

11:20am
XML Messaging Service

a) XMPP server, in public IP space. Consider AMQP server? Consider IF-MAP server?

b) Entities connect, and are authenticated.

c) An entity may start a pub/sub node.

d) When an entity subscribes, a message is sent to publisher requesting authorization.

e) Use for OMF messages.

f) Use for "event record messages".

g) Who: Rudra Dutta (NCSU); Shu Huang (RENCI); Chirstoph Dwertmann (NICTA); Martin Swany (IU); Prasad Calyam (OSC); Deniz Gurken (UH)

4.7) Lookup Service

11:25am
Lookup Service

Note: Merged into 4.5)

4.8) Portal Service

11:30am
Portal Service

a) Towards Max Ott's vision for experiment support

b) Consider INSTOOLS portal service

c) Define portal service for GIMI tools, with multiple functions.

d) How are partitions for different users managed?

e) Can these portal services be merged?

f) Are these portal services really a combination of gateway and user workspace services?

g) Who: Jim Griffioen or ? (U Kentucky); Christoph Dwertmann (NICTA); Jason Zurawski, for NetKarma (Internet2)

4.9) User Workspace and Archive Services

11:40am
User Workspace and Archive Services

a) Consider CNRI prototype user workspace and archive service

b) Consider U Kentucky archive service

c) Consider iRODS service

d) How to move data to service: move file; move SQL DB; or?

e) How are partitions for different users managed?

f) How is data in MDOD used to set archive sharing policy? what is required in MDOD?

g) Who: Giridhar Manepalli (CNRI); Shu Huang (RENCI) ; Larry Lannom (CNRI); Wesley Wu (U Kentucky)

4.10 Operational Services

11:50am
Persistent Operational Services
Services Shared by GIMI and GEMINI

a) What persistent operational services must be supported:

1) Descriptor registry. DOR? iRODS? IF-MAP?
2) Object registry. DOR?
3) XML messaging service
4) Home and global Lookup Services; also Topology Service? UNIS?
5) INSTOOLS portal service
6) GIMI portal service
7) U Kentucky archive service
8) CNRI prototype user workspace and archive service
9) iRODs archive service

b) What services can be shared by GIMI and GEMINI tools?

c) How do these relate to other GENI services/functions, including clearinghouse?

d) Who: Mike Zink (UMass Amherst); Martin Swany (Inidana U); Jim Griffioen (U Kentucky); Giridhar Manepalli (CNRI); Aaron Helsinger (GPO)

5) Adjourn

12noon

Background Reading

 I&M integration wiki
 GENI I&M Capabilities Catalog
 GENI I&M Architecture document

Attachments