1 / 5

GENI I&M Update: Sharing MD Objects with Researchers, MDA Service

GENI I&M Update: Sharing MD Objects with Researchers, MDA Service. Goals Architecture Overview Process Functional Services Measurement Data Flows/Transfers Measurement Traffic Flows Principal Use Cases Types of Services Control Framework Implications

tao
Download Presentation

GENI I&M Update: Sharing MD Objects with Researchers, MDA Service

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GENI I&M Update:Sharing MD Objects with Researchers, MDA Service • 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: http://groups.geni.net/geni/wiki/GeniInstMeas • I&M capabilities catalog: http://groups.geni.net/geni/wiki/GENIIandMCAPCAT • I&M architecture document: http://groups.geni.net/geni/wiki/GeniInstrumentationandMeasurementsArchitecture • Available I&M tools: http://groups.geni.net/geni/wiki/GeniInstMeas#AvailableGENIIMTools

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

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

  4. User Workspace Service • Each User Workspace (UW) service: • Is a Type 2 common service, assembled, configured and managed by a Service Provider in their sliver using Control Framework (CF) mechanisms • Service Provider offers UW slivers (e.g., Linux file systems) to Experimenters and Operators via CF mechanisms • UW service sliver is a resource to be obtained by an Operator via CF, and then configured and managed • Policy is required to make sliver available to selected experimenters and operators

  5. Digital Object Archive (DOA) Service • Each DOA service: • Is a Type 4 service with a web portal to observe and share MD • Required to follow sharing policy within Descriptor when sharing Digital Object • Policy required to make digital object available to selected users within GENI, selected users outside of GENI, and/or all others

More Related