Page tree

This is an archive of the ONOS 1.2 wiki. For the current ONOS wiki, look here.

Skip to end of metadata
Go to start of metadata
HATestSingleInstanceRestart at 07 Jul 2015 03:04:26

commit 0c41ba26a900107788532b29649a671a83bfe6ec (HEAD, origin/master, origin/HEAD, master)
Author: Bri Prebilic Cole [bri@onlab.us]
AuthorDate: Mon Jul 6 15:09:48 2015 -0700
Commit: Bri Prebilic Cole [bri@onlab.us]
CommitDate: Mon Jul 6 15:09:56 2015 -0700

GUI -- Cleaned up directives - onos-sortable-header and icon no longer use isolate scope. Icon directive moved to icon.js. Deleted unneeded TableService.

Case 1: Setting up test environment - PASS

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

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

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

  • 2.1 Assign switches to controllers - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)

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 (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

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

  • 5.1 Check that each switch has a master - PASS (tick)
  • 5.2 Get the Mastership of each switch - No Result (warning)
  • 5.3 Get the intents from each controller - No Result (warning)
  • 5.4 Get the flows from each controller - No Result (warning)
  • 5.5 Get the OF Table entries - No Result (warning)
  • 5.6 Collecting topology information from ONOS - No Result (warning)
  • 5.7 Each host has an IP address - PASS (tick)
  • 5.8 There is only one dataplane cluster - PASS (tick)
  • 5.9 Comparing ONOS topology to MN - PASS (tick)
  • 5.10 Device information is correct - PASS (tick)
  • 5.11 Links are correct - PASS (tick)
  • 5.12 Hosts are correct - PASS (tick)

Case 14: Start Leadership Election app - PASS

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

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

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

Case 16: Install Primitives app - PASS

  • 16.1 Install Primitives app - PASS (tick)

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

Test the methods of the distributed primitives (counters and sets) throught the cli

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

Case 6: Restart ONOS node - PASS

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

  • 6.1 Killing ONOS processes - PASS (tick)
  • 6.2 Checking if ONOS is up yet - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)

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 (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 7: Running ONOS Constant State Tests - PASS

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Check if switch roles are consistent across all nodes - PASS (tick)
  • 7.3 Compare switch roles from before failure - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Get the OF Table entries and compare to before component failure - PASS (tick)
  • 7.6 Leadership Election is still functional - PASS (tick)

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

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

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

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

Test the methods of the distributed primitives (counters and sets) throught the cli

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

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

  • 9.1 Kill Link between s3 and s28 - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

  • 10.1 Bring link between s3 and s28 back up - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

Case 11: Killing a switch to ensure it is discovered correctly - PASS

  • 11.1 Kill s5 - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

Case 12: Adding a switch to ensure it is discovered correctly - PASS

  • 12.1 Add back s5 - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful

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

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

  • 4.1 Ping across added host intents - PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

Case 13: Test Cleanup - PASS

  • 13.1 Killing tcpdumps - No Result (warning)
  • 13.2 Copying MN pcap and ONOS log files to test station - No Result (warning)
  • 13.3 Stopping Mininet - PASS (tick)
  • 13.4 Checking ONOS Logs for errors - No Result (warning)
  • 13.5 Packing and rotating pcap archives - No Result (warning)