Tags:
create new tag
, view all tags
-- TomLehman - 20 Jul 2011

Network Stitching WorkFlow Examples

This page contains some example GENI Network Stitching Workflows

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 Stitching Path Computation

For this example the above request was translated manually into the following. In the future, this translation is what we would expect the GENI Slice Computation Engine to accomplish:

client request after (manual) computation

For this example we needed to develop a distinct RSPEC request for each of the three Aggregates. This is because the MAX and ION do not yet support ProtoGENIv2 Style RSPECs. Once the MAX and ION AM do support the ProtoGENIv2 style RSPECs, then the same RSPEC request can be submitted to all three AMs. This common RSPEC Request is as shown for the ProtoGENI Request below.

Tree Mode Stitching Workflow Actions

  • Tree Mode Workflow agent uses OMNI client and the following logic to request Slivers:
    • Inspect the advertisement RSPECs for all three Aggregate Managers and observe that only ION does VLAN translation
    • Decide to order the Aggreate Requests per the following:
      • Submit a CreateSliver request to the ProtoGENI AM and wait for VLAN number to be returned.
      • Submit a CreateSliver request to the MAX 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 modified RSPEC and 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 504, which is translated by ION to VLAN 3203, and VLAN 3203 is extended across MAX all the way to node PlanetLab2.

overall manifest view




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)

Edit | Attach | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2011-07-20 - TomLehman
 
  • Edit
  • Attach
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