Page History

...

commit 97a7033e8873b3a0a6450434167a0601023a29d1 b455803e67c4551bc722e2db08f36805b685133d (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska Jonathan Hart [tom@onlabjono@onlab.us]
AuthorDate: Wed May 20 0916:2932:55 04 2015 -0700
Commit: Thomas Vachuska Jonathan Hart [tom@onlabjono@onlab.us]
CommitDate: Wed May 20 0919:2917:55 26 2015 -0700
Fixed onos-package and put hazelcast back into features for now
Fix priorities of our rules higher than ARP.

<iframe src="https://onos-jenkins.onlab.us/job/HASingleInstanceRestartHASanity/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 master - No Result 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

...

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device. Then manually assign mastership to specific ONOS nodes using 'device-role'

• 2.1 Assign switches to controllers - PASS
• 2.2 Assign mastership of switches to specific controllers - PASS
• 2.3 Check mastership was correctly assigned - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes Collecting topology information from ONOS - PASS

Case 3: Adding host Intents - PASS

...

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch - No Result 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 - No Result PASS
• 5.4 6 Get the flows from each controller - No Result 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 6 Create TestONTopology object - No Result
• 5.7 11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.8 13 Each host has an IP address - PASS
• 5.9 There is only one dataplane cluster 14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - PASS
• 5.10 16 Comparing ONOS topology to MN - PASS

...

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS

Case 15: Check that Leadership Election is still functional - PASS

• 15.1 Find current leader and withdraw - PASS
• 15.2 Make sure new leader is elected - PASS
• 15.3 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.4 Node became leader when it ran for election 14.3 Check that each node shows the same leader - PASS

Case 16: Install Primitives app - PASS

...

• 17.1 Increment and get a default counter on each node - PASS
• 17.2 Increment and get an in memory counter on each node - PASS
• 17.3 Check counters are consistant across nodes - PASS
• 17.4 Counters we added have the correct values - PASS
• 17.5 Distributed Set get - PASS
• 17.6 Distributed Set size - PASS
• 17.7 Distributed Set add() - PASS
• 17.8 Distributed Set addAll() - PASS
• 17.9 Distributed Set contains() - PASS
• 17.10 Distributed Set containsAll() - PASS
• 17.11 Distributed Set remove() - PASS
• 17.12 Distributed Set removeAll() - PASS
• 17.13 Distributed Set addAll() - PASS
• 17.14 Distributed Set clear() - PASS
• 17.15 Distributed Set addAll() - PASS
• 17.16 Distributed Set retain() - PASS

Case 6:

...

Killing ONOS process and restart cli sessions once onos is up.

...

Wait 60 seconds instead of inducing a failure - PASS

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

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - 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

• Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes
• 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

Case 7: Running ONOS Constant State Tests - PASS

...

• 7.1 Check that each switch has a master - PASS
• 7.2 Check if switch roles are consistent across all nodes Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS
• 7.3 4 Compare switch roles from before failure - PASS
• 7.4 5 Get the intents and compare across all nodes - PASS
• 7.6 Check for consistency in Intents from each controller - PASS
• 7.7 Compare current intents with intents before the failure - PASS
• 7.8 5 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 6 Leadership Election is still functional - PASS

...

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - 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 - PASS

• 15.1 Check that each node shows the same leader - PASS
• 15.2 Find current leader and withdraw - PASS
• 15.2 3 Make sure new leader is elected - PASS
• 15.3 4 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.4 Node became leader when it ran for election 5 Leader did not change when old leader re-ran - PASS

Case 17: Check for basic functionality with distributed primitives - PASS

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes Collecting topology information from ONOS - PASS

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

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes Collecting topology information from ONOS - PASS

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

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes Collecting topology information from ONOS - PASS

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

...

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - PASS
• 8.4 Checking ONOS nodes Collecting topology information from ONOS - PASS

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

...