Page History

...

commit 0d752b9e1b8a810f3fadfa313f8251208223a6c8 152b88508ab42dc93cce77fedfdafb35b4899fd9 (HEAD, origin/onos-1.4, onos-1.4)
Author: lishuai Jian Li [lishuai12@huaweipyguni@gmail.com]
AuthorDate: Tue Mon Dec 29 7 14:4947:59 25 2015 +-0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Mon Jan 5 174 18:4850:24 06 2016 +0000

[Falcon][ONOS-3641] Update the bug which is finded by fuel installer: the3537] Implement control message collecting logic w/ unit test

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

Case 12: Bring down leader ONOS node, check: route number, P2P intent number, M2S intent number, ping test - PASS

• 12.1 Find out ONOS leader node - No Result
• 12.2 Uninstall ONOS/SDN-IP leader node - PASS
• 12.3 Check routes installed - PASS
• 12.4 Check M2S intents installed - PASS
• 12.5 Check P2P intents installed - PASS
• 12.6 Check whether all flow status are ADDED - PASS
• 12.7 BGP speakers ping peers, expect all tests to succeed - PASS
• 12.8 BGP speakers ping peers, expect all tests to succeed - PASS
• 12.9 Check ping between each host pair - PASS