Page History

...

commit 2fdbe0d1e013e3c4b2a3d933b25850d21aa5319f 24439fe26da68860da0d42d7033b85acf0b6179e (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlabRay Milkey [ray@onlab.us]
AuthorDate: Fri Apr 8 1921:1450:04 55 2016 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Fri Sat Apr 8 199 02:1455:15 18 2016 -0700
Small fixes to onos-buck
app buck refactor for apps: aaa, acl, bgprouter

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

...

• 2.1 Assign switches to controllers - 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 - FAIL
• ONOS nodes have different views of clusters
• 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 -

...

PASS

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 PASS

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

...

• 4.1 Check Intent state - PASS
• 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 5: Setting up and gathering data for current state -

...

PASS

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

...

• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning 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 - FAIL
ONOS nodes have different views of hosts
• 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

...

• 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 failure - FAIL
• The Intents changed during failure
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
Changes were found in the flow tables
• PASS
• 7.8 Leadership Election is still functional - PASS FAIL
• Something went wrong with Leadership election

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

...

• 4.1 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 15: Check that Leadership Election is still functional -

...

No Result

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