Page History

...

commit cb4f8fdab9be6f26d413d699153d22815c5f5963 (HEAD -] onos-1.14, origin/onos-1.14)
Author: ONOS Jenkins User [jenkins@onlab.us]
AuthorDate: Thu Aug 30 23:35:15 2018 +0000
Commit: ONOS Jenkins User [jenkins@onlab.us]
CommitDate: Thu Aug 30 23:35:15 2018 +0000

Starting snapshot 1.14.0-SNAPSHOT

Case 1: Constructing test variables and building

...

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

...

ONOS package

...

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

...

- FAIL