Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/HAkillNodes/628/

...

commit b1ad99ae8afb67c03e640c1aadc62815a508f24a 0fc09dc516cc19b3dc524d2aae1393fc9c9bc969 (HEAD, origin/onos-1.7, onos-1.7)
Author: Jayasree Ghosh Thomas Vachuska [jghosh@partnertom@onlab.ciena.comus]
AuthorDate: Tue Aug 30 01:24:45 2016 +0530Oct 4 11:50:29 2016 -0700
Commit: Jayasree Ghosh Thomas Vachuska [jghosh@partnertom@onlab.ciena.comus]
CommitDate: Mon Sep 26 04:55:58 Tue Oct 25 22:33:07 2016 +0000
ONOS-5214:Fix-For-Meter-WrongBandType-with-NPE-And-WrongUNITType-Issue
Fixing onos-create-app to bomb if mvn command fails for some reason.
--
(cherry picked from commit 726839c57f8a5df62c5d28ec205f128f417ffef7525651fdc03f8437e3c6fe69d4fb564a78f3e50a)
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAkillNodes/plot/Plot-HA/getPlot?index=21&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 61.1 Checking ONOS Logs for errors - No Result (warning)
  • 61.2 Kill 2 ONOS nodes - PASS (tick)
  • 61.3 Checking ONOS nodes - 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 topology - PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 7: Running ONOS Constant State Tests - PASS

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Read device roles from ONOS - PASS (tick)
  • 7.3 Check for consistency in roles from each controller - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)
  • 7.6 Compare current intents with intents before the failure - PASS (tick)
  • 7.7 Get the OF Table entries and compare to before component failure - PASS (tick)
  • 7.8 Leadership Election is still functional - PASS (tick)

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

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

  • 4.1 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - 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 Run for election on each node - PASS (tick)
  • 15.2 Check that each node shows the same leader and candidates - PASS (tick)
  • 15.3 Find current leader and withdraw - PASS (tick)
  • 15.4 Check that a new node was elected leader - PASS (tick)
  • 15.5 Check that that new leader was the candidate of old leader - PASS (tick)
  • 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS (tick)
  • 15.7 Check that oldLeader is a candidate, and leader if only 1 node - 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 then get a default counter on each node - PASS (tick)
  • 17.2 Get then Increment a default counter on each node - PASS (tick)
  • 17.3 Counters we added have the correct values - PASS (tick)
  • 17.4 Add -8 to then get a default counter on each node - PASS (tick)
  • 17.5 Add 5 to then get a default counter on each node - PASS (tick)
  • 17.6 Get then add 5 to a default counter on each node - PASS (tick)
  • 17.7 Counters we added have the correct values - PASS (tick)
  • 17.8 Distributed Set get - PASS (tick)
  • 17.9 Distributed Set size - PASS (tick)
  • 17.10 Distributed Set add() - PASS (tick)
  • 17.11 Distributed Set addAll() - PASS (tick)
  • 17.12 Distributed Set contains() - PASS (tick)
  • 17.13 Distributed Set containsAll() - PASS (tick)
  • 17.14 Distributed Set remove() - PASS (tick)
  • 17.15 Distributed Set removeAll() - PASS (tick)
  • 17.16 Distributed Set addAll() - PASS (tick)
  • 17.17 Distributed Set clear() - PASS (tick)
  • 17.18 Distributed Set addAll() - PASS (tick)
  • 17.19 Distributed Set retain() - PASS (tick)
  • 17.20 Partitioned Transactional maps put - PASS (tick)
  • 17.21 Partitioned Transactional maps get - PASS (tick)

Case 62: Restart minority of ONOS nodes - PASS

  • 62.1 Restarting 2 ONOS nodes - PASS (tick)
  • 62.2 Checking if ONOS is up yet - PASS (tick)
  • 62.3 Restarting ONOS main.CLIs - PASS (tick)
  • 62.4 Checking ONOS nodes - PASS (tick) 62.5 Rerun for election on the node(s) that were killed - PASS (tick)