Changes between Version 46 and Version 47 of GeniNetworkStitchingTestStatus/Functional


Ignore:
Timestamp:
06/10/13 09:52:09 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/Functional

    v46 v47  
    1 
     1[[PageOutline]]
    22= Stitching Functional Tests =
    33
     
    3838
    3939
    40 == GENI AM API Functions ==
     40== 1.0 GENI AM API Functions ==
    4141
    4242The following GENI AM API functions are verified in managing stitching resources using GENI AM API V3. The GCF tool (stitcher.py) negotiates to V2 when an aggregate does not support V3.
    4343
    44 === List Resources for aggregate ===
     44=== 1.1 List Resources for aggregate ===
    4545List resources for the 4 aggregate listed in the assumptions and verify that Advertisement:
    4646 - can pass rspeclint
     
    247247
    248248
    249 === Getversion ===
     249=== 1.2 Getversion ===
    250250
    251251GPO InstaGENI:
     
    588588}}}
    589589
    590 === Create Sliver ===
     590=== 1.3 Create Sliver ===
    591591
    592592Using AM API V3 commands, first create a slice and then using stitcher.py create a sliver (allocate, provision, perform operational action start/stop/restart)  from GPO InstaGENI to Utah InstaGENI.  Create slice:
     
    10921092'''Note:''' Could not use V3 provision and poa functions with stitcher.py, slivers were ready after the allocate command.
    10931093
    1094 === List resources for sliver ===
     1094=== 1.4 List resources for sliver ===
    10951095
    10961096Could not use describe function with stitcher.py:
     
    11161116'''Note:''' Could not use V3 describe function with stitcher.py.
    11171117
    1118 === Sliver status ===
     1118=== 1.5 Sliver status ===
    11191119
    11201120Could not use the V3 status command with stitcher.py:
     
    11851185'''Note:''' Could not use the V3 status command with stitcher.py
    11861186
    1187 === Renew sliver ===
     1187=== 1.6 Renew sliver ===
    11881188First slice expiration, renew slice and then sliver:
    11891189{{{
     
    12481248}}}
    12491249
    1250 === Delete sliver ===
     1250=== 1.7 Delete sliver ===
    12511251Could not use V3 delete command:
    12521252{{{
     
    13121312'''Note:''' Could not use V3 delete command
    13131313
    1314 === Shutdown Sliver ===
     1314=== 1.8 Shutdown Sliver ===
    13151315
    13161316Ran shutdown on stitched slice ln-ext1:
     
    13391339
    13401340
    1341 == GENI RSpec Support ==
     1341== 2.0 GENI RSpec Support ==
    13421342
    13431343GENI RSpec support tests validate that each of the RSpec (Advertisement, Manifest, and Request) provide complete and accurate information.
     
    13901390
    13911391
    1392 === Stitching Extensions ===
     1392=== 2.1 Stitching Extensions ===
    13931393
    13941394Verified that request RSpec with stitching extension results in an extension being used. The sliver in the functional test was also created with an RSpec that did include the stitching extension. No issues found.
     
    14031403 
    14041404
    1405 === Requests RSpec validation ===
     1405=== 2.2 Requests RSpec validation ===
    14061406
    14071407Verified RSpec Versions 3 support by the creation of the sliver in the functional test which used a V3 RSpec. Rspec is attached as [http://groups.geni.net/geni/attachment/wiki/GeniNetworkStitchingTestStatus/Functional/stitch-ig-gpo-ig-utah.rspec stitch-ig-gpo-ig-utah.rspec].
     
    16521652
    16531653 
    1654 === Bandwidth and VLAN Negotiation ===
     1654=== 2.3 Bandwidth and VLAN Negotiation ===
    16551655
    16561656The stitcher tool does not directly negotiate bandwidth. Bandwidth can be requested in the link property element. Some aggregates along the network path may refuse the bandwidth request and allocate some other amount.
     
    17611761
    17621762
    1763 === RSpec Input Validation ===
     1763=== 2.4 RSpec Input Validation ===
    17641764Test in this section validated the handling of various RSpec input scenarios:
    17651765
    1766 ==== 1. Request link with only 1 component_manager tag ====
     1766==== 2.4.1 Request link with only 1 component_manager tag ====
    17671767The following RSpec was used defining only one component_manager for PG Utah and not including the IG Utah component_manager:
    17681768{{{
     
    18221822}}}
    18231823
    1824 ==== 2. Request link with 2 interface_ref elements but no component_manager elements ====
    1825 ==== 3. Request link with 2 local interface_ref elements and 1 remote interface_ref element ====
    1826 ==== 4. Request link with an interface_ref whose client_id is not the ID for any interface in the RSpec ====
    1827 ==== 5. Request stitching extension with a path that has 0 hops ====
    1828 ==== 6. Request capacity that is below minimum and above maximum reservable Capacity ====
    1829 ==== 7. Invalid Path options ====
     1824==== 2.4.2 Request link with 2 interface_ref elements but no component_manager elements ====
     1825==== 2.4.3 Request link with 2 local interface_ref elements and 1 remote interface_ref element ====
     1826==== 2.4.4 Request link with an interface_ref whose client_id is not the ID for any interface in the RSpec ====
     1827==== 2.4.5 Request stitching extension with a path that has 0 hops ====
     1828==== 2.4.6 Request capacity that is below minimum and above maximum reservable Capacity ====
     1829==== 2.4.7 Invalid Path options ====
    18301830(not sure what this is and how to do it ?)
    18311831  - Invalid Routing profiles (not sure what this is and how to do it ?)