Page History

...

commit 1b0a39af06ca7f1c7979ad247570b4d0482cf165 7fbb9b39407fe0bd0f7857dab4c8163048abca31 (HEAD, origin/master, origin/HEAD, mastertag: 1.7.1)
Author: Bharat saraswal [bharat.saraswal@huawei.comBrian O'Connor [bocon@onlab.us]
AuthorDate: Fri Dec 16 16:29:02 2016 +0530
Commit: bharat saraswal-huawei [bharat.saraswal@huawei.com]
CommitDate: Fri Dec 30 05:01:50 2016 +0000
[ONOS-5763] YSR changes to support decode without module name.Mon Oct 24 22:30:47 2016 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Mon Oct 24 22:30:47 2016 -0700

Tagging 1.7.1 (Hummingbird)

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 1 Constructing test variables - No Result
• 1.4 Using mvn clean install - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing ONOS package - FAIL
• ONOS install failed
• 1.7 Checking if ONOS is up yet - PASS
• 1.8 Starting ONOS CLI sessions 2 Uninstalling ONOS package - PASS
• 1.3 Create cell file 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

• 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 .4 Apply cell to environment - PASS
• 3.3 Check ovsdb node 1 manager is 10.128.20.11 - PASS
• 3.4 Check ovsdb node 2 manager is 10.5 Creating ONOS package - FAIL
• Failed to create ONOS package
• 1.6 Installing ONOS package - FAIL
Failed to install ONOS package
• 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