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 14 Next »

USECASE_SdnipFunctionCluster at 08 Jun 2016 11:35:10

commit f57eee3e1d741200a05e70e7f4f0dd5f1f2f5e9b (HEAD, origin/onos-1.6, onos-1.6)
Author: Saurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Fri May 27 13:54:07 2016 -0700
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Wed Jun 8 10:02:44 2016 -0700

In this commit:
Bug fix where filtering objectives are not installed due to available ports becoming enabled later.
Bug fix where flow objective store had no listener for notifications from drivers across multiple instances of the controller.
NPE fix in ofdpa driver for non-existing groups.
Preventing ofdpa driver from sending spurious pass notification to app.
Incrementing retry filter timer from 1 to 5 secs in default routing handler.
Made several debug messages clearer.

Case 101: Setting up ONOS environment - PASS

  • 101.1 Copying config files - PASS (tick)
  • 101.2 Create cell file - No Result (warning)
  • 101.3 Applying cell variable to environment - PASS (tick)
  • 101.4 Verify cell connectivity - PASS (tick)
  • 101.5 Creating ONOS package - PASS (tick)
  • 101.6 Installing ONOS package - PASS (tick)
  • 101.7 Checking if ONOS is up yet - PASS (tick)
  • 101.8 Checking if ONOS CLI is ready - PASS (tick)
  • 101.9 Checking if ONOS CLI is ready for issuing commands - PASS (tick)

Case 100: Setup the Mininet testbed - PASS

  • 100.1 Starting Mininet Topology - PASS (tick)
  • 100.2 Connect switches to controllers - PASS (tick)

Case 200: Activate sdn-ip application - PASS

  • 200.1 Get links in the network - PASS (tick)
  • 200.2 Activate sdn-ip application - PASS (tick)

Case 102: Load methods from other Python file and create tunnels - PASS

  • 102.1 Set up tunnel from Mininet node 1.1.1.2:2000 to ONOS node 10.254.1.201:2000 - PASS (tick)
  • 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254.1.202:2000 - PASS (tick)
  • 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254.1.203:2000 - PASS (tick)

Case 1: Ping between BGP peers and speakers - PASS

  • 1.1 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 1.2 BGP speakers ping peers, expect all tests to succeed - PASS (tick)

Case 2: Check point-to-point intents - PASS

  • 2.1 Check P2P intents number from ONOS CLI - PASS (tick)

Case 3: Check routes and M2S intents to all BGP peers - FAIL

  • 3.1 Check routes installed - PASS (tick)
  • 3.2 Check M2S intents installed - FAIL (error)
    • MultiPointToSinglePoint Intent Num is wrong!
  • 3.3 Check whether all flow status are ADDED - PASS (tick)

Case 4: Ping test for each route, all hosts behind BGP peers - FAIL

  • 4.1 Check ping between each host pair, expect all to succede=True - FAIL (error)
    • Ping test results are Not expected

Case 5: Bring down links and check routes/intents - FAIL

  • 5.1 Bring down the link between sw32 and peer64514 - PASS (tick)
  • 5.2 Check routes installed - PASS (tick)
  • 5.3 Check M2S intents installed - FAIL (error)
    • M2S intent number is wrong!
  • 5.4 Bring down the link between sw8 and peer64515 - PASS (tick)
  • 5.5 Check routes installed - PASS (tick)
  • 5.6 Check M2S intents installed - FAIL (error)
    • M2S intent number is wrong!
  • 5.7 Bring down the link between sw28 and peer64516 - PASS (tick)
  • 5.8 Check routes installed - PASS (tick)
  • 5.9 Check M2S intents installed - PASS (tick)
  • 5.10 Check whether all flow status are ADDED - PASS (tick)
  • 5.11 BGP speakers ping peers, expect all tests to fail - PASS (tick)
  • 5.12 Check ping between each host pair, expect all to succede=False - PASS (tick)

Case 6: Bring up links and check routes/intents - FAIL

  • 6.1 Bring up the link between sw32 and peer64514 - PASS (tick)
  • 6.2 Check routes installed - PASS (tick)
  • 6.3 Check M2S intents installed - FAIL (error)
    • M2S intent number is wrong!
  • 6.4 Bring up the link between sw8 and peer64515 - PASS (tick)
  • 6.5 Check routes installed - PASS (tick)
  • 6.6 Check M2S intents installed - FAIL (error)
    • M2S intent number is wrong!
  • 6.7 Bring up the link between sw28 and peer64516 - PASS (tick)
  • 6.8 Check routes installed - PASS (tick)
  • 6.9 Check M2S intents installed - FAIL (error)
    • M2S intent number is wrong!
  • 6.10 Check whether all flow status are ADDED - PASS (tick)
  • 6.11 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 6.12 Check ping between each host pair, expect all to succede=True - FAIL (error)
    • Ping test results are Not expected
  • No labels