FUNCovsdbtest at 12 Nov 2015 02:57:41
commit b0e1dd018a160134bc8fdd874a787f2bad3fc6dd (HEAD, origin/onos-1.3, onos-1.3)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Wed Sep 23 17:54:11 2015 -0700
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Thu Sep 24 13:22:23 2015 -0700
IntentManager: Don't compile all failed intents on every event
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 App Ids check - No Result
- 1.9 Install onos-ovsdatabase - PASS
- 1.10 Install onos-app-vtnrsc - PASS
- 1.11 Install onos-app-vtn - PASS
- 1.12 Install onos-app-vtnweb - 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 - FAIL
- ovsdb node 2 manager check failed
- 3.5 Check default br-int bridge on ovsdb node 10.128.10.11 - PASS
- 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: - 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 - FAIL
- ovsdb node 2 manager check failed
- 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 - FAIL
- 4.7 Check onoscli devices have ovs 10.128.10.11 - PASS
- 4.8 Check onoscli devices have ovs 10.128.20.11 - FAIL
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: - PASS
- 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 - PASS
Case 6: Configure Network Subnet Port - PASS
Configure Network Subnet Port Verify post is OK
- 6.1 Generate Post Data - No Result
- 6.2 Post Network Data via HTTP(Post port need post network) - PASS
- 6.3 Post Subnet Data via HTTP(Post port need post subnet) - PASS
- 6.4 Post Port1 Data via HTTP - PASS
- 6.5 Post Port2 Data via HTTP - PASS
Case 7: - FAIL
- 7.1 ovsdb node 1 set ovs manager to 10.128.20.11 - PASS
- 7.2 ovsdb node 2 set ovs manager to 10.128.20.11 - PASS
- 7.3 Create host1 on node 1 10.128.10.11 - PASS
- 7.4 Create host2 on node 2 10.128.20.11 - PASS
- 7.5 Create port on host1 on the node 10.128.10.11 - PASS
- 7.6 Create port on host2 on the node 10.128.20.11 - PASS
- 7.7 Add port to ovs br-int and host go-online on the node 10.128.10.11 - PASS
- 7.8 Add port to ovs br-int and host go-online on the node 10.128.20.11 - PASS
- 7.9 Check onos set host flows on the node 10.128.10.11 - PASS
- 7.10 Check onos set host flows on the node 10.128.20.11 - FAIL
- 7.11 Check hosts can ping each other - FAIL
Case 8: - FAIL
- 8.1 Delete ovsdb node 1 manager - PASS
- 8.2 Delete ovsdb node 2 manager - PASS
- 8.3 Delete ovsdb node 1 bridge br-int - PASS
- 8.4 Delete ovsdb node 2 bridge br-int - PASS
- 8.5 Delete ip netns host on the ovsdb node 1 - PASS
- 8.6 Delete ip netns host on the ovsdb node 2 - PASS
- 8.7 Check onoscli devices openflow session is false 10.128.10.11 - PASS
- 8.8 Check onoscli devices have ovs 10.128.20.11 - FAIL