Changes between Version 8 and Version 9 of GeniNetworkStitching

11/03/11 10:07:26 (10 years ago)
Aaron Helsinger



  • GeniNetworkStitching

    v8 v9  
    33A 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 ?
     5Currently there is an adopted architecture, including an RSpec schema for describing stitching resources and requests.
    57This question was the topic of one of the four software engineering meetings at GEC10. Details are on the meeting page.
    79[wiki:GEC10Stitching GEC10 meeting]
     11The session concluded by adopting a specific stitching architecture: [ Stitching Architecture as adopted at GEC10]. Next steps centered around developing a schema for describing interconnections, and continued API discussions.
    913The topic was re-visited at GEC11.
    1115[wiki:GEC11Stitching GEC11 stitching meeting]
     17At this session, we
     18 - described and adopted a schema for describing stitching resources and requests, as a GENI RSpec extension: [ Proposed Stitching schema and workflow]
     19 - demonstrated a tree mode VLAN stitch across PG, ION and MAX aggregates using the Omni client
     21At GEC12, there was a brief [attachment:wiki:GEC12ControlFrameworkTopics:stitching-session-gec12-lehman-v2.pdf] update on status from Tom Lehman
     22 - Omni1.4 includes a library demonstrating tree mode stitching without negotiation
     23 - Negotiation should be the next focus, specifically AM API changes to createSliver or using tickets
     24 - Work continues on exploring a production aggregate manager for ION
     25 - Chain mode stitching needs attention
    1327== Links ==