Page History

...

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAfullNetPartition_master_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0">

commit 581c8407e613a27aaa573a600828b30a37066fb8 commit ef2e63998b679c456cbb3f641cec8307263e262b (HEAD, origin/master, origin/HEAD, master)
Author: Bharat saraswal pierventre [bharatpier@opennetworking.saraswal@huawei.comorg]
AuthorDate: Tue Apr 19 Thu Sep 23 19:5003:32 2016 14 2021 +05300200
Commit: Gerrit Code Review [gerrit@onlab.usPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Apr Mon Sep 27 19 17:1727:49 2016 55 2021 +0000
YANG augment's generated file name resolver implementation and UT fixes.

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

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

[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 package

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling Atomix
• 1.1 Create cell file - No Result
• 1.2 Applying cell variable to environment - No Result
• 1.3 Starting Mininet - PASS
• 1.4 Git checkout and pull master - No Result Uninstalling ONOS package - PASS
• 1.5 Using mvn clean install 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 8 Checking if ONOS is up yet - PASS
• 1.9 14 Checking ONOS nodes - PASS
• 1.10 15 Activate apps defined in the params file - No Result
• 1.11 16 Set ONOS configurations - PASS
• 1.17 Check app ids - PASS
• 1.18 Set logging levels 12 App Ids check - 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 - PASS 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 - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case

...

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

• 3.1 Install reactive forwarding app - PASS
• 3.2 Check app ids - PASS
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

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

...