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

FUNCovsdbtest at 08 Mar 2017 23:47:21

commit 75a1c40849db079c005ef9b19368d810071daea5 (HEAD, origin/onos-1.8, onos-1.8)
Author: Ray Milkey [ray@onlab.us]
AuthorDate: Wed Mar 8 15:50:27 2017 -0800
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Wed Mar 8 15:50:27 2017 -0800

Snapshot reference fix

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, start ONOS.

  • 1.1 Constructing test variables - No Result (warning)
  • 1.2 Uninstalling ONOS package - PASS (tick)
  • 1.3 Create cell file - No Result (warning)
  • 1.4 Apply cell to environment - PASS (tick)
  • 1.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing ONOS package - PASS (tick)
  • 1.7 Starting ONOS service - PASS (tick)
  • 1.8 Set up ONOS secure SSH - PASS (tick)
  • 1.9 Starting ONOS CLI sessions - PASS (tick)
  • 1.10 App Ids check - PASS (tick)
  • 1.11 Install onos-ovsdb - PASS (tick)
  • 1.12 Install onos-app-vtn - PASS (tick)

Case 3: Test default br-int configuration and vxlan port - FAIL

onos create default br-int bridge and vxlan port on the ovsdb node

  • 3.1 ovsdb node 1 set ovs manager to 10.128.20.11 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.128.20.11 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.128.20.11 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.128.20.11 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.128.10.11 - FAIL (error)
    • onos add default bridge on the node 1 failed
  • 3.6 Check default br-int bridge on ovsdb node 10.128.20.11 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • 3.7 Check default vxlan port on ovsdb node 10.128.10.11 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 3.8 Check default vxlan port on ovsdb node 10.128.20.11 - FAIL (error)
    • onos add default vxlan port on the node 2 failed

Case 4: - PASS

  • 4.1 ovsdb node 1 set ovs manager to 10.128.20.11 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.128.20.11 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.128.20.11 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.128.20.11 - PASS (tick)
  • 4.5 Check ovsdb node 1 bridge br-int controller set to 10.128.20.11 - PASS (tick)
  • 4.6 Check ovsdb node 2 bridge br-int controller set to 10.128.20.11 - PASS (tick)
  • 4.7 Check onoscli devices have ovs 10.128.10.11 - PASS (tick)
  • 4.8 Check onoscli devices have ovs 10.128.20.11 - PASS (tick)

Case 2: Test ovsdb connection and teardown - PASS

Test ovsdb connection create and delete over ovsdb node and onos node

  • 2.1 Set ovsdb node manager - PASS (tick)
  • 2.2 Check ovsdb node manager is 10.128.20.11 - PASS (tick)
  • 2.3 Delete ovsdb node manager - PASS (tick)
  • 2.4 Check ovsdb node delete manager 10.128.20.11 - PASS (tick)

Case 5: - FAIL

  • 5.1 ovsdb node 1 set ovs manager to onos - PASS (tick)
  • 5.2 Check ovsdb node 1 manager is 10.128.20.11 - PASS (tick)
  • 5.3 Check ovsdb node 1 bridge br-int default flows on 10.128.10.11 - FAIL (error)
  • No labels