commit a2e61a5eb03e503d09003a8a37f1cf0737353c0c (HEAD, origin/master, origin/HEAD, master)
Author: gaurav [GS00347734@techmahindra.com]
AuthorDate: Thu May 5 03:39:31 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Jun 3 22:22:59 2016 +0000

clean up the SingleSwitchFibInstaller, added the predeactivate hook and modified unit test CORD-663

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

This test case is mainly for loading from params file, and pull and build the latest ONOS package

• 1.1 Constructing test variables - PASS

Case 2: Starting up 1 node(s) ONOS cluster - PASS

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out if topology did not start correctly

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

• 13.1 Create scapy components - No Result
• 13.2 Start scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

• 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
• 15.2 Populate hostsData - PASS

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

• 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 1HOP: Add point intents between h1 and h3 - PASS

Case 5000: Test host mobility with host intents - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS