Page History

...

commit cc9ac30af6ba4ef4324e0cea94f118d3aaec3599 4ca2f7f7fdb71ae436aa435ff20787b9208b2436 (HEAD, origin/master, origin/HEAD, master)
Author: janani b [janani.b@huaweiCharles Chan [rascov@gmail.com]
AuthorDate: Thu Fri Mar 24 1225 13:4340:48 16 2016 +0530-0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Mar 25 0021:35:38 :41 2016 +0000
Defect fix for YANG revision
Support metadata in forwarding objective

<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 8.1 Comparing ONOS topology to MN topology - PASS
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Checking ONOS nodes - FAIL
• Nodes check NOT successful

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
• 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 FAIL

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

...