Tags:
create new tag
, view all tags

Network Stitching Architecture Discussion

Stitching Architecture Documents

The following documents have been generated to facilitate discussions regarding a GENI Network Stitching Architecture:

  • GENI Network Stitching Architecture - Overview (doc)(pdf)
    This document provides an overview of a proposed stitching architecture.

  • GENI Network Stitching Architecture - Example (doc)(pdf)
    This document provides an example of the proposed architecture base on Use Cases.

  • GENI Network Stitching Component Design - Example (doc) (pdf)
    This document provides an example of a specific design for each of the architecture components. The intent is to convince ourselves that a detailed design can be develop to support the proposed architecture, not necessarily to define the final design details.

  • GENI Network Stitching Schema Example (geni-stitching.xsd)
    This is an xsd file of an example Common Stitching Topology Schema.

  • GENI Network Stitching RSPEC Instance Example
    The below file is an example instantiation of a Stitching Resource Element (Stitching RSPEC info) that an Aggregate would use to describe an external link to another aggregate. In this example, the MAX Aggregate is describing an external link to the ProtoGENI Aggregate. This Stitching RSPEC is in accordance with the above schema.

Stitching Architecture Summary

Below is a very high level summary of the content in these documents. Please see the above documents for detailed discussions.

The proposed GENI Network Stitching Architecture has the following six components:

  • Stitching Resource Element - This is an element which would be provided by all Aggregate Managers. The purpose of this component is to define the external connection points for the local AM.

  • Common Stitching Topology Schema - In order to conduct operations across multiple AMs, the Stitching Resource Component needs to be based on a common topology schema to be used by all GENI AMs. This does not require any standardization or other changes to the structures of the unique AM RSpecs. The intent here is that any entity which can exercise the ListResources (with "all resources" set) feature of the GENI AM API, will get back an AM unique RSpec. In a similar manner the Stitching Resource Element which is formatted in accordance with a GENI standard network stitching topology schema will be made available.

  • GENI Stitching Topology Service - This is a function which has the ability to collect the Stitching Resource Components from all the GENI AMs, and build a global view of the inter-connected GENI AM space. The service provided will be to make this global topology view available to other processes, such as the GENI Stitching Function described below, so that the details of a specific network stitching event can be calculated and coordinated.

  • GENI Stitching Path Computation Function - This function has the ability to obtain the global network stitching topology view from the Stitching Topology Service, perform slice instantiation specific path computations.

  • GENI Stitching Workflow Function - This function has the ability to take the path computations results and execute the workflow steps required to accomplish network stitching. This includes interacting with the specific AM APIs and external network resources to instantiate the network stitching provisioning actions.

  • GENI AM API Network Stitching Extensions - Some extensions will be needed to the GENI AM API to support robust and globally scalable network stitching functions. These extensions will revolve around the concepts of stitching specific resource queries, resource negotiations for multi-aggregate stitching operations, basic stitching interfaces, and status interfaces.

The objective is that the above GENI Network Stitching Components can support multiple stitching modes of operation, which include:

  • Tree Mode
    The Stitching Workflow Function takes responsibility for talking to all the AMs individually, and then acting on all the received information to find a solution which works for the specific stitching activity.

  • Chain Mode
    The AMs will talk directly to each other and information sharing and processing is done in a chain from AM to AM.

  • Hybrid Mode (Tree and Chain)
    The Stitching Workflow Function will initiate communications with multiple AMs, but there may also be CHAIN regions where there is direct AM to AM communications.

Stitching Architecture Figures

The figures below describe examples of stitching architecture and the modes of operation.

  • Figure 3a Tree Model - Client Tools Initiated (png)
  • Figure 3b Tree Model - Aggregate Manager Initiated (png)
  • Figure 3c Chain Model (png)
  • Figure 3c Chain Model - ProtoGENI Focused (png)
  • Figure 3d Hybrid Model - Tree and Chain (png)










Figure 3a Tree Model - Client Tools Initiated

  • fig3a-tree-client.png:
    fig3a-tree-client.png

Figure 3b Tree Model - Aggregate Manager Initiated

  • fig3b-tree-am.png:
    fig3b-tree-am.png

Figure 3c Chain Model

  • fig3c-chain.png:
    fig3c-chain.png

Figure 3c Chain Model - ProtoGENI

  • fig3c-chain-pg.png:
    fig3c-chain-pg.png

Figure 3d Hybrid Stitching Example - Tree and Chain

  • fig3d-tree-chain.png:
    fig3d-tree-chain.png

Topic revision: r14 - 2013-06-25 - XiYang
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback