FUNCnetconf at 10 May 2016 05:33:45
commit 5be3e820cfeedd763b874e6581161f7e1a0e4850 (HEAD, origin/master, origin/HEAD, master)
Author: HIGUCHI Yuta [y-higuchi@ak.jp.nec.com]
AuthorDate: Tue May 3 13:51:42 2016 -0700
Commit: Yuta HIGUCHI [y-higuchi@onlab.us]
CommitDate: Mon May 9 23:39:00 2016 +0000
ONOS-4417 Remove OtuPort out of core.
Case 1: Constructing test variables and building ONOS package - PASS
This test case is mainly for loading from params file, and pull and build the latest ONOS package
- 1.1 Constructing test variables - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 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 - 1 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 - 1 NODES(S) - PASS
- 200.1 Assembling configuration file - PASS
Case 300: Uploading the configuration Test - 1 NODES(S) - FAIL
- 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
- 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.