Page History

...

commit fdba99862c594dca7672eb09fea8584a3dd99a87 4558268c1a390dde483defcb38c5f91381e07fb5 (HEAD, origin/onos-1.2, onos-1.2master, origin/HEAD, master)
Author: alshabib Thomas Vachuska [alshabibitom@onlab.ali@gmail.comus]
AuthorDate: Fri Tue Jun 26 30 13:2047:54 10 2015 -0700
Commit: alshabib Thomas Vachuska [alshabibitom@onlab.ali@gmail.comus]
CommitDate: Fri Tue Jun 26 1530 13:4347:59 10 2015 -0700
adding a dockerfile for onos-1.2
Adding ATT topo with CLI to generate traffic - courtesy of Bob Lantz.

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

...

• 1.1 Applying cell variable to environment - No Result
• 1.2 Starting Mininet - PASS
• 1.3 Git checkout and pull onosmaster - 1.2 - PASS
• 1.4 Using mvn clean install - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing ONOS package - PASS
• 1.7 Checking if ONOS is up yet - PASS
• 1.8 App Ids check - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 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 - PASS - FAIL
• Intent ECM anti-entropy took too long

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 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 -

...

FAIL

• 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 FAIL
• ONOS nodes have different views of intents
• 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 Create TestONTopology object - No Result
• 5.11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.13 Each host has an IP address - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - PASS FAIL
• ONOS shows 2 SCCs
• 5.16 Comparing ONOS topology to MN - PASS FAIL
• Topology Check Test NOT successful

Case 14: Start Leadership Election app - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 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 Compare switch roles from before failure - FAIL
Mastership of some switches changed
• PASS
• 7.5 Get the intents and compare across all nodes - PASS
• 7.6 Check for consistency in Intents from each controller - PASS FAIL
• ONOS nodes have different views of intents
• 7.7 Compare current intents with intents before the failure - PASS FAIL
• The Intents changed during failure
• 7.8 Get the OF Table entries and compare to before component failure - PASS
• 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - PASS
• 7.10 Leadership Election is still functional - PASS

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

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - FAIL
Some topics were lost
• PASS
• 4.4 Wait a minute then ping again - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

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

Ping across added host intents to check functionality and check the state of the intent

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

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

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

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - FAIL
• Some topics were lost
• PASS
• 4.4 Wait a minute then ping again - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

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

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - FAIL
Some topics were lost
• PASS
• 4.4 Wait a minute then ping again - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

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

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - FAIL
Some topics were lost
• PASS
• 4.4 Wait a minute then ping again - PASS

...