Date: Fri, 29 Mar 2024 00:15:58 +0000 (UTC)
Message-ID: <1902834087.927.1711671358467@ip-10-30-146-46.us-west-2.compute.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_926_1318344304.1711671358464"
------=_Part_926_1318344304.1711671358464
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
FUNCintent at 14 Nov 2020 14:03:08=20
commit 7898ceda95b0e27a048c9fcee5e5c8daa332a4d4 (HEAD, origin/onos-1.15, on=
os-1.15)
Author: Jian Li [pyguni@gmail.com]
AuthorDate: Mon Oct 5 22:36:41 2020 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Mon Oct 5 22:56:34 2020 +0900
Fix: make all openstack resource name optional
Case 1: Pull onos branch and build onos on Teststation. - PASS
For loading from params file, and pull and build the latest ONOS package=
- 1.1 Constructing test variables - PASS :tick:
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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out i=
f topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS :tick:
Case 1=
2: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: Cre=
ate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case 15=
: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case 1=
6: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Using Flo=
w Rules - PASS
This test case tests Host intents using 1 node(s) cluster; Different typ=
e 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 F=
low Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Using F=
low 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 sta=
ck, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile i=
ntents using Flow Rules
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents Test -=
1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents Test -=
1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Rules
- 4000.1 NOOPTION: Add multi point to single point intents - PASS :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
Case 5000: Test host mobility with host inten=
ts - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Point Fa=
ilure - 1 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - PASS :tick:
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 :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy karaf =
logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out i=
f topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Using Flo=
w Rules - PASS
This test case tests Host intents using 3 node(s) cluster; Different typ=
e 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 F=
low Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using F=
low 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 sta=
ck, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile i=
ntents using Flow Rules
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents Test -=
3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents Test -=
3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Rules
- 4000.1 NOOPTION: Add multi point to single point intents - PASS :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
Case 5000: Test host mobility with host inten=
ts - 3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Point Fa=
ilure - 3 NODE(S) - OF 1.0 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - PASS :tick:
Case 18: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out i=
f topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS :tick:
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - Usin=
g Flow Objectives - PASS
This test case tests Host intents using 1 node(s) cluster; Different typ=
e 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 F=
low Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - Us=
ing 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 sta=
ck, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile i=
ntents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :cross:
- 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 :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents T=
est - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents T=
est - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Objectives
- 4000.1 NOOPTION: Add multi point to single point intents - PASS :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
Case 5000: Test host mobility with host =
intents - 1 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - FAIL :cross:<=
/li>
- Mobility: Failed to move h1 to s6 to single point intents with IPV4 typ=
e and MAC addresses in the same VLAN
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Poi=
nt Failure - 1 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - PASS :tick:
Case 18: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 10: Start Mininet topology with OF 1.0 switches - PASS
Start mininet topology with OF 1.0 switches to test intents, exits out i=
f topology did not start correctly
- 10.1 Starting Mininet topology with OF 1.0 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.0 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 17: Enable intent compilation using Flow Objectives - PASS<=
/h3>
- 17.1 Enabling Flow Objectives - PASS :tick:
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Usin=
g Flow Objectives - PASS
This test case tests Host intents using 3 node(s) cluster; Different typ=
e 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 F=
low Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Us=
ing 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 sta=
ck, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile i=
ntents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents T=
est - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents T=
est - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet =
and compile intents using Flow Objectives
- 4000.1 NOOPTION: Add multi point to single point intents - PASS :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
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 :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Poi=
nt Failure - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - FAIL :cross:
- Assertion results for IPV4 multi to single with partial failures allowe=
d
- 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 :cross:
- 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 w=
ith partial failures allowed - FAIL :cross:
- Assertion results for IPV4 single to multi point intent with partial fa=
ilures 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: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out i=
f topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flo=
w Rules - PASS
This test case tests Host intents using 1 node(s) cluster; Different typ=
e 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 F=
low Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using F=
low 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 sta=
ck, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile i=
ntents using Flow Rules
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
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 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
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 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
Case 5000: Test host mobility with host inten=
ts - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Point Fa=
ilure - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - PASS :tick:
Case 18: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out i=
f topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flo=
w Rules - PASS
This test case tests Host intents using 3 node(s) cluster; Different typ=
e 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 F=
low Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Using F=
low 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 sta=
ck, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile i=
ntents using Flow Rules
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
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 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
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 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
Case 5000: Test host mobility with host inten=
ts - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Point Fa=
ilure - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - PASS :tick:
Case 18: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out i=
f topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 17: Enable intent compilation using Flow Objectives - PASS<=
/h3>
- 17.1 Enabling Flow Objectives - PASS :tick:
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Usin=
g Flow Objectives - PASS
This test case tests Host intents using 1 node(s) cluster; Different typ=
e 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 F=
low Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Us=
ing 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 sta=
ck, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile i=
ntents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents T=
est - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents T=
est - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 1 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
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 :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Poi=
nt Failure - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - FAIL :cross:
- Assertion results for IPV4 multi to single with partial failures allowe=
d
- 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 :cross:
- 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 w=
ith partial failures allowed - FAIL :cross:
- Assertion results for IPV4 single to multi point intent with partial fa=
ilures 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: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
Cas=
e 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 :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out i=
f topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS :tick:
Case=
12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS :tick:
Case 13: C=
reate scapy components - PASS
- 13.1 Create scapy components - No Result :warning:
- 13.2 Start scapy components - PASS :tick:
Case =
15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos dis=
covery - PASS :tick:
- 15.2 Populate hostsData - PASS :tick:
Case=
16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS :tick:
Case 17: Enable intent compilation using Flow Objectives - PASS<=
/h3>
- 17.1 Enabling Flow Objectives - PASS :tick:
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Usin=
g Flow Objectives - PASS
This test case tests Host intents using 3 node(s) cluster; Different typ=
e 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 F=
low Objectives
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS :tick:
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS :tick:
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS :tick:
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS :tick:
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS :tick:
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS :tick:
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS :tick:<=
/li>
- 1000.8 Confirm that ONOS leadership is unchanged - PASS :tick:
Case 2000: Point Intents Test - 3 NODE(S) - OF 1.3 - Us=
ing 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 sta=
ck, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile i=
ntents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS :tick:
- 2000.2 IPV4: Add point intents between h1 and h9 - PASS :tick:
- 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS :tick:
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL :cross:=
li>
- 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 :tick:
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS :tick:=
li>
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS :tick:
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS :tick:
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS :tic=
k:
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point i=
ntents between h1 and h9 - PASS :tick:
Case 3000: Single to Multi Point Intents T=
est - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:
- 3000.2 IPV4: Install and test single point to multi point intents - PAS=
S :tick:
- 3000.3 IPV4_2: Add single point to multi point intents - PASS :tick:
- 3000.4 VLAN: Add single point to multi point intents - PASS :tick:
- 3000.5 VLAN: Add single point to multi point intents - PASS :tick:
Case 4000: Multi To Single Point Intents T=
est - 3 NODE(S) - OF 1.3 - Using Flow Objectives - PASS
This test case will test single point to multi point intents using 3 nod=
e(s) cluster; Different type of hosts will be tested in each step such as I=
PV4, 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 :tick:<=
/li>
- 4000.2 IPV4: Add multi point to single point intents - PASS :tick:
- 4000.3 IPV4_2: Add multi point to single point intents - PASS :tick:
- 4000.4 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.5 VLAN: Add multi point to single point intents - PASS :tick:
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS :t=
ick:
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 :tick:=
li>
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS :tick:
Case 6000: Test Multi to Single End Poi=
nt Failure - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - P=
ASS :tick:
- 6000.2 Installing Multi to Single Point intents with partial failure al=
lowed - PASS :tick:
- 6000.3 NOOPTION: Install and test single point to multi point intents -=
PASS :tick:
- 6000.4 NOOPTION: Install and test single point to multi point intents w=
ith partial failures allowed - FAIL :cross:
- Assertion results for IPV4 single to multi point intent with partial fa=
ilures 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: Sto=
p Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 18.2 Stopping Mininet - PASS :tick:
Case 19: Copy kara=
f logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS :tick:
------=_Part_926_1318344304.1711671358464--