Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCovsdbtest_master_20-builds_graph.jpg", alt="FUNCovsdbtest", style="width:525px;height:350px;border:0">

commit 080969a3c185dcac06e0f74a91c9f6e2455616bc 9417e13b3d9d764f9ec94691ef6d5c1ff902a3d8 (HEAD -] master, origin/master, origin/HEAD, master)
Author: Carmelo Cascone Jian Li [carmelo@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Tue Aug 27 16:06:55 2019 -0700Sep 7 15:13:42 2021 +0900
Commit: Andrea Campanella Jian Li [andrea@opennetworkingpyguni@gmail.orgcom]
CommitDate: Tue Oct 1 09:56:51 2019 +0000
Simplify packet i/o trace logging for P4RuntimeWed Sep 8 00:55:09 2021 +0000

Support to inject controller IP address to API config for tenant NW
--
(cherry picked from commit 0a05d6fe81c13ddffa4aba674d33103df8e5121b)

Case 1: Starting up

...

5 node(s) ONOS cluster

...

-

...

FAIL

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

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

Case

...

1

...

  • sudo ovs-vsctl show
  • 69d75e74-ec31-40a6-9908-c1fc20d9faab
  • is_connected: true
  • sdn@new-prod-test-station:~$

...

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.192.19.231 - PASS (tick)
  • 2.3 Delete ovsdb node manager - PASS (tick)
  • 2.4 Check ovsdb node delete manager 10.192.19.231 - 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.192.19.231 - PASS (tick)
  • 5.3 Check ovsdb node 1 bridge br-int default flows on 10.192.19.229 - FAIL (error)

Case 6: Configure Network Subnet Port - PASS

Configure Network Subnet Port Verify post is OK

  • 6.1 Generate Post Data - No Result (warning)
  • 6.2 Post Network Data via HTTP(Post port need post network) - PASS (tick)
  • 6.3 Post Subnet Data via HTTP(Post port need post subnet) - PASS (tick)
  • 6.4 Post Port1 Data via HTTP - PASS (tick)
  • 6.5 Post Port2 Data via HTTP - PASS (tick)

Case 7: - FAIL

  • 7.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS (tick)
  • 7.3 Create host1 on node 1 10.192.19.229 - PASS (tick)
  • 7.4 Create host2 on node 2 10.192.19.231 - PASS (tick)
  • 7.5 Create port on host1 on the node 10.192.19.229 - PASS (tick)
  • 7.6 Create port on host2 on the node 10.192.19.231 - PASS (tick)
  • 7.7 Add port to ovs br-int and host go-online on the node 10.192.19.229 - PASS (tick)
  • 7.8 Add port to ovs br-int and host go-online on the node 10.192.19.231 - PASS (tick)
  • 7.9 Check onos set host flows on the node 10.192.19.229 - FAIL (error)
  • 7.10 Check onos set host flows on the node 10.192.19.231 - PASS (tick)
  • 7.11 Check hosts can ping each other - FAIL (error)

Case 8: - FAIL

...

: Starting up 5 node(s) ONOS cluster - FAIL