Page History

...

commit 8d12930da9966f12029e5222b3121dddb458df34 a23f07db4ddba8e3251b62f805d0ddc7826d6207 (HEAD, origin/onos-1.6, onos-1.6)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.necsdn [dvaddire@partner.ciena.com]
AuthorDate: Thu Jul 21 07Tue Aug 30 04:12:54 :19 2016 -0700
Commit: Thomas Vachuska [tom@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Aug 1 18:22:29 Fri Sep 23 23:44:57 2016 +0000
BugFix
Fix for ONOS-4942.-5033 hosts - dynamic or static

Case 1: Constructing test variables and building ONOS package - 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 - FAIL
• Assertion results for IPV4 multi to single to multi point intent end point failure with no options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 Passed
• Link Up Scapy Packet Received Passed
• Remove Intents Passed
• 6000.4 NOOPTION: Install and test single point to multi point 2 Installing Multi to Single Point intents with partial failures failure allowed - FAIL
• Assertion results for IPV4 multi to single to multi point intent with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State FailedPassed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check FailedPassed
• 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 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 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - 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 - 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

...

• 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
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

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

...

PASS

This test case will test single point to multi point 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

• 4000 1000.1 NOOPTIONIPV4: Add multi point to single point intents host intents between h1 and h9 - PASS 4000
• 1000.2 IPV4DUALSTACK1: Add multi point to single point intents host intents between h3 and h11 - PASS 4000
• 1000.3 IPV4_2DUALSTACK2: Add multi point to single point intents host intents between h1 and h11 - PASS 4000
• 1000.4 VLAN1HOP: Add multi point to single point intents host intents between h1 and h3 - PASS 4000
• 1000.5 VLANVLAN1: Add multi point to single point intents - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

• vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point
• 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 - FAIL

• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 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
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 6000 2000.3 NOOPTION: Install and test single point to multi point intents 6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 6000 2000.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
• 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 Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Failed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State Failed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved 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 - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS

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

• 1000.1 IPV4: Add 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 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

...

• 8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - 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 - 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 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 - 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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - PASS
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
• 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS

This test case will test single point to multi point 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

• 3000 1000.1 NOOPTION: Install and test single point to multi point intents IPV4: Add host intents between h1 and h9 - PASS 3000
• 1000.2 IPV4: Install and test single point to multi point intents DUALSTACK1: Add host intents between h3 and h11 - PASS 3000
• 1000.3 IPV4_2DUALSTACK2: Add single point to multi point intents host intents between h1 and h11 - PASS 3000
• 1000.4 VLAN1HOP: Add single point to multi point intents host intents between h1 and h3 - PASS 3000
• 1000.5 VLAN: Add single point to multi point intents VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS

...

• 1000.7 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Objectives -

...

PASS

This test case will test 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 2000.1 NOOPTION: Add multi point to single point intents - intents between h1 and h9 - PASS 4000
• 2000.2 IPV4: Add multi point to single point intents between h1 and h9 - PASS 4000
• 2000.3 IPV4_2: Add multi point to single point intents intents between h1 and h9 - PASS 4000
• 2000.4 VLANSDNIP-ICMP: Add multi point to single point intents intents between h1 and h9 - PASS 4000
• 2000.5 VLANSDNIP-TCP: Add multi point to single point intents - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

• point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• 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
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Ping Failed
• Bad Sender Ping Passed
• Link Down Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State FailedPassed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Failed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Pingall Failed
• Link Up Passed
• Link Up Intent State PassedLink 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 - 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
• 18 5000.2 Stopping Mininet Topology - IPV4: Add host intents between h1 and h9 - PASS

Case

...

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

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

• 1000.1 IPV4: Add 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 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

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

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

• 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
• 3000.2 IPV4: Install and test single point to multi point intents - PASS
• 3000.3 IPV4_2: Add single point to multi point intents - PASS
• 3000.4 VLAN: Add single point to multi point intents - PASS
• 3000.5 VLAN: Add single point to multi point intents - PASS

Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - 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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - FAIL
• Assertion results for IPV4 multi to single point intent end point failure with no options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 Passed
• Link Up Scapy Packet Received Passed
• Remove Intents Passed
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
• Assertion results for IPV4 multi to single with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Passed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State 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
• 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 Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 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 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - 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 - FAIL

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

• 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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

6000: Test Multi to Single End Point Failure - 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
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - 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 17: - 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 Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 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 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - 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 - FAIL

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

• 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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - 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
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Passed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State 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 - FAIL
• Assertion results for IPV4 single to multi point intent with no options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 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 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - 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.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 - FAIL

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

• 4000.1 NOOPTION: Add multi point to single point intents - PASS
• 4000.2 IPV4: Add multi point to single point intents - PASS
• 4000.3 IPV4_2: Add multi point to single point intents - PASS
• 4000.4 VLAN: Add multi point to single point intents - PASS
• 4000.5 VLAN: Add multi point to single point intents - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping
• 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
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Passed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State 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 - FAIL
• Assertion results for IPV4 single to multi point intent with no options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 FailedPassed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Partial failure isolation link Down Flow State PassedPartial failure isolation link Down
• Link Up Topology State PassedPartial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Failed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received Passed
• Scapy Packet Recieved Failed
• Remove Intents Passed

Case

...

5000: Test host mobility with host intents - 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
• 18 5000.2 Stopping Mininet Topology IPV4: Add host intents between h1 and h9 - PASS

Case

...

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 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 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

...

6000: Test Multi to Single End Point Failure - FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - PASS
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
• 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

...

Objectives - PASS

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

• 3000 1000.1 NOOPTION: Install and test single point to multi point intents IPV4: Add host intents between h1 and h9 - PASS 3000
• 1000.2 IPV4: Install and test single point to multi point intents DUALSTACK1: Add host intents between h3 and h11 - PASS 3000
• 1000.3 IPV4_2DUALSTACK2: Add single point to multi point intents host intents between h1 and h11 - PASS 3000
• 1000.4 VLAN1HOP: Add single point to multi point intents host intents between h1 and h3 - PASS 3000
• 1000.5 VLAN: Add single point to multi point intents VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS

...

• 1000.7 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test -

...

1 NODE(S) - OF 1.3 - Using Flow

...

Objectives -

...

PASS

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

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

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

• 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
• 3000.2 IPV4: Install and test single point to multi point intents - PASS
• 3000.3 IPV4_2: Add single point to multi point intents - PASS
• 3000.4 VLAN: Add single point to multi point intents - PASS
• 3000.5 VLAN: Add single point to multi point intents - PASS

Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL

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

• 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 - FAIL
• Assertion results for multi to single point intent with VLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

• 6000.1 Installing Multi to Single Point intents with no options set - FAIL
• Assertion results for IPV4 multi to single point intent end point failure with no options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State 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 Passed
• Link Up Scapy Packet Received Passed
• Remove Intents Passed
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
• Assertion results for IPV4 multi to single with partial failures allowed
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Passed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State 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
• 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 - FAIL
• Assertion results for IPV4 single to multi to single point intent with VLAN ID treatmentno options set
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping FailedBad Sender Ping Connectivity Check PassedBad Recipient Ping
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State PassedFailed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Link Up Intent State PassedLink Up
• Isolation link Down Flow State Passed
• Link Up 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 - 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 - FAIL

• 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 PassedFailed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Failed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State Failed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved 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 - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

Case 1000: Host Intents Test - 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 Confirm that ONOS leadership is unchanged - PASS

...

• State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• 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 - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

This test case will test point to 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.3 OVS running in Mininet and compile intents using Flow Objectives

• 2000 1000.1 NOOPTIONIPV4: Add point host intents between h1 and h9 - PASS 2000
• 1000.2 IPV4DUALSTACK1: Add point host intents between h1 h3 and h9 h11 - PASS 2000
• 1000.3 IPV4_2DUALSTACK2: Add point host intents between h1 and h9 h11 - PASS
• 2000 1000.4 SDNIP-ICMP1HOP: Add point host intents between h1 and h9 h3 - PASS 2000
• 1000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 2000 1000.9 1HOP6 VLAN2: Add point vlan host intents between h1 and h3 h4 and h13 - PASS
• 1000.7 Confirm that ONOS leadership is unchanged - PASS

Case

...

2000:

...

Point Intents Test -

...

3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

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

...

intents using Flow Objectives

• 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
• 2000.2 IPV4: Add point intents between h1 and h9 - PASS
• 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
• 2000.7 VLAN: Add point intents between h5 and h21 - PASS
• 2000.8 VLAN: Add point intents between h5 and h21 - PASS
• 2000.9 1HOP: Add point intents between h1 and h3 - PASS

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

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

• 4000 3000.1 NOOPTION: Add multi Install and test single point to single multi point intents - PASS 4000
• 3000.2 IPV4: Add multi Install and test single point to single multi point intents - PASS
• 4000 3000.3 IPV4_2: Add multi single point to single multi point intents - PASS
• 4000 3000.4 VLAN: Add multi single point to single multi point intents - PASS
• 4000 3000.5 VLAN: Add multi single point to single multi point intents - FAIL
• Assertion results for single to multi to single point intent with VLAN ID treatment
• 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 PassedFailed
• 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

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - FAIL

• 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 - 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
• 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 multi to single to multi point intent with no options setVLAN ID treatment
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Ping Failed
• Bad Sender Ping Passed
• Bad Recipient Ping PassedLink Down Flow State Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Isolation link Down Intent State Passed
• Isolation link Down Flow State Passed
• Isolation link Down Topology State Passed
• Isolation link Down Connectivity Check PassedIsolation link Down Connectivity Check
• Link Down Flow State Passed
• Link Up Down Topology State Passed
• Link Up PassedDown 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
• Up Scapy Packet Recieved Failed
• Remove Intents Passed

Case 5000: Test host mobility with host intents - PASS

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

Case 6000: Test Multi to Single End Point Failure - 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 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 allowedno options set
• 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 Failed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check Failed
• Link Up Initial Connectivity Check Passed
• Link Up Down Passed
• Link Up Down Passed
• Link Up Down Intent State Passed
• Link Up Down Flow State PassedFailed
• Link Up Down Topology State Passed
• Link Up Scapy Packet Received Down Connectivity Check 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 - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - 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

• 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 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 - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• 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 Failed
• Partial failure isolation link Down Flow State Passed
• Partial failure isolation link Down Topology State Passed
• Partial failure isolation link Down Connectivity Check Passed
• Partial failure isolation link Down Connectivity Check 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

• 18.1 Stopping and Removing Scapy Host Components - PASS
• 18.2 Stopping Mininet Topology - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs
• 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 Confirm that ONOS leadership is unchanged - PASS