1 / 8

GENI Federation Scenarios and Requirements

GENI Federation Scenarios and Requirements. Sangjin Jeong (ETRI) Andy Bavier (Princeton Univ.) March 18, 2010 Control Framework WG meeting @ GEC7. Objective. Discuss the scenarios and requirements for GENI federation in several contexts. Motivation. Objective

oria
Download Presentation

GENI Federation Scenarios and Requirements

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 Federation Scenarios and Requirements Sangjin Jeong (ETRI) Andy Bavier (Princeton Univ.) March 18, 2010 Control Framework WG meeting @ GEC7

  2. Objective • Discuss the scenarios and requirements for GENI federation in several contexts

  3. Motivation • Objective • Resource federation permits the interconnection of independently owned and administered facilities so that users can create slices and perform experiment while allowing the facilities owners to enforce their local policies for operation, allocation and usage for facilities • Motivation • Use their own control frameworks for managing testbeds • Hard to build large-scale testbed in the global scale • Federation can provide large scale, diverse, and realistic network testing environment • Resources must be able to appear and be useful on more than one testbed • Increase utilization/resource diversity rather than exclusive use

  4. Problem description • Classification of federation problems • Different identity/authority management • Identity allocation/authorization policy • Authentication and authorization mechanism • Different control procedures • Control flows (resource discovery/allocation, slice creation, ...) • Different interfaces/APIs • Different resources and experiments description • Resource description schemes (syntax, context, entity, …) • Description of experiments, services, experimental results

  5. GENI federation scenarios Federation with non-GENI infrastructures Control Manager Authn / Resource Resources Authz Manager Manager Clearinghouse A Clearinghouse B Authn / Authn / Registry Slice Registry Slice Authz Authz Manager Manager Manager Manager Manager Manager Federation among GENI infrastructures Agg . A - 1 Agg . A - 2 Agg . B - 1 Agg . B - 2 Agg . Agg . Agg . Agg . Manager Manager Manager Manager Authn / Authn / Authn / Authn / Authz Authz Authz Authz Agg . C - 1 Agg . C - 2 Federation with resources (Aggregate) Agg . Agg . Manager Manager Authn / Authn / Authz Authz

  6. Federation requirements • Common interfaces or adapters for different control procedures • Common interfaces or adapters for authority services • Unified profiles for certificate and authority management • Common resources and experiments description schemes • Common data access interfaces • Policy agreement on resource usage

  7. Summary of federation requirements for each scenario

  8. Next steps • There are increasing interest in investigating testbed federation scenarios and issues, requirements • Within the scope of control framework WG? • Adopt WG work item? • Documentation may be necessary • Federation scenarios & requirements • Develop standard interfaces and adapters? • …

More Related