Versions Compared

Old Version 436

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 437

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

...

commit cd64e899e9a7c09b1c96a33efbb706d90ee11846 61d9ea9dd50355f6c2ca012420ba7264fb0e5e78 (HEAD, origin/master, origin/HEAD, master)
Author: Pier Ventre Jian Li [pierventre@hotmailpyguni@gmail.com]
AuthorDate: Mon Oct 24 1331 00:1541:48 09 2016 -0700+0900
Commit: Brian O'Connor [bocon@onlab.usJian Li [pyguni@gmail.com]
CommitDate: Sat Mon Oct 29 0131 00:3641:09 2016 +0000
Bumping openflowj version to 0.9.7.onos0900

Add onos-lisp-msg into app.xml and features.xml

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 - FAIL (error)
    • Assertion results for IPV4 multi to single with partial failures allowedpoint 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 Failed
    • Link Down Topology State Passed
    • Link Down Connectivity Check Passed
    • Isolation link Down Passed
    • Partial failure isolation Isolation link Down Intent State PassedPartial failure isolation
    • Isolation link Down Flow State Passed
    • Partial failure isolation Isolation link Down Topology State Passed
    • Partial failure isolation Isolation link Down Connectivity Check PassedPartial failure isolation
    • 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 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 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
  • PASS (tick)
  • 6000.4 NOOPTION: Install and test single point to multi point intents with partial failures allowed - FAIL (error)
    • Assertion results for IPV4 single to multi point intent with partial failures allowed
    • Install Intent State Passed
    • Flow duration check Passed
    • Initial Intent State Passed
    • Initial Flow State Passed
    • Initial Connectivity Check Passed
    • Link Down Passed
    • Link Down Passed
    • Link Down Intent State Passed
    • Link Down Flow State 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

...

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 1000: Host Intents Test - 3 NODE(S) - OF 1.0 - 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.0 OVS running in Mininet and compile intents using Flow Rules

  • 1000.1 IPV4: Add host intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 host intent with mac addresses
    • Install Intent State Failed
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • Assertion Result for dualstack IPV4 with MAC addresses
    • Install Intent State Failed
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL (error)
    • Assertion Result for dualstack2 host intent
    • Install Intent State Failed
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
    • Assertion Result for 1HOP for IPV4 same switch
    • Install Intent State Failed
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL (error)
    • Assertion Result vlan IPV4
    • Install Intent State Failed
  • 1000.6 VLAN2: Add vlan host intents between h4 and h13 - FAIL (error)
    • Assertion Result vlan IPV4
    • Install Intent State Failed
  • 1000.7 Encapsulation: Add host intents between h1 and h9 - FAIL (error)
    • Assertion Result for VLAN Encapsulated host intent
    • Install Intent State Failed
  • 1000.8 Confirm that ONOS leadership is unchanged - PASS (tick)

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

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for NOOPTION point intent
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 point intent
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for IPV4 no mac address point intents
  • 2000.4 SDNIP-ICMP: Add point intents between h1 and h9 - FAIL (error)
    • Assertion Result for SDNIP-ICMP IPV4 using TCP point intents