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 8bfea5ec60caa14aa61b4efba1758f0394be8a4e 45ff4863ae71436c6fd2cdb7946b9e64c72744a4 (HEAD -] master, origin/master, origin/HEAD)
Author: Chinmaya Agarwal Ivan Eroshkin [chinmayaivan.agarwal@hsceroshkin@nokia.com]
AuthorDate: Wed Tue Oct 9 168 14:5359:22 38 2019 +05300200
Commit: Pier Luigi Ventre [pier@opennetworking.orgIvan Eroshkin [ivan.eroshkin@nokia.com]
CommitDate: Wed Thu Oct 16 1017 15:4542:26 47 2019 +0000
Fix for Bug 8005. Parsing Sub Tlv for multiple neighbors0200

Adding PowerConfig capability to the existing Nokia Transponder driver

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

...

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

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

...

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

Assertion results for IPV4 multi to single 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 PassedRecieved 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 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

...

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

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

3000 1000.1 NOOPTION: Install and test single point to multi point intents IPV4: Add host intents between h1 and h9 - PASS 3000
1000.2 IPV4: Install and test single point to multi point intents DUALSTACK1: Add host intents between h3 and h11 - PASS 3000
1000.3 IPV4_2DUALSTACK2: Add single point to multi point intents host intents between h1 and h11 - PASS 3000
1000.4 VLAN1HOP: Add single point to multi point intents host intents between h1 and h3 - PASS 3000
1000.5 VLAN: Add single point to multi point intents - 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: 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 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 2000.1 NOOPTION: Add multi point to single point intents - PASS 4000point 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 Failed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents PassedAfter removing intents Flow State Passed

2000.2 IPV4: Add multi point to single point intents - PASS 4000between 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 Failed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents PassedAfter removing intents Flow State Passed

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

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 Failed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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

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

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 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
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
Install Intent State Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Connectivity Check PassedPing Failed
Link Down Passed
Link Down Intent State Passed
Link Down Intent State PassedLink Down Flow 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
Pingall Failed
Link Up Passed
Link Up PassedLink 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

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

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

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

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 VLAN1VLAN: Add vlan host intents between h4 and h12 multi point to single point intents - PASS 1000
4000.6 VLAN2ENCAPSULATION: Add vlan host intents between h4 and h13 multi point to single point intents - PASS
1000.7 Encapsulation: Add host intents between h1 and h9 - PASS

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 - 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 1000.8 Confirm that ONOS leadership is unchanged - 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 partial failures allowed
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 FailedConnectivity 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 Pingall FailedDown 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 PassedFailed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Recieved Failed
Remove Intents PassedAfter FailedAfter removing intents Flow State Passed
2000.5 SDNIP-TCP: Add point intents between h1 and h9 - 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 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS 2000.7 VLAN: Add point intents between h5 and h21
18.2 Stopping Mininet - 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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

19.1 Copying karaf logs 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS

Case

...

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

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

2.1 Apply cell to environment 3000.1 NOOPTION: Install and test single point to multi point intents - PASS 3000
2.2 IPV4: Install and test single point to multi point intents Uninstalling Atomix - PASS 3000
2.3 IPV4_2: Add single point to multi point intents Uninstalling ONOS package - PASS 3000
2.4 VLAN: Add single point to multi point intents Creating ONOS package - PASS 3000.5 VLAN: Add single point to multi point intents
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

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

...

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 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
5000 1000.2 IPV4DUALSTACK1: Add host intents between h1 h3 and h9 h11 - PASS

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

1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
1000.4 1HOP: Add host intents between h1 and h3 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
1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
6000 1000.3 NOOPTION: Install and test single point to multi point intents 6 VLAN2: Add vlan host intents between h4 and h13 - PASS 6000
1000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed 7 Encapsulation: Add host intents between h1 and h9 - 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

...

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 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 3000.1 IPV4: Add host intents between h1 and h9 NOOPTION: Install and test single point to multi point intents - PASS 1000
3000.2 DUALSTACK1: Add host intents between h3 and h11 IPV4: Install and test single point to multi point intents - PASS 1000
3000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 single point to multi point intents - PASS 1000
3000.4 1HOPVLAN: Add host intents between h1 and h3 single point to multi point intents - PASS 1000
3000.5 VLAN1VLAN: Add vlan host intents between h4 and h12 single point to multi point intents - 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

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 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 4000.1 NOOPTION: Add multi point to single point intents between h1 and h9 - PASS 2000
4000.2 IPV4: Add multi point intents between h1 and h9 to single point intents - PASS
2000 4000.3 IPV4_2: Add multi point to single point intents between h1 and h9 - PASS 2000
4000.4 SDNIP-ICMPVLAN: Add multi point to single 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
- 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 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point 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

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

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 3000.1 NOOPTION: Install and test single point to multi point intents - PASS 3000
6000.2 IPV44 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS 3000.3 IPV4_2: Add single point to multi point intents

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
3000.4 VLAN: Add single point to multi point intents 18.2 Stopping Mininet - PASS 3000.5 VLAN: Add single point to multi point intents

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

2.1 Apply cell to environment 4000.1 NOOPTION: Add multi point to single point intents - PASS 4000
2.2 IPV4: Add multi point to single point intents Uninstalling Atomix - PASS 4000
2.3 IPV4_2: Add multi point to single point intents Uninstalling ONOS package - PASS 4000
2.4 VLAN: Add multi point to single point intents Creating ONOS package - PASS 4000
2.5 VLAN: Add multi point to single point intents Installing Atomix - PASS 4000
2.6 ENCAPSULATION: Add multi point to single point intents Installing ONOS package - PASS

Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Rules - 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
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

...

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

Case

...

13: Create scapy components - PASS

Stopping the current mininet topology to start up fresh

13.1 Create scapy components - No Result
13.2 Start scapy components
18.1 Stopping and Removing Scapy Host Components - PASS
18.2 Stopping Mininet - PASS

Case

...

15: Discover all hosts using scapy - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

15.1 Send packets from each host to the first host and confirm onos discovery - PASS
15.2 Populate hostsData 19.1 Copying karaf logs - PASS

Case

...

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

...

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

2000 3000.1 NOOPTION: Add Install and test single point to multi point intents between h1 and h9 - PASS 2000
3000.2 IPV4: Add Install and test single point to multi point intents between h1 and h9 - PASS
2000 3000.3 IPV4_2: Add single point intents between h1 and h9 to multi point intents - PASS 2000
3000.4 SDNIP-ICMPVLAN: Add single 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 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

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 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point 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 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

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 3000.1 NOOPTION: Install and test single point to multi point intents - PASS 3000
6000.2 IPV44 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS 3000.3 IPV4_2: Add single point to multi point intents

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
3000.4 VLAN: Add single point to multi point intents 18.2 Stopping Mininet - PASS 3000.5 VLAN: Add single point to multi point intents

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

2.1 Apply cell to environment - PASS
2.2 Uninstalling Atomix 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 .3 Uninstalling ONOS package - PASS 4000
2.4 VLAN: Add multi point to single point intents Creating ONOS package - PASS 4000
2.5 VLAN: Add multi point to single point intents Installing Atomix - PASS 4000
2.6 ENCAPSULATION: Add multi point to single point intents Installing ONOS package - PASS

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

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

...

11: Start Mininet topology with OF 1.3 switches - PASS

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

11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

16.1 Balancing mastership of switches - PASS

Case 17: Enable intent compilation using Flow Objectives - PASS

17.1 Enabling Flow Objectives - PASS

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

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

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

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

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

2000.1 NOOPTION: Add point intents between h1 and h9 - 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

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 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 PassedRecieved Failed
Remove Intents FailedAfter PassedAfter 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

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.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 Received Passed
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 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 - FAIL

Assertion Result for NOOPTION point intent
Install Intent State Passed

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 Failed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Passed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents 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 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.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 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.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 FailedPassed
Link Down Passed
Link Down Intent State PassedFailed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall FailedPassed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Recieved FailedReceived Passed
Remove Intents PassedAfter removing intents Flow State Passed

2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for 2 IPV4: Add point intents between h1 and h9 - FAIL

Assertion Result for BANDWIDTH ALLOCATION for IPV4 point intent
Install Intent State PassedBandwidth Allocation check Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Ping FailedPassed
Link Down Passed
Link Down Intent State PassedFailed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall FailedPassed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Recieved FailedReceived Passed
Remove Intents PassedAfter 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 NOOPTION: Install and test single point to multi point intents - PASS
3000.2 IPV4: Install and test single point to multi point intents - PASS
3000.3 IPV4_2: Add single point to multi point intents - PASS
3000.4 VLAN: Add single point to multi point intents - PASS
3000.5 VLAN: Add single point to multi point intents - PASS

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

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

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

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

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
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 Failed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Pingall Failed
Link Up Passed
Link Up Intent State Passed
Link Up Flow State Passed
Link Up Topology State Passed
Link Up Scapy Packet Recieved Failed
Remove Intents PassedAfter removing intents Flow State Passed

2000.5 SDNIP-TCP: Add point
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 - 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 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL

Assertion results Result for Dualstack1 IPV4 multi to single with partial failures allowedwith 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
Initial Connectivity Check Link Down Topology State Passed
Link Down Pingall Passed
Link Down Up Passed
Link Down Up Intent State Passed
Link Down Up Flow State Passed
Link Down Up 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
Up Scapy Packet Received Passed
Remove Intents PassedAfter removing intents Flow State Passed

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 Passed
Link Down Passed
Link Down Intent State Passed
Link Down Flow State Failed
Link Down Topology State Passed
Link Down Pingall
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 PassedFailed
Link Up Topology State Passed
Link Up Scapy Packet Received Passed
Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

6000.3 NOOPTION: Install and test single point to multi point intents 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL

Assertion results for IPV4 single to multi Result for BANDWIDTH ALLOCATION for point intent with no options set
Install Intent State Passed
Bandwidth Allocation check Passed
Flow duration check Passed
Initial Intent State Passed
Initial Flow State Passed
Initial Connectivity Check Ping Passed
Link Down Passed
Link Down PassedLink Down Intent State PassedFailed
Link Down Flow State Passed
Link Down Topology State Passed
Link Down Connectivity Check Pingall PassedIsolation link Down
Link Up Passed
Isolation link Down Link Up Intent State PassedIsolation link Down
Link Up Flow State Passed
Isolation link Down Link Up 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 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

Link Up Scapy Packet Received Passed
Remove Intents PassedAfter 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 NOOPTION: Install and test single point to multi point intents - PASS
3000.2 IPV4: Install and test single point to multi point intents - PASS
3000.3 IPV4_2: Add single point to multi point intents - PASS
3000.4 VLAN: Add single point to multi point intents - PASS
3000.5 VLAN: Add single point to multi point intents - PASS

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

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

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

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

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

Case 18: Stop Mininet and Scapy - PASS

...

Page tree

Page History

Versions Compared

Old Version 855

New Version 856

Key

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

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

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

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

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 -