Master-SDNIP Function Cluster

commit 85897573552a302fe5b6369cfe4cec5ded7dfac1 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Tue Oct 20 16:29:51 2015 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Tue Oct 20 16:32:07 2015 -0700

GUI Topo -- added NodeBadge field to NodeHighlight.

Case 101: Setting up ONOS 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

Case 100: - PASS

• 100.1 Starting Mininet Topology - PASS
• 100.2 Connect switches to controllers - PASS

Case 200: Activate sdn-ip application - PASS

• 200.1 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 tests 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

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 speaker1 - PASS
• 7.7 Check ping between BGP peers and speaker2 - 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 - PASS

• 8.1 Start sw32 - PASS
• 8.2 Check routes installed - PASS
• 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 - 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 - PASS
• 9.3 Check flow entry number in sw7 - PASS
• 9.4 Stop sw11 - PASS
• 9.5 Check routes installed - PASS
• 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 - FAIL
• Ping test results are Not expected

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 - FAIL
• Flow number in sw7 is wrong!
• 10.3 Start sw11 - PASS
• 10.4 Check routes installed - PASS
• 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 - PASS

Case 11: Kill speaker1, check:route number, P2P intent number, M2S intent number, ping test - PASS

• 11.1 Check routes installed - PASS
• 11.2 Check M2S intents installed - PASS
• 11.3 Check P2P intents installed - PASS
• 11.4 Check whether all flow status are ADDED - PASS
• 11.5 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.6 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.7 Check ping between each host pair - PASS
• 11.8 Kill speaker1 - PASS
• 11.9 Check routes installed - PASS
• 11.10 Check M2S intents installed - PASS
• 11.11 Check P2P intents installed - PASS
• 11.12 Check whether all flow status are ADDED - PASS
• 11.13 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.14 Check ping between each host pair - PASS