Sponsored by the National Science Foundation 1 March 15, 2011 GENI I&M Update: I&M Service Types, Arrangements, Assembling Goals Architecture Overview –Process –Functional Services –Measurement Data Flows/Transfers –Measurement Traffic Flows –Principal Use Cases –Types of Services –Control Framework Implications –Measurement Data Objects and Descriptors –Controlling Access to Measurement Data Objects –Current Status Current I&M Design and Prototyping Efforts I&M Service Deployments References: –I&M work in progress: –I&M capabilities catalog: –I&M architecture document: –Available I&M tools:

Sponsored by the National Science Foundation 2 March 15, 2011 GENI I&M Architecture Overview: Functional Services GENI I&M services have been defined by function: Measurement Point (MP) service Measurement Collection (MC) service Measurement Analysis and Presentation (MAP) service Measurement Orchestration (MO) service Measurement Information (MI) service User Workspace (UW) service Digital Object Archive (MDA) service

Sponsored by the National Science Foundation 3 March 15, 2011 GENI I&M Architecture Overview: Principal Use Cases Use Case 1: Experimenter gathering measurement data (MD) from their slice Use Case 2: Operator (or Service Provider) gathering measurement data (MD) from GENI infrastructure Use Case 3: Experimenter gathering measurement data (MD) from their slice and from GENI infrastructure Use Case 4: Experimenter (or Operator) moving measurement data (MD) to an archive, with an option to share with other Researchers

Sponsored by the National Science Foundation 4 March 15, 2011 Use Case 1: Experimenter gathering MD from their slice Each I&M service is setup as part of the Experimenter’s slice GENI I&M project examples: –Instrumentation Tools (for use with protoGENI) –OMF/OML –LAMP (uses perfSONAR technology, for use with protoGENI) –OnTimeMeasure (for use with protoGENI or PlanetLab) Includes: –Type 1 service: dedicated to a slice –Type 4 service: with portal to share MD

Sponsored by the National Science Foundation 5 March 15, 2011 Type 1 I&M Service: Dedicated to a slice Each Type 1 I&M service: –Dedicated to a slice –Assembled by Slice Owner (e.g., Experimenter) using Control Framework mechanisms –Configured by Slice Owner (e.g., Experimenter) –Managed by Slice Owner (e.g., Experimenter) –I&M service management interface and API required on service

Sponsored by the National Science Foundation 6 March 15, 2011 Type 4 I&M Service: With portal to share MD Each Type 4 I&M service: Has web portal to observe and share MD Web portal authorization mechanism required to admit only specified users; should reuse accepted certificate/credential arrangements Example: Presentation service that is part of Instrumentation Tools Example: Digital Object Archive (DOA) service prototype from CNRI DOA service required to follow sharing policy within Descriptor associated with a Digital Object

Sponsored by the National Science Foundation 7 March 15, 2011 Use Case 2: Operator (or Service Provider) Gathering MD from GENI infrastructure An Operator (or Service Provider) can gather MD from GENI infrastructure into their slice –For their own use –To share with other operators, e.g., share with GMOC Includes: –Type 2 service: common service with multiple slivers –Type 3 service: common service with MD to multiple slices

Sponsored by the National Science Foundation 8 March 15, 2011 Type 2 I&M Service: Common service with multiple slivers Each Type 2 I&M service: –Common service, assembled, configured and managed by a Service Provider (or Operator) in their sliver using Control Framework (CF) mechanisms –Service Provider runs an AggMgr interface and offers slivers (e.g., MP service slivers, or UW service slivers, as shown above) to other Operators (or Experimenters) via CF mechanisms –Each sliver is a resource with an rspec –Example: Measurement System for packet capture from Univ Wisconsin –Example: User Workspace (UW) service prototype from CNRI

Sponsored by the National Science Foundation 9 March 15, 2011 Type 3 I&M Service: Common service with MD to multiple slices Each Type 3 I&M service: Common service assembled, configured and managed by a Service Provider (or Operator) in their sliver using Control Framework (CF) mechanisms Service Provider (or Operator) registers Descriptors of available MD Objects (e.g., MD flows, as shown above) with Measurement Information (MI) service Example: perfSONAR MP and MI services Operator (or Experimenter) finds and requests a flow from the I&M service Authorization mechanism required to make flow available to selected operators/experimenters.

Sponsored by the National Science Foundation 10 March 15, 2011 Use Case 3: Experimenter gathering MD from their slice and from GENI infrastructure An Experimenter can gather MD from their slice and from GENI infrastructure –Combines Use Case 1 with Use Case 2 Includes Type 2 service: common service with multiple slivers –Policy required to make sliver available to selected experimenters Includes Type 3 service: common service with MD to multiple slices –Access mechanism required to make flow available to selected experimenters Includes Type 1 service: dedicated to a slice –Configured to stitch flow into experimenter’s I&M service

Sponsored by the National Science Foundation 11 March 15, 2011 Use Case 4: Experimenter (or Operator) moving MD to an archive, with an option to share with other Researchers An Experimenter (or Operator) can move MD Objects (directories or files) to (and from) a Type 2 User Workspace (UW) service Always includes associated MD Object Descriptor (“metadata”) Identifiers and annotation in Descriptors allow Experimenter (or Operator) to manage thousands of files gathered during an experiment, or when monitoring infrastructure The Experimenter (or Operator) can move selected MD Objects (directories or files) from UWservice to the Type 4 Digital Object Archive (DOA) service, to become persistent Digital Objects Digital Object receives a persistent global identifier Digital Object includes an associated Descriptor Descriptor includes sharing policy, that DOA service is obligated to follow

Sponsored by the National Science Foundation 12 March 15, 2011 GENI I&M Architecture Overview: Control Framework (CF) Implications I&M services are built by Experimenters/Operators/Service Providers using CF functions –I&M service is a resource An I&M service (type 2) can offer slivers as resources via CF –I&M service must support an AggMgr interface –I&M sliver as a resource requires an rspec –Requires policy for selected experimenters and/or operators I&M service has a standardized management interface/API linked to Measurement Orchestration (MO) service via CF mechanisms –For example, keys are installed that are used to sign messages I&M service requires proxies (or other methods) to permit measurement traffic flows (data and management) to reach servers in private address space