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

USECASE_SdnipFunctionCluster at 14 Oct 2015 08:00:29

commit b0e1dd018a160134bc8fdd874a787f2bad3fc6dd (HEAD, origin/onos-1.3, onos-1.3)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Wed Sep 23 17:54:11 2015 -0700
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Thu Sep 24 13:22:23 2015 -0700

IntentManager: Don't compile all failed intents on every event

Case 101: Setting up ONOS environment - PASS

  • 101.1 Applying cell variable to environment - PASS (tick)
  • 101.2 Creating ONOS package - PASS (tick)
  • 101.3 Installing ONOS package - PASS (tick)
  • 101.4 Checking if ONOS is up yet - PASS (tick)
  • 101.5 Checking if ONOS CLI is ready - PASS (tick)

Case 100: - 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 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 tests 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 - PASS

  • 3.1 Check routes installed - PASS (tick)
  • 3.2 Check M2S intents installed - PASS (tick)
  • 3.3 Check whether all flow status are ADDED - PASS (tick)

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

  • 4.1 Check ping between each host pair - PASS (tick)

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

  • 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 - PASS (tick)
  • 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 - PASS (tick)
  • 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 - PASS (tick)

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

  • 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 - PASS (tick)
  • 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 - PASS (tick)
  • 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 - PASS (tick)
  • 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 - PASS (tick)

Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS

  • 7.1 Stop sw32 - PASS (tick)
  • 7.2 Check routes installed - PASS (tick)
  • 7.3 Check M2S intents installed - PASS (tick)
  • 7.4 Check P2P intents installed - PASS (tick)
  • 7.5 Check ping between hosts behind BGP peers - PASS (tick)
  • 7.6 Check ping between BGP peers and speaker1 - PASS (tick)
  • 7.7 Check ping between BGP peers and speaker2 - PASS (tick)
  • 7.8 Check whether all flow status are ADDED - PASS (tick)

Case 8: Start the edge sw32, check P-2-P and M-2-S intents, ping test - PASS

  • 8.1 Start sw32 - PASS (tick)
  • 8.2 Check routes installed - PASS (tick)
  • 8.3 Check M2S intents installed - PASS (tick)
  • 8.4 Check P2P intents installed - PASS (tick)
  • 8.5 Check whether all flow status are ADDED - PASS (tick)
  • 8.6 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 8.7 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 8.8 Check ping between each host pair - PASS (tick)

Case 9: Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test - FAIL

  • 9.1 Check flow entry number in sw11 - PASS (tick)
  • 9.2 Check flow entry number in sw1 - PASS (tick)
  • 9.3 Check flow entry number in sw7 - PASS (tick)
  • 9.4 Stop sw11 - PASS (tick)
  • 9.5 Check routes installed - PASS (tick)
  • 9.6 Check M2S intents installed - PASS (tick)
  • 9.7 Check P2P intents installed - PASS (tick)
  • 9.8 Check whether all flow status are ADDED - PASS (tick)
  • 9.9 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 9.10 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 9.11 Check ping between each host pair - FAIL (error)
    • Ping test results are Not expected

Case 10: Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - PASS

  • 10.1 Check flow entry number in sw1 - PASS (tick)
  • 10.2 Check flow entry number in sw7 - PASS (tick)
  • 10.3 Start sw11 - PASS (tick)
  • 10.4 Check routes installed - PASS (tick)
  • 10.5 Check M2S intents installed - PASS (tick)
  • 10.6 Check P2P intents installed - PASS (tick)
  • 10.7 Check whether all flow status are ADDED - PASS (tick)
  • 10.8 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 10.9 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 10.10 Check ping between each host pair - PASS (tick)

Case 11: Kill speaker1, check:route number, P2P intent number, M2S intent number, ping test - PASS

  • 11.1 Check routes installed - PASS (tick)
  • 11.2 Check M2S intents installed - PASS (tick)
  • 11.3 Check P2P intents installed - PASS (tick)
  • 11.4 Check whether all flow status are ADDED - PASS (tick)
  • 11.5 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.6 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.7 Check ping between each host pair - PASS (tick)
  • 11.8 Kill speaker1 - PASS (tick)
  • 11.9 Check routes installed - PASS (tick)
  • 11.10 Check M2S intents installed - PASS (tick)
  • 11.11 Check P2P intents installed - PASS (tick)
  • 11.12 Check whether all flow status are ADDED - PASS (tick)
  • 11.13 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.14 Check ping between each host pair - PASS (tick)

Case 12: Bring down leader ONOS node, check: route number, P2P intent number, M2S intent number, ping test - FAIL

  • 12.1 Find out ONOS leader node - No Result (warning)
  • 12.2 Uninstall ONOS/SDN-IP leader node - PASS (tick)
  • 12.3 Check routes installed - FAIL (error)
    • Route number is wrong!
  • 12.4 Check M2S intents installed - PASS (tick)
  • 12.5 Check P2P intents installed - PASS (tick)
  • 12.6 Check whether all flow status are ADDED - FAIL (error)
    • Flow status is wrong!
  • 12.7 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 12.8 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 12.9 Check ping between each host pair - FAIL (error)
    • Ping test results are Not expected
  • No labels