Page History

...

08 

commit 6584989c59151a1f84eaee250116ac83ebeb305e 6e4f7eb58c13d762a690257e61099f3df09cd29b (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.comCarmelo Cascone [carmelo@opennetworking.org]
AuthorDate: Fri Mon Aug 18 1321 23:0900:41 43 2017 -0700+0200
Commit: Ray Milkey Carmelo Cascone [ray@opennetworkingcarmelo@opennetworking.org]
CommitDate: Sat Mon Aug 19 0221 23:5200:33 43 2017 +0000
minor fixes around HexString0200

ONOS-6648 Bumped version of p4c with support for cmake build system

Case 1: Pull onos branch and build onos on Teststation. - 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

...

• 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.0 - 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.0 OVS running in Mininet and compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 VLAN: Add point intents between h5 and h21 - PASS
• 2000.10 1HOP: Add point intents between h1 and h3 - PASS
• 2000.11 Add point to point intents using VLAN Encapsulation - PASS
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS 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(Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

...

• 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 Rules -

...

FAIL

This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

• 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 FAIL
• Assertion results for VLAN Encapsulation multi to single point intent

Case 5000: Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS

...

• 6000.1 Installing Multi to Single Point intents with no options set - 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 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

...

• 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules -

...

FAIL

This test case will test point to point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 VLAN: Add point intents between h5 and h21 - PASS
• 2000.10 1HOP: Add point intents between h1 and h3 - PASS
• 2000.11 Add point to point intents using VLAN Encapsulation - PASS
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS 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 Rules - PASS

...

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 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.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 IntentInstall Intent State Passed
• Encapsulation intents check Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping PassedFailed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State 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.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 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

...

• 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 - PASS

This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives

• 4000.1 NOOPTION: 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.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 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 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
• 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 Failed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received Passed
• Remove Intents Passed
• 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 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 will test single point to multi point tests Host intents using 1 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectiveswill 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 - FAIL
• Assertion Result for IPV4 host intent with 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 - 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 PassedBad Recipient
• Initial Ping PassedFailed
• Link Down Passed
• Link Down Intent State Passed
• 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 FailedPingall Passed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS

• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Encapsulation
• 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 - 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 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

...

• 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 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 - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL

This test case will test point to point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives

• 2000.1 NOOPTION: Add point intents between h1 and h9 - 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 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 Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received Passed
• Remove Intents Passed
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

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 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 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 IPV4_2: Add single point to multi point intents - PASS 1000
• 3000.7 Encapsulation4 VLAN: Add host intents between h1 and h9 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 - 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 ObjectivesOF 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
• 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 IntentInstall Intent State Passed
• Encapsulation intents check 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 PassedFailed
• 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 - PASS

...

Case 5000: Test host mobility with host intents - 3 NODE(S

...

) - OF 1.0

...

- Using Flow Objectives - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6
• 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
• 5000.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 2 IPV4: Add host intents between h1 and h9 - PASS

Case

...

6000: Test Multi

...

to Single End Point

...

Failure - 3 NODE(S) - OF 1.0 - Using Flow Objectives

...

- FAIL

• 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 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 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 Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State PassedInitial Flow
• Link Down Topology State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Connectivity Check Failed
• Isolation link Link Down Passed
• Link Isolation link Down Intent State Passed
• Link Isolation link Down Flow State Passed
• Link Isolation link Down Topology State Passed
• Isolation link Down Connectivity Check Passed
• Isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Down Pingall 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

Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Objectives - 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
• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case

...

19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

Case 2: Starting up 1 node(s) ONOS cluster - PASS

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling 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 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules

• 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point

• 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

...

Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

This test case tests Host 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 Rulesand compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000 2000.2 7 DUALSTACK1: Add host point intents between h3 and h11 - PASS 1000
• 2000.3 DUALSTACK28 VLAN: Add host point intents between h1 h5 and h11 h21 - PASS 1000
• 2000.4 1HOP9 VLAN: Add host point intents between h1 h5 and h3 h21 - PASS
• 1000 2000.5 VLAN110 1HOP: Add vlan host point intents between h4 h1 and h12 h3 - PASS 1000
• 2000.6 VLAN2: Add vlan host intents between h4 and h13 11 Add point to point intents using VLAN Encapsulation - PASS
• 1000.7 Encapsulation: Add host 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - 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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 VLAN: Add point intents between h5 and h21 - PASS
• 2000.10 1HOP: Add point intents between h1 and h3 - PASS
• 2000.11 Add point to point intents using VLAN Encapsulation - PASS
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

...

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

• 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - PASS 3000
• 4000.2 IPV4: Install and test single Add multi point to multi single point intents - PASS
• 3000 4000.3 IPV4_2: Add single multi point to multi single point intents - PASS
• 3000 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 3000.5 VLAN: Add single point to multi point intents

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

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
• 6000.6 ENCAPSULATION: Add multi 4 NOOPTION: Install and test single point to single 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

• 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 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

• 13.1 Create scapy components - No Result
• 13.2 Start scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

• 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
• 15.2 Populate hostsData - PASS

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules

• 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
• 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
• 1000.4 1HOP: Add host intents between h1 and h3 - PASS
• 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point

• 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

...

Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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 Rulesand compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000 2000.2 7 DUALSTACK1: Add host point intents between h3 and h11 - PASS 1000
• 2000.3 DUALSTACK28 VLAN: Add host point intents between h1 h5 and h11 h21 - PASS 1000
• 2000.4 1HOP9 VLAN: Add host point intents between h1 h5 and h3 h21 - PASS
• 1000 2000.5 VLAN110 1HOP: Add vlan host point intents between h4 h1 and h12 h3 - PASS 1000
• 2000.6 VLAN2: Add vlan host intents between h4 and h13 11 Add point to point intents using VLAN Encapsulation - PASS
• 1000.7 Encapsulation: Add host 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case

...

3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 Protected: Add point intents between h1 and h9 - PASS
• 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 VLAN: Add point intents between h5 and h21 - PASS
• 2000.10 1HOP: Add point intents between h1 and h3 - PASS
• 2000.11 Add point to point intents using VLAN Encapsulation - PASS
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

...

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 - 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

• 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - PASS 3000
• 4000.2 IPV4: Install and test single Add multi point to multi single point intents - PASS
• 3000 4000.3 IPV4_2: Add single multi point to multi single point intents - PASS
• 3000 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 3000.5 VLAN: Add single point to multi point intents

Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case

...

6000: Test Multi

...

to Single End Point

...

Failure - 3 NODE(S) - OF 1.3 - Using Flow Rules -

...

FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - 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 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules

• 4000.1 NOOPTION: Add multi point to single point intents - PASS
• 4000.2 IPV4: Add multi point to single point intents - PASS
• 4000.3 IPV4_2: Add multi point to single point intents - PASS
• 4000.4 VLAN: Add multi point to single point intents - PASS 4000
• 6000.5 VLAN: Add multi 4 NOOPTION: Install and test single point to single multi 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

• 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 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 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.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

...

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 -

...

FAIL

This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow ObjectivesMininet 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 1000.1 IPV4: Add host intents between h1 and h9 - PASS
• 1000.2 DUALSTACK16 VLAN2: Add vlan host intents between h3 h4 and h11 h13 - PASS
• 1000.3 DUALSTACK27 Encapsulation: 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
• 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 Passed
• Link Down Pingall Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Pingall Failed
• Remove Intents Passed
• 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 IntentInstall Intent State Passed
• Encapsulation intents check failedPassed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping FailedPassed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received PassedRecieved Failed
• Remove Intents Passed
• 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

...

• 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 FailedPassed
• 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 PassedFailed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received PassedRecieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Objectives - 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 13: Create scapy components - PASS

• 13.1 Create scapy components - No Result
• 13.2 Start scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

...

• 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
• 15.2 Populate hostsData - PASS

Case 16: Balance mastership of switches - PASS

...

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

...

• 17.1 Enabling Flow Objectives - PASS

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives -

...

PASS

This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives

• 1000.1 IPV4: Add 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
• and h13 - PASS
• 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
Remove Intents Passed
• 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_2: Add point intents between h5 h1 and h21 h9 - PASS
• 2000.10 1HOP5 SDNIP-ICMP: Add point intents between h1 and h3 h9 - PASS
• 2000.11 Add point to point intents using VLAN Encapsulation 6 SDNIP-TCP: Add point intents between h1 and h9 - 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 Passed
• Link Down Pingall Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
Remove Intents Passed
• SDNIP-TCP IPV4 using ICMP point intents
• Initial Iperf Passed
• Remove Intents Failed
• 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
• PASS

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

...

• 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 Objectives -

...

PASS

This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives

• 4000.1 NOOPTION: Add multi point to single point intents - 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 Objectives - PASS

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 4000 5000.3 2 IPV4_2: Add multi point to single point intents - PASS 4000.4 VLAN: Add multi point to single point intents host intents between h1 and h9 - PASS

Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - PASS 4000.5
• VLAN: Add multi point to single point intents 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 4000 6000.6 ENCAPSULATION: Add multi 3 NOOPTION: Install and test single point to single multi point intents - FAIL
• Assertion results for VLAN Encapsulation multi to single 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 PassedInitial Ping PassedBad Sender Ping
• Initial Connectivity Check Passed
• Bad Recipient Ping Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Connectivity Check Failed
• Link Up Isolation link Down Passed
• Link Up Isolation link Down Intent State PassedLink Up
• Isolation link Down Flow State PassedLink Up Topology State
• Isolation link Down Topology State Passed
• Isolation link Down Connectivity Check Passed
• Isolation link Down Connectivity Check Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

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 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

• 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.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

...