Page History

...

commit 1b9c8ac7b22d0f4915d577f60bb5736b8177c22f 1d0019ca7dd4d44e41c43ceea911815a7cbecb03 (HEAD, origin/master, origin/HEAD, master)
Author: HIGUCHI Yuta [y-higuchi@ak.jp.nec.comThomas Vachuska [tom@onlab.us]
AuthorDate: Fri Mon Aug 28 1531 17:3502:43 17 2015 -0700
Commit: HIGUCHI Yuta [y-higuchi@ak.jp.nec.comGerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Aug 28 17:17:52 2015 -0700
Workaround for Eclipse
Tue Sep 1 02:56:07 2015 +0000

ONOS-2780 Correcting condition logic.

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

...

• 2.1 Assign switches to controllers - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

...

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

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

...

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS

Case 5: Setting up and gathering data for current state -

...

PASS

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - PASS
• 5.3 Check for consistency in roles from each controller - PASS
• 5.4 Get the intents from each controller - PASS
• 5.5 Check for consistency in Intents from each controller - PASS
• 5.6 Get the flows from each controller - PASS
• 5.7 Check for consistency in Flows from each controller - PASS
• 5.8 Get the OF Table entries - No Result
• 5.9 Start continuous pings - No Result
• 5.10 Collecting topology information from ONOS - No Result
• 5.11 Host view is consistent across ONOS nodes - PASS
• 5.12 Each host has an IP address - PASS
• 5.13 Cluster view is consistent across ONOS nodes - PASS
• 5.14 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 2 SCCs
• PASS
• 5.15 Comparing ONOS topology to MN - PASS
• 5.16 Device information is correct - FAIL
Device information is incorrect
• PASS
• 5.17 Links are correct - PASS
• 5.18 Hosts are correct - PASS

...

• 6.1 Killing ONOS nodes - PASS
• 6.2 Checking if ONOS is up yet - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
ONOS shows 2 SCCs
• SCC - PASS
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• 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

...

• 17.1 Increment then get a default counter on each node - PASS FAIL
• Error incrementing default counter
• 17.2 Get then Increment a default counter on each node - PASS FAIL
• Error incrementing default counter
• 17.3 Counters we added have the correct values - PASS FAIL
• Added counters are incorrect
• 17.4 Add -8 to then get a default counter on each node - PASS FAIL
• Error incrementing default counter
• 17.5 Add 5 to then get a default counter on each node - PASS FAIL
• Error incrementing default counter
• 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 - PASS FAIL
• Added counters are incorrect
• 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 a in-memory counter on each node - FAIL
• Error incrementing in-memory counter
on each node - PASS
• 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
• 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() - PASS
• 17.20 Distributed Set addAll() - PASS
• 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() - FAIL
Set clear was incorrect
• PASS
• 17.27 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• PASS
• 17.28 Distributed Set retain() - PASS
• 17.29 Partitioned Transactional maps put - PASS
• 17.30 Partitioned Transactional maps get - PASS
• 17.31 In-memory Transactional maps put - PASS
• 17.32 In-Memory Transactional maps get - PASS

...

• 9.1 Kill Link between s3 and s28 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

...

• 10.1 Bring link between s3 and s28 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

...

Case 11: Killing a switch to ensure it is discovered correctly - PASS

• 11.1 Kill s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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

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

Case 12: Adding a switch to ensure it is discovered correctly - PASS

• 12.1 Add back s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 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 - FAIL
ONOS shows 2 SCCs
• PASS
• 8.8 Device information is correct - FAIL
Device information is incorrect
• PASS
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

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

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

...