Page History

...

<img src="https://onos-jenkins.onlab.usonosproject.org/view/QA/job/Pipeline_postjob_-VM/lastSuccessfulBuild/artifact/HAfullNetPartition_unexpected ONOS branchmaster_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0">

commit 37f80912503813c8a9027ab0353434a974ff43c9 581c8407e613a27aaa573a600828b30a37066fb8 (HEAD, origin/master, origin/HEAD, master)
Author: Sean Condon pierventre [seanpier@opennetworking.condon@microsemi.comorg]
AuthorDate: Tue Feb 27 22Thu Sep 23 19:03:58 2018 14 2021 +00000200
Commit: Sean Condon [sean.condon@microsemi.comPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Wed Feb 28 08:41:06 2018 Mon Sep 27 19:27:55 2021 +0000
Refactor of CFM code part3 - Microsemi driver
[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)

Case 1:

...

Constructing test variables and building ONOS package - PASS

For loading from params file, and pull and build the latest ONOS packageSet up ONOS with 7 node(s) ONOS cluster

• 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.4 5 Starting Mininet - PASS
• 1.5 6 Creating ONOS package - PASS
• 1.7 Installing Atomix - PASS
• 1.6 8 Installing ONOS package - PASS
• 1.7 9 Set up ONOS secure SSH - PASS
• 1.8 10 Checking ONOS service - PASS
• 1.9 11 Starting ONOS CLI sessions - PASS
• 1.12 Checking ONOS nodes - PASS
• 1.13 Checking ONOS applications - PASS
• 1.10 14 Checking ONOS nodes - PASS
• 1.11 15 Activate apps defined in the params file - No Result
• 1.12 16 Set ONOS configurations - FAIL
Failed to set config
• PASS
• 1.13 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 - FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 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 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 3: Adding host Intents - FAIL