Master-FUNCintent

commit c3e0c600cce48efab8827c5e5260a491d7ea7a73 (HEAD -] master, origin/master, origin/HEAD)
Author: Daniel Park [dan.mcpark84@gmail.com]
AuthorDate: Thu Aug 30 21:27:25 2018 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Fri Aug 31 02:30:58 2018 +0000

Fixes to deal with unsupported vendor type interface in OpenstackSwitchingDirectPortProvider

Case 1: Pull onos branch and build onos on Teststation. - PASS

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 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - 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 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 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 - PASS

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

• 4000.1 NOOPTION: Add multi point to single point intents - PASS
• 4000.2 IPV4: Add multi point to single point intents - PASS
• 4000.3 IPV4_2: Add multi point to single point intents - PASS
• 4000.4 VLAN: Add multi point to single point intents - PASS
• 4000.5 VLAN: Add multi point to single point intents - PASS
• 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Rules - 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 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

• 6000.1 Installing Multi to Single Point intents with no options set - PASS
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
• 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - 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 - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - 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 - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

This test case tests Host intents using 3 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 - FAIL
• Assertion Result for IPV4 host intent with mac addresses
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Pingall Passed
• Remove Intents FailedAfter removing intents Flow State Passed
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
• Assertion Result for dualstack IPV4 with MAC addresses
• Install Intent State Failed
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL
• Assertion Result for dualstack2 host intent
• Install Intent State Failed
• After removing intents Flow State Passed
• 1000.4 1HOP: Add host intents between h1 and h3 - FAIL
• Assertion Result for 1HOP for IPV4 same switch
• Install Intent State Failed
• After removing intents Flow State Passed
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
• Assertion Result vlan IPV4
• Install Intent State Failed
• After removing intents Flow State Passed
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - FAIL
• Assertion Result vlan IPV4
• Install Intent State Failed
• After removing intents Flow State Passed
• 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
• Assertion Result for VLAN Encapsulated host intent
• Install Intent State Failed
• After removing intents Flow State Passed
• 1000.8 Confirm that ONOS leadership is unchanged - PASS