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 8586c6478888cebf56c8069d76e6e184baca7668 d8f04aadeac169949a3f403e7d051c8bef63d82c (HEAD -] onos-1.14, origin/onos-1.14)
Author: Charles Chan Carmelo Cascone [rascov@gmailcarmelo@opennetworking.comorg]
AuthorDate: Fri Aug 31 17:46:37 2018 -0700Thu Dec 13 23:16:10 2018 -0800
Commit: Carmelo Cascone [carmelo@opennetworking.org]
CommitDate: Wed Sep 5 07:05:04 Fri Dec 14 20:01:49 2018 +0000
Implement NOP in routing v4 table
Working STC trellis-p4 scenario with connectivity test

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

...

• 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 Setup server for cluster metadata file - PASS
• 1.6 Generate initial metadata file - PASS
• 1.7 Copying backup config files - PASS
• 1.8 Starting Mininet - PASS
• 1.9 6 Creating ONOS package - PASS
• 1.10 7 Installing Atomix - PASS
• 1.11 8 Installing ONOS package - PASS
• 1.12 9 Set up ONOS secure SSH - PASS
• 1.13 10 Checking ONOS service - PASS
• 1.14 11 Starting ONOS CLI sessions - PASS
• 1.15 12 Checking ONOS nodes - PASS
• 1.16 13 Checking ONOS applications - PASS 1.17 Clean up ONOS service changes - No Result
• 1.18 14 Checking ONOS nodes - PASS
• 1.19 15 Activate apps defined in the params file - No Result
• 1.20 16 Set ONOS configurations - PASS
• 1.21 17 Check app ids - PASS
• 1.22 18 Set logging levels - PASS

...

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

Case 3: Adding host Intents -

...

FAIL

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 FAIL

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 Compare current intents with intents before the scaliing scaling - FAIL
• The Intents changed during scaliingscaling
• 7.7 Get the OF Table entries and compare to before component scaliing scaling - PASS
• 7.8 Leadership Election is still functional - PASS

...

• 17.1 Increment then get a default counter on each node - PASS
• 17.2 Get then Increment a default counter on each node - PASS
• 17.3 Counters we added have the correct values - PASS
• 17.4 Add -8 to then get a default counter on each node - PASS
• 17.5 Add 5 to then get a default counter on each node - PASS
• 17.6 Get then add 5 to a default counter on each node - PASS
• 17.7 Counters we added have the correct values - PASS
• 17.8 Distributed Set get - PASS
• 17.9 Distributed Set size - PASS
• 17.10 Distributed Set add() - PASS
• 17.11 Distributed Set addAll() - PASS
• 17.12 Distributed Set contains() - PASS
• 17.13 Distributed Set containsAll() - PASS
• 17.14 Distributed Set remove() - PASS
• 17.15 Distributed Set removeAll() - PASS
• 17.16 Distributed Set addAll() - PASS
• 17.17 Distributed Set clear() - FAIL
• Set clear was incorrect
• 17.18 Distributed Set addAll() - PASS
• 17.19 Distributed Set retain() - PASS
• 17.20 Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - PASS
• 17.22 Get the value of a new value - FAIL
• Error getting atomic Value None, found: [None, found: ['baz', 'baz', 'baz', 'baz', 'baz']
• 17.23 Atomic Value set() - PASS
• 17.24 Get the value after set() - PASS
• 17.25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17.28 Get the value after getAndSet() - PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - FAIL
• Error getting atomic Value None, found: ['baz', 'baz', 'baz', 'baz', 'baz']
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - FAIL
• Work Queue stats incorrect
• 17.33 Work Queue addMultiple() - PASS
• 17.34 Check the work queue stats - FAIL
• Work Queue stats incorrect
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats - FAIL
• Work Queue stats incorrect
• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - FAIL
• Work Queue stats incorrect
• 17.39 Work Queue destroy() - PASS
• 17.40 Check the work queue stats - FAIL
• Work Queue stats incorrect

...

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

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 -

...

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

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 -

...

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

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 -

...

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

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

...

• 13.1 Checking raft log size - PASS
• 13.2 Killing tcpdumps - No Result
• 13.3 Checking ONOS Logs for errors - No Result
• 13.4 Stopping Mininet - PASS 13.5 Stopping webserver - PASS