Page History

...

commit bbc352fe7d829c8b809af8ee3a4c2ca3a43dcdca (HEAD, origin/master, origin/HEAD, master)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Tue Oct 27 19:24:36 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Oct 28 02:35:36 2015 +0000

vBNG: Make the compute node to connect point map configurable

...

• 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 - FAIL
• Flow status is wrong!
• 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 - PASS 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 - PASS

...