Changes between Version 4 and Version 5 of GeniNetworkStitchingTestStatus/Functional


Ignore:
Timestamp:
06/06/13 08:42:53 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/Functional

    v4 v5  
    66''Last update: 06/06/13''
    77
    8 || '''Function''' || '''State'''              || ''' Ticket ''' || '''Comments''' ||
     8|| '''Function'''        || '''State'''              || ''' Ticket ''' || '''Comments''' ||
     9|| GENI AM API Functions ||  || || ||
     10|| RSpec Support         ||  || || ||
     11||Negative and Boundary  ||  || || ||
     12
    913
    1014[[BR]]
     
    2125
    2226Assumptions:
    23  - It is expected that aggregates will not support GENI AM API V3 before GEC17, and that the GCF tool (stitcher.py will negotiate to GENI AM API V2. 
     27 - It is expected that aggregates will not support GENI AM API V3 before GEC17, and that the GCF tool (stitcher.py) will negotiate to GENI AM API V2. 
    2428
    2529== GENI AM API Functions ==
     
    8892 - Request a VLAN that is already in use, verify handling.
    8993 - Create a request race condition where two slices (Slice1 and Slice2) request the same resources (AM1 <->VLAN1<->AM2), but Slice1 gets VLAN1 at AM1 and Slice2 gets VLAN1 at AM2. Verify results tools handle the results and properly handle resources.
    90  - Psuedo Loop Scenario:  Request PG Utah to ION to IG GPO. Then request a 2nd interface at PG Utah node to ION to same interface on same node at IG GPO.  If that fails, then request a 2nd interface on that node at IG GPO - that should work.
     94 - Pseudo Loop Scenario:  Request PG Utah to ION to IG GPO. Then request a 2nd interface at PG Utah node to ION to same interface on same node at IG GPO.  If that fails, then request a 2nd interface on that node at IG GPO - that should work.
    9195