master-FUNCformCluster

commit 85dab42e8b9a584dcabf8027c4da651e3217f678 (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey [ray@opennetworking.org]
AuthorDate: Fri Dec 15 13:10:02 2017 -0800
Commit: Ray Milkey [ray@opennetworking.org]
CommitDate: Fri Dec 15 13:40:07 2017 -0800

Sonar fix - bad equals method

Case 0: Constructing test variables and building ONOS package - PASS

For loading from params file, and pull and build the latest ONOS package

• 0.1 Constructing test variables - PASS

Case 1: Starting ONOS with indepenent configuration - PASS

Starting ONOS with one node itself.

• 1.1 Uninstalling ONOS package - PASS
• 1.2 Creating ONOS package - PASS
• 1.3 Installing ONOS package - PASS
• 1.4 Set up ONOS secure SSH - PASS
• 1.5 Checking ONOS service - PASS
• 1.6 Starting ONOS CLI sessions - PASS

Case 3: Checking the configuration of the ONOS - PASS

Checking the number of the nodes and apps

• 3.1 Checking the number of the nodes - PASS
• 3.2 Checking the app status. Only the first node should have org.onosproject.fwd installed. - PASS

Case 2: Starting ONOS with form cluster. - PASS

This will connect all the clusters of the ONOS.

• 2.1 Executing onos-form-cluster - PASS
• 2.2 Checking ONOS service - PASS
• 2.3 Starting ONOS CLI sessions - PASS

Case 4: Checking the configuration of the ONOS after form-cluster - PASS

Checking the number of the nodes and apps

• 4.1 Checking the number of the nodes - PASS
• 4.2 Checking the status of the nodes - PASS
• 4.3 Checking the app status. All nodes should have org.onosproject.fwd installed. - PASS

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

Compare topology elements between Mininet and ONOS

• 5.1 Starting Mininet - PASS
• 5.2 Pingall hosts to confirm ONOS discovery - FAIL
• Failed to discover hosts
• 5.3 Comparing Mininet topology to ONOS topology - FAIL
• ONOS incorrectly discovered the topology