Tags:
create new tag
, view all tags

Network Stitching WorkFlow Examples

This page contains an example GENI Network Stitching Workflow.

Tree WorkFlow Example 1

This stitching workflow creates a slice which has slivers on the following Aggregates:

  • ProtoGENI
  • Internet2 ION
  • MAX

The ION Aggregate is a "Network Stitching" only Aggregate, that is, it does not contain any host resources in its advertisement RSPEC. However, the interaction with the ION Aggregate Manager (AM) is the same as for any other AM.

Client Request

Here is what a client would like:

client request

Client Request Expanded based on Path Computation by Stitching Computation Service (SCS)

For this example the above request was translated into the following.

client request after (manual) computation

The same RSPEC request will be submitted to all three AMs following their order in computed workflow.

Tree Mode Stitching Workflow Actions

  • Tree Mode Workflow agent uses OMNI client and the following logic to request Slivers:
    • Inspect the requests RSPECs for all three Aggregate Managers and use knowledge that only ION does VLAN translation
    • Decide to order the Aggregate Requests per the following:
      • Submit a CreateSliver request to the MAX AM and wait for VLAN number to be returned.
      • Submit a CreateSliver request to the ProtoGENI AM and wait for VLAN number to be returned.
      • Submit a CreateSliver request to the ION AM using the the VLAN numbers received from ProtoGENI and MAX AM. This will likely require VLAN translation.
  • The final configuration will be reflected in the subsequent Manifests.

Manifest RSPEC

At the end of this process we will have three Manifests RSPEC, one from each Aggregate Manager. These are as listed below:

Below is a graphical view of the overall Slice based on the Manifest's information. It shows that we go from ProtoGENI node PG45 to VLAN 764, which is translated by ION to VLAN 3020, and VLAN 3020 is extended across MAX all the way to node PlanetLab2.

overall manifest view

  • Note that the drawings are for illustration purpose and you may find inconsistent artifacts between the the drawings and the above request and manifests.




Related and Future Work

  • Chain Mode Stitching Workflow
    • AM API Stitching Extensions (negotiation features)
    • AM Chain Mode Workflow Processing (basic and more advanced)

  • Tree Mode Stitching Workflow
    • AM API Stitching Extensions (negotiation features)
    • AM Tree Mode Workflow Processing (basic and more advanced)

  • Aggregate Manager Future Scheduling Capabilities?

  • Topology Service (Collects Aggregate Manager Advertisements)

  • Slice Computation Service (based on information in Topology Service)

GENI Stitching Architecture Implementation Status

The below diagram outlines how the current implementation and demonstration work relates to the overall GENI Stitching Architecture.


geni-stiching-arch-implement-status.png

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