...
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintentRest_master_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0"> |
commit b53d626fb03195129c0ec0802e1f953f85dcbef8 commit 03398d53cb68bc43fa37bfe3a8d2b42fc71e2115 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li pierventre [pyguni@gmailpier@opennetworking.comorg]
AuthorDate: Tue May 23 14Wed Sep 22 11:24:11 2017 38 2021 +09000200
Commit: Jian Li [pyguni@gmail.comPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue May Thu Sep 23 2207:1938:15 2017 +0000
Fix: resolve potential NPE in LispInfo request and reply36 2021 +0000
[SDFAB-612] Cluster not ready when using recent tost master images
--
(cherry picked from commit ec0e942320ef27932b4173172055151015261d7c)
Case 1:
...
Pull onos branch and build onos on Teststation. - PASS
This test case is mainly for For loading from params file, and pull and build the latest ONOS package
...
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Uninstalling ONOS package Apply cell to environment - PASS
- 2.2 Apply cell to environment Uninstalling Atomix - PASS
- 2.3 Creating Uninstalling ONOS package - PASS
- 2.4 Installing Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service 8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.7 Start 11 Checking ONOS cli applications - PASS
Case 10: Start Mininet topology with OF 1.0 switches - PASS
...
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules -
...
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 Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2 3000.4 VLAN: Add single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - PASS FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
Case 19: Copy karaf logs - PASS
...
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Uninstalling ONOS package Apply cell to environment - PASS
- 2.2 Apply cell to environment Uninstalling Atomix - PASS
- 2.3 Creating Uninstalling ONOS package - PASS
- 2.4 Installing Creating ONOS package - PASS
- 2.5 Set up ONOS secure SSH Installing Atomix - PASS
- 2.6 Starting Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications 7 Start ONOS cli - PASS
Case 10: Start Mininet topology with OF 1.0 switches - PASS
...
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -
...
FAIL
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2 3000.4 VLAN: Add single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - PASS FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
Case 19: Copy karaf logs - PASS
...
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Uninstalling ONOS package Apply cell to environment - PASS
- 2.2 Apply cell to environment Uninstalling Atomix - PASS
- 2.3 Creating Uninstalling ONOS package - PASS
- 2.4 Installing Creating ONOS package - PASS
- 2.5 Set up ONOS secure SSH Installing Atomix - PASS
- 2.6 Starting Installing ONOS service package - PASS
- 2.7 Start ONOS cli 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
...
- 17.1 Enabling 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 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 and test host intents between h1 and h9 - FAIL
- Assertion result for IPV4 host intent with mac addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Remove Intents Passed
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
- Assertion Result for dualstack IPV4 with MAC addresses
- 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 Pingall Failed
- Remove Intents Passed
- 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 - FAIL
- Assertion Result vlan IPV4
- 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 Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.6 Confirm that ONOS leadership is unchanged - FAIL
- ONOS Leader Mismatch
...
- PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow 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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 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
- 2000 3000.1 NOOPTION: Add Install and test single point to multi point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION results for IPV4 single to multi point intent with no options set
- 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 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 Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 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 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 Passed
- 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 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 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 Recieved Failed
- Remove Intents Passed
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for 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 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 Passed
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
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
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
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 Uninstalling ONOS package - PASS
- 2.2 Apply cell to environment - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service - PASS
- 2.7 Start ONOS cli - PASS
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out if topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 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 - FAIL
This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives
- 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL
- Assertion result for IPV4 host intent with mac addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping 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 Pingall Failed
- Remove Intents Passed
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL
- Assertion Result for dualstack2 host intent
- 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 Pingall Failed
- Remove Intents Passed
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
- Assertion Result vlan IPV4
- 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 Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.6 Confirm that ONOS leadership is unchanged - FAIL
- ONOS Leader Mismatch
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 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
- 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 Failed
- 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 Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 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 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 Recieved Failed
- Remove Intents Passed
- 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address 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 Passed
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address 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 Passed
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
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
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - FAIL
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - FAIL
- Failed to stop mininet
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 Uninstalling ONOS package - PASS
- 2.2 Apply cell to environment - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service - PASS
- 2.7 Start ONOS cli - PASS
Case 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 - FAIL
- 15.1 Send packets from each host to the first host and confirm onos discovery - FAIL
- ONOS incorrectly discovered hosts
- Skipping the rest of this case.
Case 16: - FAIL
- Skipping the rest of this case.
Case 1000: - FAIL
- Skipping the rest of this case.
Case 2000: - FAIL
- Skipping the rest of this case.
Case 3000: - FAIL
- Skipping the rest of this case.
Case 5000: - FAIL
- Skipping the rest of this case.
...
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out if topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 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 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
- 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test point to point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow 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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 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
- 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
...
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - FAIL
- Failed to stop 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 Uninstalling ONOS package Apply cell to environment - PASS
- 2.2 Apply cell to environment Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 4 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service 8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.7 Start 11 Checking ONOS cli 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
...
- 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 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.1 IPV4: Add and test host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test -
...
1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
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.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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 3000: Single to Multi Point Intents Test -
...
1 NODE(S) - OF 1.3 - Using Flow Rules -
...
FAIL
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.1 NOOPTION: Install and test single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - PASS FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2: Add single point to multi point intents - PASS 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 - PASS FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - PASS - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
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 1 3 node(s) ONOS cluster
- 2.1 Uninstalling ONOS package Apply cell to environment - PASS
- 2.2 Apply cell to environment Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 4 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service 8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.7 Start 11 Checking ONOS cli 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
...
- 16.1 Balancing mastership of switches - PASS
Case
...
- 17.1 Enabling Flow Objectives - PASS
...
1000: Host Intents Test -
...
3 NODE(S) - OF 1.3 - Using Flow
...
Rules -
...
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 OVS running in Mininet and compile intents using Flow ObjectivesRules
- 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL
- Assertion result for IPV4 host intent with mac addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Remove Intents Passed
- and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
- Assertion Result for dualstack IPV4 with MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Remove Intents Passed
- and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL
- Assertion Result for dualstack2 host intent
- 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 Pingall Failed Remove Intents Passed
- PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
- Assertion Result vlan IPV4
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Remove Intents Passed
- PASS
- 1000.6 Confirm that ONOS leadership is unchanged - FAIL ONOS Leader Mismatch
- PASS
Case 2000: Point Intents Test -
...
3 NODE(S) - OF 1.3 - Using Flow
...
Rules -
...
PASS
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 OVS running in Mininet and compile intents using Flow ObjectivesRules
- 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
- 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 Passed
- - PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for 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 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 Recieved Failed Remove Intents Passed
- - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address 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 Passed
- and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 3000: Single to Multi 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 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
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passedoptions set
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
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 Uninstalling ONOS package - PASS
- 2.2 Apply cell to environment - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Starting ONOS service - PASS
- 2.7 Start ONOS cli - PASS
Case 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 and test host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL
- Assertion Result for dualstack IPV4 with MAC addresses
- 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 Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents Passed
- 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 - FAIL
- Assertion Result vlan IPV4
- 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 Pingall Failed
- Remove Intents Passed
- 1000.6 Confirm that ONOS leadership is unchanged - FAIL
- ONOS Leader Mismatch
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
- in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - 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 and test host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
Case 3000: Single to Multi 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
- 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - 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 - 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 Objectives
- 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
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
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.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 Failed
- 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 Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 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 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 Recieved Failed
- Remove Intents Passed
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- Assertion Result for 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 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 Passed
- 2000.7 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address 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 Passed
- 2000.8 1HOP: Add point intents between h1 and h3 - PASS
...
- 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passedoptions set
- 3000.2 IPV4: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passedintent 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
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passedtype and MAC addresses in the same VLAN
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet Topology - PASS
Case 19: Copy karaf logs - PASS
...