Version 2 (modified by, 8 years ago) (diff)


GNS-T6 - Topology 6 - Utah PG to GPO InstaGENI

This page captures status and execution details for Topology 6 - Utah PG to GPO InstaGENI. For overall status see the GENI Network Stitching Test Status page and for test details see the GENI Network Stitching Test Plan page.

Last update: 06/11/13

Step State Ticket Comments
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10

State Legend Description
Color(green,Pass)? Test completed and met all criteria
Color(#98FB98,Pass: most criteria)? Test completed and met most criteria. Exceptions documented
Color(red,Fail)? Test completed and failed to meet criteria.
Color(yellow,Complete)? Test completed but will require re-execution due to expected changes
Color(orange,Blocked)? Blocked by ticketed issue(s).
Color(#63B8FF,In Progress)? Currently under test.

Test Execution


  • credential are used for tests in this page.


  • Stitcher currently does not support AM API v3, and is delivered to run AM API V2.

GNS-T1 - Utah ProtoGENI to GPO InstaGENI

Verify stitching path for a scenario that has the end-points Utah ProtoGENI and GPO InstaGENI via Internet2 ION. This scenario will verify experimenter functions and some operator functions as described below.

Step 1. Create sliver

As Experimenter, use GENI AM API client to submit create sliver for initial Request RSpec. No aggregate needs to be specified, aggregates are determined from the Request RSpec.

Step 2. Verify Request RSpec for each Stitching Path Aggregate

Verify that request RSpec is expanded after Path Computation into one RSpec for each Stitching Path Aggregates (PG Utah, ION, and IG GPO).

Step 3. Verify VLAN negotiation for PG Utah

Verify that workflow agent negotiates VLAN with Utah ProtoGENI using the RSpec from step 2 and generates a manifest for PG Utah resources.

Step 4. Verify VLAN negotiation for IG GPO

Verify that workflow agent negotiates VLAN with GPO InstaGENI using the GPO RSpec from step 2 and generates a manifest for GPO resources.

Step 5. Verify VLAN negotiation for I2/ION aggregate

Verify that workflow agent negotiates VLAN with ION using the ION RSpec from step 2 and generates a manifest for ION resources.

Step 6. Verify combined Manifest RSpec

Verify that the final "combined" RSpec reflects the allocate stitching and non-stitching resources.

Step 7. End-point to end-point measurements

Log in to compute resources at each Utah ProtoGENI and GPO InstaGENI, gather delay and throughput measurements. Leave traffic exchange running between the end-hosts.

Step 8. Operator review of experiment resources

As Operator, verify that nodes, ports, links, capacity can be determined as allocated for this experiment.

Step 9. Sliver expiration and resource de-allocation

As Experimenter, leave resources running with traffic being exchanged. Allow sliver to expire, verify that sliver resources/traffic have been deleted.

Step 10. Operator verify resources release

As Operator, verify that expired resource resources (nodes, ports, links, capacity) are released properly and made available and part of the Advertisement RSpec.