Changes between Version 62 and Version 63 of GeniNetworkStitchingTestStatus/Functional


Ignore:
Timestamp:
06/11/13 08:29:16 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/Functional

    v62 v63  
    88|| '''Function'''        || '''State'''                  || ''' Ticket ''' || '''Comments'''                            ||
    99|| 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 || ||
    1111||Negative and Boundary  ||  || || ||
    1212
     
    19041904....
    19051905}}}
    1906 Using the rspec above RSpec results in a
     1906Using the rspec above RSpec results in the rspec being evaluated as a multi-point topology, which is not supported until after GEC 17.
    19071907
    19081908{{{
     
    19291929
    19301930==== 2.4.4 Request link with an interface_ref whose client_id is not the ID for any interface in the RSpec ====
     1931
    19311932An RSpec that has interface_ref that use client_ids not in the interfaces defined in the RSpec was defined, which looks as follows:
    19321933{{{
     
    19781979
    19791980==== 2.4.5 Request stitching extension with a path that has 0 hops ====
     1981
    19801982Created a request RSpec that meets that defines a 0 hop scenario from PG Utah to PG Utah:
    19811983{{{
     
    22562258Note: Stitcher continues to run and keeps requesting this invalid request. #1049
    22572259
    2258 ==== 2.4.8 Invalid Path input - Invalid Routing profiles  ====
     2260==== 2.4.8 Invalid Path options ====
     2261
     2262Verify the options (geni_hold_path, geni_start_time, geni_end_time) defined at  http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingAPI.
     2263
     2264Note: These options are not yet available via the GENI AM API. Ticket #1050
     2265
     2266==== 2.4.9 Invalid Routing profiles  ====
    22592267
    22602268(not sure what this is and how to do it ?)
     
    22622270==== 2.4.9  Invalid Path input - Include/exclude invalid VLANs ====
    22632271
    2264 FIgure out???
     2272For this scenario, the initial plan was to have a stitching path added to the RSpec requesting both a valid and an invalid VLAN.
     2273Working on figuring out the syntax. (TODO)
     2274
     2275
    22652276 
    22662277=== 2.5 Advertisement RSpecs ===