Page History

...

commit 8032d8b73cb7935c59f28ec2ad54e368266c465b 54d8243e53850adcbc340a4114a2efd19d0a998e (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@opennetworking.orgSean Condon [sean.condon@microsemi.com]
AuthorDate: Fri Aug 11 19:46:48 2017 -0700Wed Jul 26 22:27:25 2017 +0100
Commit: Simon Hunt Ray Milkey [simon@opennetworkingray@opennetworking.org]
CommitDate: Fri Tue Aug 11 1915 00:4659:48 52 2017 -0700+0000

Patch for ONOS-6730: Topo View i18n:6840 NETCONF timeouts per device

<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

Case 1: Starting

...

up

...

7 node(s)

...

ONOS

...

cluster

...

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