Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

FUNCintent at 29 Jul 2015 11:29:26

commit 9f1600aa53c483b600671bd0c572b5c1f5158626 (HEAD, origin/master, origin/HEAD, master)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Tue Jul 28 13:58:31 2015 -0700
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Wed Jul 29 09:26:46 2015 -0700

Use isConnected rather than isWriteable to detemine if we can send to switch

Case 1: Constructing test variables and building ONOS package - PASS

This test case is mainly for loading from params file, and pull and build the latest ONOS package

  • 1.1 Constructing test variables - 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 Creating ONOS package - PASS (tick)
  • 2.3 Uninstalling 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 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology elements between Mininet and ONOS

  • 8.1 Gathering topology information - No Result (warning)
  • 8.2 Conmparing MN topology to ONOS topology - PASS (tick)

Case 13: Discover all hosts - PASS

  • 13.1 Discover all hosts using pingall - PASS (tick)

Case 1000: Host Intents Test - 1 NODE(S) - OF 1.0 - FAIL

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

  • 1000.1 IPV4: Add host intents between h1 and h9 - FAIL (error)
    • IPV4: Host intent test failed between two IPV4 hosts
  • 1000.2 DUALSTACK1: Add host intents between h3 and h11 - FAIL (error)
    • DUALSTACK: Host intent test failed between twodual stack host using IPV4
  • 1000.3 DUALSTACK2: Add host intents between h1 and h11 - FAIL (error)
    • DUALSTACK2: Host intent test failed between twodual stack host using IPV4
  • 1000.4 1HOP: Add host intents between h1 and h3 - FAIL (error)
    • 1HOP: Host intent test failed between twohost using IPV4 in the same switch
  • 1000.5 VLAN1: Add vlan host intents between h4 and h12 - FAIL (error)
    • VLAN1: Host intent test failed between twohost using IPV4 in the same VLAN
  • 1000.6 VLAN2: Add inter vlan host intents between h13 and h20 - PASS (tick)

Case 2000: Point Intents Test - 1 NODE(S) - OF 1.0 - No Result

  • 2000.1 NOOPTION: Add point intents between h1 and h9 - FAIL (error)
    • NOOPTION: Point intent test failed using no match action
  • 2000.2 IPV4: Add point intents between h1 and h9 - FAIL (error)
    • IPV4: Point intent test failed using IPV4 type with MAC addresses
  • 2000.3 IPV4_2: Add point intents between h1 and h9 - FAIL (error)
    • IPV4_2: Point intent test failed using IPV4 type with no MAC addresses
  • 2000.4 SDNIP-TCP: Add point intents between h1 and h9 - FAIL (error)
    • SDNIP-TCP: Point intent test failed using IPV4 type with IP protocol TCP enabled
  • No labels