Version 3 (modified by 11 years ago) (diff) | ,
---|
GNS-T3 - Topology 3 - InstaGENI Utah to GPO ExoGENI to LONI and MAX
This page captures status and execution details for Topology 3 - InstaGENI Utah to GPO ExoGENI to LONI and MAX. 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 | |||
Step 11 | |||
Step 12 | |||
Step 13 |
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
Assumptions:
- pgeni.gpolab.bbn.com credential are used for tests in this page.
Notes:
- Stitcher currently does not support AM API v3, and is delivered to run AM API V2.
GNS-T3 - InstaGENI Utah to GPO ExoGENI to LONI and MAX
Verify stitching negotiation for a scenario that has Utah InstaGENI, GPO ExoGENI and non-rack endpoints at LONI and MAX via Internet2 ION.
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 (IG Utah, PG Utah, ION, EG GPO, LONI and MAX).
Step 3. Verify VLAN negotiation for IG Utah
Verify that workflow agent negotiates VLAN with Utah InstaGENI using the RSpec from step 2 and generates a manifest for IG Utah resources.
Step 4. 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 5. Verify VLAN negotiation for EG GPO
Verify that workflow agent negotiates VLAN with GPO ExoGENI using the GPO RSpec from step 2 and generates a manifest for GPO resources.
Step 6. 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 7. Verify VLAN negotiation for LONI aggregate
Verify that workflow agent negotiates VLAN with LONI using the LONI RSpec from step 2 and generates a manifest for LONI resources.
Step 8. Verify VLAN negotiation for MAX aggregate
Verify that workflow agent negotiates VLAN with MAX using the MAX RSpec from step 2 and generates a manifest for MAX resources.
Step 9. Verify combined Manifest RSpec
Verify that the final "combined" RSpec reflects the allocate stitching and non-stitching resources.
Step 10. End-point to end-point measurements
Log in to compute resources at each Utah InstaGENI, GPO ExoGENI, LONI and MAX, gather delay and throughput measurements. Leave traffic exchange running between the end-hosts.
Step 11. Operator review of experiment resources
As Operator, verify that nodes, ports, links, capacity can be determined as allocated for this experiment.
Step 12. 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 13. 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.