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.
FUNCovsdbtest at 01 Jan 2017 12:47:14
commit 2a62ef0a9f9dcf21e17c92bd524e635ea4893d98 (HEAD, origin/onos-1.5, onos-1.5)
Author: Changhoon Yoon [chyoon87@kaist.ac.kr]
AuthorDate: Wed Jun 29 16:34:38 2016 +0900
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Thu Aug 4 00:29:41 2016 +0000
ONOS-4774, ONOS-4775, ONOS-4776 + some minor fixes
Case 1: Setting up test environment - FAIL
Setup the test environment including installing ONOS, start ONOS.
- 1.1 Create cell file - No Result
- 1.2 Applying cell variable to environment - No Result
- 1.3 Git checkout and pullmaster - No Result
- 1.4 Using mvn clean install - PASS
- 1.5 Creating ONOS package - PASS
- 1.6 Installing ONOS package - PASS
- 1.7 Checking if ONOS is up yet - PASS
- 1.8 App Ids check - No Result
- 1.9 Install onos-ovsdatabase - PASS
- 1.10 Install onos-app-vtnrsc - FAIL
- Install onos-app-vtnrsc failed
- 1.11 Install onos-app-vtn - PASS
- 1.12 Install onos-app-vtnweb - FAIL
- Install onos-app-vtnweb failed
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
- 5.1 ovsdb node 1 set ovs manager to onos - PASS
- 5.2 Check ovsdb node 1 manager is 10.128.20.11 - PASS
- 5.3 Check ovsdb node 1 bridge br-int default flows on 10.128.10.11 - FAIL