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.
...
commit 0c41ba26a900107788532b29649a671a83bfe6ec 6db0b448444b964de6808f52c22bc2673b0ce033 (HEAD, origin/master, origin/HEAD, master)
Author: Bri Prebilic Cole [bri@onlabMadan Jampani [madan@onlab.us]
AuthorDate: Mon Tue Jul 6 157 20:0927:48 59 2015 -0700
Commit: Bri Prebilic Cole [bri@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Wed Jul 6 158 04:0927:56 39 2015 -0700
GUI -- Cleaned up directives - onos-sortable-header and icon no longer use isolate scope. Icon directive moved to icon.js. Deleted unneeded TableService.+0000
Registered atomic versions of int, long and boolean to KryoNamespace.BASIC
| HTML |
|---|
<iframe src="https://onos-jenkins.onlab.us/job/HASanity/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 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 - FAIL
- Intent ECM anti-entropy took too long
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - FAIL Intents are not all in INSTALLED state
- Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
...
- 7.1 Check that each switch has a master - PASS
- 7.2 Read device roles from ONOS - PASS
- 7.3 Check for consistency in roles from each controller - PASS
- 7.4 Compare switch roles from before failure - PASS
- 7.5 Get the intents and compare across all nodes - PASS
- 7.6 Check for consistency in Intents from each controller - FAIL
- ONOS nodes have different views of intents
- 7.7 Compare current intents with intents before the failure - FAIL
- The Intents changed during failure
- 7.8 Get the OF Table entries and compare to before component failure - PASS
- 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - PASS
- 7.10 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
...
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Hosts are correct - PASS
- 8.11 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Hosts are correct - PASS
- 8.11 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Hosts are correct - PASS
- 8.11 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 12: Adding a switch to ensure it is discovered correctly - PASS
- 12.1 Add back s5 - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - FAIL Links are incorrect
- PASS
- 8.10 Hosts are correct - PASS
- 8.11 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - FAIL Intents are not all in INSTALLED state
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
...