wiki:GEC11InstMeasWorkingSession

Version 34 (modified by hmussman@bbn.com, 8 years ago) (diff)

--

Instrumentation and Measurement (I&M) Working Session

Thursday, July 28, 2011, 1:00pm - 3:00pm
Room:
Session Leader: Harry Mussman, (GPO, Raytheon BBN Technologies)

Description

This session will review the latest DRAFT of the measurement_data_object_descriptor, commonly known as "metadata"; review the status of current I&M design and prototyping efforts; and review new topics and next steps.

Summary

Agenda

This is a tentative agenda, which may change.

1) Introductions

1:00pm

2) Measurement Data Object Descriptor (MDOD)

1:05pm
Harry Mussman

2.1) Overview

Format (syntax)

Goal remains: one data model for GENI
Assume: transfer format is XML record (file)
Have example in XML-like format, and schema/types in RelaxNG
Need: first software to generate (and consume) MDODs

Contents (semantics)

Few required elements, many optional elements
To meet use cases in arch document, sec 4.5
Want one-for-one mapping to key elements in current tools (started: perfSONAR; GENI rspec)

Point-of-view

Often global; therefore includes locators for data objects; must be updated as objects are copied, moved
Sometimes associated; need to understand
Should we consider: storing all MDODs in global, MI srvc? this becomes a MD object registry

Structure

identifier(s)
descriptor(s)
holder(s)

2.2) Use Cases

Read the following sections of the Architecture document:

4.5 GATHERING, TRANSFERRING AND SHARING MD

4.5.1 Schema and Provenance of MD

schema for MD object contained in MDOD
provenance of MD object contained in MDOD

4.5.2 Gathering MD into a Slice

by first holder, the "owner"
starts MDOD
as owner, sets sharing policy, disposal policy
as gatherer, deals with privacy

4.5.3 Transferring MD between I&M Services in the Same Slice

holder updates MDOD as transfers MD object between locations
option: registers MDOD with MI service

4.5.4 Transferring MD between I&M Services in Different Slices

e.g., holder 1 to holder 2
holder 1 authorizes transfer, sends object and copy of MDOD
holder 1 records the transfer in their MDOD
holder 2 accepts MD object and MDOD, and adds their local location to their MDOD
holder 2 tracks further transfers in their MDOD

4.5.5 Sharing MD with Others

e.g., holder 1 offers MD object at a portal, and registers this with MI srvc
user 7 requests MD object
holder 1 checks their sharing policy, authorizes transfer, and records the transfer in their MDOD

e.g., holder 1 transfers MD object to DOA srvc
user 9 requests MD object from DOA srvc
DOA srvc checks sharing policy in associated MDOD, authorizes transfer, and records the transfer in their MDOD

Use these figures

A summary of the topic is presented in these slides

See: I&M in Experimenter's Slice


See: I&M in Operator's Infrastructure Measurement Slice
For example: a GENI operator could get resources, setup a long-running measurement slice, and make data available to other operators or even experimenters.


2.3) Content (Semantics)

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.3 MD OBJECT DESCRIPTOR DATA MODEL
8.4 MD OBJECT DESCRIPTOR SCHEMAS

A summary of the topic is presented in these slides

DRAFT MDOD Data Models, Elements and Values

v0.2.x XML-like example (HEM)
v0.2 text
v0.2.1 text
v0.2.1 text, only mandatory elements

v0.3.x RelaxNG-Compact version (EK); includes RNC and converted XSD files, both schema and types
v0.3 schema RNC
v0.3 schema converted XSD
v0.3 types RNC
v0.3 types converted XSD

XML examples provided by Jason Zurawski:
example of proposed schema, with questions
modified schema, for further discussion

MDOD Discussion Points

For meeting on 072611 text

2.4) Supported Object Types and Formats

Instrumentation Tools (Kentucky)
OMF/OML (NICTA)
perSONAR/LAMP (Delaware, I2)
OnTimeMeasure (Ohio State)
Scalable Sensing Service? (Purdue, HP Labs)
GMOC? (Indiana)
NetCDF?
others?

2.5 Next Steps

First review of data model and schema (completed)

For each tool: map key elements into current data model; review expected use cases who? when?
Review suggested approach to recording provenance who? when?
Review choice for primary and secondary identifiers who? when?
Review formats for slice_id, etc. who? when?

Understand relationship to rspec? who? when?

Complete third pass at data model and schema who? when?

Complete first prototype software to create MDOD who? when?

3) Current I&M Design and Prototyping Efforts

1:35pm

3.1) Instrumentation Tools (Kentucky)

1:35pm
Jim Griffioen, Hussam Nassir

slides
Summary and status
Intended use(s): experimenter's slice operator's infrastructure measurement slice?
Creates or includes info for MDOD? in druple DB? mapping to MDOD elements? object_type? object_format? interpretation_method?
Includes persistent operational services? portal local archive
Integrates with MDA service? how? stores tarball status? issues?
Authorization methods supported? issues?

Note from Jim on 7/6: As for other topics you may want to discuss, one of the things that continues to be a big headache for us is limiting access to measurement data. Currently we have to deal with several different users accounts, authentication schemes, object granularity, etc. BTW, we have integrated INSTOOLS with the CNRI workspace model, but again, they have yet another set of user accounts and passwords to deal with. If we could start moving toward some standards in this area, that would be very helpful.

3.2) OMF/OML (NICTA)

1:45pm
Max Ott

slides
Summary and status
Intended use(s): experimenter's slice operator's infrastructure measurement slice?
Creates or includes info for MDOD? mapping to MDOD elements? object_type? object_format? interpretation_method?
Includes persistent operational services? centralized OML data service (will be needed for WiMAX base stations)
Integrates with MDA service? how? status? issues?
Authorization methods supported? issues?

3.3) perSONAR/LAMP (Delaware, I2)

1:55pm
Jason Zurawski, Ezra Kissel, Martin Swany

slides
Summary and status
Intended use(s): experimenter's slice? operator's infrastructure measurement slice?
Creates or includes info for MDOD? mapping to MDOD elements? object_type? object_format? interpretation_method?
Includes persistent operational services? lookup (meas info) services
Integrates with MDA service? how? status? issues?
Authorization methods supported? issues?

3.4) OnTimeMeasure (Ohio State)

2:05pm
Prasad Calyam

slides
Summary and status
Intended use(s): experimenter's slice? operator's infrastructure measurement slice?
Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method?
Includes persistent operational services?
Integrates with MDA service? how? status? issues?
Authorization methods supported? issues?

3.5) Meas Data Archive (MDA) Prototype Service

2:15pm
Giridhar Manepalli, Larry Lannom

slides
Summary and status
Intended use(s): experimenter's slice operator's infrastructure measurement slice
Receives MDOD? mapping to MDOD elements? object_format? uses sharing_policy? uses disposal policy?
Provides persistent operational services? user workspace service object archive service
Integrates with other tools and services? how? status? issues?
Authorization methods supported? issues?

3.6) Others?

Scalable Sensing Service? (Purdue, HP Labs)
GMOC? (Indiana)

NetKarma: Experiment Provenance
Mehmet Aktas, Beth Plale, Scott Jensen
slides

4) New Topics and Next Steps

2:30pm
Open discussion, led by Harry Mussman

4.1) Measurement Data Object Descriptors (MDODs) (“metadata”)

First review of data model and schema (completed)

For each tool: map key elements into current data model; review expected use cases who? when?
Review suggested approach to recording provenance who? when?
Review choice for primary and secondary identifiers who? when?
Review formats for slice_id, etc. who? when?

Understand relationship to rspec? who? when?

Complete third pass at data model and schema who? when?

Complete first prototype software to create MDOD who? when?

4.3) Deploy Prototype Operational Services

Measurement Data Archive (MDA) service, including User Workspace (UW) service and Digital Object Archive (DOA) service (ongoing)
INSTOOLS portal? who? when?
INSTOOLS archive service? who? when?
perfSONAR/LAMP lookup (Measurement Information) service? who? when?
other MI service? who? when?
Centralized OML server? (useful for monitoring WiMAX sites) who? when?
others?

4.4) Integrate I&M services for Experimenters

INSTOOLS tools with MDA service (ongoing)
OnTimeMeas tools, with MDA service (ongoing)

4.5) Integrate I&M services for Operators monitoring infrastructure

LAMP for OpenFlow slice monitoring (Ali Sydney)

4.6) Use DOA for Sharing Data with Others

Who? when?

4.7) Authorization Mechanisms

Define situation who? when?
Note from Jim on 7/6: As for other topics you may want to discuss, one of the things that continues to be a big headache for us is limiting access to measurement data. Currently we have to deal with several different users accounts, authentication schemes, object granularity, etc. BTW, we have integrated INSTOOLS with the CNRI workspace model, but again, they have yet another set of user accounts and passwords to deal with. If we could start moving toward some standards in this area, that would be very helpful.

Suggest approaches who? when?

4.8) Extensions

Use MDA as a full Experiment Repository to archive all experiment objects, including: meas data; software; topology/rspec?
Use various versions of MDOD to negotiate transfer of data object, e.g., like GENI resource assignment; use versions of MDOD to like rspec advertisement, request, amnifest.

Use MDOD with descriptor and holder/transaction records for "object assignment record"; use similar structure in GENI resource assignment to give "resource usage record"

Adjourn

3:00pm

Background Reading

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

Attachments (19)