Changes between Version 46 and Version 47 of GeniNetworkStitchingTestStatus/Functional
- Timestamp:
- 06/10/13 09:52:09 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniNetworkStitchingTestStatus/Functional
v46 v47 1 1 [[PageOutline]] 2 2 = Stitching Functional Tests = 3 3 … … 38 38 39 39 40 == GENI AM API Functions ==40 == 1.0 GENI AM API Functions == 41 41 42 42 The 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. 43 43 44 === List Resources for aggregate ===44 === 1.1 List Resources for aggregate === 45 45 List resources for the 4 aggregate listed in the assumptions and verify that Advertisement: 46 46 - can pass rspeclint … … 247 247 248 248 249 === Getversion ===249 === 1.2 Getversion === 250 250 251 251 GPO InstaGENI: … … 588 588 }}} 589 589 590 === Create Sliver ===590 === 1.3 Create Sliver === 591 591 592 592 Using 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: … … 1092 1092 '''Note:''' Could not use V3 provision and poa functions with stitcher.py, slivers were ready after the allocate command. 1093 1093 1094 === List resources for sliver ===1094 === 1.4 List resources for sliver === 1095 1095 1096 1096 Could not use describe function with stitcher.py: … … 1116 1116 '''Note:''' Could not use V3 describe function with stitcher.py. 1117 1117 1118 === Sliver status ===1118 === 1.5 Sliver status === 1119 1119 1120 1120 Could not use the V3 status command with stitcher.py: … … 1185 1185 '''Note:''' Could not use the V3 status command with stitcher.py 1186 1186 1187 === Renew sliver ===1187 === 1.6 Renew sliver === 1188 1188 First slice expiration, renew slice and then sliver: 1189 1189 {{{ … … 1248 1248 }}} 1249 1249 1250 === Delete sliver ===1250 === 1.7 Delete sliver === 1251 1251 Could not use V3 delete command: 1252 1252 {{{ … … 1312 1312 '''Note:''' Could not use V3 delete command 1313 1313 1314 === Shutdown Sliver ===1314 === 1.8 Shutdown Sliver === 1315 1315 1316 1316 Ran shutdown on stitched slice ln-ext1: … … 1339 1339 1340 1340 1341 == GENI RSpec Support ==1341 == 2.0 GENI RSpec Support == 1342 1342 1343 1343 GENI RSpec support tests validate that each of the RSpec (Advertisement, Manifest, and Request) provide complete and accurate information. … … 1390 1390 1391 1391 1392 === Stitching Extensions ===1392 === 2.1 Stitching Extensions === 1393 1393 1394 1394 Verified 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. … … 1403 1403 1404 1404 1405 === Requests RSpec validation ===1405 === 2.2 Requests RSpec validation === 1406 1406 1407 1407 Verified 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]. … … 1652 1652 1653 1653 1654 === Bandwidth and VLAN Negotiation ===1654 === 2.3 Bandwidth and VLAN Negotiation === 1655 1655 1656 1656 The 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. … … 1761 1761 1762 1762 1763 === RSpec Input Validation ===1763 === 2.4 RSpec Input Validation === 1764 1764 Test in this section validated the handling of various RSpec input scenarios: 1765 1765 1766 ==== 1.Request link with only 1 component_manager tag ====1766 ==== 2.4.1 Request link with only 1 component_manager tag ==== 1767 1767 The following RSpec was used defining only one component_manager for PG Utah and not including the IG Utah component_manager: 1768 1768 {{{ … … 1822 1822 }}} 1823 1823 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 ==== 1830 1830 (not sure what this is and how to do it ?) 1831 1831 - Invalid Routing profiles (not sure what this is and how to do it ?)