Page History

...

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

commit c08f31e35acf37e7b3781ac1330dcc3cf5b2e359 1a8b039ff68ef6f1cfb2f7a388a6ed281b5d8213 (HEAD -] onos-1.14, origin/onos-1.14)
Author: Jordan Halterman Charles Chan [jordan@opennetworkingrascov@gmail.orgcom]
AuthorDate: Thu Fri Oct 18 1326 15:4154:45 32 2018 -0700
Commit: Thomas Vachuska Charles Chan [tom@opennetworkingcharles@opennetworking.org]
CommitDate: Fri Oct 19 1726 23:1024:29 46 2018 +0000
Upgrade to Atomix 3.0.7
Update onos-diagnostics to include the latest SR commands

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

...

• 6.1 Checking ONOS Logs for errors - No Result
• 6.2 Start new nodes - PASS
• 6.3 Set up ONOS secure SSH - PASS
• 6.4 Checking ONOS service - PASS
• 6.5 Starting ONOS CLI sessions - PASS
• 6.6 Checking ONOS nodes - 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 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 FAIL
• Nodes check NOT successful

Case 3: Adding host Intents - 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
• 7.4 Get the intents from each controller - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Compare current intents with intents before the scaling - FAIL
• The Intents changed during scaling
• 7.7 Get the OF Table entries and compare to before component scaling - FAIL
• Changes were found in the flow tables
• PASS
• 7.8 Leadership Election is still functional - PASS

...

• 9.1 Kill Link between s28 and s3 - 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 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 FAIL
• Nodes check NOT successful

Case 4: Verify connectivity by sending traffic across Intents - PASS

...

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

Case 4: Verify connectivity by sending 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 -

...

FAIL

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 FAIL
• Nodes check NOT successful

Case 4: Verify connectivity by sending traffic across Intents - 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 -

...

FAIL

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 FAIL
• Nodes check NOT successful

Case 4: Verify connectivity by sending traffic across Intents - PASS

...