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/HAclusterRestart/166/

...

commit c008511f5036cb3e2aa775a1e4870f916af3e714 2b49e944eabe2211e7ee8ccfecf3f84517374cfe (HEAD, origin/master, origin/HEAD, master)
Author: andrea [andrea@onlab.usSho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Tue Wed Nov 24 25 18:0134:45 10 2015 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Thu Nov 25 0326 02:2654:45 51 2015 +0000
[ONOS-3394] Json Models for Intents
Ensure returning null on allocation failure
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=0&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 (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Git checkout and pull master - No Result (warning)
  • 1.5 Using mvn clean install - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing ONOS package - PASS (tick)
  • 1.8 Checking if ONOS is up yet - PASS (tick)
  • 1.9 App Ids check - PASS (tick)FAIL (error)
    • Something is wrong with app Ids

Case 2: Assigning devices to controllers - PASS

...

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

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 (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)FAIL (error)

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - 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

...

  • 17.1 Increment then get a default counter on each node - PASS (tick)FAIL (error)
    • Error incrementing default counter
  • 17.2 Get then Increment a default counter on each node - PASS (tick)FAIL (error)
    • Error incrementing default counter
  • 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)FAIL (error)
    • Error incrementing default counter
  • 17.6 Get then add 5 to a default counter on each node - PASS (tick)FAIL (error)
    • Error incrementing default counter
  • 17.7 Counters we added have the correct values - PASS (tick)
  • 17.8 Increment and get an in-memory counter on each node - PASS (tick)
  • 17.9 Get then Increment a in-memory counter on each node - PASS (tick)
  • 17.10 Counters we added have the correct values - PASS (tick)
  • 17.11 Add -8 to then get a in-memory counter on each node - PASS (tick)- FAIL (error)
    • Error incrementing in-memory counter
  • 17.12 Add 5 to then get a in-memory counter on each node - PASS (tick)- FAIL (error)
    • Error incrementing in-memory counter
  • 17.13 Get then add 5 to a in-memory counter on each node - PASS (tick)
  • 17.14 Counters we added have the correct values - PASS (tick)
  • 17.15 Check counters are consistant across nodes - PASS (tick)
  • 17.16 Counters we added have the correct values - PASS (tick)
  • 17.17 Distributed Set get - PASS (tick)
  • 17.18 Distributed Set size - PASS (tick)
  • 17.19 Distributed Set add() - PASS (tick)
  • 17.20 Distributed Set addAll() - FAIL (error)
  • Set addAll was incorrect
  • PASS (tick)
  • 17.21 Distributed Set contains() - PASS (tick)
  • 17.22 Distributed Set containsAll() - PASS (tick)
  • 17.23 Distributed Set remove() - PASS (tick)
  • 17.24 Distributed Set removeAll() - PASS (tick)
  • 17.25 Distributed Set addAll() - PASS (tick)
  • 17.26 Distributed Set clear() - PASS (tick)
  • 17.27 Distributed Set addAll() - PASS (tick)
  • 17.28 Distributed Set retain() - PASS (tick)
  • 17.29 Partitioned Transactional maps put - PASS (tick)
  • 17.30 Partitioned Transactional maps get - PASS (tick)
  • 17.31 In-memory Transactional maps put - PASS (tick)
  • 17.32 In-Memory Transactional maps get - PASS (tick)

...