Page History

...

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

commit ed77aeb7bc8525da868f6e5b13715df2aaf4c720 6341ff8002512520a4a5b5e1ef81033bde78c510 (HEAD -] master, origin/master, origin/HEAD)
Author: Sean Condon pier [sean@opennetworkingpier@opennetworking.org]
AuthorDate: Sun Mar 15 21Fri Feb 28 09:24:43 11 2020 +00000100
Commit: Sean Condon Charles Chan [sean@opennetworkingcharles@opennetworking.org]
CommitDate: Mon Wed Mar 16 1018 17:5357:38 50 2020 +0000
Upgraded some components for GUI2
Fixes an NPE in OFDPA pipeliners

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

...

16.1 Balancing mastership of switches - PASS

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

...

FAIL

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

Assertion Result for dualstack2 host intent
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping 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 Pingall Failed
Remove Intents PassedAfter removing intents Flow State Passed

1000.4 1HOP 1000.7 Encapsulation: Add host intents between h1 and h9 h3 - PASS
1000.8 Confirm that ONOS leadership is unchanged 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 Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

...

6000.1 Installing Multi to Single Point intents with no options set - PASS
6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
6000.3 NOOPTION: Install and test single point to multi 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 to single 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 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

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

Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
Initial Iperf Failed
Remove Intents Passed

2000.6 DUALSTACK1: Add point
1000.1 IPV4: Add host intents between h1 and h9 - PASS
1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS 1000
2000.3 DUALSTACK27 VLAN: Add host point intents between h1 h5 and h11 h21 - PASS 1000
2000.4 1HOP8 VLAN: Add host point intents between h1 h5 and h3 h21 - PASS
1000 2000.5 VLAN19 1HOP: Add vlan host point intents between h4 h1 and h12 h3 - PASS 1000
2000.6 VLAN2: Add vlan host intents between h4 and h13 10 Add point to point intents using VLAN Encapsulation - PASS 1000.7 Encapsulation: Add host
2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point 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

FAIL

Assertion Result for BANDWIDTH ALLOCATION for point intent
Install Intent State Passed
Bandwidth Allocation check Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall 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 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL

This test case will test single point to multi 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 3000.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 Install and test single point to multi point intents - FAIL

Assertion Result results for SDNIP-ICMP IPV4 using TCP point intentsIPV4 single to multi point intent with no options set
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping FailedPing Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall FailedPassed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Recieved FailedReceived Passed
Remove Intents PassedAfter FailedAfter removing intents Flow State Passed

2000.5 SDNIP-TCP: Add point intents between h1 and h9 3000.2 IPV4: Install and test single point to multi point intents - 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

results for IPV4 single to multi point intent with IPV4 type and MAC addresses
Install Intent State Passed
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 Passed
Link Down Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter removing intents Flow State Passed

2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 3000.3 IPV4_2: Add single point to multi point intents - FAIL

Assertion Result for BANDWIDTH ALLOCATION for point intentresults for IPV4 single to multi point intent with IPV4 type and no MAC addresses
Install Intent State Passed
Bandwidth Allocation check Failed
After removing intents Flow State Passed

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

Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall 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
After removing intents Flow State Passed

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 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 4000.1 NOOPTION: Install and test single point to multi Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - FAIL 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 - 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 no options set
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter removing intents Flow State Passed

3000.2 IPV4: Install and test single point to multi point intents - FAIL

Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addressespartial failures allowed
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Connectivity Check Passed
Bad Sender Ping Passed
Link Down Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Bad Recipient Ping Passed
Link Down Topology State Passed
Link Down Connectivity Check Passed
Isolation link Down Passed
Partial failure isolation link Down Intent State Passed
Link Partial failure isolation link Down Flow State Passed
Link Partial failure isolation link Down Topology State Passed
Partial failure isolation link Down Connectivity Check Passed
Partial failure isolation link Down Connectivity Check Passed
Link Up Passed
Link Up Link Down Pingall Passed
Link Up Passed
Link Up Intent State PassedFailed
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

3000.3 IPV4_2: Add single point to multi point intents - FAIL

Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall 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
After removing intents Flow State Passed

3000.4 VLAN: Add single point to multi point intents - FAIL

Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter removing intents Flow State Passed

3000.5 VLAN: Add single point to multi point intents - FAIL

Assertion results for single to multi point intent with VLAN treatment
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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 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 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.0 3 OVS running in Mininet and compile intents using Flow ObjectivesRules

4000 2000.1 NOOPTION: Add multi point to single point intents 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 results for NOOPTION multi to single point intentResult for SDNIP-ICMP IPV4 using TCP point intents
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping PassedFailed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall PassedFailed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received PassedRecieved Failed
Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

4000.2 IPV4 2000.5 SDNIP-TCP: Add multi point to single point intents - FAIL

Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter removing intents Flow State Passed

4000.3 IPV4_2: Add multi point to single point intents - FAIL

Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall 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

4000.4 VLAN: Add multi point to single point intents - FAIL
Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed

Remove Intents FailedAfter removing intents Flow State Passed

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 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - FAIL

Assertion results for multi to single point intent with VLAN ID treatment
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter removing intents Flow State Passed

4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL

Assertion results for VLAN Encapsulation multi to single point intent
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall 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 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL

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

Assert result for IPV4 host intent between h1, moved, and h9
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Pingall Passed
Remove Intents FailedAfter removing intents Flow State Passed

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

PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

2.1 Apply cell to environment - PASS
2.2 Uninstalling 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 - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

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

Case 2000: Point 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

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
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.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 PassedAfter 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 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 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 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 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

19.1 Copying karaf logs - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

2.1 Apply cell to environment - PASS
2.2 Uninstalling 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 - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

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

Case 2000: Point 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 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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

19.1 Copying karaf logs - PASS

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

Set up ONOS with 1 node(s) ONOS cluster

2.1 Apply cell to environment - PASS
2.2 Uninstalling 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

...

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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

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

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

...

Rules - PASS

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 6000.1 Installing Multi to Single Point intents with no options set - PASS 1000
6000.2 DUALSTACK1: Add host intents between h3 and h11 Installing Multi to Single Point intents with partial failure allowed - PASS 1000
6000.3 DUALSTACK2: Add host intents between h1 and h11 NOOPTION: Install and test single point to multi point intents - PASS 1000
6000.4 1HOP: Add host intents between h1 and h3 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
1000.5 VLAN1: Add vlan host intents between h4 and h12 - 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 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
18.2 Stopping Mininet - PASS

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

19.1 Copying karaf logs 1000.8 Confirm that ONOS leadership is unchanged - PASS

Case

...

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

Set up ONOS with 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 ObjectivesONOS cluster

2.1 Apply cell to environment 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS 2000
2.2 IPV4: Add point intents between h1 and h9 Uninstalling Atomix - PASS 2000
2.3 IPV4_2: Add point intents between h1 and h9 Uninstalling ONOS package - PASS 2000
2.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 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

...

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 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.3 OVS running in Mininet and compile intents using Flow Objectives

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 vlan host intents between h4 and h12 - PASS 4000
1000.6 ENCAPSULATIONVLAN2: Add multi point to single point intents - PASS

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

5000.1 Testing host mobility by moving h1 from s5 to s6 vlan host intents between h4 and h13 - PASS
5000 1000.2 IPV47 Encapsulation: Add host intents between h1 and h9 - PASS

...

1000.8 Confirm that ONOS leadership is unchanged - PASS

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

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

2000.1 NOOPTION: Add point intents between h1 and h9 6000.1 Installing Multi to Single Point intents with no options set - PASS 6000
2000.2 Installing Multi to Single Point intents with partial failure allowed IPV4: Add point intents between h1 and h9 - PASS
6000 2000.3 NOOPTION: Install and test single point to multi point intents IPV4_2: Add point intents between h1 and h9 - PASS 6000
2000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed SDNIP-ICMP: Add point intents between h1 and h9 - FAIL

Assertion results Result for IPV4 single to multi point intent with partial failures allowedSDNIP-ICMP IPV4 using TCP point intents
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Connectivity Check PassedLink Down PassedPing Failed
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
Pingall Failed
Link Up Passed
Link Up Partial failure isolation link Down Intent State PassedPartial failure isolation link Down
Link Up 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

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 17: Enable intent compilation using Flow Objectives - PASS

17.1 Enabling Flow Objectives - PASS

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

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

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

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

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

2000.1 NOOPTION: Add point intents between h1 and h9 - PASS
2000.2 IPV4: Add point intents between h1 and h9 - PASS
2000.3 IPV4_2: Add point intents between h1 and h9 - PASS
2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - 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 - PASS
2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

...

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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

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

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

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
After 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
After 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 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 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 Objectivesintents 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 3000.1 NOOPTION: Install and test single point to multi point intents - PASS 3000
1000.2 IPV4: Install and test single point to multi point intents 4 1HOP: Add host intents between h1 and h3 - PASS 3000.3 IPV4_2: Add single point to multi point intents
1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
3000 1000.4 VLAN6 VLAN2: Add single point to multi point intents vlan host intents between h4 and h13 - PASS 3000
1000.5 VLAN7 Encapsulation: Add single point to multi point intents 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 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 2000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
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 Failed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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 Failed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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 Failed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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 Assertion results for VLAN Encapsulation multi to single point intent
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping Passed
Bad Sender Ping Passed
Bad Recipient Ping PassedFailed
Link Down Passed
Link Down Intent State PassedFailed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Failed
Link Up Passed
Link Up Intent State FailedPassed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received PassedRecieved Failed
Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

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

5000.1 Testing host mobility by moving h1 from s5 to s6 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
5000 2000.2 IPV46 DUALSTACK1: Add host point intents between h1 h3 and h9 h11 - FAIL

Assert result Assertion Result for IPV4 host intent between h1, moved, and h9Dualstack1 IPV4 with 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 PassedFailed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Pingall Scapy Packet Received Passed
Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

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

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

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
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Connectivity Check Ping Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Failed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Down Up Flow State PassedFailed
Link Down Up Topology State Passed
Link Down Connectivity Check Passed
Isolation link Down Passed
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 intent
Install Intent State Passed
Bandwidth Allocation check Passed
Flow duration check Passed
Initial Isolation link Down Intent State PassedIsolation link Down
Initial Flow State Passed
Initial Ping Passed
Link Down Isolation link Down Topology State PassedIsolation link Down Connectivity Check
Link Down Intent State Passed
Isolation link Down Connectivity Check Passed
Link Down Flow State Failed
Link Down Topology State Link Up Passed
Link Up Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter PassedAfter removing intents Flow State 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
After removing intents Flow State Passed

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 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL point to multi point intents - PASS
3000.2 IPV4: Install and test single point to multi point intents - PASS
3000.3 IPV4_2: Add single point to multi point intents - PASS
3000.4 VLAN: Add single point to multi point intents - PASS
3000.5 VLAN: Add single point to multi point intents - PASS

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

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

4000.1 NOOPTION: Add multi point to single point intents - PASS
4000.2 IPV4: Add multi point to single point intents - PASS
4000.3 IPV4_2: Add multi point to single point intents - PASS
4000.4 VLAN: Add multi point to single point intents - PASS
4000.5 VLAN: Add multi point to single point intents - PASS
4000.6 ENCAPSULATION: Add multi point to single point intents - PASS

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

5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
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

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

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

Case 18: Stop Mininet and Scapy - PASS

...

Page tree

Page History

Versions Compared

Old Version 905

New Version 906

Key

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

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

FAIL

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

Case 18: Stop Mininet and Scapy - PASS

Case 19: Copy karaf logs - PASS

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

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

Case 12: Assign switches to controllers - PASS

Case 13: Create scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

Case 16: Balance mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

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

Case 18: Stop Mininet and Scapy - PASS

Case 19: Copy karaf logs - PASS

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

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

Case 12: Assign switches to controllers - PASS

Case 13: Create scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

Case 16: Balance mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

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

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

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

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

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

Case 19: Copy karaf logs - PASS

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

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

Case 12: Assign switches to controllers - PASS

Case 13: Create scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

Case 16: Balance mastership of switches - PASS

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

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

3 - Using Flow

Rules - FAIL

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

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

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

Case 19: Copy karaf logs - PASS

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

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

Case 12: Assign switches to controllers - PASS

Case 13: Create scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

Case 16: Balance mastership of switches - PASS

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

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

Case 18: Stop Mininet and Scapy - PASS

Case 19: Copy karaf logs - PASS

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

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

Case 12: Assign switches to controllers - PASS

Case 13: Create scapy components - PASS

Case 15: Discover all hosts using scapy - PASS

Case 16: Balance mastership of switches - PASS

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

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

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS