Page tree

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

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 219 Next »

FUNCovsdbtest at 23 Mar 2017 11:26:53

commit d1172636d135ada46a1d690e9533b24dee0ceb7b (HEAD, origin/master, origin/HEAD, master)
Author: Charles Chan [rascov@gmail.com]
AuthorDate: Wed Mar 15 17:33:09 2017 -0700
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Wed Mar 22 20:55:07 2017 +0000

CORD-810 Remove VLAN extension selector from OFDPA 3

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 Set up ONOS secure SSH - PASS (tick)
  • 1.8 Starting ONOS service - 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