| Jon Hall | 0e24037 | 2018-05-02 11:21:57 -0700 | [diff] [blame] | 1 | This test is designed to verify that an ONOS cluster behaves correctly when |
| 2 | ONOS nodes die due to power failures. Currently, we will kill nodes so that |
| 3 | each raft partition will lose a member, but we make sure that there is always |
| 4 | a majority of nodes available in each partition. |
| 5 | |
| 6 | As written, the test only supports an ONOS cluster of 3,5, or 7 nodes. |
| 7 | This is because the test doesn't apply to a single node cluster, ONOS clusters |
| 8 | should be deployed in odd numbers, and the partition generation and node |
| 9 | killing scheme used doesn't give the same properties for clusters of more |
| 10 | than 7 nodes. Namely, each partition won't have exactly one node killed. |
| 11 | |
| 12 | The gerneral structure for the test: |
| 13 | - Startup |
| 14 | - Assign switches |
| 15 | - Verify ONOS state and functionality |
| 16 | - Device mastership |
| 17 | - Intents |
| 18 | - Leadership election |
| 19 | - Distributed Primitives |
| 20 | - Kill some ONOS nodes |
| 21 | - Verify ONOS state and functionality |
| 22 | - Restart ONOS nodes |
| 23 | - Verify ONOS state and functionality |
| 24 | - Dataplane failures |
| 25 | - link down and up |
| 26 | - switch down and up |