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 61fc91c534596aebaf1bdd3e9ae0224460a96ec1 cba4b63f76550a242af085b79ec272a6a13a47c6 (HEAD, origin/onos-1.3, onos-1.3)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Wed Fri Sep 16 2218 14:5440:24 38 2015 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Thu Fri Sep 17 18 14:1240:31 38 2015 -0700
Updating onos-package for debian packaging
Starting snapshot 1.3.1-SNAPSHOT
| 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> |
...
- 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 - 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 - FAIL
Device information is incorrect - PASS
- 8.9 Links are correct - PASS
- 8.10 Hosts are correct - PASS
- 8.11 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 - PASS
Compare topology objects between Mininet and ONOS
...
- 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 FAIL
- Intent ECM anti-entropy took too long
Case 4: Verify connectivity by sendind traffic across Intents - PASS
...
Case 6: Wait 60 seconds instead of inducing a failure - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
...
- 9.1 Kill Link between s3 and s28 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
...
- 10.1 Bring link between s3 and s28 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
...
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 11: Killing a switch to ensure it is discovered correctly -
...
FAIL
- 11.1 Kill s5 - PASS FAIL
- Failed to kill switch?
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
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 FAIL
- ONOS shows 2 SCCs
- 8.8 Device information is correct - PASS FAIL
- Device information is incorrect
- 8.9 Links are correct - PASS
- 8.10 Hosts are correct - PASS
- 8.11 Checking ONOS nodes - PASS
...