Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-master/1182/

...

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 6fb95fccf8356a7549fbb4d0fd638d7537982c7d c8e6a50216e81944db5f37541f658484b78fa6d9 (HEAD -] master, origin/master, origin/HEAD)
Author: Andrea Campanella [andrea@opennetworking.org]
AuthorDate: Mon Mar 12 1119:0725:35 44 2018 -0700
Commit: Ray Milkey Andrea Campanella [ray@opennetworkingandrea@opennetworking.org]
CommitDate: Tue Thu Mar 13 15 01:5013:38 19 2018 +0000

T3: bugfixes and avoid override of finalizeAdding summary to pingall, false if any of the path in the trace fails and minor fixes
--
(cherry picked from commit 3577bae12a5b395e2113c6035edca08a6339c1a06207715317b140dd8d6e324a974c1d8a449c0fb8)

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

...

  • 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)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

...

FAIL

This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents 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 Protected: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents 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 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (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)

...

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

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

  • 4000 3000.1 NOOPTION: Add multi Install and test single point to single multi point intents - PASS (tick) 4000
  • 3000.2 IPV4: Add multi Install and test single point to single multi point intents - PASS (tick)
  • 4000 3000.3 IPV4_2: Add multi single point to single multi point intents - PASS (tick)
  • 4000 3000.4 VLAN: Add multi single point to single multi point intents - PASS (tick) 4000
  • 3000.5 VLAN: Add multi single point to single point intents - PASS (tick) 4000.6 ENCAPSULATION: Add multi point to single point intents - PASS (tick)

Case

...

4000:

...

Multi To Single Point Intents Test - 1 NODE(S) - OF 1.0 - Using Flow Rules -

...

FAIL

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

  • 4000.1 NOOPTION: Add multi point to single point intents 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000 4000.2 IPV4: Add host intents between h1 and h9 multi point to single point intents - PASS (tick)

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

  • 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
  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS (tick)
  • 6000.3 NOOPTION: Install and test single point to multi point intents - PASS (tick) 6000
  • 4000.4 NOOPTION: Install and test single 6 ENCAPSULATION: Add multi point to multi single point intents with partial failures allowed - PASS (tick)

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • - FAIL (error)
    • Assertion results for VLAN Encapsulation multi to single point intent

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

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9
  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case

...

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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 Flow Rules - PASS

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

  • 1000.1 IPV4: Add 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)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

...

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

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - 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 with 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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 Flow Rules -

...

PASS

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

  • 2000 1000.1 NOOPTIONIPV4: Add point host intents between h1 and h9 - PASS (tick) 2000
  • 1000.2 IPV4DUALSTACK1: Add point host intents between h1 h3 and h9 h11 - PASS (tick)
  • 2000 1000.3 ProtectedDUALSTACK2: Add point host intents between h1 and h9 h11 - PASS (tick) 2000
  • 1000.4 IPV4_21HOP: Add point host intents between h1 and h9 h3 - PASS (tick) 2000
  • 1000.5 SDNIP-ICMPVLAN1: Add point vlan host intents between h1 h4 and h9 h12 - PASS (tick) 2000
  • 1000.6 SDNIP-TCPVLAN2: Add point vlan host intents between h1 h4 and h9 h13 - PASS (tick)
  • 2000 1000.7 DUALSTACK1Encapsulation: Add point host intents between h3 h1 and h11 h9 - PASS (tick) 2000.8 VLAN: Add point intents between h5 and h21
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

  • 2000.1 NOOPTION: Add
  • .9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL (error)
    • Assertion Result for BANDWIDTH ALLOCATION for NOOPTION point intent
    • Install Intent State Passed
    • Bandwidth Allocation check Failed

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

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (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 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Rules

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 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 (tick)

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

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

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

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - 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 with 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 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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 - Using Flow Objectives - FAIL

This test case tests Host intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow 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 - FAIL (error)
    • Assertion Result for VLAN Encapsulated host intent
    • Install Intent State Passed
    • Encapsulation intents check failed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - 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.0 OVS running in Mininet and compile intents 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 Protected: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS (tick)

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

This test case will test single point to multi point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.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 - PASS (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 Objectives - FAIL

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 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 - FAIL (error)
    • Assertion results for VLAN Encapsulation multi to single point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall 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 Passed

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

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

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

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - 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 with partial failures allowed - FAIL (error)
    • 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 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 Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents 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 (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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 - 3 NODE(S) - OF 1.0 - Using Flow Objectives - FAIL

This test case tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow 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 - FAIL (error)
    • Assertion Result for VLAN Encapsulated host intent
    • Install 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 Pingall Failed
    • Remove Intents Passed
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

Case 2000: Point Intents Test - 3 NODE(S) - OF 1.0 - 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.0 OVS running in Mininet and compile intents 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 Protected: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS (tick)

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

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

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (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 Objectives - FAIL

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 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 - FAIL (error)
    • Assertion results for VLAN Encapsulation multi to single point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall 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 Passed

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)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

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

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - 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 with 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 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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 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 (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)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 Protected: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL (error)
    • 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 Failed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

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 (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (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 - FAIL

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 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 - FAIL (error)
    • Assertion results for VLAN Encapsulation multi to single point intent

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

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - FAIL (error)
    • Assert result for IPV4 host intent between h1, moved, and h9
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Pingall Passed
    • Remove Intents Failed

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

  • 6000.1 Installing Multi to Single Point intents with no options set - FAIL (error)
    • Assertion results for IPV4 multi to single point intent end point failure with no options set
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Connectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Isolation link Down Intent State Passed
    • Isolation link Down Flow State Passed
    • Isolation link Down Topology State Passed
    • Isolation link Down Connectivity Check Passed
    • Isolation link Down Connectivity Check Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Failed
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL (error)
    • Assertion results for IPV4 multi to single with partial failures allowed
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Connectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Intent State Passed
    • Partial failure isolation link Down Flow State Passed
    • Partial failure isolation link Down Topology State Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Failed
  • 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • 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 Failed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • 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 Failed

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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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 Flow Rules - PASS

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

  • 1000.1 IPV4: Add host intents between h1 and h9 - PASS (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)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 Protected: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
    • Initial Iperf Passed
    • Remove Intents Failed
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.11 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.12 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL (error)
    • Assertion Result for BANDWIDTH ALLOCATION for point intent
    • Install Intent State Passed
    • Bandwidth Allocation check Failed

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 (tick)
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (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 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 (tick)
  • 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 (tick)

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 (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)

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

  • 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick)
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - FAIL (error)
    • 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 Failed
    • 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 Passed
  • 6000.3 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • 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 Failed
    • 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 Passed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with 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 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 ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - 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 if 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: Create 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 discovery - 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.3 - Using Flow Objectives - FAIL

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

    • 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 Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 point intent
    • 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 Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.3 Protected: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for protected point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Intial Flow State Failed
    • Initial Ping Passed
    • Link Down Passed
    • Link down Scapy Packet Received Passed
    • Protected Intent Check 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 Passed
  • 2000.4 IPV4_2: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 no mac address point intents
    • 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 Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.5 SDNIP-ICMP: Add point
  • 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 - FAIL (error)
    • Assertion Result for VLAN Encapsulated host intentSDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Encapsulation intents check failed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State PassedFailed
    • Initial Ping FailedPassed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall FailedPassed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State PassedFailed
    • Link Up Topology State Passed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

    • Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
    • Initial Iperf Passed
    • Remove Intents Failed
  • 2000.7 DUALSTACK1 2000.1 NOOPTION: Add point intents between h1 h3 and h9 h11 - FAIL (error)
    • Assertion Result for NOOPTION point intentDualstack1 IPV4 with mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State PassedFailed
    • Initial Ping FailedPassed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall FailedPassed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State PassedFailed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved FailedReceived Passed
    • Remove Intents Passed
  • 2000.2 IPV48 VLAN: Add point intents between h1 h5 and h9 h21 - FAIL (error)
    • Assertion Result for VLAN IPV4 with mac address point intentintents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State PassedFailed
    • Initial Ping FailedPassed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall FailedPassed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State PassedFailed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved FailedReceived Passed
    • Remove Intents Passed
  • 2000.3 Protected9 VLAN: Add point intents between h1 h5 and h9 h21 - FAIL (error)
    • Assertion Result for protected point intentVLAN IPV4 point intents with VLAN treatment
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State PassedFailed
    • Initial Ping FailedPassed
    • Link Down Passed
    • Link down Scapy Packet Recieved Failed
    • Protected Intent Check Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall FailedPassed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State PassedFailed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved FailedReceived Passed
    • Remove Intents Passed
  • 2000.4 IPV4_210 1HOP: Add point intents between h1 and h9 h3 - FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State PassedFailed
    • Initial Ping FailedPassed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State PassedFailed
    • Link Down Topology State Passed
    • Link Down Pingall FailedPassed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.5 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
    • Initial Iperf Failed
    • Remove Intents Passed
  • 2000.7 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 VLAN: Add point intents between h5 and h21 - PASS (tick)
    • Passed
    • Link Up Flow State Failed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
    2000.10 1HOP: Add point intents between h1 and h3 - PASS (tick)