wiki:GEC13Agenda/InstrumentationAndMeasurement

Version 33 (modified by chaos@bbn.com, 8 years ago) (diff)

--

Instrumentation and Measurement (I&M) Working Session at the GEC-13

Tuesday, March 13, 10:00am - 12noon and 1:30pm - 3:00pm
Room:
Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies)

Description

This is the I&M working session that will review progress towards a comprehensive set of I&M tools for GENI experimenters and for infrastructure measurement.

It will start with reports from several of the design topic teams formed at the GEC-12 working session; these will include the contributions of the I&M projects continuing from Solicitation 2.

Then the two large Solicitation 3 I&M D&P projects, GIMI and GEMINI, will review their progress.

Finally, we will discuss how to support experimenters and infrastructure measurement.

Summary

Agenda

This is a tentative agenda, which may change.

1) Introductions

10:00am

2) Reports by I&M design topic teams

10:05am

At GEC12, nine I&M priority design topics were identified, and nine teams were assigned to understand and resolve these topics by GEC13.

See the list of topics, including a brief summary of each topic.

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

10:05am

Team

CO-LEAD Jim Griffioen (U Kentucky)
CO-LEAD Mike Zink (UMass Amherst)
Hussamuddin Nasir (U Kentucky)
David Irwin (UMass Amherst)
Max Ott (NICTA)
Prasad Calyam (Ohio Super Center)
Harry Mussman (GPO)

Tasks

Provide a concise but complete definition of I&M Use Cases for Experiments
Define use cases for a wide range of experiments: complex (by skilled experimenters) to simple (by novice experimenter, i.e., a student)
Identify the support that should be available to experimenters, i.e., on-line instructions, examples and help desks.
Update the GENI I&M Architecture document:

Sec. 3.1. I&M Use cases for Experimenters
Sec. 4.2.1 Typical Arrangements of I&M Services: For Experimenter Gathering MD from their Slice
Sec. 4.3.1 Type 1 I&M Service: Service Contained within a Slice

Use as guidance in the design of GENI I&M tools, particularly for the GEMINI and GIMI projects

Work in Progress

Summary of current status

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

10:20am

Team

LEAD Martin Swany (Indiana U)
Guilherme Fernandes (?)
Eric Boyd (Internet2)
Jason Zurawski (Internet2)
Prasad Calyam (Ohio Super Center)
Chris Small, for NetKarma (Indiana U)
Ilia Baldine, for ExoGENI racks (RENCI)
Jonathan Mills (RENCI)
?, for InstaGENI racks (HP)
?, for GMOC
Sarah Edwards (GPO)
Chaos Golubitsky (GPO)
Harry Mussman (GPO)

Tasks

Provide a concise but complete definition of I&M Use Cases for Infrastructure Measurement
Identify the support that should be available to operators
Update the GENI I&M Architecture document:

Sec. 3.3. I&M Use cases for Central Operators (i.e., GMOC)
Sec. 3.4. I&M Use cases for Aggregate Providers and Operators
Sec. 4.2.2 Typical Arrangements of I&M Services: For Operator Gathering MD from GENI Infrastructure
Sec. 4.2.3 Typical Arrangements of I&M Services: For Experimenters Gathering MD from their Slice and from GENI Infrastructure
Sec. 4.3.3 Type 3 I&M Service: Common Service with MD for Multiple Slices

Use as guidance in the design of GENI I&M tools, particularly for the GEMINI and GIMI projects

Work in Progress

Summary of current status

T4) GENI I&M Tool Testing Environment

10:35am

Team

LEAD Harry Mussman (GPO)
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)
Vic Thomas (GPO)
Jeanne Ohren (GPO)
Luisa Nevers (GPO)

Tasks

Provide a concise definition of the environment where the GENI I&M tools will be tested, including:
User tools for experiment and measurement setup and orchestration
Interfaces/protocols between user tools and GENI aggregates
Supported GENI aggregtaes

Work in Progress

Summary of current status

T5) Descriptors, Objects and Registries

10:50am

Team

LEAD Giridhar Manepalli (CNRI)
Jason Zurawski (Internet2)
Ezra Kissel (U Delaware)
Eric Boyd (Internet2)
Beth Plale (IU)
Chris Small (GEMINI, IU)
Scott Jensen (Indiana U)
Larry Lannom (CNRI)
Deniz Gurken (GIMI, UH)
Harry Mussman (GPO)

Tasks

Need to finalize MDOD schema, for XML file. References
Want to extend MDOD to cover all types of objects, i.e., software images. (NetKarma)
Want to use MDOD schema to define Event Record schema. (NetKarma)
Do we need MDOD registry? Use UNIS lookup service? Use DOR registry? Include in iRODS? Consider IF-MAP server?
Need MDOD creation and editing service. (CNRI)
Need Measurement Data Object identifiers (names); sometimes need a persistent, public reference; consider DataCite approach, which uses handle

Work in Progress

Summary of current status

T6) XML Messaging Service

11:05am

Team

LEAD Anirban Mandal (RENCI)
Ilia Baldine (RENCI)
Rudra Dutta (NCSU)
Christoph Dwertmann (NICTA)
Ahmed El-Hassany (IU)
Harry Mussman (GPO)

Tasks

Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13.
The XML Mesaaging service will be built by the IMF project. For a detailed task list, see the Spiral 4 SOW of the IMF project.
Support use in GENI by many tools, including GEMINI and GIMI I&M tools
Define operations plan for XML Messaging service.

Work in Progress

Summary of current status - Slides

T7) Measurement Information (MI) Service

11:15am

Team

LEAD Ahmed El-Hassany (IU)
Martin Swany (IU)
Harry Mussman (GPO)

Tasks

The MI service will be built by the GEMINI project using UNIS technology; see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include:
1) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances:
2) Update topology model to Rspec version 3 and AM API (February 2012)
3) Modifications to allow local UNIS to register with global UNIS (March 2012)
4) Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012)
5) Complete noSQL (MongoDB) backend (September 2012)
6) Unify Perl and Python implementations (September 2012)
Define, prototype, demonstrate and operate a MI service, starting in May, 2012.
Support use in GENI by many tools, including GEMINI and GIMI I&M tools
Define operations plan for MI service.

Work in Progress

Summary of current status

T8) GENI User Tools and Services

11:25am

Team

LEAD Jeanne Ohren (GPO)
Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)
Max Ott and/or Christoph Dwertmann (NICTA)
Chris Small (NetKarma, IU)
Ahmed El-Hassany (IU)
Giridhar Manepalli (CNRI)
Harry Mussman (GPO)
Vic Thomas (GPO)
Niky Riga (GPO)
Luisa Nevers (GPO)

Goals

Work towards Max Ott's vision for experiment support
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".
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 the measurement data.
These services should work together via APIs, etc., to streamline the experiment process.

Tasks

Based upon the configuration defined below, the implementation is split into:
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
2) Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user.

Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user, or on a server hosting multiple user workspaces for multiple users.
Gather the various "user tools" that have been implemented to date, and fit into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure.
Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).

Work in Progress

Summary of current status

T9) Digital Object Archive (DOA) Service

11:40am

Team

Co-LEAD Giridhar Manepalli (CNRI)
Co-LEAD Shu Huang (RENCI)
Larry Lannom (CNRI)
Wesley Wu (U Kentucky)
Hussam Nasir (U Kentucky)
Chris Small (NetKarma, IU)
Jeannie Ohren (GPO)

Tasks

Start with CNRI prototype digital object archive service
Plan transition to use of iRODS service
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 data in MDOD used to set archive sharing policy? what is required in MDOD?
Operations plans for Digital Object Archive (DOA) and Object Identifier (OI) services.

Work in Progress

Summary of current status

T10) List of Operational Services

(no report)

Team

Mike Zink (UMass Amherst)
Martin Swany (Inidana U)
Jim Griffioen (U Kentucky)
Giridhar Manepalli (CNRI)
Jeanne Ohren (GPO)
Harry Mussman (GPO)

Tasks:

What persistent operational services must be supported:
a) Descriptor registry required? use UNIS? DOR? iRODS? IF-MAP?
b) Object registry required? use DOR?
c) XML Messaging service
d) Measurement Information (MI)service
e) GENI User services
f) Digital Object Archive (DOA) service
Can all services can be shared by GIMI and GEMINI tools?
How do these relate to other GENI services/functions, including clearinghouse?

Work in Progress

Discussion of next steps

11:55am

3) Break for lunch

12noon

4) Update on GIMI project

1:30pm
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 focuse: 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 for digital object archive.

Members of the GIMI project will review:

*Current architecture and design

*Current status

*Preview of tonight's GEC-13 demo

*Plan for GEC-14 tutorial

5) Update on GEMINI project

2pm
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:

Starts with LAMP, which provides flexible tools based on perfSONAR for active infrastructure measurements
++Fold INSTOOLS features into LAMP to form GEMINI tools, and then discontinue INSTOOLS

*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
*Consider how to gather basic host measurements with BLiPP service (as was done by INSTOOLS using SNMP)
*Consider how to gather customized data from applications (as provided by OML Client)

++Extending LAMP 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

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

*Continue INSTOOLS portal service, in user workspace, to find GUIs
*Continue LAMP local and global UNIS service, to register available measurement data, and network topology

Members of the GEMINI project will review:

*Current architecture and design

*Current status

*Preview of tonight's GEC-13 demo

*Plan for GEC-14 tutorial

6) Support for experimenters

2:30pm

Round-table discussion:

What use cases must be supported by GEC14? by GEC15?
What tools must be available by GEC14? by GEC15?
How can we best verify that available tools meet the needs of experimenters? process for fixing bugs? process for making extensions?
How can we best reach out to experimenters? tutorials? workshops? on-line instructions? examples? help desks?

7) Support for infrastructure measurement

2:45pm

Round-table discussion:

What use cases must be supported by GEC14? by GEC15?
What tools must be available by GEC14? by GEC15?
What use cases/tools will support experimenters?
What use cases/tools will support operators?
How can we best verify that available tools meet the needs of experimenters and operators? process for fixing bugs? process for making extensions?
How can we best reach out to experimenters? tutorials? workshops? on-line instructions? examples? help desks?

8) Adjourn

3pm

Attachments (15)