Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
| HTML |
|---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintent_master_20-builds_graph.jpg", alt="FUNCintent", style="width:525px;height:350px;border:0"> |
commit 933b0fe7bb8639124a5679714e4d80462953a012 46d557f868c4a1d904de7669f7bff0241e7b709f (HEAD -] master, origin/master, origin/HEAD)
Author: Ai Hamano pier [ai.hamano@ntt-at.co.jppier@opennetworking.org]
AuthorDate: Fri Tue Nov 30 27 11:2223:37 50 2018 +0900-0800
Commit: Andrea Campanella [andrea@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Fri Dec 4 237 21:0020:49 07 2018 +0000
[ODTN]Update TAPI YANG files
Provides a separate executor to handle map events.
Case 1: Pull onos branch and build onos on Teststation. - 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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed After removing intents Flow State Passed
- PASS
- 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 - FAIL
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- 2000.4 IPV4_2: Add point intents between h1 and h9 - FAIL
- 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
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow State Passed
- 2000.5 SDNIP-ICMPTCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- PASS
- 2000.6 DUALSTACK1 2000.6 SDNIP-TCP: Add point intents between h1 h3 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
- Initial Iperf Passed Remove Intents Failed
- h11 - PASS
- 2000.7 DUALSTACK1VLAN: Add point intents between h3 h5 and h11 - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents After removing intents Flow State Passed
- h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL Assertion Result for VLAN IPV4 with mac address point intents
- PASS
- 2000.9 VLAN1HOP: Add point intents between h5 h1 and h21 - FAIL Assertion Result for VLAN IPV4 point intents with VLAN treatment
- h3 - PASS
- 2000.10 1HOP: Add point to point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents After removing intents Flow State Passed
- using VLAN Encapsulation - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent After removing intents Flow State Passed
- 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 - FAIL
- Assertion results for IPV4 single to multi point intent with no options set After removing intents Flow State Passed
- PASS
- 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 After removing intents Flow State Passed
- PASS
- 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
- PASS
- 3000 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 After removing intents Flow State Passed
- PASS
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment After removing intents Flow State Passed
- 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 - FAIL
- Assertion results for NOOPTION multi to single point intent After removing intents Flow State Passed
- PASS
- 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 After removing intents Flow State Passed
- PASS
- 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
- After removing intents Flow State Passed
- PASS
- 4000 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 After removing intents Flow State Passed
- PASS
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment After removing intents Flow State Passed
- PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent After removing intents Flow State Passed
- 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 - FAIL
- Assertion results for IPV4 multi to single point intent end point failure with no options set
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS After removing intents Flow State Passed
- 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 After removing intents Flow State Passed
- PASS
- 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 After removing intents Flow State Passed
- PASS
Case 18: Stop Mininet and Scapy - PASS
...
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -
...
PASS
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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed After removing intents Flow State Passed
- PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL 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 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents Assertion Result for NOOPTION point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping PassedFailed
- Link Down Passed
- Link Down Intent State FailedPassed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall PassedFailed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received PassedRecieved Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV45 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 point intentusing ICMP point intents
- Initial Iperf Failed
- Remove Intents After removing intents Flow State Passed
- 2000.3 Protected6 DUALSTACK1: Add point intents between h1 h3 and h9 - FAIL
- Assertion Result for protected point intent After removing intents Flow State Passed
- h11 - PASS
- 2000.4 IPV4_27 VLAN: Add point intents between h1 h5 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents After removing intents Flow State Passed
- h21 - PASS
- 2000.5 SDNIP-ICMP8 VLAN: Add point intents between h1 h5 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- h21 - PASS
- 2000.9 1HOP 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 Failed
- h3 - PASS
- 2000.7 DUALSTACK1: 10 Add point to point intents between h3 and h11 using VLAN Encapsulation - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- VLAN Encapsulation Point IntentInstall Intent State Passed
- Encapsulation intents check failed
- 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 Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
- point intent
- Install Intent State Passed
- Bandwidth Allocation check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
Case 3000Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
...
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter After removing intents Flow State PassedFailed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State FailedAfter removing intents Flow State Passed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- After removing intents Flow State PassedFailed
- 3000.5 4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
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
- IPV4 type and MAC addresses in the same VLAN
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
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
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- After removing intents Flow State Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation NOOPTION multi to single point intent
- After removing intents Flow State Passed
Case 5000: Test host mobility with host intents - 3 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 - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.2 IPV4: Add multi point to single point intents - FAIL
- Assertion
- 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- with IPV4 type and MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.3 IPV4_2: Add multi point to single point intents 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 multi to single to multi point intent with partial failures allowed
- After removing intents Flow State Passed
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 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 17: Enable intent compilation using Flow Objectives - FAIL
- 17.1 Enabling Flow Objectives - FAIL
- Failed to activate Flow Objectives
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - 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 Objectives
- 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 - 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
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - 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 Objectives
- IPV4 type and no MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION 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 Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall FailedPassed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State PassedFailed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Failed
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 - PASS
- 5000.2 IPV4: Add host
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- 2000.4 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow State Passed
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
- Initial Iperf Failed
- Remove Intents Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
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 Objectives
- Assert result for IPV4 host intent between h1, moved, and h9
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents PassedAfter removing intents Flow 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Failed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 multi to 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
- After removing intents Flow State Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
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 Objectives
- with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Failed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 single to multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- After removing intents Flow State Passed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- After removing intents Flow State Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- After removing intents Flow State Passed
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Objectives - 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 Objectives - 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
Case 18: Stop Mininet and Scapy - PASS
- partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- 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 PassedAfter removing intents Flow State Passed
Case 18: Stop Mininet and Scapy - PASS
Stopping 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
...
1 node(s) ONOS cluster - PASS
Set up ONOS with 3 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 17: Enable intent compilation using Flow Objectives -
...
PASS
- 17.1 Enabling Flow Objectives - FAIL Failed to activate Flow Objectives
- PASS
Case 1000: Host Intents Test -
...
1 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
This test case tests Host intents using 3 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 Objectives
- 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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed After removing intents Flow State Passed
- PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test -
...
1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
This test case will test point to point intents using 3 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 Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping PassedFailed
- Link Down Passed
- Link Down Intent State FailedPassed
- 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 PassedRecieved Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- 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
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- 2000.4 3 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow Install Intent State Passed
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 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 Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- 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
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN4 SDNIP-ICMP: Add point intents between h5 h1 and h21 h9 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intentsSDNIP-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.5 SDNIP-TCP 2000.9 VLAN: Add point intents between h5 h1 and h21 h9 - FAIL
- Assertion Result for VLAN SDNIP-TCP IPV4 using ICMP point intents with VLAN treatment
- Initial Iperf Failed
- Remove Intents Passed
- 2000.10 1HOP6 DUALSTACK1: Add point intents between h1 h3 and h3 h11 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents IntentInstall Intent State Passed
- Encapsulation intents check failed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - 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 Objectives
- 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.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check 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
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
Case
...
3000: Single to Multi
...
Point Intents Test -
...
1 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
This test case will test single point to multi point intents using 3 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 Objectives
- 4000 3000.1 NOOPTION: Add multi Install and test single point to single multi point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- After removing intents Flow State Passed
- PASS
- 3000 4000.2 IPV4: Add multi Install and test single point to single multi point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
- After removing intents Flow State Passed
- PASS
- 3000 4000.3 IPV4_2: Add multi single point to single multi point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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 Objectives - 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 Objectives
- 4000.1 NOOPTION 4000.5 VLAN: Add multi point to single point intents - FAIL Assertion results for multi
- PASS
- 4000.2 IPV4: Add multi point to single point intent with VLAN ID treatmentAfter removing intents Flow State Passed
- intents - PASS
- 4000.6 ENCAPSULATION3 IPV4_2: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- 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 After removing intents Flow State Passed
Case 5000: Test host mobility with host intents -
...
1 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - FAIL PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 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 - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down
- Assert result for IPV4 host intent between h1, moved, and h9
- 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 FailedPassed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Failed
- Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Link Up Flow State Passed
- Link Up Topology State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Failed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Failed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Link Up Pingall Failed
- Remove Intents PassedAfter FailedAfter removing intents Flow State Passed
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
- 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
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 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.3 0 switches to test intents, exits out if topology did not start correctly
- 11 10.1 Starting Mininet topology with OF 1.3 0 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test -
...
3 NODE(S) - OF 1.
...
0 - Using Flow
...
Objectives -
...
PASS
This test case tests Host intents using 1 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.3 0 OVS running in Mininet and compile intents using Flow RulesObjectives
- 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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed After removing intents Flow State Passed
- PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test -
...
3 NODE(S) - OF 1.
...
0 - Using Flow
...
Objectives - FAIL
This test case will test point to point intents using 1 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.3 0 OVS running in Mininet and compile intents using Flow RulesObjectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL 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 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- Install Intent State Passed
- Assertion Result for NOOPTION point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping PassedFailed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State FailedPassed
- Link Down Topology State Passed
- Link Down Pingall PassedFailed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received PassedRecieved Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV45 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN 2000.3 Protected: Add point intents between h1 h5 and h9 h21 - FAIL
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP 2000.4 IPV4_2: Add point intents between h1 and h9 h3 - FAIL
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow State Passed
- PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 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 Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
...
- PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
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 Objectives
- 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 - 3 NODE(S) - OF 1.
...
0 - Using Flow
...
Objectives -
...
PASS
This test case will test single point to multi point intents using 1 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.3 0 OVS running in Mininet and compile intents using Flow RulesObjectives
- 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- After removing intents Flow State Passed
- PASS
- 4000 3000.2 IPV4: Install and test single Add multi point to multi single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- After removing intents Flow State Passed
- PASS
- 4000 3000.3 IPV4_2: Add single multi point to multi single 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
- After removing intents Flow State Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
...
- 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 - 3 NODE(S) - OF 1.0 - Using Flow Objectives - 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 - 3 NODE(S) - OF 1.
...
0 - Using Flow
...
Objectives - FAIL
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.3 OVS running in Mininet and compile intents using Flow Rules
- 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 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION IPV4 single to multi to single point intent
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Failed
- Isolation link Down Passed
- Isolation link Down Intent State Failed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Failed
- Link Up Passed
- Link Up Passed
- 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 PassedAfter
- Assertion results for multi to single point intent with VLAN ID treatment
- After removing intents Flow State Passed
- 4000 6000.6 ENCAPSULATION: Add multi 4 NOOPTION: Install and test single point to single multi point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- After removing intents Flow State Passed
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 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
- 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
...
19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - 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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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.3 - 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.3 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
- 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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
...
NODE(S) - OF 1.3 - Using Flow Rules - FAIL
This test case tests Host will test point to point intents using 3 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.3 OVS running in Mininet and compile intents using Flow Rules
- 1000 2000.1 IPV4NOOPTION: Add host point intents between h1 and h9 - PASS 1000
- 2000.2 DUALSTACK1IPV4: Add host point intents between h3 h1 and h11 h9 - PASS 1000
- 2000.3 DUALSTACK2IPV4_2: Add host point intents between h1 and h11 h9 - PASS 1000
- 2000.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 SDNIP-ICMP: Add point 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
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - 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.3 OVS running in Mininet and compile intents using Flow Rules
- 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
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION 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 Intent State FailedPassed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall PassedFailed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received PassedRecieved Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV45 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN 2000.3 Protected: Add point intents between h1 h5 and h9 h21 - FAIL
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP 2000.4 IPV4_2: Add point intents between h1 and h9 h3 - FAIL
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow State Passed
- PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 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 Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
...
- PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - 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.3 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.3 - Using Flow Rules -
...
PASS
This test case will test single point to multi point intents using 3 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.3 OVS running in Mininet and compile intents using Flow Rules
- 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000 3000.3 IPV4_2: Add single multi point to multi single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- PASS
- 4000 3000.4 VLAN: Add single multi point to multi single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- After removing intents Flow State Passed
- PASS
- 4000 3000.5 VLAN: Add single multi point to multi single point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
...
- 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.3 - 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.3 - 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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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.3 - Using Flow Rules - PASS
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.3 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 - 3 NODE(S) - OF 1.3 - 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.3 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 - 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.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 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point
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.3 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- After removing intents Flow State Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- After removing intents Flow State Passed
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - 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 - 3 NODE(S) - OF 1.3 - 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
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 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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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 17: Enable intent compilation using Flow Objectives - FAIL
- 17.1 Enabling Flow Objectives - FAIL
- Failed to activate Flow Objectives
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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
- 2000.5 VLAN1: Add vlan host intents between h4 and h12 10 Add point to point intents using VLAN Encapsulation - PASS 1000.6 VLAN2: Add vlan host intents between h4 and h13
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
- 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
...
Case 3000: Single to Multi Point Intents Test -
...
3 NODE(S) - OF 1.3 - Using Flow
...
Rules -
...
PASS
This test case will test single point to multi point intents using 1 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.3 OVS running in Mininet and compile intents using Flow ObjectivesRules
- 2000 3000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION 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 Intent State Passed
- Link Down Flow State Failed
- 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 PassedAfter removing intents Flow State Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- After removing intents Flow State Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- 2000.4 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents
- After removing intents Flow State Passed
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 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 Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
...
- 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 - 3 NODE(S) - OF 1.3 - 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.3 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 - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- Install 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 Passed
- 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 PassedAfter removing intents Flow State Failed
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Rules - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 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 Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents PassedAfter removing intents Flow State Failed
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - 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
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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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
- After removing intents Flow Install Intent State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- After removing intents Flow State Passed
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
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.3 OVS running in Mininet and compile intents using Flow Objectives
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Failed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Failed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
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 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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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 - 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.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 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 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.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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.3 - Using Flow Objectives - 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.3 - Using Flow Objectives - FAIL
- 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 - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Failed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.3 NOOPTION: Install and test single point to multi
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 single to multi to single point intent with IPV4 type and no MAC addresses in the same VLANno options set
- After removing intents Flow State Passed
- 4000 6000.5 VLAN: Add multi 4 NOOPTION: Install and test single point to single multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi to single point intent with VLAN ID treatmentpartial failures allowed
- After removing intents Flow State Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- After removing intents Flow State Passed
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Objectives - 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.3 - Using Flow Objectives - 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
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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 17: Enable intent compilation using Flow Objectives - FAIL
- 17.1 Enabling Flow Objectives - FAIL
- Failed to activate Flow Objectives
...
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 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 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 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Passed
- Encapsulation intents check failed
- 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 Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
This test case tests Host 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 1000 2000.1 IPV4NOOPTION: Add host point 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
- FAIL
- Assertion Result for NOOPTION 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 Intent State Failed
- 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 Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV4: Add point 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intentIPV4 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 Install Intent State Failed
- After removing intents Flow State Passed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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 Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.3 IPV4_2 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intentIPV4 no mac address point intents
- 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 Failed
- Link Down Topology State Passed
- Link Down Pingall FailedPassed
- 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 PassedAfter removing intents Flow State Passed
- 2000.2 IPV44 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 point intent
- After removing intents Flow State Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- 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 Failed
- 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
- Assertion Result for protected point intent
- After removing intents Flow State Passed
- 2000.4 IPV4_25 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address SDNIP-TCP IPV4 using ICMP point intents
- Initial Iperf Failed
- Remove Intents After removing intents Flow State Passed
- 2000.5 SDNIP-ICMP6 DUALSTACK1: Add point intents between h1 h3 and h9 h11 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- After removing intents Flow State Passed
- 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 Failed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Dualstack1 IPV4 with mac address point intents
- 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 Failed
- 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 Scapy Packet Received Passed
- Remove Intents PassedAfter
- Assertion Result for Dualstack1 IPV4 with mac address point intents
- After removing intents Flow State Passed
- 2000.8 7 VLAN: Add point intents between h5 and h21 - FAIL Assertion Result for VLAN IPV4 with mac address point intents
- PASS
- 2000.9 8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- After removing intents Flow State Passed
- PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 2000.11 Add point to point intents using VLAN Encapsulation - FAIL Assertion Result for VLAN Encapsulation Point IntentAfter removing intents Flow State Passed
- PASS
- 2000.12 11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check 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 Failed
- 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 Scapy Packet Received Passed
- Remove Intents PassedAfter
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- After removing intents Flow State Passed
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives -
...
PASS
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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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 After removing intents Flow State Passed
- PASS
- 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 After removing intents Flow State Passed
- PASS
- 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
- PASS
- 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 After removing intents Flow State Passed
- PASS
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment After removing intents Flow State Passed
- PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives -
...
PASS
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.3 OVS running in Mininet and compile intents using Flow Objectives
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- 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
- After removing intents Flow State Passed
- PASS
- 4000.2 IPV4 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
- After removing intents Flow State Passed
- PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 4000.5 VLAN: Add multi point to single point intents - FAIL Assertion results for multi
- PASS
- 4000.5 VLAN: Add multi point to single point intent with VLAN ID treatmentAfter removing intents Flow State Passed
- intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent After removing intents Flow State Passed
- PASS
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
...
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAILObjectives - FAIL
- 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 6000.1 Installing Multi to Single Point intents with no options set - FAIL
- Assertion results for IPV4 single to multi to single point intent end point failure with no options set
- After removing intents Flow State Passed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- After removing intents Flow State Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Failed
- Isolation link Down Passed
- Isolation link Down Intent State Failed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Failed
- Link Up Passed
- Link Up Passed
- 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 PassedAfter
- Assertion results for IPV4 single to multi point intent with no options set
- After removing intents Flow State Passed
- 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 After removing intents Flow State Passed
- PASS
Case 18: Stop Mininet and Scapy - PASS
...