Changes between Version 1 and Version 2 of GeniNetworkStitchingTestStatus/GNS-T6


Ignore:
Timestamp:
06/11/13 10:16:28 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/GNS-T6

    v1 v2  
    44This page captures status and execution details for Topology 6 - Utah PG to GPO InstaGENI.   For overall status see the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestStatus GENI Network Stitching Test Status] page and for test details see  the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestPlan GENI Network Stitching Test Plan] page.
    55
    6 ''Last update: 06/06/13''
     6''Last update: 06/11/13''
    77
    88|| '''Step''' || '''State'''              || ''' Ticket ''' || '''Comments''' ||
     9|| Step 1     || || || ||
     10|| Step 2     || || || ||
     11|| Step 3     || || || ||
     12|| Step 4     || || || ||
     13|| Step 5     || || || ||
     14|| Step 6     || || || ||
     15|| Step 7     || || || ||
     16|| Step 8     || || || ||
     17|| Step 9     || || || ||
     18|| Step 10    || || || ||
    919
    1020[[BR]]
     
    1727|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
    1828[[BR]]
     29
     30
     31= Test Execution =
     32
     33'''Assumptions:'''
     34 - pgeni.gpolab.bbn.com credential are used for tests in this page.
     35
     36'''Notes:'''
     37 - Stitcher currently does not support AM API v3, and is delivered to run AM API V2.
     38
     39== GNS-T1 - Utah ProtoGENI to GPO InstaGENI ==
     40
     41Verify 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.
     42
     43=== Step 1. Create sliver ===
     44
     45As 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.
     46
     47=== Step 2. Verify Request RSpec for each Stitching Path Aggregate ===
     48Verify that request RSpec is expanded after Path Computation into one RSpec for each Stitching Path Aggregates (PG Utah, ION, and IG GPO).
     49
     50=== Step 3. Verify VLAN negotiation for PG Utah ===
     51Verify that workflow agent negotiates VLAN with Utah ProtoGENI using the RSpec from step 2 and generates a manifest for PG Utah resources.
     52
     53=== Step 4. Verify VLAN negotiation for IG GPO ===
     54Verify that workflow agent negotiates VLAN with GPO InstaGENI using the GPO RSpec from step 2 and generates a manifest for GPO resources.
     55
     56=== Step 5. Verify VLAN negotiation for I2/ION aggregate ===
     57Verify that workflow agent negotiates VLAN with ION using the ION RSpec from step 2 and generates a manifest for ION resources.
     58
     59=== Step 6. Verify combined Manifest RSpec ===
     60Verify that the final "combined" RSpec reflects the allocate stitching and non-stitching resources.
     61
     62=== Step 7. End-point to end-point measurements ===
     63
     64Log in to compute resources at each Utah ProtoGENI and GPO InstaGENI, gather delay and throughput measurements. Leave traffic exchange running between the end-hosts.
     65
     66=== Step 8. Operator review of experiment resources ===
     67As Operator, verify that nodes, ports, links, capacity can be determined as allocated for this experiment.
     68
     69=== Step 9. Sliver expiration and resource de-allocation ===
     70As Experimenter, leave resources running with traffic being exchanged. Allow sliver to expire, verify that sliver resources/traffic have been deleted.
     71
     72=== Step 10. Operator verify resources release ===
     73As Operator, verify that expired resource resources (nodes, ports, links, capacity) are released properly and made available and part of the Advertisement RSpec.