Page History

...

commit 6a8cb4f3e54bb186331e7fbb4062551f63366461 bef16cde61b422073304bc6e32c841989115dd0f (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.usYuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Tue Wed Aug 9 1510 14:0855:57 48 2016 -0700
Commit: Simon Hunt Ray Milkey [simon@onlabray@onlab.us]
CommitDate: Tue Thu Aug 9 11 03:20:31 :24 2016 -0700
ONOS-4970: Device data for topology view -- WIP.+0000

Simplify ConnectPoint#toString format

Case 1: Setting up test environment - FAIL

...

• 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 FAIL
• Something is wrong with app Ids
• 1.10 Install onos-ovsdatabase - PASS FAIL
• Install onos-ovsdatabase failed
• 1.11 Install onos-app-vtnrsc - FAIL
• Install onos-app-vtnrsc failed
• 1.12 Install onos-app-vtn - PASS
• 1.13 Install onos-app-vtnweb - FAIL
• Install onos-app-vtnweb failed

...

• 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: -

...

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 - 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 FAIL
• 4.8 Check onoscli devices have ovs 10.128.20.11 - PASS FAIL

Case 2: Test ovsdb connection and teardown - PASS

...