USECASE_SdnipFunctionCluster at 21 Apr 2017 01:42:10
commit 20913c6646607c58c0f7e637373aa26d71d41e03 (HEAD, origin/master, origin/HEAD, master)
Author: Marc De Leenheer [marc@onlab.us]
AuthorDate: Wed Apr 12 14:45:15 2017 -0700
Commit: Yuta HIGUCHI [y-higuchi@onlab.us]
CommitDate: Fri Apr 21 02:12:18 2017 +0000
Adding visual mapping of packet to optical path.
Case 101: Setting up ONOS environment - PASS
- 101.1 Copying config files - PASS
- 101.2 Create cell file - No Result
- 101.3 Applying cell variable to environment - PASS
- 101.4 Verify cell connectivity - PASS
- 101.5 Uninstalling ONOS - PASS
- 101.6 Creating ONOS package - PASS
- 101.7 Installing ONOS package - PASS
- 101.8 Set up ONOS secure SSH - PASS
- 101.9 Checking if ONOS is up yet - PASS
- 101.10 Checking if ONOS CLI is ready - PASS
- 101.11 Checking if ONOS CLI is ready for issuing commands - PASS
Case 100: Setup the Mininet testbed - PASS
- 100.1 Starting Mininet Topology - PASS
- 100.2 Connect switches to controllers - PASS
Case 200: Activate sdn-ip application - PASS
- 200.1 Get links in the network - PASS
- 200.2 Activate sdn-ip application - PASS
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
- 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254.1.202:2000 - PASS
- 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254.1.203:2000 - PASS
Case 1: Ping between BGP peers and speakers - PASS
- 1.1 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.2 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.3 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.4 BGP speakers ping peers, expect all tests to succeed - PASS
Case 2: Check point-to-point intents - FAIL
- 2.1 Check P2P intents number from ONOS CLI - FAIL
- PointToPointIntent Intent Num is wrong!
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, expect all to succede=True - PASS
- 4.2 Check ping between each host pair, expect all to succede=True - PASS
- 4.3 Check ping between each host pair, expect all to succede=True - PASS
Case 5: Bring down links and check routes/intents - FAIL
- 5.1 Bring down the link between sw32 and p64514 - PASS
- 5.2 Check routes installed - FAIL
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - FAIL
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and p64516 - PASS
- 5.8 Check routes installed - FAIL
- 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, expect all to succede=False - PASS
Case 6: Bring up links and check routes/intents - FAIL
- 6.1 Bring up the link between sw32 and p64514 - PASS
- 6.2 Check routes installed - FAIL
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and p64515 - PASS
- 6.5 Check routes installed - FAIL
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and p64516 - PASS
- 6.8 Check routes installed - FAIL
- 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, expect all to succede=True - PASS
Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - FAIL
- 7.1 Stop sw32 - PASS
- 7.2 Check routes installed - FAIL
- 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 spk1 - PASS
- 7.7 Check ping between BGP peers and spk2 - PASS
- 7.8 Check whether all flow status are ADDED - PASS
Case 8: Start the edge sw32, check P-2-P and M-2-S intents, ping test - FAIL
- 8.1 Start sw32 - PASS
- 8.2 Check routes installed - FAIL
- 8.3 Check M2S intents installed - PASS
- 8.4 Check P2P intents installed - PASS
- 8.5 Check whether all flow status are ADDED - PASS
- 8.6 BGP speakers ping peers, expect all tests to succeed - PASS
- 8.7 BGP speakers ping peers, expect all tests to succeed - PASS
- 8.8 Check ping between each host pair, expect all to succede=True - PASS
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
- 9.2 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 9.3 Check flow entry number in sw7 - PASS
- 9.4 Stop sw11 - PASS
- 9.5 Check routes installed - FAIL
- 9.6 Check M2S intents installed - PASS
- 9.7 Check P2P intents installed - PASS
- 9.8 Check whether all flow status are ADDED - PASS
- 9.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.10 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.11 Check ping between each host pair, expect all to succede=True - PASS
Case 10: Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - FAIL
- 10.1 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 10.2 Check flow entry number in sw7 - PASS
- 10.3 Start sw11 - PASS
- 10.4 Check routes installed - FAIL
- 10.5 Check M2S intents installed - PASS
- 10.6 Check P2P intents installed - PASS
- 10.7 Check whether all flow status are ADDED - PASS
- 10.8 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.10 Check ping between each host pair, expect all to succede=True - PASS