Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 561 Next »

FUNCnetconf at 21 Mar 2018 21:30:50

FUNCnetconf

commit d1cc1a371fe0bc32d2e020f60edfe4945b5f80ac (HEAD -] master, origin/master, origin/HEAD)
Author: Andrea Campanella [andrea@opennetworking.org]
AuthorDate: Wed Mar 21 10:08:55 2018 -0700
Commit: Andrea Campanella [andrea@opennetworking.org]
CommitDate: Wed Mar 21 21:01:22 2018 +0000

Adding complete path to failed traces
--
(cherry picked from commit fec00e55291e26984d4af6a4030e99844598fd36)

Case 1: Pull onos branch and build onos on Teststation. - PASS

For loading from params file, and pull and build the latest ONOS package

  • 1.1 Constructing test variables - PASS (tick)

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

Set up ONOS with 1 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling ONOS package - PASS (tick)
  • 2.3 Creating ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Set up ONOS secure SSH - PASS (tick)
  • 2.6 Checking ONOS service - PASS (tick)
  • 2.7 Starting ONOS CLI sessions - PASS (tick)

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

  • 100.1 Starting NETCONF app - PASS (tick)
  • 100.2 Starting OFC-Server - PASS (tick)

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

  • 200.1 Assembling configuration file - PASS (tick)

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

  • 300.1 Sending the configuration file - PASS (tick)
  • No labels