HAbackupRecover at 27 May 2018 08:41:40
commit e8d5f41f62fce2156b02a2fc5f23d415206da309 (HEAD -] onos-1.13, origin/onos-1.13)
Author: Andreas Pantelopoulos [andreas@opennetworking.org]
AuthorDate: Tue May 1 14:56:05 2018 -0700
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Fri May 25 01:00:12 2018 +0000
Refactored DestinationSet and nextobj for pws.
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 ONOS package - PASS
- 1.4 Starting Mininet - PASS
- 1.5 Creating ONOS package - PASS
- 1.6 Installing ONOS package - PASS
- 1.7 Set up ONOS secure SSH - PASS
- 1.8 Checking ONOS service - PASS
- 1.9 Starting ONOS CLI sessions - PASS
- 1.10 Checking ONOS nodes - PASS
- 1.11 Activate apps defined in the params file - No Result
- 1.12 Set ONOS configurations - PASS
- 1.13 Check app ids - PASS
- 1.14 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 - PASS
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 - PASS