...
commit a578d76b0fbf84bdc77f7699c074c16e24e05441 0ee6aa2d9275178391480a2d1beab56bc6a020e8 (HEAD, origin/master, origin/HEAD, master)
Author: Yoonseon Han Yi Tseng [yoonseon@onlaba86487817@gmail.uscom]
AuthorDate: Mon Fri May 8 1319 14:4243:02 27 2017 -0700
Commit: Yoonseon Han Luca Prete [yoonseon@onlabluca@onlab.us]
CommitDate: Thu Fri May 18 1219 23:1301:22 35 2017 -0700+0000
[ONOS-6395] (vNet) Defining mastership service6493] Fix VPLS Intent failure handling problem
Case 1: Constructing test variables and building ONOS package - PASS
...
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules -
...
FAIL
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 FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
- 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 - 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
- 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 FAIL
- Assertion Result for VLAN Encapsulation Point Intent
- 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
...
- 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 - FAIL
- Assertion results for VLAN Encapsulation multi to single point intentInstall Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- 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 Received Passed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Rules - 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 - 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 FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
This test case will test point to point 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
- 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 - PASS
- 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 - FAIL
- Assertion Result for VLAN Encapsulation Point Intent
- 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 - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
This test case will test single point to multi point 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
- 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
This test case will test single point to multi point 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
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- 4000.2 IPV4: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
- 4000.3 IPV4_2: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - FAIL
- Mobility: Failed to move h1 to s6 to single point intents with IPV4 type and MAC addresses in the same VLAN
- 5000.2 IPV4: Add host intents between h1 and h9 - FAIL
- Assert result for IPV4 host intent between h1, moved, and h9
- Install Intent State Failed
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - FAIL
- Assertion results for IPV4 multi to single point intent end point failure with no options set
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
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
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS