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

USECASE_SdnipFunctionCluster at 03 May 2017 07:47:27

commit d3c2d7419e859e6b92e9fbb21a7704193cccc016 (HEAD, origin/onos-1.9, onos-1.9)
Author: Ray Milkey [ray@onlab.us]
AuthorDate: Mon May 1 16:00:53 2017 -0700
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Tue May 2 19:42:03 2017 +0000

Fix filtering of UI archetype java files
--
(cherry picked from commit 14b62a08da1b1051f23ed683840d1615b67f62c9)

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 Uninstalling ONOS - PASS (tick)
  • 101.6 Creating ONOS package - PASS (tick)
  • 101.7 Installing ONOS package - PASS (tick)
  • 101.8 Set up ONOS secure SSH - PASS (tick)
  • 101.9 Checking if ONOS is up yet - PASS (tick)
  • 101.10 Checking if ONOS CLI is ready - PASS (tick)
  • 101.11 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)
  • 1.3 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 1.4 BGP speakers ping peers, expect all tests to succeed - PASS (tick)

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

  • 2.1 Check P2P intents number from ONOS CLI - FAIL (error)
    • PointToPointIntent Intent Num is wrong!

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, expect all to succede=True - PASS (tick)
  • 4.2 Check ping between each host pair, expect all to succede=True - PASS (tick)
  • 4.3 Check ping between each host pair, expect all to succede=True - PASS (tick)

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

  • 5.1 Bring down the link between sw32 and p64514 - 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 p64515 - 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 p64516 - 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 p64514 - 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 p64515 - 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 p64516 - 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, expect all to succede=True - FAIL (error)
    • Ping test results are Not expected

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 spk1 - PASS (tick)
  • 7.7 Check ping between BGP peers and spk2 - 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, expect all to succede=True - PASS (tick)
  • No labels