Versions Compared

Old Version 41

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 42

changes.mady.by.user Jenkins Technical User

Saved on

Key

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

...

commit f91909f490c822d8f9a90a830bec6131a941c786 6a306f2145977472ab373ee9b3402aee8295fd8d (HEAD, origin/onos-1.6, onos-1.6)
Author: Kavitha Alagesan Changhoon Yoon [kalagesa@partnerchyoon87@kaist.cienaac.comkr]
AuthorDate: Wed Jun 15 14:26:04 2016 +0530Fri Jul 8 22:27:09 2016 +0900
Commit: Kavitha Alagesan [kalagesa@partner.ciena.comGerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Tue Aug 4 119 00:5305:20 2016 +0530
Fix for wipe-out please command ONOS-46530000

ONOS-4507,ONOS-4774, ONOS-4775, ONOS-4776 + some minor fixes

Case 1: Constructing test variables and building ONOS package - 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 - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options setpartial failures allowed
    • 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 FailedPassed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down PassedIsolation
    • Partial failure isolation link Down Intent State PassedFailed
    • Isolation Partial failure isolation link Down Flow State Passed
    • Isolation Partial failure isolation link Down Topology State Passed
    • Isolation Partial failure isolation link Down Connectivity Check PassedIsolation
    • Partial failure isolation link Down Connectivity Check PassedFailed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with partial failures allowed
    • 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 Failed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Intent State Failed
    • Partial failure isolation link Down Flow State Passed
    • Partial failure isolation link Down Topology State Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Partial failure isolation link Down Connectivity Check Failed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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 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 Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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 Case 1000: Host Intents Test - 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 - FAIL (error)
    • Assertion results for IPV4 single to multi to single point intent end point failure with no options set
    • 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 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 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 Passed
  • 6000.2 Installing Multi to Single Point intents with partial failure allowed - PASS (tick) 6000.3 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 no options setpartial failures allowed
    • 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 FailedPassed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down PassedIsolation
    • Partial failure isolation link Down Intent State PassedFailed
    • Isolation Partial failure isolation link Down Flow State Passed
    • Isolation Partial failure isolation link Down Topology State Passed
    • Isolation Partial failure isolation link Down Connectivity Check PassedIsolation
    • Partial failure isolation link Down Connectivity Check PassedFailed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with partial failures allowed
    • 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 Failed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Intent State Failed
    • Partial failure isolation link Down Flow State Passed
    • Partial failure isolation link Down Topology State Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Partial failure isolation link Down Connectivity Check Failed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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 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 Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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 tests Host intents using 3 node(s) cluster; Different type of hosts will be tested in each step such as IPV4, Dual stack, VLAN etc; The test will use OF 1.0 OVS running in Mininet and compile intents using Flow Objectives

  • 1000.1 IPV4: Add host intents between h1 and h9 - PASS (tick)
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - PASS (tick)
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - PASS (tick)
  • 1000.4 1HOP: Add host intents between h1 and h3 - PASS (tick)
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - PASS (tick)
  • 1000.6 VLAN2: Add vlan host intents between h4 and h13 - PASS (tick)
  • 1000.7 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 tests Host 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

  • 1000 2000.1 IPV4NOOPTION: Add host point intents between h1 and h9 - PASS (tick) 1000
  • 2000.2 DUALSTACK1IPV4: Add host point intents between h3 h1 and h11 h9 - PASS (tick) 1000
  • 2000.3 DUALSTACK2IPV4_2: Add host point intents between h1 and h11 h9 - PASS (tick)
  • 1000 2000.4 1HOPSDNIP-ICMP: Add host point intents between h1 and h3 h9 - PASS (tick)
  • 1000 2000.5 VLAN1SDNIP-TCP: Add vlan host point intents between h4 h1 and h12 h9 - PASS (tick) 1000
  • 2000.6 VLAN2DUALSTACK1: Add vlan host point intents between h4 h3 and h13 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 1000.7 Confirm that ONOS leadership is unchanged - 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

  • 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 intents between h1 and h9 to multi point intents - PASS (tick) 2000
  • 3000.4 SDNIP-ICMPVLAN: Add single point to multi 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 3000.5 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 single point to multi point intents - PASS (tick)

Case

...

4000: Multi To Single

...

Point Intents Test - 3 NODE(S) - OF 1.0 - Using Flow Objectives -

...

FAIL

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

  • 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - PASS (tick) 3000
  • 4000.2 IPV4: Install and test single Add multi point to multi single point intents - PASS (tick)
  • 3000 4000.3 IPV4_2: Add single multi point to multi single point intents - PASS (tick)
  • 3000 4000.4 VLAN: Add single multi point to multi single point intents - PASS (tick) 3000
  • 4000.5 VLAN: Add single multi point to multi single point intents - PASS (tick)

...

  • - FAIL

...

  • (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • Initial Intent State Passed

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 4000.2 IPV4: Add multi point to single point intents - PASS (tick)
  • 4000.3 IPV4_2: Add multi point to single point intents - PASS (tick)
  • 4000.4 VLAN: Add multi point to single point intents - PASS (tick)
  • 4000.5 VLAN: Add multi point to single point intents - FAIL (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed

...

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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components 6000.3 NOOPTION: Install and test single point to multi point intents - PASS (tick)
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with partial failures allowed
    • 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 Failed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Intent State Failed
    • Partial failure isolation link Down Flow State Passed
    • Partial failure isolation link Down Topology State Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Partial failure isolation link Down Connectivity Check Failed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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)

...

  • 18.2 Stopping Mininet Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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 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 tests Host 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

  • 1000 2000.1 IPV4NOOPTION: Add host point intents between h1 and h9 - PASS (tick) 1000
  • 2000.2 DUALSTACK1IPV4: Add host point intents between h3 h1 and h11 h9 - PASS (tick) 1000
  • 2000.3 DUALSTACK2IPV4_2: Add host point intents between h1 and h11 h9 - PASS (tick)
  • 1000 2000.4 1HOPSDNIP-ICMP: Add host point intents between h1 and h3 h9 - PASS (tick)
  • 1000 2000.5 VLAN1SDNIP-TCP: Add vlan host point intents between h4 h1 and h12 h9 - PASS (tick) 1000
  • 2000.6 VLAN2DUALSTACK1: Add vlan host point intents between h4 h3 and h13 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 1000.7 Confirm that ONOS leadership is unchanged - 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

  • 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 intents between h1 and h9 to multi point intents - PASS (tick) 2000
  • 3000.4 SDNIP-ICMPVLAN: Add single point intents between h1 and h9 to multi point intents - 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 3000.5 VLAN: Add point intents between h5 and h21 - PASS (tick) 2000.8 VLAN: Add point intents between h5 and h21 single point to multi point intents - PASS (tick)
  • 2000.9 1HOP: Add point intents between h1 and h3 - PASS (tick)

...

Case 4000: Multi To Single Point Intents Test - 1 NODE(S) - OF 1.3 - Using Flow Rules -

...

FAIL

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

  • 3000 4000.1 NOOPTION: Install and test single Add multi point to multi single point intents - PASS (tick) 3000
  • 4000.2 IPV4: Install and test single Add multi point to multi single point intents - PASS (tick)
  • 3000 4000.3 IPV4_2: Add single multi point to multi single point intents - PASS (tick)
  • 3000 4000.4 VLAN: Add single multi point to multi single point intents - PASS (tick) 3000
  • 4000.5 VLAN: Add single multi point to multi single point intents - PASS (tick)

...

  • -

...

  • FAIL

...

  • (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed

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

  • 4000.1 NOOPTION: Add multi point to single point intents - PASS (tick)
  • 4000.2 IPV4: Add multi point to single point intents - PASS (tick)
  • 4000.3 IPV4_2: Add multi point to single point intents - PASS (tick)
  • 4000.4 VLAN: Add multi point to single point intents - PASS (tick)
  • 4000.5 VLAN: Add multi point to single point intents - FAIL (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed

...

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

Case 18: Stop Mininet and Scapy - PASS

Stopping the current mininet topology to start up fresh

  • 18.1 Stopping and Removing Scapy Host Components - PASS (tick)
  • 18.2 Stopping Mininet Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - 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

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 Topology - 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 Uninstalling ONOS package - PASS (tick)
  • 2.2 Apply cell to environment - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)
  • 2.6 Start ONOS cli - PASS (tick)

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

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

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

Case 12: Assign switches to controllers - PASS

Assign OF 1.3 switches to ONOS nodes

  • 12.1 Assigning switches to controllers - PASS (tick)

Case 13: Create scapy components - PASS

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

Case 15: Discover all hosts using scapy - PASS

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

Case 16: Balance mastership of switches - PASS

  • 16.1 Balancing mastership of switches - PASS (tick)

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

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

...

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

Case 18: Stop Mininet and Scapy - 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 Objectivestested 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 - FAIL (error)
    • Assertion results for multi to single point intent with VLAN ID treatment
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Bad Recipient Ping Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • Link Down Pingall Failed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Recieved Failed
    • Remove Intents Passed

Case 5000: Test host mobility with host intents - 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 - 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
  • 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 - FAIL (error)
    • Assertion results for IPV4 multi to single point intent with VLAN ID treatmentwith partial failures allowed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Ping Failed
    • Bad Sender Ping Passed
    • Connectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Bad Recipient Ping 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
    • Link Down Flow State Passed
    • Link Down Topology State Passed
    • 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 PassedLink 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 FailedReceived Passed
    • Remove Intents Passed

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 6000: Test Multi to Single End Point Failure - 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 - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with no options set
    • 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 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 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 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
    • 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 FailedPassed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation link Down Intent State Failed
    • Partial failure isolation link Down Flow State Passed
    • Partial failure isolation link Down Topology State Passed
    • Partial failure isolation link Down Connectivity Check Passed
    • Partial failure isolation link Down Connectivity Check Failed
    • Link Up Passed
    • Link Up Passed
    • Link Up Passed
    • Link Up Intent State Passed
    • Link Up Flow State Passed
    • Link Up Topology State Passed
    • Link Up Scapy Packet Received Passed
    • Remove Intents Passed

...