Page History

...

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

commit 1c0d5f81cfbac395ffb6c170c5927bb1163867d0 b8a2505d80037308fba4f38fec2a21404cbb489f (HEAD -] master, origin/master, origin/HEAD)
Author: psneha Carmelo Cascone [snehacarmelo@opennetworking.prem@infosys.comorg]
AuthorDate: Tue Mar 26 06:31:41 2019 -0400Mon Apr 8 15:22:32 2019 -0700
Commit: Pier Luigi Ventre [pier@opennetworkingCarmelo Cascone [carmelo@opennetworking.org]
CommitDate: Sat Mon Apr 6 138 23:5201:44 01 2019 +0000
Route Simplification programming
More robust deferring for P4Runtime MasterArbitrationUpdate messages

Case 1: Starting

...

up

...

7 node(s

...

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling Atomix - PASS
• 1.4 Uninstalling ONOS package - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.7 Installing ONOS package - PASS
• 1.8 Set up ONOS secure SSH - PASS
• 1.9 Checking ONOS service - PASS
• 1.10 Starting ONOS CLI sessions - PASS
• 1.11 Checking ONOS nodes - PASS
• 1.12 Checking ONOS applications - PASS
• 1.13 Checking ONOS nodes - PASS
• 1.14 Activate apps defined in the params file - No Result
• 1.15 Set ONOS configurations - PASS
• 1.16 Check app ids - PASS
• 1.17 Set logging levels - PASS

Case 102: Starting Mininet Topology - PASS

• 102.1 Pushing Network config - PASS
• 102.2 Check Network config - PASS
• 102.3 Start Mininet topology - 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 - FAIL
• ONOS topology don't match Mininet
• 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 0 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 104: Check connectivity - FAIL

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

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 - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 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 0 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - FAIL
• Hosts are incorrect
• 8.10 Checking ONOS nodes - PASS

Case 5: Setting up and gathering data for current state - FAIL

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - No Result
• 5.3 Read device roles from ONOS - PASS
• 5.4 Check for consistency in roles from each controller - PASS
• 5.5 Get the intents from each controller - PASS
• 5.6 Check for consistency in Intents from each controller - PASS
• 5.7 Get the flows from each controller - PASS
• 5.8 Check for consistency in Flows from each controller - PASS
• 5.9 Get the OF Table entries - No Result
• 5.10 Start continuous pings - No Result
• 5.11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.13 Each host has an IP address - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 0 SCCs
• 5.16 Comparing ONOS topology to MN - FAIL
• ONOS7 hosts don't match Mininet
• 5.17 Device information is correct - PASS
• 5.18 Links are correct - PASS
• 5.19 Hosts are correct - FAIL
• Hosts are incorrect

Case 14: Start Leadership Election app - PASS

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS
• 14.3 Active node was elected leader? - 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 16: Install Primitives app - PASS

• 16.1 Install Primitives app - PASS

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

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

...

)

...

ONOS cluster

...

• 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 - FAIL
• Failed to rerun for election

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 - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 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 0 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - FAIL
• Hosts are incorrect
• 8.10 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests - 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 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election

Case 104: Check connectivity - FAIL

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

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 spine102 and leaf1 - PASS

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

...

FAIL

...

• ONOS topology don't match Mininet

...

• Host information is incorrect

...

• ONOS shows 0 SCCs

...

• Hosts are incorrect

...

Case 104: Check connectivity - FAIL

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

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

• 10.1 Bring link between spine102 and leaf1 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 - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 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 0 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - FAIL
• Hosts are incorrect
• 8.10 Checking ONOS nodes - PASS

Case 104: Check connectivity - FAIL

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

Case 13: Test Cleanup - PASS

...