Master-FUNCintent

FUNCintent at 11 May 2017 16:22:42

commit 66fee924a6f956e4edbf1cdcb4e9340a74851671 (HEAD, origin/master, origin/HEAD, master)
Author: Saritha [saritha.rt@samsung.com]
AuthorDate: Wed May 10 12:40:48 2017 +0530
Commit: Thomas Vachuska [tom@onlab.us]
CommitDate: Thu May 11 22:30:04 2017 +0000

Suspicious reference comparison - Questionable use of reference equality rather than calling equals

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 Set up ONOS secure SSH - PASS
2.6 Starting ONOS service - PASS
2.7 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 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 VLAN2: Add vlan host intents between h4 and h13 - PASS
1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
1000.8 Confirm that ONOS leadership is unchanged - PASS

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

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 Protected: Add point intents between h1 and h9 - FAIL

Assertion Result for protected point intent
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Link Down Passed
Link down Scapy Packet Received Passed
Protected Intent Check Passed
Link Down Intent State Failed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Failed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents Passed

2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL

Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
Initial Iperf Passed
Remove Intents Passed

2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
2000.8 VLAN: Add point intents between h5 and h21 - PASS
2000.9 VLAN: Add point intents between h5 and h21 - PASS
2000.10 1HOP: Add point intents between h1 and h3 - PASS
2000.11 Add point to point intents using VLAN Encapsulation - PASS
2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL

Assertion Result for BANDWIDTH ALLOCATION for point intent
Bandwidth Allocation Failed

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

This test case will test single point to multi 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

3000.1 NOOPTION: Install and test single point to multi point intents - PASS
3000.2 IPV4: Install and test single point to multi point intents - PASS
3000.3 IPV4_2: Add single point to multi point intents - PASS
3000.4 VLAN: Add single point to multi point intents - PASS
3000.5 VLAN: Add single point to multi point intents - PASS

Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - FAIL