Changes between Version 3 and Version 4 of GeniNetworkStitchingTestStatus/Functional


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

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/Functional

    v3 v4  
    1717|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
    1818[[BR]]
     19
     20= Test Execution =
     21
     22Assumptions:
     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. 
     24
     25== GENI AM API Functions ==
     26
     27The following GENI AM API functions are verified in managing stitching resources using GENI AM API V3. It is expected that GCF tool (stitcher.py) will negotiate to V2 for aggregates that do not support V3.
     28      * List Resources for aggregate
     29      * Getversion
     30      * Create Sliver (allocate, provion, perform operational action start/stop/restart)
     31      * List resources for sliver (describe)
     32      * Sliver status 
     33      * Renew sliver
     34      * Delete sliver
     35      * Shutdown Sliver
     36
     37
     38
     39== GENI RSpec Support ==
     40
     41GENI RSpec support tests will validate that each of the RSpec (Advertisement, Manifest, and Request) provide complete and accurate information.
     42
     43'''Stitching Extensions:''' [[BR]]
     44
     45    - Request RSpec with stitching extension -> to verify that extension is used
     46    - Request RSpec without stitching extension -> to verify that one is created
     47    - Stitching Path support:
     48      * Point-to-point path only
     49      * Multiple point-to-point
     50
     51'''Requests RSpec validation:''' [[BR]]
     52
     53   - RSpec Versions support (V3)
     54   - Routing profile options to include or exclude:
     55     * hop_include_list
     56     * hop_exclude_list
     57     * VLAN tags (exclude only)
     58  - Verify '''only''' bandwidth and VLAN are negotiable.
     59
     60
     61'''RSpec Input Validation:'' [[BR]]
     62
     63  - Request link with only 1 component_manager tag
     64  - Request link with 2 interface_ref elements but no component_manager elements
     65  - Request link with 2 local interface_ref elements and 1 remote interface_ref element
     66  - Request link with an interface_ref whose client_id is not the ID for any interface in the RSpec
     67  - Request stitching extension with a path that has 0 hops
     68  - Request capacity that is below minimum and above maximum reservable Capacity
     69  - Invalid Path options (not sure what this is and how to do it ?)
     70  - Invalid Routing profiles (not sure what this is and how to do it ?)
     71  - Include/exclude invalid VLANs
     72
     73 
     74'''Advertisement RSpecs:''' [[BR]]
     75
     76Advertisement RSpecs will be reviewed to verify that they accurately capture:
     77 - Stitching elements (nodes, ports, links, capacity)
     78 - VLAN IDs and their availability
     79 - VLAN Bandwidth capability
     80 
     81
     82== Negative and Boundary tests ==
     83
     84This is a starting list of scenarios that will validate negative and boundary conditions:
     85 - At ION, InstaGENI and ExoGENI, allocate resources that are not advertised, verify failure.
     86 - At ION, InstaGENI and ExoGENI, allocate VLAN tags that are already in use, verify failure.
     87 - Kill an ION circuit manually, verify recovery and logging of event.
     88 - Request a VLAN that is already in use, verify handling.
     89 - 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.
     91