...
HTML |
---|
<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/lastSuccessfulBuild/artifact/FUNCintent_master_20-builds_graph.jpg", alt="FUNCintent", style="width:525px;height:350px;border:0"> |
commit 59ad65730a2c7fdecd8204bce8e4df4912673e1e 73f9aeaa11fead280f72da1b79c4af9806c70c19 (HEAD, origin/master, origin/HEAD, master)
Author: Manjunath Vanaraj Laszlo Papp [manjurajlaszlo.v@samsungpapp@hubersuhner.com]
AuthorDate: Tue Dec 26 11:10:57 2017 +0530Mon Jan 15 19:23:45 2018 +0000
Commit: Carmelo Cascone [carmelo@opennetworking.orgLaszlo Papp [laszlo.papp@hubersuhner.com]
CommitDate: Sat Mon Jan 13 0215 19:0523:59 45 2018 +0000
[ONOS-7334] Using Cache Loader to remove stale entries in p4runtime
Avoid division by zero
Case 1: Pull onos branch and build onos on Teststation. - PASS
...
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
This test case will test 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
...
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -
...
PASS
This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed
- PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL Assertion Result for VLAN Encapsulation Point Intent
- PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -
...
PASS
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add 3000.2 IPV4: Install and test single point to multi point intents - FAIL PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- 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 FailedPassed
- Link Down Topology State PassedFailed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State PassedFailed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 3000 4000.3 2 IPV4_2: Add single point to multi point intents - multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addressesVLAN Encapsulation multi to single point intent
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - 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
- Initial Flow State Passed
- Initial
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State FailedPassed
- 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 Pingall Passed
- Remove Intents Passed
- 3000.4 VLAN: Add single point to multi point intents - PASS
- Failed
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 multi to single to multi point intent with VLAN treatmentend point failure with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Connectivity Check Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State FailedPassed
- Link Down Topology State Passed
- Link Down Pingall Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State PassedFailed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules
- Failed
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Connectivity Check Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Link Down Passed
- Link Down Passed
- Link Down Intent State FailedPassed
- Link Down Flow State Passed
- Link Down Topology State PassedFailed
- Link Down Connectivity Check Failed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Failed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State PassedFailed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedFailed
- 4000 6000.2 IPV4: Add multi 3 NOOPTION: Install and test single point to single multi point intents - FAIL
- Assertion results for IPV4 single to multi to single point intent with IPV4 type and MAC addressesno options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Connectivity Check Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Link Down Passed
- Link Down Passed
- Link Down Intent State FailedPassed
- Link Down Flow State Passed
- Link Down Topology State PassedFailed
- Link Down Pingall Connectivity Check Passed
- Link Up Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Failed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State PassedFailed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedFailed
- 4000.3 IPV4_2: Add multi point to single point intents 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi to single point intent with IPV4 type and no MAC addressespartial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Connectivity Check Failed
- Link Down Passed
- Link Down Passed
- Link Down Intent State FailedPassed
- Link Down Flow State Passed
- Link Down Topology State PassedFailed
- Link Down Pingall Connectivity Check PassedLink Up
- Isolation link Down Passed
- Link Up Partial failure isolation link Down Intent State PassedLink Up
- Partial failure isolation link Down Flow State Passed
- Link Up Partial failure isolation link Down Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- 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 Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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 - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Failed
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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 - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Passed
- Encapsulation intents check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall 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.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
This test case will test point to point 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 2000.1 IPV4NOOPTION: Add host point intents between h1 and h9 - PASS 1000
- 2000.2 DUALSTACK1IPV4: Add host point intents between h3 h1 and h11 h9 - PASS 1000
- 2000.3 DUALSTACK2Protected: Add host point intents between h1 and h11 - PASS h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point 1000.4 1HOP: Add host intents between h1 and h3 h9 - PASS
- 1000 2000.5 VLAN1SDNIP-ICMP: Add vlan host point intents between h4 h1 and h12 h9 - PASS 1000
- 2000.6 VLAN2SDNIP-TCP: Add vlan host point intents between h4 h1 and h13 h9 - PASS 1000.7 Encapsulation: Add host intents between h1 and h9
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulated host intentInstall Encapsulation Point IntentInstall Intent State Passed
- Encapsulation intents check failedPassed
- 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 Scapy Packet Recieved Failed
- Remove Intents Passed
- 1000.8 Confirm that ONOS leadership is unchanged 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case
...
3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives
- 2000 3000.1 NOOPTION: Add Install and test single point to multi point intents between h1 and h9 - PASS 2000
- 3000.2 IPV4: Add Install and test single point to multi point intents between h1 and h9 - PASS 2000
- 3000.3 ProtectedIPV4_2: Add single point to multi point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- - PASS
- 3000.4 VLAN: Add single point to multi point intents 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS 2000
- 3000.5 SDNIP-ICMPVLAN: Add single point to multi point intents between h1 and h9 - PASS
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
...
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow 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
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall 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 - 1 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS 4000
- 6000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for VLAN Encapsulation multi to single IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Connectivity Check PassedBad Sender Ping
- Link Down 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
- Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Link Up Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Link Up Flow State Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved FailedReceived Passed
- Remove Intents Passed
Case
...
18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000 18.2 IPV4: Add host intents between h1 and h9 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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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 host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Passed
- Encapsulation intents check failed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Failed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Failed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received PassedPingall Failed
- Remove Intents Passed
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components 1000.8 Confirm that ONOS leadership is unchanged - 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
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 Set up ONOS with 3 node(s) ONOS clustercluster; 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 2.1 Apply cell to environment - PASS
- 2 2000.2 Uninstalling ONOS package IPV4: Add point intents between h1 and h9 - PASS 2
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point intents between h1 and h9 Creating ONOS package - PASS 2.4 Installing ONOS package - PASS 2.
- 5 Set up ONOS secure SSH 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2 2000.6 Checking ONOS service SDNIP-TCP: Add point intents between h1 and h9 - PASS 2
- 2000.7 Starting ONOS CLI sessions DUALSTACK1: Add point intents between h3 and h11 - 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
...
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check Failed
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives -
...
PASS
This test case tests Host 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
- 1000 3000.1 IPV4: Add host intents between h1 and h9 - FAIL NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - 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
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- 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
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- 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
- 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 FailedPassed
- Link Down Pingall PassedFailed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State FailedPassed
- Link Up Pingall PassedScapy Packet Recieved Failed
- Remove Intents Passed
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4 1000.4 1HOP: Add host intents between h1 and h3 h9 - FAIL PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Assertion Result for 1HOP for IPV4 same switch
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State FailedPassed
- Link Down Pingall Connectivity Check PassedLink Up
- Isolation link Down Passed
- Link Up Isolation link Down Intent State PassedLink Up
- Isolation link Down Flow State Passed
- Link Up Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Failed
- Isolation link Down Connectivity Check Passed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL
- Passed
- Link Up Passed
- Link
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State FailedPassed
- Link Up Pingall Scapy Packet Received Passed
- Remove Intents Passed
- 1000 6000.6 VLAN2: Add vlan host intents between h4 and h13 - 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Passed
- Encapsulation intents check 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case tests Host intents using 1 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 3 OVS running in Mininet and compile intents using Flow ObjectivesRules
- 2000 1000.1 NOOPTIONIPV4: Add point host intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- 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
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - FAIL
This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 2000.1 NOOPTION 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - FAIL
- protected point intent
- 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 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
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Rules - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed Assertion Result for Dualstack1 IPV4 with mac address point intents
- Install Intent State Passed
- Flow duration check PassedPassed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Initial Intent State Passed
- Initial Link Down Flow State PassedInitial Ping
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Link Down Intent State Passed
- Link Partial failure isolation link Down Flow State Passed
- Link Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Failed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State FailedPassed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 2000.8 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 with mac address point intents
- 2000.9 VLAN: Add point intents between h5 and h21 - FAIL
- Assertion Result for VLAN IPV4 point intents with VLAN treatment
- 2000.10 1HOP: Add point intents between h1 and h3 - FAIL
- Assertion Result for 1HOP IPV4 with no mac address point intents
- 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 Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Failed
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
- Encapsulation intents check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Failed
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Scapy Packet Received Passed
- Remove Intents Failed
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 4000: Multi To Single 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
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- 4000.2 IPV4: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
- 4000.3 IPV4_2: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - FAIL
- Assert result for IPV4 host intent between h1, moved, and h9
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Failed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Failed
- Link Up Pingall Passed
- Remove Intents Passed
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- Received Passed
- Remove Intents Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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 4000: - FAIL
- Skipping the rest of this case.
Case 5000: - FAIL
- Skipping the rest of this case.
Case 6000: - FAIL
- Skipping the rest of this case.
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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intent
- 6000.1 Installing Multi to Single Point intents with no options set - FAIL
- Assertion results for IPV4 multi to single point intent end point failure with no options set
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Ping Failed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Intent State Failed
- Link Down Flow State Failed
- 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.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 Link Down Topology State Failed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Link Down Intent State FailedPartial failure isolation link Passed
- Link Down Flow State Passed
- Partial failure isolation link Link Down Topology State FailedPartial failure isolation link Down Connectivity Check PassedPartial failure isolation link Down Connectivity Check Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State FailedPassed
- Link Up Scapy Packet Received PassedRecieved Failed
- Remove Intents Passed
- 6000 2000.3 NOOPTION: Install and test single point to multi point intents Protected: Add point intents between h1 and h9 - FAIL
- Assertion results for IPV4 single to multi Result for protected point intent with no options set
- 6000 2000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion results Result for IPV4 single to multi point intent with partial failures allowedno mac address point intents
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check FailedLink Down PassedPing Failed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State FailedPassed
- Link Down Connectivity Check Failed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Failed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Pingall Failed
- Link Up Passed
- Link Up PassedLink Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State FailedPassed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - 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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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
...
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
- Initial Iperf Failed
- Remove Intents Passed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
- Encapsulation intents check failed
- 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.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping 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 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow
...
Objectives - PASS
This test case tests Host 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 RulesObjectives
- 1000 3000.1 IPV4: Add host intents between h1 and h9 NOOPTION: Install and test single point to multi point intents - PASS 1000
- 3000.2 DUALSTACK1: Add host intents between h3 and h11 IPV4: Install and test single point to multi point intents - PASS 1000
- 3000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 single point to multi point intents - PASS 1000
- 3000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 VLAN: Add single point to multi point intents - PASS 1000.8
- Confirm that ONOS leadership is unchanged 3000.5 VLAN: Add single point to multi point intents - PASS
Case
...
4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow
...
Objectives - 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 RulesObjectives
- 2000 4000.1 NOOPTION: Add multi point intents between h1 and h9 to single point intents - PASS 2000
- 4000.2 IPV4: Add multi point to single point intents between h1 and h9 - PASS 2000
- 4000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add multi point intents between h1 and h9 to single point intents - PASS 2000.5 SDNIP-ICMP
- 4000.4 VLAN: Add point intents between h1 and h9 - PASS 2000.6 SDNIP-TCP: Add point intents between h1 and h9 multi point to single point intents - PASS
- 2000 4000.7 DUALSTACK15 VLAN: Add multi point intents between h3 and h11 to single point intents - PASS 2000
- 4000.8 VLAN6 ENCAPSULATION: Add multi point to single point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 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
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - 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
...
- - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping 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 - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - FAIL
- Mobility: Failed to move h1 to s6 to single point intents with IPV4 type and MAC addresses in the same VLAN
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install Intent State Failed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow
...
Objectives -
...
FAIL
This test case tests Host will test point to point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules; 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 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point 1000.1 IPV4: Add host intents between h1 and h9 - PASS 1000.2
- DUALSTACK1 2000.5 SDNIP-ICMP: Add host point intents between h3 h1 and h11 h9 - PASS 1000.3 DUALSTACK2
- 2000.6 SDNIP-TCP: Add host point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 1000 2000.4 1HOP8 VLAN: Add host point intents between h1 h5 and h3 h21 - PASS 1000
- 2000.5 VLAN19 VLAN: Add vlan host point intents between h4 h5 and h12 h21 - PASS 1000
- 2000.6 VLAN210 1HOP: Add vlan host point intents between h4 h1 and h13 h3 - PASS 1000.7 Encapsulation: Add host
- 2000.11 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point Intent
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
- FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
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 RulesMininet and compile intents using Flow Objectives
- 3000.1 NOOPTION: Install and test single point to multi point intents
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS
- 2000.11 Add point to point intents using VLAN Encapsulation - PASS
- 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
- Assertion Result for BANDWIDTH ALLOCATION for point intent
- Install Intent State Passed
- Bandwidth Allocation check Failed
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 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
- 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 Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
...
- single point to multi point intents
...
- - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- 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 Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
Case 4000: Multi To Single 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
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Failed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 4000.2 IPV4: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents Passed
- 4000.3 IPV4_2: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 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 ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- 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 FailedPing Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State PassedFailed
- 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 FailedReceived Passed
- Remove Intents Passed
- 2000 4000.2 IPV44 VLAN: Add multi point intents between h1 and h9 to single point intents - FAIL
- Assertion Result results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State PassedFailed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall FailedPassed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents Passed
- 2000.3 Protected: Add point intents between h1 and h9 - FAIL
- Assertion Result for protected point intent
- Received Passed
- Remove Intents Passed
- 4000.5 VLAN: Add multi point to single point intents 2000.4 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intentsresults for multi to single point intent with VLAN ID treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping FailedPassed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State PassedFailed
- Link Down Topology State Passed
- Link Down Pingall FailedPassed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved FailedReceived Passed
- Remove Intents Passed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs
- 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
- Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
- Initial Iperf Failed
- Remove Intents Passed
- 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 VLAN: Add point intents between h5 and h21 - PASS
- 2000.10 1HOP: Add point intents between h1 and h3 - PASS