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 21c14018a65fc32dda46fe8ef651b175f142ba0c 58c6af2321f25601325fa62961d389b8b8351ad6 (HEAD, origin/master, origin/HEAD, master)
Author: Michele Santuari Ray Milkey [michele.santuari@create-net.orgray@onlab.us]
AuthorDate: Mon Tue Nov 14 1322 17:3126:33 52 2016 +0100-0800
Commit: Gerrit Code Review [gerrit@onlabRay Milkey [ray@onlab.us]
CommitDate: Mon Tue Nov 21 2122 17:3826:56 52 2016 +0000
Juniper driver for netconf-0800
Starting snapshot 1.8.0-SNAPSHOT
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 Starting ONOS service - PASS
- 1.8 Set up ONOS secure SSH - 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
- 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