Changes between Version 27 and Version 28 of OpenFlow/FOAM/Testing
- Timestamp:
- 06/25/12 10:56:09 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/FOAM/Testing
v27 v28 531 531 * Four that specify ethertypes: The first two don't overlap, the third overlaps with one of the first two, the fourth overlaps with all of the first three. 532 532 * One that specifies a subnet, a MAC address, and an ethertype, each of which overlaps with one of the rspecs in the corresponding one of the three groups above. 533 * One that includes a more complex flowspace: Asubnet that doesn't overlap with anything else, but also an entire VLAN (which should not be auto-approved).534 * One that includes two ports that are in a you-can-only-have-one-of-these port group. (FIXME: What does FOAM actually call this? And for that matter, how do you set it?)533 * One that includes a subnet that doesn't overlap with anything else, but also an entire VLAN (which should not be auto-approved). 534 * Five that test various combinations of port groups. 535 535 536 536 {{{ … … 935 935 This subsection tests the behavior of FOAM when new slivers are created and geni.approval.approve-on-creation is set to 1 (always). The expected behavior is that all slivers will automatically be approved after they're created. 936 936 937 Note that we don't test port groups in mode 1, assuming that if an admin is going to always auto-approve everything, they wouldn't even create port groups in the first place. 938 937 939 Double-check the FOAM server's current configuration: 938 940 … … 1061 1063 1062 1064 This subsection tests the behavior of FOAM when new slivers are created and geni.approval.approve-on-creation is set to 0 (never). The expected behavior is that all slivers will automatically be pending after they're created. 1065 1066 Note that we don't test port groups in mode 0, assuming that if an admin is going to never auto-approve anything, they wouldn't even create port groups in the first place. 1063 1067 1064 1068 Double-check the FOAM server's current configuration: