...
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 d14f1a3f22a212ae2a0f5e97fa416264a1c5903d 42e8c2527e3877511d061ef28b228e25e12a4c72 (HEAD, origin/master, origin/HEAD, master)
Author: Yi Tseng [yi@opennetworking.orgMatteo Scandolo [matteo.scandolo@gmail.com]
AuthorDate: Tue Fri Oct 13 1923 10:1517:12 00 2020 -0700
Commit: Yi Tseng pierventre [yi@opennetworkingpier@opennetworking.org]
CommitDate: Fri Sat Oct 23 0124 10:0924:40 02 2020 -0700
Support install IntIntents to device with postcard mode+0200
Adding helper method in RADIUS packet
Case 1: Pull onos branch and build onos on Teststation. - PASS
...
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL
- Assertion results for IPV4 multi to single with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check FailedPassed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State FailedPassed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check PassedFailed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State PassedFailed
- 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 PassedFailed
- 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 FailedAfter removing intents Flow State Passed
...
- 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 - FAIL
- Assertion Result for VLAN Encapsulated host intent
- Install 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 Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Pingall Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
- PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 3 NODE(Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives - PASS
...
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.0 - Using Flow Objectives -
...
FAIL
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- FAIL
- Assertion results for IPV4 multi to single
- with partial failures allowed
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 1000.1 IPV4: Add host intents between h1 and h9 - PASS
- 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS
- 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS
- 1000.4 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case 2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
...
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Failed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Failed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Failed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Failed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents FailedAfter removing intents Flow State Passed
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
...
This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 1000.1 IPV4: Add host intents between h1 and h9 6000.1 Installing Multi to Single Point intents with no options set - PASS 6000
- 1000.2 Installing Multi to Single Point intents with partial failure allowed DUALSTACK1: Add host intents between h3 and h11 - PASS
- 6000 1000.3 NOOPTION: Install and test single point to multi point intents DUALSTACK2: Add host intents between h1 and h11 - PASS 6000
- 1000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 18.1 Stopping and Removing Scapy Host Components - PASS 18.2 Stopping Mininet
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case
...
2000: Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test point to point intents using 1
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 clustercluster; 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 2.1 Apply cell to environment - PASS
- 2 2000.2 Uninstalling Atomix IPV4: Add point intents between h1 and h9 - PASS 2
- 2000.3 Uninstalling ONOS package IPV4_2: Add point intents between h1 and h9 - PASS 2
- 2000.4 Creating ONOS package SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2 2000.5 Installing Atomix SDNIP-TCP: Add point intents between h1 and h9 - PASS 2
- 2000.6 Installing ONOS package DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2 2000.7 Set up ONOS secure SSH VLAN: Add point intents between h5 and h21 - PASS 2
- 2000.8 Checking ONOS service VLAN: Add point intents between h5 and h21 - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation 2.10 Checking ONOS nodes - PASS 2
- 2000.11 Checking ONOS applications 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
...
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
...
- Using Flow Rules - PASS
This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case tests Host will test single point to multi point intents using 3 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS 1000
- 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS 1000
- 4000.3 DUALSTACK2: Add host intents between h1 and h11 IPV4_2: Add 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
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
Case 5000: Test host mobility with host intents - 1 NODE(S) - OF 1.3 - 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.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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 4000.1 NOOPTION: Add multi point to single point intents - PASS
- 4000.2 IPV4: Add multi point to single point intents - PASS
- 4000.3 IPV4_2: Add multi point to single point intents - PASS
- 4000.4 VLAN: Add multi point to single point intents - PASS
- 4000.5 VLAN: Add multi point to single point intents - PASS
- 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
...
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 1000: Host Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 1000.1 IPV4: Add host intents between h1 and h9 6000.1 Installing Multi to Single Point intents with no options set - PASS 6000
- 1000.2 Installing Multi to Single Point intents with partial failure allowed DUALSTACK1: Add host intents between h3 and h11 - PASS
- 6000 1000.3 NOOPTION: Install and test single point to multi point intents DUALSTACK2: Add host intents between h1 and h11 - PASS 6000
- 1000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed 1HOP: Add host intents between h1 and h3 - PASS
- 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS
- 1000.7 Encapsulation: Add host intents between h1 and h9 18.1 Stopping and Removing Scapy Host Components - PASS 18.2 Stopping Mininet
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
Case
...
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
...
2000: Point Intents Test - 3 NODE(S) - OF 1.3 - 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.3 OVS running in Mininet and compile intents using Flow Rules
- 2000.1 NOOPTION: Add point intents between h1 and h9
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS 2
- 2000.2 Uninstalling Atomix IPV4: Add point intents between h1 and h9 - PASS
- 2 2000.3 Uninstalling ONOS package IPV4_2: Add point intents between h1 and h9 - PASS 2
- 2000.4 Creating ONOS package - PASS SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 2.5 Installing Atomix - PASS 2
- 2000.6 Installing ONOS package DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2 2000.7 Set up ONOS secure SSH VLAN: Add point intents between h5 and h21 - PASS 2
- 2000.8 Checking ONOS service VLAN: Add point intents between h5 and h21 - PASS
- 2 2000.9 Starting ONOS CLI sessions 1HOP: Add point intents between h1 and h3 - PASS 2
- 2000.10 Checking ONOS nodes Add point to point intents using VLAN Encapsulation - PASS 2
- 2000.11 Checking ONOS applications BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case
...
3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3
...
- Using Flow Rules - PASS
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Rules
- 3000.1 NOOPTION: Install and test single point to multi point intents - PASS
- 3000.2 IPV4: Install and test single point to multi point intents - PASS
- 3000.3 IPV4_2: Add single point to multi point intents - PASS
- 3000.4 VLAN: Add single point to multi point intents - PASS
- 3000.5 VLAN: Add single point to multi point intents - PASS
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
This test case will test single point to multi point intents using 3
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 ObjectivesRules
- 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS 1000
- 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS 1000
- 4000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 multi point to single point intents - PASS 1000
- 4000.4 1HOPVLAN: Add host intents between h1 and h3 multi point to single point intents - PASS 1000
- 4000.5 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
- 1000.8 Confirm that ONOS leadership is unchanged - PASS
...
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow
...
Rules -
...
PASS
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - PASS
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Rules - PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS
- 6000.3 NOOPTION: Install and test single point to multi point intents - PASS
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 17: Enable intent compilation using Flow Objectives - PASS
- 17.1 Enabling Flow Objectives - PASS
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
This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL
- Assertion Result for NOOPTION point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.2 IPV4: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL
- Assertion Result for IPV4 no mac address point intents
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Passed
- 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS
- 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
- 1000.7 VLAN3 DUALSTACK2: Add point host intents between h5 h1 and h21 h11 - PASS 2000
- 1000.8 VLAN4 1HOP: Add point host intents between h5 h1 and h21 h3 - PASS 2000
- 1000.9 1HOP5 VLAN1: Add point vlan host intents between h1 h4 and h3 h12 - PASS 2000
- 1000.10 Add point to point intents using VLAN Encapsulation - FAIL
- Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
- Encapsulation intents check failed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Failed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Pingall Failed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents PassedAfter removing intents Flow State Passed
- 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 - PASS
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 - PASS
- 2000.5 SDNIP-TCP: Add 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 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
- 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) - Case 3000: Single to Multi Point Intents Test - 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 -
...
PASS
- 6000.1 Installing Multi to Single Point intents with no options set - PASS
- 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL Assertion results for IPV4 multi to single
- 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
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Isolation link Down Intent State Passed
- Isolation link Down Flow State Passed
- Isolation link Down Topology State Passed
- Isolation link Down Connectivity Check Passed
- Isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Passed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents FailedAfter removing intents Flow State Passed
- 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL
- Assertion results for IPV4 single to multi point intent with partial failures allowed
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Passed
- Link Down Topology State Passed
- Link Down Connectivity Check Passed
- Isolation link Down Passed
- Partial failure isolation link Down Intent State Passed
- Partial failure isolation link Down Flow State Passed
- Partial failure isolation link Down Topology State Passed
- Partial failure isolation link Down Connectivity Check Passed
- Partial failure isolation link Down Connectivity Check Passed
- Link Up Passed
- Link Up Passed
- Link Up Passed
- Link Up Intent State 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 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 - 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.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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 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 - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Initial Flow State Passed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 3000.3 IPV4_2: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- After removing intents Flow State Failed
- 3000.4 VLAN: Add single point to multi point intents - FAIL
- Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 3000.5 VLAN: Add single point to multi point intents - FAIL
- Assertion results for single to multi point intent with VLAN treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
Case 4000: Multi To Single Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.3 OVS running in Mininet and compile intents using Flow Objectives
- 4000.1 NOOPTION: Add multi point to single point intents - FAIL
- Assertion results for NOOPTION multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.2 IPV4: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.3 IPV4_2: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.4 VLAN: Add multi point to single point intents - FAIL
- Assertion results for IPV4 multi to single point intent with IPV4 type and no MAC addresses in the same VLAN
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.5 VLAN: Add multi point to single point intents - FAIL
- Assertion results for multi to single point intent with VLAN ID treatment
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 4000.6 ENCAPSULATION: Add multi point to single point intents - FAIL
- Assertion results for VLAN Encapsulation multi to single point intent
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Bad Sender Ping Passed
- Bad Recipient Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
Case 5000: Test host mobility with host intents - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS
- 5000.2 IPV4: Add host intents between h1 and h9 - FAIL
- Assert result for IPV4 host intent between h1, moved, and h9
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Ping Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- Link Down Topology State Passed
- Link Down Pingall Passed
- Link Up Passed
- Link Up Intent State Passed
- Link Up Flow State Failed
- Link Up Topology State Passed
- Link Up Pingall Passed
- Remove Intents PassedAfter removing intents Flow State Failed
Case 6000: Test Multi to Single End Point Failure - 3 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL
- - PASS
Case 18: Stop Mininet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 18.1 Stopping and Removing Scapy Host Components - PASS
- 18.2 Stopping Mininet - PASS
Case 19: Copy karaf logs - PASS
Copying the karaf logs to preserve them throughreinstalling ONOS
- 19.1 Copying karaf logs - PASS
Case 2: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 11: Start Mininet topology with OF 1.3 switches - PASS
Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly
- 11.1 Starting Mininet topology with OF 1.3 switches - PASS
Case 12: Assign switches to controllers - PASS
Assign OF 1.3 switches to ONOS nodes
- 12.1 Assigning switches to controllers - PASS
Case 13: Create scapy components - PASS
- 13.1 Create scapy components - No Result
- 13.2 Start scapy components - PASS
Case 15: Discover all hosts using scapy - PASS
- 15.1 Send packets from each host to the first host and confirm onos discovery - PASS
- 15.2 Populate hostsData - PASS
Case 16: Balance mastership of switches - PASS
- 16.1 Balancing mastership of switches - PASS
Case 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 - 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.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 - PASS
- 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS
- 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS
- 2000.7 VLAN: Add point intents between h5 and h21 - PASS
- 2000.8 VLAN: Add point intents between h5 and h21 - PASS
- 2000.9 1HOP: Add point intents between h1 and h3 - PASS
- 2000.10 Add point to point intents using VLAN Encapsulation - PASS
- 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS
Case 3000: Single to Multi Point Intents Test - 3 NODE(S) - OF 1.3 - Using Flow 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 - 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.1 Installing Multi to Single Point intents with no options set - FAIL
- Assertion results for IPV4 multi to single point intent end point failure with no options set
- Install Intent State Passed
- Flow duration check Passed
- Initial Intent State Passed
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- 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 Failed
- 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 Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- 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 Failed
- 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 Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed
- Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Intial Flow State Failed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State Failed
- 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 Failed
- 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 Failed
- Link Up Topology State Passed
- Link Up Scapy Packet Received Passed Remove Intents PassedAfter removing intents Flow State Failed
- 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
- Intial Initial Flow State FailedPassed
- Initial Connectivity Check Passed
- Link Down Passed
- Link Down Passed
- Link Down Intent State Passed
- Link Down Flow State FailedPassed
- 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 FailedPassed
- 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 FailedPassed
- Link Up Topology State Passed
- Link Up Scapy Packet Recieved Failed
- Remove Intents FailedAfter removing intents Flow State FailedPassed
Case 18: Stop Mininet and Scapy - PASS
...