Changes between Version 10 and Version 11 of OpenFlow/FOAM/Testing
- Timestamp:
- 05/02/12 11:16:34 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/FOAM/Testing
v10 v11 29 29 * 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 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.) 31 * On the FOAM server you're testing, when the 'www-data' user runs a cron job that has output, it sends mail to 'www-data', and you can receive this mail. 31 32 32 33 You 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. … … 229 230 }}} 230 231 231 Confirm that the sliver was a uto-approved: Check that 'status' is "Approved", and that the sliver shows up in FlowVisor, with two flowspace rules:232 Confirm that the sliver was approved at creation time: Check that 'status' is "Approved", and that the sliver shows up in FlowVisor, with two flowspace rules: 232 233 233 234 {{{ … … 245 246 }}} 246 247 247 (Within a minute (when the cron job fires), that should generate a message to gpo-opssaying 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.)248 (Within a minute (when the cron job fires), that should generate a message to www-data 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.) 248 249 249 250 Disable the sliver, to put it back into the pending queue: … … 271 272 }}} 272 273 273 (Within a minute (when the cron job fires), that should generate a message to gpo-opssaying that the cron job ran; and e-mail to the FOAM admin with a list of pending slivers, including your test sliver.)274 (Within a minute (when the cron job fires), that should generate a message to www-data saying that the cron job ran; and e-mail to the FOAM admin with a list of pending slivers, including your test sliver.) 274 275 275 276 Clean up the cron job: … … 343 344 The steps in this section look at a newly-created sliver, and test expiration in FOAM, by changing its expiration date and, then running the scripts that expire slivers and notify about soon-to-expire ones. 344 345 345 First, review and approve the sliver. 346 347 Show the sliver, and confirm that 'status' is "Pending": 346 Confirm that the sliver was approved at creation time: Check that 'status' is "Approved", and that the sliver shows up in FlowVisor, with two flowspace rules: 348 347 349 348 {{{ 350 349 ssh $foamserver foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd 351 }}}352 353 Confirm that the sliver doesn't yet show up in FlowVisor:354 355 {{{356 ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename357 }}}358 359 (Expect a "slice does not exist" error.)360 361 Show the sliver's rspec:362 363 {{{364 ssh $foamserver foamctl geni:show-sliver -r -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd365 }}}366 367 Show the sliver's flowspec:368 369 {{{370 ssh $foamserver foamctl geni:show-sliver -s -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd371 }}}372 373 Show the sliver's flowspace rules:374 375 {{{376 ssh $foamserver foamctl geni:show-sliver -f -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd377 }}}378 379 Approve the sliver, and confirm that 'status' is now "Approved":380 381 {{{382 ssh $foamserver foamctl geni:approve-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd383 ssh $foamserver foamctl geni:show-sliver -u $sliver_urn --passwd-file=/opt/foam/etc/foampasswd384 }}}385 386 (That should generate a "sliver approved" e-mail message, one to the experimenter and one to the FOAM admin.)387 388 Confirm that the sliver now shows up in FlowVisor, with two flowspace rules:389 390 {{{391 350 ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd getSliceInfo $fv_slicename 392 351 ssh $fvserver fvctl --passwd-file=/etc/flowvisor/fvpasswd listFlowSpace | grep $fv_slicename 393 352 }}} 394 353 395 ( 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.)354 (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.) 396 355 397 356 Now, do some tests to make sure FOAM notifies you about a sliver that will expire within a day, but only once. … … 418 377 }}} 419 378 420 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)379 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 421 380 422 381 Add the cron job again, to confirm that it doesn't send a second notification: … … 426 385 }}} 427 386 428 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)387 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 429 388 430 389 Next, test to make sure FOAM notifies you again if you change the expiration date. … … 445 404 }}} 446 405 447 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)406 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 448 407 449 408 Next, do some tests to make sure that FOAM notifies you about a sliver that will expire within a week, but only once. … … 464 423 }}} 465 424 466 (Within a minute (when the cron job fires), that should generate a "sliver expiring soon" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)425 (Within a minute (when the cron job fires), that should generate a "sliver expiring soon" e-mail message, one to the experimenter and one to the FOAM admin; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 467 426 468 427 Add the cron job again, to confirm that it doesn't send a second notification: … … 472 431 }}} 473 432 474 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)433 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 475 434 476 435 Next, test to make sure FOAM doesn't notify you at all if your sliver is expiring more than a week from now. … … 491 450 }}} 492 451 493 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to gpo-opssaying that the cron job ran.)452 (Within a minute (when the cron job fires), that should generate no messages about slivers expiring in the future; no messages about expired slivers being deleted; and one message to www-data saying that the cron job ran.) 494 453 495 454 Finally, test to make sure FOAM deletes a sliver if its expiration date is in the past. … … 510 469 }}} 511 470 512 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; a "sliver expired" message, one to the experimenter and one to the FOAM admin; and one message to gpo-opssaying that the cron job ran.)471 (Within a minute (when the cron job fires), that should generate a "sliver expiring shortly" e-mail message, one to the experimenter and one to the FOAM admin; a "sliver expired" message, one to the experimenter and one to the FOAM admin; and one message to www-data saying that the cron job ran.) 513 472 514 473 Confirm that the sliver no longer shows up in FOAM:
