Page History

...

commit 6baf303bb42991ad95adaa6acf56699fa8944354 c559910f64595f3e2c6c3cc9c9bfdfb79ac88f8b (HEAD, origin/onos-tag: 1.10, onos-1.10.0-rc4)
Author: Charles Chan Ray Milkey [rascov@gmailray@onlab.comus]
AuthorDate: Wed Tue May 24 1530 12:4253:49 02 2017 -0700
Commit: Charles Chan Ray Milkey [charles@onlabray@onlab.us]
CommitDate: Thu Tue May 25 2130 12:0453:17 02 2017 +0000
Remove CORD config dependency from SR-0700

Tagging 1.10.0-rc4

<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>

...

• 6.1 Checking ONOS Logs for errors - No Result
• 6.2 Generate new metadata file - PASS
• 6.3 Start new nodes - PASS
• 6.4 Checking if ONOS is up yet - PASS
• 6.5 Starting ONOS CLI sessions - PASS
• 6.6 Checking ONOS nodes - FAIL
• Failed to rerun for election
• 6.7 Reapplying cell variable to environment - 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 - 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 - FAIL
• ONOS nodes have different views of intents
• 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