HAfullNetPartition at 14 Oct 2018 06:19:03

commit 615e98a90cc01cad04e8dd8a388ade39457d5e14 (HEAD -] onos-1.14, origin/onos-1.14)
Author: Saurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Thu Oct 11 15:29:24 2018 -0700
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Fri Oct 12 00:03:16 2018 +0000
Allow applications to specify a few other packet-request flow priorities.
--
(cherry picked from commit 6f58cf1e5aae371cb8c7e0ad69552f3e68672f05)
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 - 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