Changes between Version 62 and Version 63 of GeniNetworkStitchingTestStatus/Functional
- Timestamp:
- 06/11/13 08:29:16 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniNetworkStitchingTestStatus/Functional
v62 v63 8 8 || '''Function''' || '''State''' || ''' Ticket ''' || '''Comments''' || 9 9 || GENI AM API Functions ||[[Color(yellow,Complete)]] || #1031 #1036 #1039 #1040 #1043|| || 10 || RSpec Support ||[[Color(#63B8FF,In Progress)]]|| #1037 #1038 [http://trac.gpolab.bbn.com/gcf/ticket/300 gcf ticket 300] #1048 #1049 || ||10 || RSpec Support ||[[Color(#63B8FF,In Progress)]]|| #1037 #1038 [http://trac.gpolab.bbn.com/gcf/ticket/300 gcf ticket 300] #1048 #1049 #1050 || || 11 11 ||Negative and Boundary || || || || 12 12 … … 1904 1904 .... 1905 1905 }}} 1906 Using the rspec above RSpec results in a1906 Using the rspec above RSpec results in the rspec being evaluated as a multi-point topology, which is not supported until after GEC 17. 1907 1907 1908 1908 {{{ … … 1929 1929 1930 1930 ==== 2.4.4 Request link with an interface_ref whose client_id is not the ID for any interface in the RSpec ==== 1931 1931 1932 An RSpec that has interface_ref that use client_ids not in the interfaces defined in the RSpec was defined, which looks as follows: 1932 1933 {{{ … … 1978 1979 1979 1980 ==== 2.4.5 Request stitching extension with a path that has 0 hops ==== 1981 1980 1982 Created a request RSpec that meets that defines a 0 hop scenario from PG Utah to PG Utah: 1981 1983 {{{ … … 2256 2258 Note: Stitcher continues to run and keeps requesting this invalid request. #1049 2257 2259 2258 ==== 2.4.8 Invalid Path input - Invalid Routing profiles ==== 2260 ==== 2.4.8 Invalid Path options ==== 2261 2262 Verify the options (geni_hold_path, geni_start_time, geni_end_time) defined at http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingAPI. 2263 2264 Note: These options are not yet available via the GENI AM API. Ticket #1050 2265 2266 ==== 2.4.9 Invalid Routing profiles ==== 2259 2267 2260 2268 (not sure what this is and how to do it ?) … … 2262 2270 ==== 2.4.9 Invalid Path input - Include/exclude invalid VLANs ==== 2263 2271 2264 FIgure out??? 2272 For this scenario, the initial plan was to have a stitching path added to the RSpec requesting both a valid and an invalid VLAN. 2273 Working on figuring out the syntax. (TODO) 2274 2275 2265 2276 2266 2277 === 2.5 Advertisement RSpecs ===