Master-HA Full Network Partition

commit 9417e13b3d9d764f9ec94691ef6d5c1ff902a3d8 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li [pyguni@gmail.com]
AuthorDate: Tue Sep 7 15:13:42 2021 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Wed Sep 8 00:55:09 2021 +0000

Support to inject controller IP address to API config for tenant NW
--
(cherry picked from commit 0a05d6fe81c13ddffa4aba674d33103df8e5121b)

Case 1: Constructing test variables and building ONOS package - PASS

For loading from params file, and pull and build the latest ONOS package

• 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 - FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 0 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• 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

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS shows 0 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 3: Adding host Intents - FAIL