Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
HAbackupRecover at 02 Sep 2018 18:55:03
commit c3e0c600cce48efab8827c5e5260a491d7ea7a73 (HEAD -] master, origin/master, origin/HEAD)
Author: Daniel Park [dan.mcpark84@gmail.com]
AuthorDate: Thu Aug 30 21:27:25 2018 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Fri Aug 31 02:30:58 2018 +0000
Fixes to deal with unsupported vendor type interface in OpenstackSwitchingDirectPortProvider
Case 1: Starting up 7 node(s) ONOS cluster - PASS
Set up ONOS with 7 node(s) ONOS cluster
- 1.1 Constructing test variables - PASS
- 1.2 Apply cell to environment - PASS
- 1.3 Uninstalling Atomix - PASS
- 1.4 Uninstalling ONOS package - PASS
- 1.5 Starting Mininet - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing Atomix - PASS
- 1.8 Installing ONOS package - PASS
- 1.9 Set up ONOS secure SSH - PASS
- 1.10 Checking ONOS service - PASS
- 1.11 Starting ONOS CLI sessions - PASS
- 1.12 Checking ONOS nodes - PASS
- 1.13 Checking ONOS applications - PASS
- 1.14 Checking ONOS nodes - PASS
- 1.15 Activate apps defined in the params file - No Result
- 1.16 Set ONOS configurations - PASS
- 1.17 Check app ids - PASS
- 1.18 Set logging levels - PASS
Case 2: Assigning devices to controllers - PASS
Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.
- 2.1 Assign switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 21: Assigning Controller roles for switches - FAIL
Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'
- 21.1 Assign mastership of switches to specific controllers - PASS
- 21.2 Check mastership was correctly assigned - FAIL
- Switches were not successfully reassigned