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.
...
commit 0f2977060214275c58a1b17ff72d31a52d0dc79a 07e31cf54da691398144d2eae0f250344a998539 (HEAD, origin/master, origin/HEAD, master)
Author: Viswanath KSP Sho SHIMIZU [kspviswasshimizu@us.github@gmailfujitsu.com]
AuthorDate: Sat Mon Aug 13 1815 11:0246:43 38 2016 +0530-0700
Commit: Simon Hunt [simon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Wed Aug 17 16 15:4837:40 19 2016 -0700
Adding first set of changes for bug onos-5071+0000
Remove public from definition in interface
Case 1: Setting up test environment - FAIL
...
- 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 Starting ONOS CLI sessions - PASS
- 1.9 App Ids check - FAIL
- Something is wrong with app Ids
- 1.10 Install onos-ovsdatabase - FAIL
- Install onos-ovsdatabase failed
- PASS
- 1.11 Install onos-app-vtnrsc - FAIL Install onos-app- vtnrsc failed
- 1.12 Install onos-app-vtn - FAIL
- Install onos-app-vtn failed
- 1.13 Install onos-app-vtnweb - FAIL
- Install onos-app-vtnweb failed
- vtn - PASS
Case 3: Test default br-int configuration and vxlan port - FAIL
...
- 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 - PASS
- 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 - FAIL PASS
- 4.8 Check onoscli devices have ovs 10.128.20.11 - FAIL PASS
Case 2: Test ovsdb connection and teardown - PASS
...