| 19 | |
| 20 | |
| 21 | = Test Execution = |
| 22 | |
| 23 | '''Assumptions:''' |
| 24 | - pgeni.gpolab.bbn.com credential are used for tests in this page. |
| 25 | |
| 26 | '''Notes:''' |
| 27 | - Stitcher currently does not support AM API v3, and is delivered to run AM API V2. |
| 28 | - Capacity '''must''' be specified for scenarios where Utah IG is end-point. |
| 29 | |
| 30 | == GNS-T1 - Utah InstaGENI to GPO InstaGENI == |
| 31 | |
| 32 | Verify stitching path for a scenario that has the end-points Utah and GPO InstaGENI via Internet2 ION. This scenario will verify experimenter functions and some operator functions as described below. |
| 33 | |
| 34 | === 1. Create sliver === |
| 35 | |
| 36 | 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. |
| 37 | === 2. Verify Request RSpec for each Stitching Path Aggregate === |
| 38 | Verify that request RSpec is expanded after Path Computation into one RSpec for each Stitching Path Aggregates (IG Utah, PG Utah, ION, and IG GPO). |
| 39 | |
| 40 | === 3. Verify VLAN negotiation for IG Utah === |
| 41 | Verify that workflow agent negotiates VLAN with Utah InstaGENI using the RSpec from step 2 and generates a manifest for IG Utah resources. |
| 42 | |
| 43 | === 4. Verify VLAN negotiation for PG Utah === |
| 44 | Verify that workflow agent negotiates VLAN with Utah ProtoGENI using the RSpec from step 2 and generates a manifest for PG Utah resources. |
| 45 | |
| 46 | === 5. Verify VLAN negotiation for IG GPO === |
| 47 | Verify that workflow agent negotiates VLAN with GPO InstaGENI using the GPO RSpec from step 2 and generates a manifest for GPO resources. |
| 48 | |
| 49 | === 6. Verify VLAN negotiation for I2/ION aggregate === |
| 50 | Verify that workflow agent negotiates VLAN with ION using the ION RSpec from step 2 and generates a manifest for ION resources. |
| 51 | |
| 52 | === 7. Verify combined Manifest RSpec === |
| 53 | Verify that the final "combined" RSpec reflects the allocate stitching and non-stitching resources. |
| 54 | |
| 55 | === 8. End-point to end-point measurements === |
| 56 | |
| 57 | Log in to compute resources at each Utah InstaGENI and GPO InstaGENI, gather delay and throughput measurements. Leave traffic exchange running between the end-hosts. |
| 58 | |
| 59 | === 9. Operator review of experiment resources === |
| 60 | As Operator, verify that nodes, ports, links, capacity can be determined as allocated for this experiment. |
| 61 | |
| 62 | === 10 Sliver expiration and resource de-allocation === |
| 63 | As Experimenter, leave resources running with traffic being exchanged. Allow sliver to expire, verify that sliver resources/traffic have been deleted. |
| 64 | |
| 65 | === Operator verify resources release === |
| 66 | As Operator, verify that expired resource resources (nodes, ports, links, capacity) are released properly and made available and part of the Advertisement RSpec. |