Version 86 (modified by, 9 years ago) (diff)


GENI Network Stitching Sites

Last update: 2015-02-04

The following 19 sites have been tested and are available for GENI Network Stitching experiments via the listed networks:

Site Name Nickname Connections
CENIC InstaGENI cenic-ig AL2S
GPO ExoGENI gpo-eg ION
GPO InstaGENI gpo-ig ION
Mid-Atlantic Crossroads (MAX) InstaGENI max-ig AL2S
Naval Postgraduate School InstaGENI nps-ig ION
NYSERNet InstaGENI nysernet-ig AL2S
Rutgers University InstaGENI rutgers-ig ION & AL2S
Stanford InstaGENI stanford-ig ION & AL2S
University of California Los Angeles InstaGENI ucla-ig AL2S
University of Chicago InstaGENI chicago-ig AL2S
University of Illinois InstaGENI illinois-ig ION
University of Kansas InstaGENI kansas-ig AL2S
University of Kentucky ProtoGENI uky-pg ION
University of Kentucky PKS2 InstaGENI ukypks2-ig ION
University of Missouri InstaGENI missouri-ig ION & AL2S
University of Utah Downtown Data Center InstaGENI utahddc-ig ION
University of Utah InstaGENI utah-ig ION
University of Utah ProtoGENI utah-pg ION
University of Wisconsin InstaGENI wisconsin-ig AL2S

GENI Network stitching is possible between all of the above InstaGENI and ExoGENI sites. Example GENI stitching RSpecs are available here. For an example experiment that uses GENI Network Stitching, see this GENI Network Stitching Example page. To determine resource availability refer to the InstaGENI Site Usage page.

You may use any of the sample Stitching RSpecs referenced by this page. To modify an RSpec example to use a different site, simply do the following:

  1. In the node definition, replace the URN for the component_manager_id with the URN for your site.
  2. In the link definition, replace the name of the component_manager with the URN for your site.
  3. Modify all instances of the client_id and source_id or dest_id to be descriptive for your site.

Stitching Notes:

  • All existing compute resource types (raw-pc, openVZ, Xen) are supported in stitched slivers.
  • Testing has verified most combinations for the sites listed. There is only one combination that does not work at this time: GPO ExoGENI to PG UKY.
  • To run stitching scenarios without the ExoSM for the GPO ExoGENI rack, use the stitcher option --noExoSM. If this option is not specified, than the request is submitted to the ExoSM aggregate.
  • Stitching RSpecs that include raw-pc sliver types must specify a capacity.
  • If any part of a sliver creation fails, the stitcher will delete the stitched sliver at each aggregate.
  • If you interrupt the stitcher sliver creation with GCF 2.8 or later the stitcher will attempt to delete all sliver, but if you are using GCF 2.7 or earlier you must delete the sliver at each of the aggregates listed by the stitcher as part of the stitched path, and re-create the entire slice.

VLANs Delegation at GENI Stitching Sites:

The following table captures GENI sites number of VLANs delegated to stitching connections:

cenic-ig 0 20
gpo-eg 30 0
gpo-ig 30 0
illinois-ig 20 0
max-ig 0 60
missouri-ig 10 5
nps-ig 15 0
nysernet-ig 0 20
rutgers-ig 10 11
stanford-ig 9 5
ucla-ig 0 20
uky-pg 10 0
ukypks2-ig 20 0
utah-ig 745 0
utah-pg 745 0
utahddc-ig 745 0
wisconsin-ig 0 15

Additional Stitching Topologies

Complex and large topologies have been tested. A few RSpecs are provided here as examples that can be referenced and modified to be used at other sites:

Topology Description Sites in topology RSpec
Three nodes linear GPO IG <-> Utah PG <-> Utah IG stitch-3linear.rspec
Triangle topology Utah PG<->UKY PG<-> GPO IG <-> Utah PG stitch-triangle.rspec
Star topology Center=UtahDDC IG; Outer=UKY PG, Utah PG, Utah IG, GPO IG stitch-star-ddc.rspec

Warning: GENI Network Stitching is actively being developed and tested, which may make the Network Stitching feature unreliable for experiments.

If additional help is needed please contact