...
...
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 74052d43a37556f385594aa505df237c2aecc6d9 (HEAD, origin/master, origin/HEAD, master)
Author: utkarsh pierventre [utkarshpier@opennetworking.ag@samsung.comorg]
AuthorDate: Thu Nov 16 10:53:55 2017 +0900Wed Sep 22 11:24:38 2021 +0200
Commit: Andrea Campanella [andrea@opennetworkingPier Luigi Ventre [pier@opennetworking.org]
CommitDate: Fri Nov 17 03:29:49 2017 +0000
Added app origin to the BUCK fileThu Sep 23 07:38:36 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
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 10: 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 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
- 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 3000.5 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 - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case Case 5000: Test host mobility with host intents - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 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
...
- 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 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 Case 5000: Test host mobility with host intents - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 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
...
- 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: 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 - 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 - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - PASS
Case 5000: Test host mobility with host intents - PASS
- 5000.1 Testing host mobility by moving 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling ONOS package Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 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
...
- 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 - 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 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
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 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.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
...
- 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 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
- 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 3000.5 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 - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 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 - PASSCase 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
...
- 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.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
- 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
- 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 3000.5 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 - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 9 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - 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
...
- 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 - 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
- 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 3000.5 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 - FAIL
- Assertion results for single to multi point intent with VLAN treatment
Case 5000: Test host mobility with host intents - PASS
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.3 4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.4 6 Installing ONOS package - PASS
- 2.5 7 Set up ONOS secure SSH - PASS
- 2.6 8 Checking ONOS service - PASS
- 2.7 9 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - 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
...
- 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 - FAIL
- Assertion result for IPV4 host intent with mac addresses
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Pingall Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.4 1HOP: Add host intents between h1 and h3 - FAIL
- Assertion Result for 1HOP for IPV4 same switch
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- 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.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
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 2000.8 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - 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.3 OVS running in Mininet and compile intents using Flow Objectives
- 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.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 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.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
- 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
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with VLAN treatmentIPV4 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
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- 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 - 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Failed
- Link Up Pingall Passed Remove Intents Passed
- .2 IPV4: Add host intents between h1 and h9 - PASS
Case 18: Stop Mininet and Scapy - PASS
...