1 / 11

Network Stitching

Network Stitching. Control Framework Working Group November 3, 2010 Tom Lehman (USC/ISI) Xi Yang (USC/ISI). Network Stitching. The topic here is the mechanics of "network stitching"

elissad
Download Presentation

Network Stitching

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. Network Stitching Control Framework Working Group November 3, 2010 Tom Lehman (USC/ISI) Xi Yang (USC/ISI)

  2. Network Stitching • The topic here is the mechanics of "network stitching" • There is an associated topic which is network stitching related user and resource authentication/authorization/policy application. • The network resources associated with stitching can be viewed as just another resource to be federated via integration into SFA. • user credentials, slice (resource) credentials: still many issues revolving around policy – definition/application/enforcement • These are important issues, but this talk is focused on what is required to accomplish the actual network stitching functions

  3. Aggregate Inter-connections • The inter-connections between Aggregates can be "viewed as a topology" • This is a view of the AM inter-connection, not a specific slice instantiation • represents resources potentially available for network stitching AM2 AM3 AM5 AM4 AM1 AM7 AM6 AM unique RSpec AM# Aggregate Manager

  4. Real World Considerations • There are other networks in-between the AM inter-connections: sometimes dynamic, sometimes static AM2 AM3 network AM5 AM4 network network network AM1 AM7 AM6 network

  5. Network Stitching - Objectives • Create Inter-Aggregate network connections • Typically Layer 2 (Ethernet) • but should also accommodate other layers • Often dynamically provisioned • Increasingly so in the future • Handle slice specific stitching parameters • Be able to accomplish the above in context of the heterogeneous AM and and interconnect topology

  6. Aggregate Inter-connections • Each AM has its own unique RSpec • RSpec defines AM unique capabilities and resources • diverse RSpec formats remain • We are suggesting that RSpec includes a "stitching resources component" • using a common schema to describe • will allow the building of stitching infrastructure global view • can also used to describe the instantiated configuration of stitching resources

  7. Network Stitching - What's Needed • Ability to develop a "view of the global AM inter-connection topology" • common topology schema for this which would show the relatively static parameters in the AM inter-connection space is needed • i.e., a link interconnecting two aggregates is10G bw with vlan range xxxx-yyyy allocated for GENI use • but the exact bw and vlans unavailable at any instant will not be reflected • amount of dynamic data can be tailored based on operational experience

  8. Network Stitching - What's Needed • AMs need to make available their part of the inter-connect topology • will happen naturally as a results of RSpec availability • external connections to other AMs is mainly what needs to be captured • not much dynamic information (but configurable) • need a "Topology Service" to collect this info

  9. Network Stitching - What's Needed • Need to define a stitching protocol/service additions to GENI AM API: • Inter-AM Topology Description: link id, remote peer id, bandwidth, vlan availability • AM stitching capabilities: vlan translation, vlan tunneling • Stitching Operations Specific functions: vlan query (what is possible?), suggested vlan ranges, two-phase commit support operations (hold resources for a period of time while I check with other AMs) • Used to find specific resources for specific slices • Network Stitching should include the notion of scheduling from the start

  10. Network Stitching - Summary • Once the following are available: • Common Network Stitching Topology Schema • Topology Service Publishing and Update Infrastructure • Network Stitching Service AM API Extensions/Definition • There will then be enough information to decide WHAT to do to respond to a specific slice request

  11. Network Stitching - Summary • The HOW to do stitching can be accomplished in multiple ways • not as hard as figuring out the what to do • "Tree" or "Chain", or "Hybrid" model are options • "Tree" – Higher Level Slice Manager (or embedded in Topology Service) looks thru the topology information (based on slice specific requirements), decides what actions are needed, and contacts the appropriate AMs • "Chain" – A source AM contacts other AMs directly • "Hybrid" - Combines both of the above

More Related