HAswapNodes at 26 Jul 2017 00:57:54
commit cfef6f9963093b87c7f8b16a10392be63f409d91 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Tue Jul 25 16:58:42 2017 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Tue Jul 25 16:58:53 2017 -0700
ONOS-6833: UiPreferencesService: augment to include getPreferences(username, prefsKey)
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 Setup server for cluster metadata file - PASS
- 1.5 Generate initial metadata file - PASS
- 1.6 Starting Mininet - PASS
- 1.7 Copying backup config files - PASS
- 1.8 Creating ONOS package - PASS
- 1.9 Installing ONOS package - PASS
- 1.10 Set up ONOS secure SSH - PASS
- 1.11 Starting ONOS service - PASS
- 1.12 Starting ONOS CLI sessions - PASS
- 1.13 Checking ONOS nodes - PASS
- 1.14 Activate apps defined in the params file - No Result
- 1.15 Set ONOS configurations - PASS
- 1.16 App Ids check - 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
Case 3: Adding host Intents - PASS
Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - PASS