| Jon Hall | a478b85 | 2017-12-04 15:00:15 -0800 | [diff] [blame] | 1 | This test is designed to verify that an ONOS cluster behaves correctly when some |
| 2 | ONOS nodes are upgrade. Then test will initilize the upgrade then stop, upgrade, |
| 3 | and restart a minority of the nodes in the cluster. Then we will start the first |
| 4 | phase of the upgrade process to transfer to the new version. Then we will roll-back |
| 5 | the upgrade, Restarted the upgraded nodes with the older version. After that the |
| 6 | test will verify everything works and reset the upgrade. |
| 7 | |
| 8 | As written, the test only supports an ONOS cluster of 3, 5, or 7 nodes. |
| 9 | This is because the test doesn't apply to a single node cluster and ONOS clusters |
| 10 | should be deployed in odd numbers. |
| 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 | - Initialize an upgrade |
| 21 | - Upgrade some ONOS nodes |
| 22 | - Verify ONOS state and functionality |
| 23 | - Transfer to new version |
| 24 | - Upgrade the rest of the nodes |
| 25 | - Verify ONOS state and functionality |
| 26 | - Commit the upgrade |
| 27 | - Dataplane failures |
| 28 | - link down and up |
| 29 | - switch down and up |