Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
USECASE_SdnipFunction at 13 Nov 2015 05:03:24
Case 100: - PASS
- 100.1 Starting Mininet Topology - PASS
- 100.2 Connect switches to controller - PASS
- 100.3 Set up tunnel from Mininet node to onos node - PASS
commit 761f0040f3ce4f33a38377c7f737145b603aa334 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Wed Nov 11 19:10:17 2015 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Nov 12 21:37:58 2015 +0000
ONOS-1684 Added support for app dependencies.
Case 101: Setting up test environment - PASS
- 101.1 Applying cell variable to environment - PASS
- 101.2 Creating ONOS package - PASS
- 101.3 Installing ONOS package - PASS
- 101.4 Checking if ONOS is up yet - PASS
- 101.5 Checking if ONOS CLI is ready - PASS
- 101.6 Activate sdn-ip application - PASS
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
Case 2: Check point-to-point intents - PASS
- 2.1 Check P2P intents number from ONOS CLI - PASS
Case 3: Check routes and M2S intents to all BGP peers - PASS
- 3.1 Check routes installed - PASS
- 3.2 Check M2S intents installed - PASS
- 3.3 Check whether all flow status are ADDED - PASS
Case 4: Ping test for each route, all hosts behind BGP peers - PASS
- 4.1 Check ping between each host pair - PASS
Case 5: Bring down links and check routes/intents - PASS
- 5.1 Bring down the link between sw32 and peer64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and peer64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and peer64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - PASS
- 5.10 Check whether all flow status are ADDED - PASS
- 5.11 BGP speakers ping peers, expect all tests to fail - PASS
- 5.12 Check ping between each host pair - PASS
Case 6: Bring up links and check routes/intents - PASS
- 6.1 Bring up the link between sw32 and peer64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and peer64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and peer64516 - PASS
- 6.8 Check routes installed - PASS
- 6.9 Check M2S intents installed - PASS
- 6.10 Check whether all flow status are ADDED - PASS
- 6.11 BGP speakers ping peers, expect all tests to succeed - PASS
- 6.12 Check ping between each host pair - PASS
Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS
- 7.1 Stop sw32 - PASS
- 7.2 Check routes installed - PASS
- 7.3 Check M2S intents installed - PASS
- 7.4 Check P2P intents installed - PASS
- 7.5 Check ping between hosts behind BGP peers - PASS
- 7.6 Check ping between BGP peers and speakers - PASS
- 7.7 Check whether all flow status are ADDED - PASS