...
commit ce2d8b5680673716201089cb7039512cad2a12c0 2a9ea495215d1c03d2e0144f849fb8cb6c305f92 (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
AuthorDate: Wed Thu Jul 29 1630 15:2453:13 04 2015 -0700
Commit: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
CommitDate: Wed Thu Jul 30 23:29 16:24:13 2015 -0700
Initial implementation of the intent domain manager37 2015 +0000
Fix bug where SDN-IP installs more intents than needed
--
(cherry picked from commit 1258f86b564be76771c5cd6e1f807c4bc529168a)
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAsingleInstanceRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
Case 3: Adding host Intents -
...
FAIL
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 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
...
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
Case 3: Adding host Intents - PASS
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 7: Running ONOS Constant State Tests -
...
FAIL
- 7.1 Check that each switch has a master - PASS
- 7.2 Check if switch roles are consistent across all nodes - PASS
- 7.3 Compare switch roles from before failure - PASS
- 7.4 Get the intents and compare across all nodes - PASS
- 7.5 Get the OF Table entries and compare to before component failure - PASS FAIL
- Changes were found in the flow tables
- 7.6 Leadership Election is still functional - PASS
...
- 10.1 Bring link between s3 and s28 back up - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
Case 4: Verify connectivity by sendind traffic across Intents - PASS
...
Case 11: Killing a switch to ensure it is discovered correctly - PASS
- 11.1 Kill s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
...
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 - FAIL
Compare topology objects between Mininet and ONOS
...