Instrumentation and Measurement (I&M) Working Session

Thursday, March 17, 2011, 1:00pm - 4:00pm
Room: Bahia 2
Session Leader: Harry Mussman, (GPO, Raytheon BBN Technologies)

Description

This session will review three key instrumentation and measurement (I&M) topics still under study by the GENI I&M community, and present the status of a prototype Measurement Data Archive (MDA) service.

Each topic will be reviewed by a member of the community, and then opened for discussion and a determination of the next steps.

Summary

​slides

Dial In Arrangements

866-453-5550 (international 1-404-974-9843) 6513886#

webex:

Meeting Number: 797 494 337

Meeting Password: GENInow01

To join this meeting (Now from mobile devices!)

1. Go to ​https://bbn.webex.com/bbn/j.php?J=797494337&PW=NOTUyNGU1N2Rm

2. If requested, enter your name and email address.

3. If a password is required, enter the meeting password: GENInow01

4. Click "Join".

5. Follow the instructions that appear on your screen.

Agenda

This is a tentative agenda, which may change.

1) Introductions

1:00pm

2) I&M Services

2.1) Functions, Arrangements, Types, Assembling, Configuring and Managing I&M Services

1:05pm
Harry Mussman

Read the following sections of the ​Architecture document:[[BR]

4. I&M Services
   4.1 Functions of I&M Services
   4.2 Typical Arrangements of I&M Services (reflect principal use cases)
   4.3 Types of I&M Services
   4.4 Assembling, Configuring and Managing I&M Services
   

Use these ​figures

A summary of the topic is presented in these ​slides

Discussion

Consensus?

Next steps?

2.2) Sharing Measurement Data (MD) Objects with Other Researchers

1:30pm
Larry Lannom (CNRI)

From architecture document, summarized in these ​slides:
Use Case 4: Experimenter (or Operator) moving measurement data (MD) to an archive, with an option to share with other Researchers
Type 4 Service: with portal to share measurement data (MD)

​Discussion Slides

2.3) Prototype Measurement Data Archive (MDA) Service

1:45pm
Giridhar Manepalli (CNRI)

Measurement Data Archive (MDA) Service

Defined earlier in these ​slides

Overview of User Workspace and Digital Object Archive services presented in these summarized in these ​slides:

CNRI prototype defined:
​text
​Discussion Slides

Demo

First users?

Other uses in GENI?

Break

2:30pm

3) Gathering, Transferring and Sharing Measurement Data

2:45pm
Harry Mussman

Read the following sections of the ​Architecture document:[[BR] 4.5 GATHERING, TRANSFERRING AND SHARING MD
4.5.1 Schema and Provenance of MD
4.5.2 Gathering MD into a Slice
4.5.3 Transferring MD between I&M Services in the Same Slice
4.5.4 Transferring MD between I&M Services in Different Slices
4.5.5 Sharing MD with Others

Use these ​figures

A summary of the topic is presented in these ​slides

Discussion

Consensus?

Next steps?

4) Measurement Data Objects and Descriptors (i.e, metadata)

3:00pm
Harry Mussman

Read the following sections of the ​Architecture document:
8 SCHEMA AND ELEMENTS FOR MEASUREMENT DATA OBJECT DESCRIPTORS (MDODS)
8.1 MEASUREMENT DATA OBJECTS (MDOS)
8.2 MEASUREMENT DATA (MD) OBJECT DESCRIPTOR
8.2.1 Uses
8.2.2 One Data Model
8.2.3 Multiple Schemas
8.3 MD OBJECT DESCRIPTOR DATA MODEL
8.3.1 Vocabulary
8.3.2 Identifier Elements
8.3.3 Interoperability Elements:
8.3.4 Discovery Elements
8.3.5 Administrative Elements:
8.3.6 Mapping into Descriptors from GENI MD Schemas
8.4 MD OBJECT DESCRIPTOR SCHEMAS
8.4.1 File Schema
8.4.2 MI Registration Schema
8.4.3 Archive Schema

A summary of the topic is presented in these ​slides

DRAFT MDOD Data Model, Elements and Values:

Identifier (type, value) Mandatory

Locator (type, value) Mandatory

[Collection (member of): type; name; index] --- Optional

[Structure: (where object includes multiple sub-objects) [[BR]]

Sub-object x descriptor:

(repeat above)

Sub-object y descriptor:

(repeat above)

] Optional

Object type: flow | file | directory | data base | GUI | digital object Mandatory

Measurement data schema: template; names; parameters; types Mandatory

Size: (type, value) Optional

Encryption: (type, owner) Optional

Subject: what; where Mandatory

Time: when Optional

Keywords Optional

Description Optional

GENI-specific discovery elements: (services; identifiers; slices; experiments; runs) Mandatory

Owner/creator: (slice; experiment; run; when; who; contact; processing; annotation) Mandatory

Previous holder(s): (slice; experiment; run; when; who; contact; processing; annotation) Optional

Current holder: (slice; experiment; run; when; who; contact; processing; annotation) Optional

Last modified: (date; time; contact) Mandatory

Licenses: Optional

Private information: type; mitigation; responsibilities Optional

Transfer rules: Optional

Disposal rules: Optional

Comments from earlier discussion:

Camilo Viecco:

All parameters look fine. I have one question: The 'Time' optional parameter appears to be redundant. Should it not match the owner/creator when mandatory value?

There is also the issue of metadata for time ranges. How do we express that? If we remove the time, then I belive this is a good place to start

Hussam Nasir:

I agree with Camillo suggestions and dont see any more addition/removal i would want to make.

Max Ott:

As for meta data I first of all want to stress that we really should find a way to align this with the Resource Description spec of the Control Framework. While there is substantial reluctance there to embrace anything assembling some kind of structure, I'm not giving up the fight that easily. I just find it utterly silly to have two or more different ways to describe resources. Measurements are resources as well and metadata is all about describing where the measurements are coming from, that includes the resources we provision through the control framework.

I know , with the little (or zero as in my case) funding we have available, nobody is excited about re-factoring for alignment sakes, but we shouldn't forget why we are we doing this in the first place. We just published a paper which included an analysis of last year's edition of one of the major conferences in our field. 26 out of the 36 accepted papers had substantial flaws in their respective analysis section, ranging from not even describing the experiment to the sloppy "10-run average" without any indication of precision. The numbers would have looked a lot grimmer if we would have tried to figure out on how to repeat the results.

Coming back to meta data and repeating my RSpec argument. We first need an object/component/resource model and then we need a way to attach meaning to various 'groups' of model instances. The first part (model) should be quite stable as it gets baked into tools, services, and code and is expensive to change. The second part (semantics) should be easy to change as it inadvertently will as it reflects our changing needs, understandings, use cases. In other words, the rate of change somewhat reflects the vibrancy of the community using it.

This is sitting in my drafts folder already for a few days, still half baked, but hopefully still of some marginal value.

Discussion

Consensus?

Next steps?

5) Current I&M Design and Prototyping Efforts

3:45pm

I&M services for Experimenters, including:

Instrumentation Tools (for use with protoGENI)
OMF/OML
LAMP (uses perfSONAR technology, for use with protoGENI)
OnTimeMeasure (for use with protoGENI or PlanetLab)

I&M services for monitoring infrastructure, including:

Measurement System, for packet capture
Shadownet, for router monitoring
Scalable Sensing Service

Measurement Data Archive (MDA) service

First prototype by CNRI, including User Workspace (UW) service and Digital Object Archive (DOA) service

Management of an I&M service, from Measurement Orchestration (MO) service:

First prototype by IMF and ERM projects, following OMF approach

Measurement Data Objects, and Descriptors (“metadata”):

Defining common data model, then schemas
First prototype software by ?

Measurement traffic flows, proxies/mechanisms) to reach servers in private address space

First prototype of ssh access by ORCA project

​slides

Is anything missing?

Next steps?

6) I&M Service Deployments

3:50pm

Current I&M services for Experimenters, including:

Instrumentation Tools (for use with protoGENI)
OMF/OML
LAMP (uses perfSONAR technology, for use with protoGENI)
OnTimeMeasure (for use with protoGENI or PlanetLab)

Introduce I&M services for monitoring infrastructure, including:

perfSONAR components, with Measurement Information (MI) service, and first use of Measurement Data Object Descriptors (MDOD’s)? Who?
Measurement System for packet capture?
Scalable Sensing Service?

Introduce Measurement Data Archive (MDA) service:

Include User Workspace (UW) service
Include Digital Object Archive (DOA) service
Who are first users?
Are there other uses, e.g., software downloads?
When ready to support Researchers?

​slides

Discussion

Can we build a guide?

Adjourn

4:00pm

Background Reading

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