...
| Policy | Test case | ||
|---|---|---|---|
| Network Rule | Add and verify local network policy.
| ||
Verify traffic goes over the network with the highest priority
| |||
| Verify traffic goes over the network with the healthiest local NI even though it might not be set to highest priority | |||
| Delete local network policy and verify it has been deleted | |||
| Verify traffic returns to normal pattern when network policy is deleted | |||
| Error handling: Add policy for non-existent network | |||
| Add and verify a remote network policy. IE messages will need to be routed to that network | |||
| Verify traffic is routed to the remote network with the highest priority | |||
| Verify traffic is routed to another available network given the highest priority remote network is not reachable. | |||
| Delete remote network policy and verify it has been deleted | |||
| Verify traffic returns to normal pattern when remote network policy is deleted. | |||
| Error handling: Add policy for non-existent remote network | |||
| NID Rules | Add and verify local NID rule | ||
Verify traffic goes over the local NID with the highest priority | |||
| Verify traffic goes over the healthiest NID even if it has lower priority | |||
Delete NID policy and verify it has been deleted | |||
| Verify traffic goes back to regular pattern after NID policy is deleted. | |||
Error handling: Add policy for non-existent NID | |||
| Repeat the above tests for remote NID | |||
| NID Pair Rules | Add and verify NID Pair Rule → TODO: how do you verify that a NID Pair rule has been applied correctly. We need to show the preferred NID list in the show command. This also applies to Router Rules. | ||
| Verify traffic goes over the preferred Local NIDs | |||
| Delete NID pair rule a and verify it has been deleted | |||
| Verify traffic goes back to regular pattern after NID Pair policy is deleted. | |||
| Error handling: Add a policy that don't match any local NIDs. This should be a no-op | |||
| Router Rules | Same set of tests as above but for routers | ||
| Subsequent Addition | For each of the policy types, add a policy which doesn't match any thing currently configured. Verify that policy is added irregardless | ||
Add an LNet construct (Net, NI, Route) which matches an existing policy. Verify that policy has been applied on construct → TODO: Show commands like net show, peer show, etc should be modified to show the result of the policy application. | |||
| Verify traffic adheres to policy | |||
| Delete LNet construct. Verify that policy remains. | |||
| Dynamic Policy Addition | Run traffic. For each of the policy types add a policy which should alter traffic Verify traffic patterns change when policy is added. | ||
| Policy application order | Add all types of policies. They all should match and be applied. Verify. Run traffic. Verify that policies are applied on traffic in the order of operations defined here. | ||
| Dynamic policy Deletion | Add all types of policies. Run traffic Verify that polices are applied on traffic in the order of operations defined. Delete the policy one at a time. Verify traffic pattern change with each policy deleted. |
Work Breakdown and Schedule
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Reference Links
https://www.ece.tufts.edu/~karen/classes/final_presentation/Dragonfly_Topology_Long.pptx
...