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 fbabea0a347db6570e5416d4b7084aac38f25115 2a62ef0a9f9dcf21e17c92bd524e635ea4893d98 (HEAD, origin/onos-1.75, onos-1.75)
Author: Yixiao Chen Changhoon Yoon [yixiaochyoon87@kaist.chen@huaweiac.comkr]
AuthorDate: Wed Sep 14 Jun 29 16:2334:24 38 2016 -0400+0900
Commit: Ray Milkey Jonathan Hart [ray@onlabjono@onlab.us]
CommitDate: Tue Oct 11 12:51:10 2016 -0700
[ONOS-4880][ONOS-5021]IETF TE Topology ProviderThu 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 Starting ONOS CLI sessions - PASS
1.9 App Ids check - No Result
- 1.10 9 Install onos-ovsdb 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
...
- 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