Page History

...

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

commit d405a5d0337e0558eef2663f6fae10ed275be075 d95d3524caff5449aded4ff9397c3ed717fc91e6 (HEAD, origin/onos-2.2, onos-2.2)
Author: Charles Chan Jian Li [charles@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Mon Jun 7 16:08:43 2021 -0700Thu Aug 12 18:03:30 2021 +0900
Commit: Charles Chan Jian Li [charles@opennetworkingpyguni@gmail.orgcom]
CommitDate: Wed Jun 9 20:47:33 2021 +0000
SDFAB-76 Work around missing packet request cased by consistet multimap issue
--
(cherry picked from commit f8bd3ae768c11e4d12b9586a5865413995370be4)Thu Aug 12 18:58:19 2021 +0900

Add default route option to kubevirt network

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

...

• 1.1 Constructing test variables - PASS

Case 2: Starting up 1 node(s)

...

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 10: Start Mininet topology with OF 1.0 switches - PASS

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

• 10.1 Starting Mininet topology with OF 1.0 switches - PASS

Case 12: Assign switches to controllers - PASS

Assign OF 1.0 switches to ONOS nodes

• 12.1 Assigning switches to controllers - PASS

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

• 16.1 Balancing mastership of switches - PASS

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - 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.0 OVS running in Mininet and compile intents using Flow Rules

...

ONOS

...

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

...

cluster

...

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

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

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

• 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
• Assertion results for IPV4 single to multi point intent with no options set
• 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 addresses
• 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
• 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
• 3000.5 VLAN: Add single point to multi point intents - FAIL
• Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - PASS

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

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

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

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

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

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

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

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

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

• 3000.1 NOOPTION: Install and test single point to multi point intents - FAIL
• Assertion results for IPV4 single to multi point intent with no options set
• 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 addresses
• 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
• 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
• 3000.5 VLAN: Add single point to multi point intents - FAIL
• Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - PASS

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

...

- FAIL