Page History

...

commit ce2d8b5680673716201089cb7039512cad2a12c0 2a9ea495215d1c03d2e0144f849fb8cb6c305f92 (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
AuthorDate: Wed Thu Jul 29 1630 15:2453:13 04 2015 -0700
Commit: Brian O'Connor [bocon@onlabJonathan Hart [jono@onlab.us]
CommitDate: Wed Thu Jul 30 23:29 16:24:13 2015 -0700
Initial implementation of the intent domain manager37 2015 +0000

Fix bug where SDN-IP installs more intents than needed
--
(cherry picked from commit 1258f86b564be76771c5cd6e1f807c4bc529168a)

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

...

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

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
• 3.2 Check app ids - PASS
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL
Reactive Pingall failed, one or more ping pairs failed
• 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

...

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

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

...

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - FAIL
ONOS nodes have different views of switch roles
• PASS
• 7.4 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - FAIL
ONOS nodes have different views of intents
• controller - PASS
• 7.6 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.7 Leadership Election is still functional - PASS

...

• 17.1 Increment then get a default counter on each node - PASS
• 17.2 Get then Increment a default counter on each node - FAIL
• Error incrementing default counter
• 17.3 Counters we added have the correct values - PASS
• 17.4 Add -8 to then get a default counter on each node - PASS
• 17.5 Add 5 to then get a default counter on each node - PASS
• 17.6 Get then add 5 to a default counter on each node - PASS FAIL
• Error incrementing default counter
• 17.7 Counters we added have the correct values - FAIL
• Added counters are incorrect
• PASS
• 17.8 Increment and get an in-memory counter on each node - PASS
• 17.9 Get then Increment a in-memory counter on each node - PASS
• 17.10 Counters we added have the correct values - PASS
• 17.11 Add -8 to then get a in-memory counter on each node - PASS - FAIL
• Error incrementing in-memory counter
• 17.12 Add 5 to then get a in-memory counter on each node - PASS - FAIL
• Error incrementing in-memory counter
• 17.13 Get then add 5 to a in-memory counter on each node - PASS
• 17.14 Counters we added have the correct values - PASS FAIL
• Added counters are incorrect
• 17.15 Check counters are consistant across nodes - PASS
• 17.16 Counters we added have the correct values - PASS
• 17.17 Distributed Set get - PASS
• 17.18 Distributed Set size - PASS
• 17.19 Distributed Set add() - FAIL
Set add was incorrect
• - PASS
• 17.20 Distributed Set addAll() - PASS FAIL
• Set addAll was incorrect
• 17.21 Distributed Set contains() - PASS
• 17.22 Distributed Set containsAll() - PASS
• 17.23 Distributed Set remove() - PASS
• 17.24 Distributed Set removeAll() - PASS
• 17.25 Distributed Set addAll() - PASS
• 17.26 Distributed Set clear() - PASS
• 17.27 Distributed Set addAll() - PASS FAIL
• Set addAll was incorrect
• 17.28 Distributed Set retain() - PASS

...

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

...

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

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

...

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

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

...

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

• 8.1 Comparing ONOS topology to MN - No Result
• 8.2 Collecting topology information from ONOS - PASS
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS FAIL
• ONOS nodes have different views of clusters
• 8.7 There is only one SCC - PASS FAIL
• ONOS shows 6 SCCs
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• 8.9 Links are correct - FAIL
• Links are incorrect
• 8.10 Checking ONOS nodes - PASS

...