Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
...
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 9417e13b3d9d764f9ec94691ef6d5c1ff902a3d8 commit b7a1f8e45597412a56ec4aa511e5bc333c4e06c4 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.Jian Li [pyguni@gmail.com]
AuthorDate: Wed Mar 1 17:11:52 2017 -0800Tue Sep 7 15:13:42 2021 +0900
Commit: Yuta HIGUCHI [y-higuchi@onlab.usJian Li [pyguni@gmail.com]
CommitDate: Thu Mar 2 02:23:17 2017 +0000
cosmetic fix for OpticalPathIntent
Case 1: Setting up test environment - PASS
Setup the test environment including installing ONOS, start ONOS.
- 1.1 Constructing test variables - No Result
- 1.2 Uninstalling ONOS package - PASS
- 1.3 Create cell file - No Result
- 1.4 Apply cell to environment - PASS
- 1.5 Creating ONOS package - PASS
- 1.6 Installing ONOS package - PASS
- 1.7 Set up ONOS secure SSH - PASS
- 1.8 Starting ONOS service - PASS
- 1.9 Starting ONOS CLI sessions - PASS
- 1.10 App Ids check - PASS
- 1.11 Install onos-ovsdb - PASS
- 1.12 Install onos-app-vtn - PASS
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
- 3.2 ovsdb node 2 set ovs manager to 10.128.20.11 - PASS
- 3.3 Check ovsdb node 1 manager is 10.128.20.11 - PASS
- 3.4 Check ovsdb node 2 manager is 10.128.20.11 - PASS
- 3.5 Check default br-int bridge on ovsdb node 10.128.10.11 - FAIL
- onos add default bridge on the node 1 failed
- 3.6 Check default br-int bridge on ovsdb node 10.128.20.11 - FAIL
- onos add default bridge on the node 2 failed
- 3.7 Check default vxlan port on ovsdb node 10.128.10.11 - FAIL
- onos add default vxlan port on the node 1 failed
- 3.8 Check default vxlan port on ovsdb node 10.128.20.11 - FAIL
- 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
- 4.2 ovsdb node 2 set ovs manager to 10.128.20.11 - PASS
- 4.3 Check ovsdb node 1 manager is 10.128.20.11 - PASS
- 4.4 Check ovsdb node 2 manager is 10.128.20.11 - PASS
- 4.5 Check ovsdb node 1 bridge br-int controller set to 10.128.20.11 - PASS
- 4.6 Check ovsdb node 2 bridge br-int controller set to 10.128.20.11 - PASS
- 4.7 Check onoscli devices have ovs 10.128.10.11 - PASS
- 4.8 Check onoscli devices have ovs 10.128.20.11 - PASS
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
- 2.2 Check ovsdb node manager is 10.128.20.11 - PASS
- 2.3 Delete ovsdb node manager - PASS
- 2.4 Check ovsdb node delete manager 10.128.20.11 - PASS
Case 5: - FAIL
Wed 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
Case 1: Starting up 5 node(s) ONOS cluster - FAIL
...