Page History

...

commit f7e5f055451dbd1d119ed70e0c7782eb7a7385bf 65b38cb6c0fa8ab371f9b9a7c8878e94f98a12d2 (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.usHyunsun Moon [hyunsun.moon@gmail.com]
AuthorDate: Wed Fri May 4 116 18:2827:19 37 2016 -0700
Commit: Brian O'Connor [bocon@onlab.usHyunsun Moon [hyunsun.moon@gmail.com]
CommitDate: Wed May 4 19Fri May 6 18:29:27 :34 2016 -0700
Adding BuckLibGenerator to autogenerate lib/BUCK
Fixed consistent map event listener remove

<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&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 ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• PASS
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - FAIL
• Error looking up host ids
• PASS
• 3.7 Intent Anti-Entropy dispersion - PASS FAIL

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
ONOS topology don't match Mininet
• PASS
• 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
• PASS
• 8.6 There is only one SCC - FAIL
ONOS shows 2 SCCs
• PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• 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 - PASS
• 5.3 Check for consistency in roles from each controller - FAIL
ONOS nodes have different views of switch roles
• PASS
• 5.4 Get the intents from each controller - PASS
• 5.5 Check for consistency in Intents from each controller - PASS
• 5.6 Get the flows from each controller - PASS
• 5.7 Check for consistency in Flows from each controller - PASS
• 5.8 Get the OF Table entries - No Result
• 5.9 Start continuous pings - No Result
• 5.10 Collecting topology information from ONOS - No Result
• 5.11 Host view is consistent across ONOS nodes - PASS
• 5.12 Each host has an IP address - PASS
• 5.13 Cluster view is consistent across ONOS nodes - FAIL
ONOS nodes have different views of clusters
• PASS
• 5.14 Cluster view correct across ONOS nodes - PASS
• 5.15 Comparing ONOS topology to MN - PASS
• 5.16 Device information is correct - PASS
• 5.17 Links are correct - PASS
• 5.18 Hosts are correct - PASS

Case 14: Start Leadership Election app -

...

PASS

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - FAIL
Inconsistent leaderboards
• PASS
• 14.3 First node was elected leader - PASS

Case 16: Install Primitives app - PASS

...

• 6.1 Checking ONOS Logs for errors - No Result
• 6.2 Killing ONOS nodes - PASS
• 6.3 Checking if ONOS is up yet - 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
• ) - 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

...

• 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 FAIL
• ONOS nodes have different views of switch roles
• 7.4 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - FAIL
ONOS nodes have different views of intents
• PASS
• 7.6 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.7 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election

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 - FAIL
Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 15: Check that Leadership Election is still functional - FAIL

...

• 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

• 8.1 Comparing ONOS topology to MN topology - PASS
• 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
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

...

• 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

• 8.1 Comparing ONOS topology to MN topology - FAIL
ONOS topology don't match Mininet
• PASS
• 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
• 8.6 There is only one SCC - FAIL
• ONOS shows 3 SCCs
• PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• 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

• 8.1 Comparing ONOS topology to MN topology - FAIL
ONOS topology don't match Mininet
• PASS
• 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
• 8.6 There is only one SCC - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
Intents are not all in INSTALLED state
• .1 Check Intent state - PASS
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.
• 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 topology - FAIL
• ONOS topology don't match Mininet
• PASS
• 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
• 8.6 There is only one SCC - FAIL
ONOS shows 2 SCCs
• SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - 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 - FAIL
Intents are not all in INSTALLED state
• PASS
• 4.2 Ping across added host intents - FAIL
Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 13: Test Cleanup - PASS

...