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 844ee05c78fa96d0b907629221a99d6ac5f741b4 0f2977060214275c58a1b17ff72d31a52d0dc79a (HEAD, origin/master, origin/HEAD, master)
Author: Priyanka B Viswanath KSP [priyankakspviswa.b@huaweigithub@gmail.com]
AuthorDate: Tue Sat Aug 16 1213 18:1202:19 43 2016 +0530
Commit: Priyanka B Simon Hunt [priyankasimon@onlab.b@huawei.comus]
CommitDate: Tue Aug 16 1215:1248:30 40 2016 +0530
cherry pick [ONOS-5002] [ONOS-4986] defect fix in release bandwidth to master-0700
Adding first set of changes for bug onos-5071
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 - No Result FAIL
- Something is wrong with app Ids
- 1.10 Install onos-ovsdatabase - PASS - FAIL
- Install onos-ovsdatabase failed
- 1.11 Install onos-app-vtnrsc - FAIL
- Install onos-app-vtnrsc failed
- 1.12 Install onos-app-vtn - PASS - FAIL
- Install onos-app-vtn failed
- 1.13 Install onos-app-vtnweb - FAIL
- Install onos-app-vtnweb failed
...
- 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
- 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: -
...
FAIL
- 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 FAIL
- 4.8 Check onoscli devices have ovs 10.128.20.11 - PASS FAIL
Case 2: Test ovsdb connection and teardown - PASS
...