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

Timestamp:

04/26/12 16:31:45 (12 years ago)

Author:

Josh Smift

Comment:

--

OpenFlow/FOAM/Testing

@@ -122 +122 @@
 NOTE: Do the [wiki:OpenFlow/FOAM/Testing#Creation Creation] section immediately before starting this section.
 
+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.
+
 The 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.
 
@@ -212 +214 @@
 
 NOTE: Do the [wiki:OpenFlow/FOAM/Testing#Creation Creation] section immediately before starting this section.
+
+NOTE: These tests assume that the default auto-approval settings are active, and that the test sliver's flowspace will be auto-approved.
 
 The 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.
@@ -227 +231 @@
 }}}
 
-Show the sliver, and confirm that 'status' is "Pending":
-
-{{{
-foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
-}}}
-
-Confirm that the sliver doesn't yet show up in FlowVisor:
-
-{{{
-fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
-}}}
-
-(Expect a "slice does not exist" error; and likewise every time you do a "confirm that the sliver doesn't show up in FlowVisor" step below.)
+Confirm that the sliver was auto-approved: Check that 'status' is "Approved", and that the sliver shows up in FlowVisor, with two flowspace rules:
+
+{{{
+ssh $foamserver foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
+ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
+ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
+}}}
+
+(Ignore warnings saying that it can't connect to the sliver's controller, if any; and likewise every time you confirm that the sliver shows up in Flowvisor below.)
 
 Add a temporary cron job to tell FOAM to generate e-mail with a list of pending slivers:
@@ -247 +247 @@
 }}}
 
-(Within a minute (when the cron job fires), that should generate e-mail to the FOAM admin with a list of pending slivers, including your test sliver; and a message to gpo-ops saying that the cron job ran.)
+(Within a minute (when the cron job fires), that should generate a message to gpo-ops saying that the cron job ran, and one of two other things will happen: (a) If there are *other* pending slivers, it should generate a message to the FOAM admin listing only those slivers, and not your test sliver; OR (b) If there are no other pending slivers, it should not send any message about pending slivers to the FOAM admin.)
+
+Disable the sliver, to put it back into the pending queue:
+
+{{{
+foamctl geni:disable-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
+}}}
+
+(That should generate a "sliver disabled" e-mail message, one to the experimenter and one to the FOAM admin.)
+
+Confirm that 'status' is now "Pending", and that the sliver now does not show up in FlowVisor, and has no flowspace rules:
+
+{{{
+foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd
+fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename
+fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename
+}}}
+
+(Expect a "slice does not exist" error for the getSliceInfo step; and likewise every time you do a "confirm that the sliver doesn't show up in FlowVisor" step below.)
+
+Add a temporary cron job to tell FOAM to generate e-mail with a list of pending slivers:
+
+{{{
+sudo sh -c "echo $(date +'%M %H' -d 'now + 1 min') '* * *  www-data  /opt/foam/bin/daily-queue ; echo foamtest cron job ran at $(date)' > /etc/cron.d/foamtest"
+}}}
+
+(Within a minute (when the cron job fires), that should generate a message to gpo-ops saying that the cron job ran; and e-mail to the FOAM admin with a list of pending slivers, including your test sliver.)
+
+Clean up the cron job:
+
+{{{
+sudo rm /etc/cron.d/foamtest
+}}}
+
+This next set of tests will generate a bunch of e-mail; check at the end that it all showed up as expected.
 
 Approve the sliver, confirm that 'status' is now "Approved", and confirm that the sliver now shows up in FlowVisor, with two flowspace rules:
@@ -258 +292 @@
 }}}
 
-(Don't worry about the ouptut saying that it can't connect to the controller; this is expected if your rspec didn't include a controller that's actually running, which the example one doesn't. Likewise every time you confirm that the sliver shows up in Flowvisor below.)
-
-(That should generate a "sliver approved" e-mail message, one to the experimenter and one to the FOAM admin.)
-
-Add a temporary cron job to tell FOAM to generate e-mail with a list of pending slivers:
-
-{{{
-sudo sh -c "echo $(date +'%M %H' -d 'now + 1 min') '* * *  www-data  /opt/foam/bin/daily-queue ; echo foamtest cron job ran at $(date)' > /etc/cron.d/foamtest"
-}}}
-
-(Within a minute (when the cron job fires), either (a) if there were other slivers in the previous mail, that should generate a message to the FOAM admin listing only those slivers, and not your test sliver, or otherwise (b) not send any message to the FOAM admin; and a message to gpo-ops saying that the cron job ran.)
-
-Clean up the cron job:
-
-{{{
-sudo rm /etc/cron.d/foamtest
-}}}
-
-This next set of tests will generate a bunch of e-mail; check at the end that it all showed up as expected.
-
 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:
 
@@ -341 +355 @@
 }}}
 
-That set of tests should generate seven e-mail messages to the experimenter and seven to the FOAM admin: There should be a "sliver disabled" message, 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.
+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.
 
 == Expiration ==