Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAbackupRecover_onos-2.0_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0">

commit 871cb42d23c8e4096d14aa25206e0dad83d6d2b4 fa6af0cdbd071b19bf9a1d731bc9419135b060df (HEAD -] onos-2.0, origin/onos-2.0)
Author: Andrea Campanella Ray Milkey [andrea@opennetworkingray@opennetworking.org]
AuthorDate: Fri Mar 1 1222 16:0724:11 38 2019 +0100-0700
Commit: Andrea Campanella Ray Milkey [andrea@opennetworkingray@opennetworking.org]
CommitDate: Tue Fri Mar 12 22 16:0524:18 38 2019 -0700
Reverting change to print for OCHSignal
Implement static component properties - passed through without modification

Case 1: Starting up 7 node(s) ONOS cluster - PASS

...

• 6.1 Backup ONOS data - PASS
• 6.2 Checking ONOS Logs for errors - No Result
• 6.3 Uninstalling ONOS package - PASS
• 6.4 Installing ONOS package - PASS
• 6.5 Restore ONOS data - PASS
• 6.6 Restart ONOS nodes - No Result
• 6.7 Set up ONOS secure SSH - PASS
• 6.8 Checking ONOS service - PASS
• 6.9 Starting ONOS CLI sessions - PASS

Case 8: Compare ONOS Topology view to Mininet topology

...

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 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 - 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 Get the intents from each controller - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Leadership Election is still functional - 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 15: Check that Leadership Election is still functional - PASS

• 15.1 Run for election on each node - PASS
• 15.2 Check that each node shows the same leader and candidates - PASS
• 15.3 Find current leader and withdraw - PASS
• 15.4 Check that a new node was elected leader - PASS
• 15.5 Check that that new leader was the candidate of old leader - PASS
• 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.7 Check that oldLeader is a candidate, and leader if only 1 node - No Result

Case 17: Check for basic functionality with distributed primitives - PASS

Test the methods of the distributed primitives (counters and sets) throught the cli

...

-

...

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

• 9.1 Kill Link between s28 and s3 - 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 - 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 10: Restore a link to ensure that Link Discovery is working properly - PASS

• 10.1 Bring link between s28 and s3 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 - 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 - 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 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 - 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 - FAIL

Ping across added host intents to check functionality and check the state of the intent

...

FAIL

...

• Intents have not been installed correctly, pings failed.

...

• Intents have not been installed correctly, pings failed.

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 - 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 - FAIL

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.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...