wiki:GEC13Agenda/InstrumentationAndMeasurement

Version 18 (modified by hmussman@bbn.com, 7 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)
Hussamuddin Nasir (U Kentucky)
CO-LEAD Mike Zink (UMass Amherst)
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 Golubitski (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 Environment

Platform Targets
Experiment and Measurement Orchestration Tools
Interfaces/Protocols Between Tools and Services

Work in Progress

1) Definition of topic:

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

2) 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); LEAD Harry Mussman (GPO); Tom Mitchell (GPO); Aaron Helsinger (GPO); Marshall Brinn (GPO); Vic Thomas (GPO)

T5) Descriptors, Objects and Registries

Descriptor Schema and Registry Service
Object Names and Registry Service

Work in Progress

1) Goals

2) Tasks

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

3) Team

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

T6) XML Messaging Service

XML Messaging Service

Work in Progress

1) Goals

In I&M, a Measurement Orchestration (MO) service needs to interact with the I&M services; one way to do so is to use the OMF interface, currently used (for example) by the OMF Experiment Controller to command an OMF Resource Controller (RC) that is installed next to an application.

The OMF messages are carried between an EC and RC by an XML pub/sub messaging service, based on an XMPP server.

For GENI, an XML Messaging service will be provided to carry these OMF messages, and thus enable orchestration.

However, such a service may have other useful functions, such as transporting Event Records (ERs).

To be generally useful, authentication and authorization functions must be provided.

For a detailed list of all goals defined for the XML Messaging service, see the Spiral 4 SOW of the IMF project.

2) 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.

3) Team

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

T7) Measurement Information (MI) Service

Lookup Service

Work in Progress

1) Goals

A Lookup Service is a type of registry defined in the perfSONAR toolset; the availability of MD at perfSONAR interfaces MC services is registered there, using metadata describing the data and its location.

In addition, a similar Topology Service is used to store the topology of the network being examined.

Together, these services are combined in the Unified Network Information Service (UNIS).

The GEMINI project includes perfSONAR tools, and requires UNIS functions. Some will be provided locally (within the slice), but a global service is required if available MD is to be registered, so that users can find it and get it.

For GENI, the Measurement Information service (MI) will be provided to serve the need for a global UNIS service.

Can the MI service be used for other registry functions?

Can the MI service be used for finding web interfaces, and other types of portals?

Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI?

2) 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.

3) Team

? (GEMINI)
Giridhar Manepalli (CNRI)
Harry Mussman (GPO)

T8) GENI User Services

Portal Service

Work in Progress

1) 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.

2) Tasks

Based upon the configuration defined below, the implementation is split into:

1) A GENI User Workspace Service, 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 Service.

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).

3) Team

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)
Jeanne Ohren (GPO)
Harry Mussman (GPO)

T9) Digital Object Archive (DOA) Service

User Workspace and Archive Services

Work in Progress

1) Definition of topic:

a) Consider CNRI prototype user workspace and archive service
b) Consider U Kentucky archive service
c) Use 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) Operations plan for Archive Service.

2) Who: Giridhar Manepalli (CNRI); LEAD Shu Huang (RENCI) ; Larry Lannom (CNRI); Wesley Wu (U Kentucky); Hussam Nasir (U Kentucky); Chris Small (NetKarma, IU)

T10) List of Operational Services

Persistent Operational Services
Services Shared by GIMI and GEMINI

Work in Progress

1) 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

2) Can all services can be shared by GIMI and GEMINI tools?

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

4) Who: Mike Zink (UMass Amherst); Martin Swany (Inidana U); Jim Griffioen (U Kentucky); Giridhar Manepalli (CNRI); Aaron Helsinger (GPO); Jeanne Ohren (GPO); Harry Mussman (GPO)

3) Adjourn

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

7) Support for infrastructure measurement

2:45pm

8) Adjourn

3pm

Attachments (15)