Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCintent_onos-1.15_20-builds_graph.jpg", alt="FUNCintent", style="width:525px;height:350px;border:0">

commit 9a80af401ffc2f30fd08b2ab7116982cab6baa35 7898ceda95b0e27a048c9fcee5e5c8daa332a4d4 (HEAD, origin/onos-1.15, onos-1.15)
Author: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Wed Jul 29 23:48:39 2020 -0700Mon Oct 5 22:36:41 2020 +0900
Commit: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
CommitDate: Thu Jul 30 19:03:07 2020 +0000
Disable using projectlock during release
--
updated, or change the release process to tag a specific commit instead
of the whole branch.
Change-Id: I2060c74e01a152a07d364a4afa474d9245a3f33b
(cherry picked from commit 00ff4ce6647c2c05162b5d8cd2e0ba3085302056)
Mon Oct 5 22:56:34 2020 +0900

Fix: make all openstack resource name optional

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

• 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL 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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents Assertion Result for NOOPTION point intent
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall 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 PassedAfter removing intents Flow State Passed
• 2000.2 IPV45 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-TCP IPV4 point intent
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• using ICMP point intents
• Initial Iperf Failed
• Remove Intents Passed
• 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 2000.3 IPV4_2: Add point intents between h1 and h9 h3 - FAIL
• Assertion Result for IPV4 no mac address point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• PASS
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
• Initial Iperf Failed
• Remove Intents Passed
• 2000.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
• 2000.10 Add point to point intents using VLAN Encapsulation - FAIL
• Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
• Encapsulation intents check failed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 2000.11 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 Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed

...

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

...

FAIL

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - FAIL
• Mobility: Failed to move h1 to s6 to single point intents with IPV4 type and MAC addresses in the same VLAN
• 5000.2 IPV4: Add host intents between h1 and h9 - PASS

Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.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

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
• 6000.5 VLAN: Add 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 Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

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

• 1000.1 IPV4: Add 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 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 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 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 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

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 - FAIL
• Assertion results for IPV4 multi to single with partial failures allowed
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State 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 FailedAfter removing intents Flow State 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
• 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 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 FailedAfter removing intents Flow State 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
• 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 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 FailedAfter removing intents Flow State 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 - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

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

• 1000.1 IPV4: Add 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 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 IPV4_2: Add point intents between h1 and h9 - PASS
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 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 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 - 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

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

• 3000.2 IPV4: Install and test single point to multi point intents 18.1 Stopping and Removing Scapy Host Components - PASS 18
• 3000.2 Stopping Mininet 3 IPV4_2: Add single point to multi point intents - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 3000.4 VLAN: Add single point to multi point intents - PASS
• 3000.5 VLAN: Add single point to multi point intents 19.1 Copying karaf logs - PASS

Case

...

4000: Multi To Single 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 Set up ONOS with 1 node(s) ONOS clustercluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives

• 4000.1 NOOPTION: Add multi point to single point intents 2.1 Apply cell to environment - PASS
• 2 4000.2 Uninstalling Atomix IPV4: Add multi point to single point intents - PASS 2
• 4000.3 Uninstalling ONOS package IPV4_2: Add multi point to single point intents - PASS 2
• 4000.4 Creating ONOS package VLAN: Add multi point to single point intents - PASS
• 2 4000.5 Installing Atomix VLAN: Add multi point to single point intents - PASS 2
• 4000.6 Installing ONOS package ENCAPSULATION: Add multi point to single point intents - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - 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 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications 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 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 - FAIL
• Assertion results for IPV4 multi to single with partial failures allowed
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Connectivity Check Failed
• 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 FailedAfter removing intents Flow State 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
• 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 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 FailedAfter removing intents Flow State 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

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 Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - FAIL

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

• 2000.1 NOOPTION: 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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• 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 Passed
• Partial failure isolation link Down Connectivity Check Passed
• Link Up Passed
• Link Up Passed
• Link Up Passed
• Link Up Link Down Intent State Passed
• Link Down Up Flow State Passed
• Link Down Up 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 PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

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

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

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

...

• Up Scapy Packet Received Passed
• Remove Intents FailedAfter removing intents Flow State 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 - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

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

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

• 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 VLAN: Add multi point to single point intents - PASS
• 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

• 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

...

• 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3

...

- Using Flow Rules - FAIL

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

• 2000.1 NOOPTION: 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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

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

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

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

Case 4000: Multi To Single Point Intents Test - 1

• 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 Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

...

NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

• 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS 1000
• 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS 1000
• 4000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 multi point to single point intents - PASS 1000
• 4000.4 1HOPVLAN: Add host intents between h1 and h3 multi point to single point intents - PASS 1000
• 4000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• VLAN: Add multi point to single point intents - PASS
• 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

• 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
• 5000.2 IPV4 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - PASS

...

Case 6000: Test Multi to Single End Point Failure - 1 NODE(S)

...

-

...

OF 1.3 - Using Flow Rules - PASS

• 6000.1 Installing Multi to Single Point intents with no options set - PASS
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
• 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 1000: Host

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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 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.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

...

Intents Test - 3 NODE(S) - OF 1.3 - 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.3 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 VLAN: Add multi point to single point intents - PASS
• 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

• 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

...

• 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - 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.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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 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.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

• 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 Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

...

NODE(S) - OF 1.3 - Using Flow

...

Rules - PASS

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

• 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS 1000
• 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS 1000
• 4000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 multi point to single point intents - PASS 1000
• 4000.4 1HOPVLAN: Add host intents between h1 and h3 multi point to single point intents - PASS 1000
• 4000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
• 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
• 1000.7 Encapsulation: Add host intents between h1 and h9 VLAN: Add multi point to single point intents - PASS 1000.8
• Confirm that ONOS leadership is unchanged 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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
• Assertion Result for NOOPTION point intent
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received Passed
• Remove Intents PassedAfter removing intents Flow State Passed
• 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
• Assertion Result for IPV4 point intent
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received Passed
• Remove Intents PassedAfter removing intents Flow State Passed
• 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL
• Assertion Result for IPV4 no mac address point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall 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 PassedAfter removing intents Flow State Passed
• 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• PASS

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

• 6000.1 Installing Multi to Single Point intents with no options set - PASS
• 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
• 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
• 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

• 19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

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

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

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

• 17.1 Enabling Flow Objectives - PASS

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

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

• 1000.1 IPV4: Add host 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
• 2000 1000.6 2 DUALSTACK1: Add point 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 2000
• 1000.7 VLAN5 VLAN1: Add point vlan host intents between h5 h4 and h21 h12 - PASS 2000
• 1000.8 VLAN6 VLAN2: Add point vlan host intents between h5 h4 and h21 h13 - PASS
• 2000 1000.9 1HOP7 Encapsulation: Add point host intents between h1 and h3 - PASS 2000.10 Add h9 - PASS
• 1000.8 Confirm that ONOS leadership is unchanged - PASS

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

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

• 2000.1 NOOPTION: Add point intents between h1 and h9 - 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
VLAN Encapsulation - FAIL
• Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
• Encapsulation intents check Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State 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 PassedAfter removing intents Flow State Passed
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL
• Assertion Result for BANDWIDTH ALLOCATION for point intentSDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Bandwidth Allocation 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 Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Received PassedRemove Intents PassedAfter removing intents Flow State PassedRecieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow 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 - FAIL
• Assertion results for IPV4 multi to single with partial failures allowed
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Connectivity Check Passed
• Isolation link Down Passed
• Partial failure isolation link Down Intent State Passed
• Partial failure isolation link Down Flow State 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 PassedRecieved Failed
• Remove Intents FailedAfter removing intents Flow State 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
• 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 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 FailedAfter removing intents Flow State 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
• 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 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 Recieved Failed
• Remove Intents FailedAfter removing intents Flow State Passed

...

• 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 - FAIL
• Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Ping Failed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Pingall Failed
• Link Up Passed
• Link Up Intent State Passed
• Link Up Flow State Passed
• Link Up Topology State Passed
• Link Up Scapy Packet Recieved Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

...

• Failed
• Remove Intents PassedAfter removing intents Flow State Passed
• 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
• 2000.10 Add point to point intents using VLAN Encapsulation - PASS
• 2000.11 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.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

• 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

• 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 single multi point to multi single point intents - PASS 3000
• 4000.5 VLAN: Add multi point to single point to multi 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
• 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 - 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 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
• 6000.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
• 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

• 4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
• Assertion results for IPV4 single to multi point intent with partial failures allowed
• Install Intent State Passed
• Flow duration check Passed
• Initial Intent State Passed
• Initial Flow State Passed
• Initial Connectivity Check Passed
• Link Down Passed
• Link Down Passed
• Link Down Intent State Passed
• Link Down Flow State Passed
• Link Down Topology State Passed
• Link Down Connectivity Check Failed
• 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 Passed
• 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 FailedAfter removing intents Flow State 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

...