View Source

HATestSanity at 24 Jul 2015 02:31:08

commit 0276a32e8cd7a5cdd0480ad2c570e07f90b8162f (HEAD)
Author: samuel [jiangchuncheng@huawei.com]
AuthorDate: Mon Jul 13 16:35:17 2015 +0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Jul 14 23:16:30 2015 +0000

[ONOS-2374]Add getter method in IpTunnelEndPoint

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

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Git checkout and pull HEAD~5 - FAIL

Git pull failed

1.4 Using mvn clean install - PASS
1.5 Creating ONOS package - PASS
1.6 Installing ONOS package - PASS
1.7 Checking if ONOS is up yet - PASS
1.8 App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

2.1 Assign switches to controllers - PASS

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

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

ONOS nodes have different views of clusters

8.7 There is only one SCC - FAIL

ONOS shows 27 SCCs

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

21.1 Assign mastership of switches to specific controllers - PASS
21.2 Check mastership was correctly assigned - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result

commit 5160dbb84d39beeca1b227e0e4700dbb7ac3d77a (HEAD)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Tue Jul 14 10:21:45 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Jul 14 17:24:28 2015 +0000

Adding multiple links to the ATT MPLS test topology.

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

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Git checkout and pull HEAD~5 - FAIL

Git pull failed

1.4 Using mvn clean install - PASS
1.5 Creating ONOS package - PASS
1.6 Installing ONOS package - PASS
1.7 Checking if ONOS is up yet - PASS
1.8 App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

2.1 Assign switches to controllers - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

21.1 Assign mastership of switches to specific controllers - PASS
21.2 Check mastership was correctly assigned - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result

commit 038aedde3012f2c03e55cd89c9febad728877f25 (HEAD)
Author: Bri Prebilic Cole [bri@onlab.us]
AuthorDate: Mon Jul 13 15:25:16 2015 -0700
Commit: Bri Prebilic Cole [bri@onlab.us]
CommitDate: Mon Jul 13 16:33:14 2015 -0700

ONOS-2328 GUI -- Enhanced Topology View to show multiple links individually between devices (1 - 4). 5 or more is a thick line.

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

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Git checkout and pull HEAD~5 - FAIL

Git pull failed

1.4 Using mvn clean install - PASS
1.5 Creating ONOS package - PASS
1.6 Installing ONOS package - PASS
1.7 Checking if ONOS is up yet - PASS
1.8 App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

2.1 Assign switches to controllers - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

21.1 Assign mastership of switches to specific controllers - PASS
21.2 Check mastership was correctly assigned - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result

commit aeeb33ef1c57c619549db52f1bdfda246f4a6150 (HEAD)
Author: Bri Prebilic Cole [bri@onlab.us]
AuthorDate: Thu Jul 9 15:15:54 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Jul 9 23:59:32 2015 +0000

ONOS-2328 GUI -- Started work on seeing multiple links between devices on the topology view. Device links are now grouped based on what device they are between. Also minor bug fixes and investigations into other bugs. WIP.

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

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Git checkout and pull HEAD~5 - FAIL

Git pull failed

1.4 Using mvn clean install - PASS
1.5 Creating ONOS package - PASS
1.6 Installing ONOS package - PASS
1.7 Checking if ONOS is up yet - PASS
1.8 App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

2.1 Assign switches to controllers - PASS

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

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

ONOS nodes have different views of clusters

8.7 There is only one SCC - FAIL

ONOS shows 26 SCCs

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

21.1 Assign mastership of switches to specific controllers - PASS
21.2 Check mastership was correctly assigned - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result

commit 1937bbb6f6f7d77b28e8bdb0c3693647a4cd6892 (HEAD)
Author: Damian ONeill [doneill@btisystems.com]
AuthorDate: Wed Jul 8 17:03:19 2015 +0100
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Jul 9 20:31:04 2015 +0000

added some null checks for device instance

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

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

1.1 Applying cell variable to environment - No Result
1.2 Starting Mininet - PASS
1.3 Git checkout and pull HEAD~5 - FAIL

Git pull failed

1.4 Using mvn clean install - PASS
1.5 Creating ONOS package - PASS
1.6 Installing ONOS package - PASS
1.7 Checking if ONOS is up yet - PASS
1.8 App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

2.1 Assign switches to controllers - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

21.1 Assign mastership of switches to specific controllers - PASS
21.2 Check mastership was correctly assigned - PASS

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

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

8.8 Device information is correct - FAIL

Device information is incorrect

8.9 Links are correct - FAIL

Links are incorrect

8.10 Hosts are correct - PASS
8.11 Checking ONOS nodes - PASS

Case 13: Test Cleanup - PASS

13.1 Killing tcpdumps - No Result
13.2 Copying MN pcap and ONOS log files to test station - No Result
13.3 Stopping Mininet - PASS
13.4 Checking ONOS Logs for errors - No Result
13.5 Packing and rotating pcap archives - No Result