Changes between Version 9 and Version 10 of OpenFlow/FOAM/Testing


Ignore:
Timestamp:
05/02/12 10:52:34 (12 years ago)
Author:
Josh Smift
Comment:

Finished revising the Complex tests section to assume approval-on-creation via the overlap analsysis engine

Legend:

Unmodified
Added
Removed
Modified

  • OpenFlow/FOAM/Testing

    v9 v10  
    33= Testing FOAM =
    44
    5 NOTE that all the foamctl commands in this section now use the new 0.7 syntax.
     5NOTE that all the foamctl commands on this page now use the new 0.7 syntax.
    66
    77This page describes a couple of ways to test FOAM:
    … …  
    2828 * You know what output to expect when common things succeed. (Expected output is described here only in cases where an error is the expected result, or where it otherwise might not be obvious; if you think the expected output isn't obvious for any given step, let us know.)
    2929 * The URL of the FOAM server is also a name that you can use to log in to it. (Very likely, but might be untrue with virtualhosts or some other odd thing.)
    30  * On the FOAM server you're testing, when you create a sliver, it's marked as Pending, and isn't automatically approved.
     30 * On the FOAM server you're testing, when you create a sliver, it will be automatically approved. (More specifically, that geni.openflow.analysis-engine = True (analyze slivers for overlap), and geni.approval.approve-on-creation = 2 (approve slivers at creation time if they don't fail any overlap-analysis tests), and the test sliver's rspec describes a flowspace that will pass overlap analysis.)
    3131
    3232You can run most of these tests wherever you usually use Omni; they don't need to run on the FOAM/FV server, except as noted below.
    … …  
    9494}}}
    9595
    96 (That should generate a "sliver created" e-mail message, one to the experimenter and one to the FOAM admin.)
     96(That should generate a "sliver created" and a "sliver approved" e-mail message, one of each to the experimenter and one of each to the FOAM admin.)
    9797
    9898Confirm that it looks right via Omni:
    … …  
    122122NOTE: Do the [wiki:OpenFlow/FOAM/Testing#Creation Creation] section immediately before starting this section.
    123123
    124 NOTE: This section is not really compatible with FOAM 0.7, which auto-approves the sliver. We need to reconsider what to do as a simple test here.
     124NOTE: This section needs to be revamped to match the new assumption that when you create a sliver, it will be automatically approved.
    125125
    126126The steps in this section look at a newly-created sliver, approve it, confirm that it shows up in the FlowVisor, delete it, and confirm that it vanishes from the FlowVisor.
    … …  
    214214
    215215NOTE: Do the [wiki:OpenFlow/FOAM/Testing#Creation Creation] section immediately before starting this section.
    216 
    217 NOTE: These tests assume that the default auto-approval settings are active, and that the test sliver's flowspace will be auto-approved.
    218216
    219217The steps in this section look at a newly-created sliver, run through a sequence of approve/disable/reject actions to confirm that it can transition from any of those states to the others, and check the FlowVisor after each change; then delete the sliver, and confirm that it vanishes from the FlowVisor.
    … …  
    234232
    235233{{{
    236 ssh $foamserver foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    237 ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
    238 ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
     234foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
     235fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
     236fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
    239237}}}
    240238
    … …  
    292290}}}
    293291
     292Reject the sliver, confirm that 'status' is now "Rejected", and confirm that the sliver now does not show up in FlowVisor, and has no flowspace rules:
     293
     294{{{
     295foamctl geni:reject-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
     296foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
     297fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
     298fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
     299}}}
     300
    294301Disable the sliver, confirm that 'status' is now "Pending", and confirm that the sliver now does not show up in FlowVisor, and has no flowspace rules:
    295302
    … …  
    319326}}}
    320327
    321 Reject the sliver, confirm that 'status' is now "Rejected", and confirm that the sliver now does not show up in FlowVisor, and has no flowspace rules:
    322 
    323 {{{
    324 foamctl geni:reject-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    325 foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    326 fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
    327 fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
    328 }}}
    329 
    330 Disable the sliver, confirm that 'status' is now "Pending", and confirm that the sliver now does not show up in FlowVisor, and has no flowspace rules:
    331 
    332 {{{
    333 foamctl geni:disable-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    334 foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    335 fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
    336 fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
    337 }}}
    338 
    339 Approve the sliver, confirm that 'status' is now "Approved", and confirm that the sliver now shows up in FlowVisor, with two flowspace rules:
    340 
    341 {{{
    342 foamctl geni:approve-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    343 foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
    344 fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
    345 fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
    346 }}}
    347 
    348328Delete the sliver, confirm that 'deleted' is now "True", and confirm that the sliver now does not show up in FlowVisor, and has no flowspace rules:
    349329
    … …  
    355335}}}
    356336
    357 That set of tests should generate eight e-mail messages to the experimenter and eight to the FOAM admin: There should be a "sliver approved" message, then "sliver disabled", then "sliver rejected", then approved, rejected, disabled, approved, and deleted. Probably in that order, although e-mail is sometimes delivered out of sequence, so don't worry too much if they're not in order.
     337That set of tests should generate six e-mail messages to the experimenter and eight to the FOAM admin: There should be a "sliver approved" message, then "sliver rejected", then "sliver disabled", then rejected, approved, and deleted. Probably in that order, although e-mail is sometimes delivered out of sequence, so don't worry too much if they're not in order.
    358338
    359339== Expiration ==