blob: ee84051216f3808705e6ea22e8d872cbf05011f3 [file] [log] [blame]
Jon Hallb3ed8ed2015-10-28 16:43:55 -07001This test is designed to verify that an ONOS cluster behaves correctly when some
2ONOS nodes are stopped. Currently, we will stop nodes so that each raft partition will
Jon Hall3b489db2015-10-05 14:38:37 -07003lose a member, but we make sure that there is always a majority of nodes
4available in each partition.
5
6As written, the test only supports an ONOS cluster of 3,5, or 7 nodes.
7This is because the test doesn't apply to a single node cluster, ONOS clusters
8should be deployed in odd numbers, and the partition generation and node
9killing scheme used doesn't give the same properties for clusters of more
10than 7 nodes. Namely, each partition won't have exactly one node killed.
11
12The 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
Jon Hallb3ed8ed2015-10-28 16:43:55 -070020- Stop some ONOS nodes
21- Verify ONOS state and functionality
22- Restart nodes
Jon Hall3b489db2015-10-05 14:38:37 -070023- Verify ONOS state and functionality
24- Dataplane failures
25 - link down and up
26 - switch down and up