Page History

...

commit 5be3e820cfeedd763b874e6581161f7e1a0e4850 a84637c702a45e8e70f05f0437217f15930a7135 (HEAD, origin/master, origin/HEAD, master)
Author: HIGUCHI Yuta [y-higuchi@ak.jp.nec.comBrian O'Connor [bocon@onlab.us]
AuthorDate: Tue May 3 1310 19:5116:42 18 2016 -0700
Commit: Yuta HIGUCHI [y-higuchi@onlabBrian O'Connor [bocon@onlab.us]
CommitDate: Mon Tue May 9 2310 19:3916:00 53 2016 +0000
ONOS-4417 Remove OtuPort out of core.-0700

Updating bin/karaf to fix ^D

Case 1: Constructing test variables and building ONOS package - PASS

...

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 100: Start up NETCONF app in all nodes Test - 1 NODE(S) -

...

PASS

• 100.1 Starting NETCONF app - FAIL
Assertion result for starting NETCONF app
• PASS
• 100.2 Starting OFC-Server - PASS

...

• 200.1 Assembling configuration file - PASS

Case 300: Uploading the configuration Test - 1 NODES(S) -

...

• 300.1 Sending the configuration file - FAIL
• Assertion result for sending the configuration file
• 300.2 Confirming the device was configured - FAIL
• Assertion result for confirming a configuration.

Case 2: Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

• 2.1 Uninstalling ONOS package - PASS
• 2.2 Apply cell to environment - PASS
• 2.3 Creating ONOS package - PASS
• 2.4 Installing ONOS package - PASS
• 2.5 Starting ONOS service - PASS
• 2.6 Start ONOS cli - PASS

Case 100: Start up NETCONF app in all nodes Test - 3 NODE(S) - FAIL

• 100.1 Starting NETCONF app - FAIL
• Assertion result for starting NETCONF app
• 100.2 Starting OFC-Server - PASS

Case 200: Assemble the configuration Test - 3 NODES(S) - PASS

• 200.1 Assembling configuration file - PASS

Case 300: Uploading the configuration Test - 3 NODES(S) - FAIL

...

• Assertion result for sending the configuration file

...

No Result