USECASE_SdnipFunctionCluster at 28 Jun 2020 23:14:35
Case 101: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 101.1 Constructing test variables - No Result
- 101.2 Copying config files - PASS
- 101.3 Apply cell to environment - PASS
- 101.4 Uninstalling Atomix - PASS
- 101.5 Uninstalling ONOS package - PASS
- 101.6 Creating ONOS package - PASS
- 101.7 Installing Atomix - PASS
- 101.8 Installing ONOS package - PASS
- 101.9 Set up ONOS secure SSH - PASS
- 101.10 Checking ONOS service - PASS
- 101.11 Starting ONOS CLI sessions - PASS
- 101.12 Checking ONOS nodes - PASS
- 101.13 Checking ONOS applications - PASS
- 101.14 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.192.19.68:2000 - PASS
- 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.192.19.67:2000 - PASS
- 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.192.19.64: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 - No Result
- 3.2 Check routes installed - PASS
- 3.3 Check M2S intents installed - PASS
- 3.4 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 - PASS
- 5.1 Bring down the link between sw32 and p64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and p64516 - 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, 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 - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and p64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and p64516 - 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 fail - PASS
- 6.12 Check ping between each host pair, expect all to succede=False - FAIL
- 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
- 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 spk1 - PASS
- 7.7 Check ping between BGP peers and spk2 - PASS
- 7.8 Check whether all flow status are ADDED - PASS