Tags:
create new tag
, view all tags

RSpecs for MAX and ION DCN Aggregates

MAX Native RSpec

Before GEC14, we use a native version of RSpec schema for both MAX and ION DCN aggregates. Support for the schema by the AM code has been renewed with observation of GENI style URN format.

  • The native schema is defined here max-rspec.xsd.
  • Here is an example of request RSpec using native schema max-native1-new.rspec, which creates an internal VLAN circuit linking two PlanetLab node interfaces plus a stitching VLAN circuit from a local interface to external aggregate.

GENI RSpec Version 3

The MAX and ION DCN AMs now support the GENI RSepc v3 by default. This standard schema has been defined here.
  • Here is the GENIv3 version for the above example: max-geniv3-2.rspec.
  • Note that the link with client_id="link-stitching-link1" is a MAX-specific definition for associating a local interface with stitching VLAN circuit. This is necessary when a physical interface has more than one "interface" instances, some for internal links and other for stitching links. Other AMs will have similar implementation to attach specific native interface to stitching.
  • An example manifest: max-geniv3-2-manifest.rspec.

In ION DCN AM deployment, we need not allocate PlanetLab nodes. No host interface is attached to network links. The RSpecs look slightly different. Below are the examples in GENI RSpec v3 format.

  • For allocating a VLAN circuit in ION: ion-geniv3-1.rspec.
  • For VLAN stitching across ION: ion-geniv3-2.rspec.
  • One can combine one or more instances of the above in the same RSpec request.
Topic revision: r1 - 2012-05-14 - XiYang
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback