Page History

...

commit 041534b2908d49d19244289e37c21416979700cc d1172636d135ada46a1d690e9533b24dee0ceb7b (HEAD, origin/master, origin/HEAD, master)
Author: Jordan Halterman Charles Chan [jordan@onlabrascov@gmail.uscom]
AuthorDate: Tue Wed Mar 21 1015 17:3733:33 09 2017 -0700
Commit: Thomas Vachuska Jonathan Hart [tom@onlabjono@onlab.us]
CommitDate: Tue Wed Mar 21 2322 20:4155:28 07 2017 +0000
[ONOS-5992] Ensure futures for failed messages are completed using the supplied Executor in NettyMessagingManager.
CORD-810 Remove VLAN extension selector from OFDPA 3

<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

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

...

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS FAIL
• ONOS nodes have different views of hosts
• 8.3 Hosts information is correct - PASS 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 - 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 - 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 - 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 and compare across all nodes - 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
• 7.8 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election

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 - FAIL
• Intents are not all in INSTALLED state
• 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 - FAIL

• 15.1 Run for election on each node - PASS
• 15.2 Check that each node shows the same leader and candidates - FAIL
• Nodes have different leaderboards
• 15.3 Find current leader and withdraw - FAIL
• Node was not withdrawn from election
• 15.4 Check that a new node was elected leader - FAIL
• Something went wrong with Leadership election
• 15.5 Check that that new leader was the candidate of old leader - FAIL
• Incorrect Candidate Elected
• 15.6 Run for election on old leader( just so everyone is in the hat ) - FAIL
• App failed to run for election
• 15.7 Check that oldLeader is a candidate, and leader if only 1 node - FAIL
Something went wrong with Leadership election after the old leader re-ran for election