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

...

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 2d77c1a0498e7b8462b8040c5a25408e214ee164 efb6cc53df699e2e9efb8ccfd96af0d539f918be (HEAD -] master, origin/master, origin/HEAD)
Author: ONOS Jenkins User [jenkins@onlab.usRay Milkey [ray@opennetworking.org]
AuthorDate: Fri Wed Apr 19 1724 13:2445:24 18 2019 +0000-0700
Commit: ONOS Jenkins User [jenkins@onlab.usRay Milkey [ray@opennetworking.org]
CommitDate: Fri Wed Apr 19 1724 22:2411:24 05 2019 +0000
Starting snapshot 2.1.0-SNAPSHOT
Fix build behind web proxy - provide all jars needed by grpc java

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

...

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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 VLAN Encapsulation Point IntentInstall Intent State Passed
    • Encapsulation intents check Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Failed
  • 2000.11 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
    • 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 PassedAfter removing intents Flow State Failed

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

...

FAIL

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

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

Case 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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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)

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

  • 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
    • 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.2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • 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
    • 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.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • 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 (error)
    • 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 (error)
    • 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 - 1 NODE(S) - OF 1.0 - Using Flow Rules - FAIL

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

  • 2000 4000.1 NOOPTION: Add multi point to single point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
  • - FAIL (error)
    • Assertion results for NOOPTION multi to single point intent
    • Install Intent State Passed
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State PassedInitial
    • Intial Flow State Failed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Initial Bad Recipient 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 PassedAfter removing intents Flow State PassedFailed
  • 2000.5 SDNIP-TCP 4000.2 IPV4: Add multi point to single point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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 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

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

...

  • FAIL (error)
    • 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 - 1 NODE(S) - OF 1.0 - Using Flow Rules -

...

FAIL

  • 6000 5000.1 Installing Multi to Single Point intents with no options set Testing host mobility by moving h1 from s5 to s6 - PASS (tick) 6000
  • 5000.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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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 - PASS

  • 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
    • 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 - 1 NODE(S) - OF 1.0 - 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
    • 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 (error)
    • 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 (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
    • 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 (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
    • 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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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)

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

This test case will test point to point intents using 3 node(s) 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, 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 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point 1000.1 IPV4: Add host intents between h1 and h9 - PASS (tick)
  • 1000 2000.2 6 DUALSTACK1: Add host point intents between h3 and h11 - PASS (tick) 1000
  • 2000.3 DUALSTACK27 VLAN: Add host point intents between h1 h5 and h11 h21 - PASS (tick) 1000
  • 2000.4 1HOP8 VLAN: Add host point intents between h1 h5 and h3 h21 - PASS (tick)
  • 1000 2000.5 VLAN19 1HOP: Add vlan host point intents between h4 h1 and h12 h3 - PASS (tick) 1000
  • 2000.6 VLAN2: Add vlan host intents between h4 and h13 10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 1000.7 Encapsulation: Add host 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS (tick)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

...

Case 3000: Single to Multi Point Intents Test -

...

3 NODE(S) - OF 1.0 - Using Flow

...

Rules -

...

PASS

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

  • 2000 3000.1 NOOPTION: Add Install and test single point to multi point intents between h1 and h9 - PASS (tick) 2000
  • 3000.2 IPV4: Add Install and test single point to multi point intents between h1 and h9 - PASS (tick)
  • 2000 3000.3 IPV4_2: Add single point to multi point intents between h1 and h9 - PASS (tick) 2000
  • 3000.4 SDNIP-ICMPVLAN: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 single point to multi point intents - PASS (tick) 2000
  • 3000.6 DUALSTACK15 VLAN: Add single point to multi point intents between h3 and h11 - PASS (tick) 2000.7 VLAN: Add point intents between h5

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 and h21 - PASS (tick) 2000.8 VLAN: Add point intents between h5
  • and h21 4000.2 IPV4: Add multi point to single point intents - PASS (tick) 2000
  • .9 1HOP 4000.3 IPV4_2: Add multi point to single point intents between h1 and h3 - PASS (tick)
  • 2000 4000.10 4 VLAN: Add multi point to single point intents using VLAN Encapsulation - FAIL (error)
    • Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
    • Encapsulation intents check failed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • - PASS (tick)
  • 4000.5 VLAN: Add multi point to single point intents - PASS (tick)
  • 4000.6 ENCAPSULATION: Add multi point to single point intents 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS (tick)

Case

...

5000:

...

Test host mobility with host intents - 3 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 Objectives

  • 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 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick) 3000
  • 6000.2 IPV44 NOOPTION: Install and test single point to multi point intents with partial failures allowed - 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)

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 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

Case

...

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

Set up ONOS with 1 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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 - PASS

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

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

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

This test case will test point to point intents using 1 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.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 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - PASS (tick)

Case 3000: Single to Multi Point Intents Test - 1

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 - PASS (tick)

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 - 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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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)

...

NODE(S) - OF 1.0 - Using Flow Objectives - 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.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 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick) 1000
  • 3000.4 1HOP: Add host intents between h1 and h3 2 IPV4: Install and test single point to multi point intents - PASS (tick) 1000.5 VLAN1: Add vlan host intents between h4 and h12
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)
  • 1000 3000.6 VLAN24 VLAN: Add vlan host intents between h4 and h13 single point to multi point intents - PASS (tick) 1000
  • 3000.7 Encapsulation5 VLAN: Add host intents between h1 and h9 single point to multi point intents - PASS (tick)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

...

Case 4000: Multi To Single 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 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.0 OVS running in Mininet and compile intents using Flow Objectives

  • 2000 4000.1 NOOPTION: Add point intents between h1 and h9 multi point to single point intents - PASS (tick) 2000
  • 4000.2 IPV4: Add multi point to single point intents between h1 and h9 - PASS (tick) 2000
  • 4000.3 IPV4_2: Add multi point to single point intents between h1 and h9 - FAIL (error)- 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 - 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 - FAIL (error)
    • Assertion results for IPV4 multi to single with partial failures allowed
    • Assertion Result for IPV4 no mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000.5 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 Failed
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL (error)
    • Assertion Result for Dualstack1 IPV4 with mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping PassedLink Down Connectivity Check Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology Intent State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Down Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000.7 VLAN: Add point intents between h5 and h21 - FAIL (error)
    • Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down
    • Assertion Result for VLAN IPV4 with 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
    • 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 Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received PassedRecieved Failed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000 6000.8 VLAN: Add point intents between h5 and h21 3 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • Assertion Result results for VLAN IPV4 single to multi point intents with VLAN treatmentintent with no options set
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping 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
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology 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 Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000 6000.9 1HOP: Add point intents between h1 and h3 4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion Result results for 1HOP IPV4 with no mac address point intentssingle 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 Ping 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 Pingall 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 PassedFailed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 2000.10 Add point to point intents using VLAN Encapsulation - FAIL (error)
    • 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 FailedAfter removing intents Flow State Passed
  • 2000.11 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
    • After removing intents Flow State Passed

...

    • 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 (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 10: Start Mininet topology with OF 1.0 switches - PASS

Start mininet topology with OF 1.0 switches to test intents, exits out 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 -

...

PASS

This test case will test single point to multi point tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow ObjectivesOVS 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 - PASS (tick)
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for NOOPTION point intent
  • 3000.1 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 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 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
  • 3000.2 IPV4: Install and test single point to multi point intents - FAIL (error)
    • 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 Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 3000.3 IPV4_2: Add single point to multi point intents - FAIL (error)
    • 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
    • Initial Flow State Passed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Bad Recipient Ping PassedFailed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed
    • After removing intents Flow State Passed
  • 3000.4 VLAN: Add single point to multi point intents 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion results Result 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
    • Initial Flow State Passed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Bad Recipient Ping PassedFailed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed
  • 3000.5 VLAN 2000.3 IPV4_2: Add single point to multi point intents intents between h1 and h9 - FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatmentResult 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
    • Bad Sender Ping Passed
    • Bad Recipient Ping PassedFailed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

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 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion results for NOOPTION multi to single point intentResult for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Bad Sender Ping Passed
    • Bad Recipient Ping PassedFailed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall PassedFailed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received PassedRecieved Failed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed
  • 4000.2 IPV4 2000.5 SDNIP-TCP: Add multi point to single point intents between h1 and h9 - FAIL (error)
    • Assertion results Result for IPV4 multi to single point intent with IPV4 type and MAC addressesSDNIP-TCP IPV4 using ICMP point intents
    • Initial Iperf Failed
    • Remove Intents Passed
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - FAIL (error)
    • Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
    • Encapsulation intents check failedInstall 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 PassedFailed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter removing intents Flow State Passed
  • 4000.3 IPV4_2: Add multi point to single point intents 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL (error)
    • 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
    • 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 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
  • 4000.4 VLAN: Add multi point to single point intents - FAIL (error)
    • 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
    • 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 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
    • Result for BANDWIDTH ALLOCATION for point intent
    • Install Intent State Passed
    • Bandwidth Allocation check Failed
    • After removing intents Flow State Passed

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

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

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

  • 4000.1 NOOPTION 4000.5 VLAN: Add multi point to single point intents - FAIL (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • 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 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
  • 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 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 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
  • 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 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 - 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)
    • Assert result Assertion results for IPV4 host intent between h1, moved, and h9single 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 Ping Connectivity Check Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow Intent State Passed
    • Link Down Topology Flow 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 FailedAfter removing intents Flow State Passed

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 - 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 FailedAfter removing intents Flow State Passed
  • 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 FailedAfter removing intents Flow State 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 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 (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 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 (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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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)

...

    • 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 (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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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.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 - PASS

This test case tests Host 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

  • 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS (tick) 1000
  • 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS (tick) 1000
  • 4000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 multi point to single point intents - PASS (tick) 1000
  • 4000.4 1HOPVLAN: Add host intents between h1 and h3 multi point to single point intents - PASS (tick) 1000
  • 4000.5 VLAN1VLAN: Add vlan host intents between h4 and h12 multi point to single point intents - PASS (tick) 1000
  • 4000.6 VLAN2ENCAPSULATION: Add vlan host intents between h4 and h13 multi point to single point intents - PASS (tick)

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

...

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

...

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 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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.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)

...

- 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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

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

  • 4000 1000.1 NOOPTIONIPV4: Add multi point to single point intents host intents between h1 and h9 - PASS (tick) 4000
  • 1000.2 IPV4DUALSTACK1: Add multi point to single point intents host intents between h3 and h11 - PASS (tick) 4000
  • 1000.3 IPV4_2DUALSTACK2: Add multi point to single point intents host intents between h1 and h11 - PASS (tick) 4000
  • 1000.4 VLAN1HOP: Add multi point to single point intents host intents between h1 and h3 - PASS (tick) 4000
  • 1000.5 VLANVLAN1: Add multi point to single point intents vlan host intents between h4 and h12 - PASS (tick) 4000
  • 1000.6 ENCAPSULATIONVLAN2: Add multi point to single point intents - PASS (tick)

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

  • vlan host intents between h4 and h13 - PASS (tick)
  • 1000.7 Encapsulation
  • 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)
  • 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 6000.1 Installing Multi to Single Point intents with no options set - PASS (tick) 6000
  • 2000.2 Installing Multi to Single Point intents with partial failure allowed IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 6000 2000.3 NOOPTION: Install and test single point to multi point intents IPV4_2: Add point intents between h1 and h9 - PASS (tick) 6000
  • 2000.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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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)

...

  • SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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.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 tests Host 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
  • 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 h9 - 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 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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.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 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 (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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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 - PASS

This test case will test single point to multi point tests Host 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 RulesObjectives

  • 4000 1000.1 NOOPTIONIPV4: Add multi point to single point intents host intents between h1 and h9 - PASS (tick) 4000
  • 1000.2 IPV4DUALSTACK1: Add multi point to single point intents host intents between h3 and h11 - PASS (tick) 4000
  • 1000.3 IPV4_2DUALSTACK2: Add multi point to single point intents host intents between h1 and h11 - PASS (tick) 4000
  • 1000.4 VLAN1HOP: Add multi point to single point intents host intents between h1 and h3 - PASS (tick) 4000
  • 1000.5 VLANVLAN1: Add multi point to single point intents vlan host intents between h4 and h12 - PASS (tick) 4000
  • 1000.6 ENCAPSULATIONVLAN2: 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 vlan host intents between h4 and h13 - PASS (tick)
  • 5000 1000.2 IPV47 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

...

Objectives -

...

FAIL

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - FAIL (error)
    • Assertion Result for VLAN Encapsulation Point IntentInstall Intent State Passed
    • Encapsulation intents check Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.11 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.3 - Using Flow Objectives - PASS

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

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

  • 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 Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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)

...

Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

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

  • 1000 4000.1 IPV4NOOPTION: Add host intents between h1 and h9 multi point to single point intents - PASS (tick) 1000
  • 4000.2 DUALSTACK1IPV4: Add host intents between h3 and h11 multi point to single point intents - PASS (tick) 1000
  • 4000.3 DUALSTACK2IPV4_2: Add host intents between h1 and h11 multi point to single point intents - 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)
  • 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 - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4 1000.7 Encapsulation: Add host intents between h1 and h9 - PASS (tick) 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

Case

...

6000:

...

Test Multi to Single End Point Failure - 1 NODE(S) - OF 1.3 - Using Flow Objectives - FAIL

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

  • 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 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for NOOPTION point intentresults 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 Ping FailedLink Down Connectivity Check Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology Intent State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Down 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 (error)
    • 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
    • Assertion Result for IPV4 point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter FailedAfter removing intents Flow State Passed
  • 2000 6000.3 IPV4_2: Add point intents between h1 and h9 NOOPTION: Install and test single point to multi point intents - FAIL (error)
    • Assertion Result results for IPV4 no mac address point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
    • Initial Iperf Failed
    • Remove Intents Passed
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - FAIL (error)
    • 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
  • 2000.11 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
    • After removing intents Flow State Passed

...

    • single to multi point intent with no options set
    • After removing intents Flow State Passed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with partial failures allowed
    • After removing intents Flow State Passed

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet - PASS (tick)

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 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 - 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 (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 Objectives -

...

FAIL

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

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (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 - 1 NODE(S) - OF 1.3 - 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.3 - Using Flow Objectives - FAIL

intents using Flow Objectives

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • 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 Failed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.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
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Failed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.3 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
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Failed
    • Link Down Topology State Passed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Failed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - FAIL (error)
    • Assertion Result for Dualstack1 IPV4 with mac address point intents
  • 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 PassedLink Down Ping Passed
    • Link Down Passed
    • Link Down Intent State PassedFailed
    • 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 Down Topology State Passed
    • Link Up Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State FailedPassed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved FailedReceived Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation 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 setInstall 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 Connectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State PassedLink Down Connectivity Check
    • Initial Ping Passed
    • Isolation link Link Down PassedIsolation link
    • Link Down Intent State PassedFailed
    • Isolation link Link Down Flow State PassedIsolation
    • link Link Down Topology State Passed
    • Isolation link Down Connectivity Check Passed
    • Isolation link Down Connectivity Check Passed
    • Link Up Passed
    • Link Up Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed 2000.11 BANDWIDTH ALLOCATION: Checking bandwidth allocation for point intents between h1 and h9 - FAIL (error)
    • Assertion results for IPV4 single to multi Result for BANDWIDTH ALLOCATION for point intent with partial failures allowed
    • Install Intent State Passed
    • Bandwidth Allocation check Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Connectivity Check PassedLink Down Ping 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 PassedPartial failure isolation link Failed
    • Link Down Flow State Passed
    • Partial failure isolation link 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 Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State FailedPassed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved FailedReceived Passed
    • Remove Intents FailedAfter PassedAfter removing intents Flow State Passed

Case

...

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

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 Set up ONOS with 3 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out 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)

...

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 (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 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 (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 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.3 - Using Flow Objectives -

...

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 FailedAfter removing intents Flow State Passed
  • 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

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

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping FailedConnectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Link Up Intent State PassedLink Up
    • Partial failure isolation link Down Flow State Passed
    • Link Up 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 Scapy Packet Recieved Failed
    • Remove Intents PassedAfter removing intents Flow State Passed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)
  • 2000.10 Add point to point intents using VLAN Encapsulation - PASS (tick)
  • 2000.11 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.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 (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 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 (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 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.3 - Using Flow Objectives - PASS

    • 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 (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 FailedAfter removing intents Flow State Passed
  • 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 FailedAfter removing intents Flow State Passed
  • 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

...