Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
| HTML |
|---|
<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 1c8a4ede3d9db1b9fb0cca267015eaee5d6239b5 581c8407e613a27aaa573a600828b30a37066fb8 (HEAD -] master, origin/master, origin/HEAD, master)
Author: Carmelo Cascone pierventre [carmelo@opennetworkingpier@opennetworking.org]
AuthorDate: Mon Apr 8 15:37:03 2019 -0700Thu Sep 23 19:03:14 2021 +0200
Commit: Carmelo Cascone [carmelo@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Apr 9 06:48:36 2019 +0000
Give priority to instructions over meta when generating next_vlan ruleMon Sep 27 19:27:55 2021 +0000
[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)
Case 1: Constructing test variables and building ONOS package - PASS
...
- 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 - PASS
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
...
- 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 - 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 - PASS
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 3: Adding host Intents -
...
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 ) - PASS
- 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
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 5: Setting up and gathering data for current state - PASS
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - PASS
- 5.16 Comparing ONOS topology to MN - PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - PASS
- 5.19 Hosts are correct - PASS
...