Page History

...

commit 24439fe26da68860da0d42d7033b85acf0b6179e ea32708ba865673f532d74fa4bfa42900da774a4 (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey Simon Hunt [ray@onlabsimon@onlab.us]
AuthorDate: Fri Mon Apr 8 2111 16:5049:55 07 2016 -0700
Commit: Brian O'Connor [bocon@onlabSimon Hunt [simon@onlab.us]
CommitDate: Sat Mon Apr 9 0211 16:5549:18 13 2016 -0700
app buck refactor for apps: aaa, acl, bgprouter
Temporary patch around unavailable username during websocket failover.

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

Case 1: Setting up test environment -

...

FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

• 1.1 Create cell file - No Result
• 1.2 Applying cell variable to environment - No Result
• 1.3 Starting Mininet - PASS
• 1.4 Git checkout and pull master - No Result
• 1.5 Using mvn clean install - PASS
• 1.6 Creating ONOS package - PASS
• 1.7 Installing ONOS package - PASS
• 1.8 Checking if ONOS is up yet - PASS
• 1.9 Checking ONOS nodes - PASS FAIL
• Nodes check NOT successful
• 1.10 Activate apps defined in the params file - No Result
• 1.11 Set ONOS configurations - PASS
• 1.12 App Ids check - PASS

...

• 2.1 Assign switches to controllers - 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 - PASS 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 - PASS FAIL
• ONOS shows 7 SCCs
• 8.7 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS FAIL
• Nodes check NOT successful

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 FAIL
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - PASS FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - PASS

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

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

...

FAIL

• 5.1 Check that each switch has a master - PASS FAIL
• Some devices don't have a master assigned
• 5.2 Get the Mastership of each switch from each controller - PASS
• 5.3 Check for consistency in roles from each controller - PASS FAIL
• ONOS nodes have different views of switch roles
• 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 - PASS
• 5.14 Cluster view correct across ONOS nodes - PASS FAIL
• ONOS shows 7 SCCs
• 5.15 Comparing ONOS topology to MN - PASS
• 5.16 Device information is correct - PASS FAIL
• Device information is incorrect
• 5.17 Links are correct - PASS FAIL
• Links are incorrect
• 5.18 Hosts are correct - PASS

Case 14: Start Leadership Election app -

...

FAIL

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS FAIL
• Failed to run for leadership
• 14.3 Check that each node shows the same leader - PASS FAIL
• Nodes have different leaders

Case 16: Install Primitives app - 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 -

...

FAIL

Compare topology objects between Mininet and ONOS

• 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
• 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 FAIL
• ONOS shows 7 SCCs
• 8.7 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS FAIL
• Nodes check NOT successful

Case 7: Running ONOS Constant State Tests - FAIL

...

• 7.1 Check that each switch has a master - PASS FAIL
• Some devices don't have a master assigned
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS FAIL
• ONOS nodes have different views of switch roles
• 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
• PASS
• 7.6 Compare current intents with intents before the failure - FAIL
The Intents changed during failure
• PASS
• 7.7 Get the OF Table entries and compare to before component failure - PASS
• 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 - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - No Result

...