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.
...
...
Case 1: Setting up test environment - PASS
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 Install onos-ovsdb - PASS
- 1.11 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
...
- onos add default bridge on the node 1 failed
...
- onos add default bridge on the node 2 failed
...
- onos add default vxlan port on the node 1 failed
...
- 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
...