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


GENI Network Stitching Sites

Last update: 2015-01-21

The following 15 sites have been tested and are available for GENI Network Stitching experiments:

Site NameNickname Stitching RSpecs
GPO ExoGENI gpo-eg here
GPO InstaGENI gpo-ig here
Mid-Atlantic Crossroads (MAX) InstaGENI max-ig here
NYSERNet InstaGENI (*) nysernet-ig here
Naval Postgraduate School nps-ig here
Rutgers University rutgers-ig here
Stanford InstaGENI stanford-ig here
University of Illinois illinois-ig here
University of Kentucky ProtoGENI uky-pg here
University of Kentucky PKS2 ukypks2-ig here
University of Missouri InstaGENI missouri-ig here
University of Utah Downtown Data Center InstaGENI utahddc-ig here
University of Utah InstaGENI utah-ig here
University of Utah ProtoGENI utah-pg here
University of Wisconsin (*)wisconsin-ig here

(*) Note: Wisconsin is now connected to AL2s and will become available for stitching by experimenter soon.

Stitching is possible between all of the above InstaGENI and ExoGENI sites. Testing has verified most point-to-point combinations for the sites listed above. Only one combination does not work at this time: GPO ExoGENI to PG UKY. 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 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, 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 available at Stitching Sites:

The following is the VLAN count for each site:

gpo-eg 30
gpo-ig 30
illinois-ig 10
max-ig 62
missouri-ig 10
nps-ig 14
nysernet-ig 20
rutgers-ig 09
stanford-ig 10
uky-pg 10
ukypks2-ig 19
utah-ig 745
utah-pg 745
utahddc-ig 745
wisconsin-ig 10

Additional Stitching Topologies

Some more complex topologies have been also tested, and those 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