Changes between Version 1 and Version 2 of GeniDesign

03/07/11 14:34:25 (11 years ago)
Aaron Falk



  • GeniDesign

    v1 v2  
    1313  The GENI API is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.
    15  Identity and Attributes::
     15 [wiki:GeniIdentityAndAttributes Identity and Attributes]::
    1616  GENI requires a way of positively identifying experimenters and granting them access to tools and resources. Current control frameworks either maintain their own database of users or explicitly outsource this task to an identity provider. In addition to identifying experimenters, GENI needs information about attributes like institutional affiliation, project role, etc.
    18  Authorization::
     18 [wiki:GeniAuthorization Authorization]::
    1919  GENI requires an authorization solution that will allow architectural components (Clearinghouse, Aggregates) to determine the privileges of an experimenter. Experimenters can be granted privileges based on institutional affiliation, project role or membership attributes, for instance. Aggregates are expected to have local policies regarding resource access and use.
    21  Resource Specification::
     21 [wiki:GeniRspec Resource Specification]::
    2222  In order to truly allow interoperability among multiple control frameworks and aggregates, GENI requires a common language for describing resources, resource requests, and reservations - a single, well defined RSpec schema.
    24  Network Stitching::
     24 [wiki:GeniNetworkStitching Network Stitching]::
    2525  A key architectural question for GENI has been how to connect the resources provided by multiple aggregates into a coherent network. The key objective is to enable automated and realtime network stitching for slices which span multiple aggregates. Ethernet VLANs have been identified as the initial network technology to provide slice level inter-aggregate connections and isolation. However, there are many architecture and design decisions still required. These include, how do you select the VLAN IDs to use and inform all necessary aggregates? How do you handle external networks which may be in between two GENI Aggregates of interest? Is the network stitching service a shared service which coordinates across aggregates, or are aggregates responsible for coordinating amongst themselves, or a hybrid model? How is stitching related information described and shared ?