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

USECASE_SdnipFunction at 29 Sep 2015 15:05:34

Case 100: - PASS

  • 100.1 Starting Mininet Topology - PASS (tick)
  • 100.2 Connect switches to controller - PASS (tick)
  • 100.3 Set up tunnel from Mininet node to onos node - PASS (tick)
commit 71892221d15952691e07088eababc8cab0364073 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Tue Sep 29 13:39:40 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Sep 29 20:59:49 2015 +0000

ONOS-2901 - Added fix to ignore reserved global keys, when activating a topo overlay.

Case 101: Setting up test environment - PASS

  • 101.1 Applying cell variable to environment - PASS (tick)
  • 101.2 Git pull - PASS (tick)
  • 101.3 Using mvn clean install - PASS (tick)
  • 101.4 Creating ONOS package - PASS (tick)
  • 101.5 Installing ONOS package - PASS (tick)
  • 101.6 Checking if ONOS is up yet - PASS (tick)
  • 101.7 Checking if ONOS CLI is ready - PASS (tick)
  • 101.8 Activate sdn-ip application - PASS (tick)

Case 102: Loading methods from other Python file - PASS

Case 1: Ping tests between BGP peers and speakers - PASS

  • 1.1 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 speakers - PASS (tick)
  • 7.7 Check whether all flow status are ADDED - PASS (tick)
  • No labels