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/HAsanity/252/

...

commit 1684b00a21a3f16a39f06bd16725e720d78a056e b172d5fc8eef7877a1a3beec49e22221ceb069e6 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li kmcpeake [pyguni@gmailkmcpeake@btisystems.com]
AuthorDate: Wed Dec 16 15:38:46 2015 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Dec 18 00:55:23 2015 +0000
Bugfix: only allow REMARK band to have a precedence
: Thu Dec 10 11:30:43 2015 +0000
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Sun Dec 20 15:35:59 2015 +0000

[ONOS-3203] End-to-end demo of Fault Management via SNMP.
--
There is still code cleanup that could be done, but aim of this commit is an end-to-end proof of concept.

To demonstrate :

1) /opt/onos/bin/onos-service
onos] app activate org.onosproject.snmp
onos] app activate org.onosproject.faultmanagement
HTML
<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>

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of hosts
  • 8.3 Hosts information is correct - FAIL (error)
    • Host information is incorrect
  • 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 - FAIL (error)
    • Hosts are incorrect
  • 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

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

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

...