Page History

...

<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/lastSuccessfulBuild/artifact/HAclusterRestart_master_20-builds_graph.jpg", alt="HAclusterRestart", style="width:525px;height:350px;border:0">

commit 45d340c8394a880f666836dca67c2d484f452977 132393a4a23dba0706fb6e19fb787561d83d69bc (HEAD, origin/master, origin/HEAD, master)
Author: ONOS Jenkins User [jenkins@onlab.usCharles Chan [rascov@gmail.com]
AuthorDate: Tue Thu Jan 9 014 14:5626:13 07 2018 +0000-0800
Commit: ONOS Jenkins User [jenkins@onlab.usCharles Chan [rascov@gmail.com]
CommitDate: Tue Jan 9 0113:5655:13 27 2018 +0000
Starting snapshot 1.13.0-SNAPSHOT-0800

CORD-2470 Fix NPEs

Case 1: Starting up 7 node(s) ONOS cluster - PASS

...

• 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

Case 3: Adding host Intents - FAIL