Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/2060/

...

HTML
<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/lastSuccessfulBuild/artifact/FUNCintentRest_master_20-builds_graph.jpg", alt="FUNCintentRest", style="width:525px;height:350px;border:0">

commit 132393a4a23dba0706fb6e19fb787561d83d69bc a3f16114904bff3c8e0a20640e9ea9ebf16d977b (HEAD, origin/master, origin/HEAD, master)
Author: Charles Chan Jordan Halterman [rascov@gmailjordan@opennetworking.comorg]
AuthorDate: Thu Jan 4 1411 09:2634:07 52 2018 -0800
Commit: Charles Chan Jordan Halterman [rascov@gmailjordan@opennetworking.comorg]
CommitDate: Tue Fri Jan 9 1312 00:5533:27 2018 -0800
CORD-2470 Fix NPEs+0000

[ONOS-7365] Fix NPE in ECM peersSupplier to avoid exceptions when rebooting container

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

...

  • 17.1 Enabling Flow Objectives - PASS (tick)

Case 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives -

...

FAIL

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

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS (tick)
  • FAIL (error)
    • Assertion result for IPV4 host intent with mac addresses
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.2 DUALSTACK1 1000.3 DUALSTACK2: Add host intents between h1 h3 and h11 - PASS (tick)FAIL (error)
    • Assertion Result for dualstack IPV4 with MAC addresses
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.3 DUALSTACK2 1000.4 1HOP: Add host intents between h1 and h3 h11 - PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

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

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV4: Add point intents between h1 and h9 - PASS (tick)
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - PASS (tick)
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - PASS (tick)
  • 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 1HOP: Add point intents between h1 and h3 - PASS (tick)

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

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

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

Case 5000: Test host mobility with host intents - 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 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 1 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

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

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

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

  • FAIL (error)
    • Assertion Result for dualstack2 host intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
    • Assertion Result for 1HOP for IPV4 same switch
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL (error)
    • Assertion Result vlan IPV4
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.6 Confirm that ONOS leadership is unchanged - FAIL (error)
    • ONOS Leader Mismatch

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
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents 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 Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.4 SDNIP-ICMP
  • 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 FAIL (error)
    • Assertion Result for SDNIP-ICMP
    : Add point intents between h1 and h9 - PASS (tick)
    • IPV4 using TCP point intents
    • Install Intent State Passed
    • Flow duration check failed
  • 2000.5 SDNIP-TCP: Add point intents between h1 and h9 - PASS (tick)- FAIL (error)
    • Assertion Result for SDNIP-TCP IPV4 using ICMP point intents
  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)FAIL (error)
    • Assertion Result for Dualstack1 IPV4 with mac address point intents
    • Install Intent State Failed
  • 2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)FAIL (error)
    • Assertion Result for VLAN IPV4 with mac address point intents
    • Install Intent State Failed
  • 2000.8 1HOP: Add point intents between h1 and h3 - PASS (tick)

...

  • FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Failed

Case 3000: Single to Multi 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 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 0 OVS running in Mininet and compile intents using Flow RulesObjectives

  • 3000.1 NOOPTION: Install and test single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents -

...

FAIL

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)FAIL (error)
    • Mobility: Failed to move h1 to s6 to single point intents with IPV4 type and MAC addresses in the same VLAN
  • 5000.2 IPV4: Add host intents between h1 and h9 - PASS (tick)FAIL (error)
    • Assert result for IPV4 host intent between h1, moved, and h9
    • Install Intent 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

...

1 node(s) ONOS cluster - PASS

Set up ONOS with 3 1 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 1000: Host Intents Test -

...

1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

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

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

Case 2000: Point Intents Test -

...

1 NODE(S) - OF 1.3 - Using Flow Rules - PASS

This test case will test point to point intents using 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 RulesFlow 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 - PASS (tick)
  • 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 1HOP: Add point intents between h1 and h3 - 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 5000: Test host mobility with host intents - 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 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

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

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

  • 1000.1 IPV4: Add and test host intents between h1 and h9 - FAIL (error)
    • Assertion result for IPV4 host intent with mac addresses
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • Assertion Result for dualstack IPV4 with MAC addresses
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL (error)
    • Assertion Result for dualstack2 host intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
    • Assertion Result for 1HOP for IPV4 same switch
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL (error)
    • Assertion Result vlan IPV4
    • 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 Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Pingall Passed
    • Remove Intents Passed
  • 1000.6 Confirm that ONOS leadership is unchanged - FAIL (error)
    • ONOS Leader Mismatch

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 - 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 Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 point intent
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents 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 Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents 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 Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.5 SDNIP-TCP 2000.1 NOOPTION: Add point intents between h1 and h9 - PASS (tick)
  • 2000.2 IPV46 DUALSTACK1: 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 - PASS (tick)
  • 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)
  • 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 Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Failed
    • Link Down Pingall Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 2000.7 VLAN: Add point intents between h5 and h21 - FAIL (error)
    • Assertion Result for VLAN IPV4 with mac address point intents
    • Install Intent State Failed
    2000.7 VLAN: Add point intents between h5 and h21 - PASS (tick)
  • 2000.8 1HOP: Add point intents between h1 and h3 - PASS (tick)FAIL (error)
    • Assertion Result for 1HOP IPV4 with no mac address point intents
    • Install Intent State Failed

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

...

FAIL

This test case will test single point to multi point intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.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)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
  • 3000.2 IPV4: Install and test single point to multi point intents - PASS (tick)FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses
  • 3000.3 IPV4_2: Add single point to multi point intents - PASS (tick)intents - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and no MAC addresses
  • 3000.4 VLAN: Add single point to multi point intents - PASS (tick)
  • 3000.5 VLAN: Add single point to multi point intents - PASS (tick)

Case 5000: Test host mobility with host intents - 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 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 1 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 17: Enable intent compilation using Flow Objectives - PASS

  • 17.1 Enabling Flow Objectives - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

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

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

...

  • FAIL (error)
    • Assertion results for IPV4 single to multi point intent with IPV4 type and MAC addresses in the same VLAN
  • 3000.5 VLAN: Add single point to multi point intents - FAIL (error)
    • Assertion results for single to multi point intent with VLAN treatment

Case 5000: Test host mobility with host intents - FAIL

  • 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000.2 IPV4: Add host intents between h1 and h9 - FAIL (error)
    • Assert result for IPV4 host intent between h1, moved, and h9
    • Install Intent State 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 1 node(s) ONOS cluster - PASS

Set up ONOS with 1 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 17: Enable intent compilation using Flow Objectives - PASS

  • 17.1 Enabling Flow Objectives - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Objectives - PASS

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

  • 2000 1000.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 : Add and test host intents between h1 and h9 - PASS (tick) 2000.5 SDNIP-TCP
  • 1000.2 DUALSTACK1: Add point host intents between h1 h3 and h9 h11 - PASS (tick) 2000
  • 1000.6 DUALSTACK13 DUALSTACK2: Add point host intents between h3 h1 and h11 - PASS (tick)
  • 2000 1000.7 VLAN4 1HOP: Add point host intents between h5 h1 and h21 h3 - PASS (tick) 2000
  • 1000.8 1HOP5 VLAN1: Add point vlan host intents between h1 and h3 h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

Case

...

2000:

...

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 2000.1 NOOPTION: Install and test single point to multi point intents Add point intents between h1 and h9 - PASS (tick) 3000
  • 2000.2 IPV4: Install and test single point to multi : Add point intents between h1 and h9 - PASS (tick)
  • 3000 2000.3 IPV4_2: Add single point to multi point intents between h1 and h9 - PASS (tick) 3000
  • 2000.4 VLANSDNIP-ICMP: Add single point to multi point intents between h1 and h9 - PASS (tick) 3000
  • 2000.5 VLANSDNIP-TCP: Add single point to multi point intents intents between h1 and h9 - PASS (tick)

Case 5000: Test host mobility with host intents - PASS

  • 2000.6 DUALSTACK1: Add point intents between h3 and h11 - PASS (tick)
  • 2000.7 VLAN: Add point intents between h5 and h21 5000.1 Testing host mobility by moving h1 from s5 to s6 - PASS (tick)
  • 5000 2000.2 IPV48 1HOP: Add host point intents between h1 and h9 h3 - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 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 and test 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 Confirm that ONOS leadership is unchanged - PASS (tick)

...

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 5000: Test host mobility with host intents - 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 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

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

Case 19: Copy karaf logs - PASS

Copying the karaf logs to preserve them throughreinstalling ONOS

  • 19.1 Copying karaf logs - PASS (tick)

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

Set up ONOS with 3 node(s) ONOS cluster

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

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

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

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

  • 13.1 Create scapy components - No Result (warning)
  • 13.2 Start scapy components - PASS (tick)

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

Case 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 will test point to point tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.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 1000.1 IPV4: Add and test host intents between h1 and h9 - PASS (tick) 2000.5 SDNIP-TCP
  • 1000.2 DUALSTACK1: Add point host intents between h1 h3 and h9 h11 - PASS (tick) 2000
  • 1000.6 DUALSTACK13 DUALSTACK2: Add point host intents between h3 h1 and h11 - PASS (tick)
  • 2000 1000.7 VLAN4 1HOP: Add point host intents between h5 h1 and h21 h3 - PASS (tick) 2000
  • 1000.8 1HOP5 VLAN1: Add point vlan host intents between h1 and h3 h4 and h12 - PASS (tick)
  • 1000.6 Confirm that ONOS leadership is unchanged - PASS (tick)

Case

...

2000:

...

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 2000.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
    • 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 Failed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Failed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 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 - FAIL (error)
  • Assertion results for single to multi point intent with VLAN treatment
  • 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 Failed
  • Link Down Pingall Failed
  • Link Up Passed
  • Link Up Intent State Passed
  • Link Up Flow State Passed
  • Link Up Topology State Failed
  • Link Up Scapy Packet Received Passed
  • Remove Intents Passed
  • 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 - PASS (tick)
  • 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 1HOP: Add point intents between h1 and h3 - 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 5000: Test host mobility with host intents - 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)

...