Page History

...

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

commit a432cf87faf44704787d1379149423cde057f130 43ec470873b9f12face1283dbdde05aa8d279d87 (HEAD -] master, origin/master, origin/HEAD)
Author: Saurav Das Georgios Katsikas [sauravdas@alumnikatsikas.stanfordgp@gmail.educom]
AuthorDate: Thu Fri Oct 11 1512 08:2946:24 48 2018 -0700+0200
Commit: Charles Chan [charles@opennetworking.orgGeorgios Katsikas [katsikas.gp@gmail.com]
CommitDate: Fri Oct 12 0108:1249:27 40 2018 +0000
Allow applications to specify a few other packet-request flow priorities.
--
(cherry picked from commit 6f58cf1e5aae371cb8c7e0ad69552f3e68672f05)0200

Flow monitoring as default NIC rule action

Case 1: Constructing test variables and building ONOS package - PASS

...

• 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 104: Check connectivity -

...

FAIL

• 104.1 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts
• 104.2 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts

Case 8: Compare ONOS Topology view to Mininet topology - 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 from each controller - PASS
• 7.6 Check for consistency in Intents from each controller - PASS
• 7.7 Compare current intents with intents before the failure - PASS
• 7.8 Get the OF Table entries and compare to before component failure - PASS
• 7.9 Leadership Election is still functional - PASS

Case 104: Check connectivity -

...

FAIL

• 104.1 Ping between all hosts - PASS 104.2 Ping FAIL
• Failed to ping between all hosts
• 104.2 Ping between all hosts - FAIL
• Failed to ping between all hosts
- PASS

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

...

• 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 104: Check connectivity -

...

FAIL

• 104.1 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts
• 104.2 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts

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

...

• 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 104: Check connectivity -

...

FAIL

• 104.1 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts
• 104.2 Ping between all hosts - PASS FAIL
• Failed to ping between all hosts

Case 13: Test Cleanup - PASS

...