master-VPLSBasic

commit 901774120a7fdab10a978c4aa26f812602e585e0 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Sun Nov 15 23:27:36 2020 -0800
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Mon Nov 16 18:37:46 2020 +0000

Added ability to configure or programmatically inject default maximum number of paths when computing topology using default methods.

Case 1: Starting up 3 node(s) ONOS cluster - FAIL

Set up ONOS with 3 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling Atomix - PASS
• 1.4 Uninstalling ONOS package - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing Atomix - PASS
• 1.7 Installing ONOS package - PASS
• 1.8 Set up ONOS secure SSH - PASS
• 1.9 Checking ONOS service - PASS
• 1.10 Starting ONOS CLI sessions - PASS
• 1.11 Checking ONOS nodes - PASS
• 1.12 Checking ONOS applications - PASS
• 1.13 Starting Mininet - PASS
• 1.14 Activate apps defined in the params file - No Result
• 1.15 Set ONOS configurations - No Result
• 1.16 App Ids check - FAIL
• Something is wrong with app Ids

Case 2: - FAIL

• 2.1 Discover hosts using pings - No Result
• 2.2 Load VPLS configurations - PASS
• 2.3 Check interface configurations - FAIL
• Net Cfg not added for interfaces
• 2.4 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 2.5 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 2.6 Check connectivity - FAIL
• Connectivity is not as expected
• 2.7 Loading vpls configuration in case any configuration was missed. - PASS

Case 10: - FAIL

• 10.1 Remove an interface from a vpls network - No Result
• 10.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 10.3 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 10.4 Check connectivity - FAIL
• Connectivity is not as expected

Case 11: - FAIL

• 11.1 Clean all vpls configurations - No Result
• 11.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 11.3 Check vpls app configurations - PASS
• 11.4 Check connectivity - PASS

Case 12: - FAIL

• 12.1 Create a new vpls network - No Result
• 12.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 12.3 Check vpls app configurations - PASS
• 12.4 Check connectivity - PASS

Case 13: - FAIL

• 13.1 Add interfaces to the network - No Result
• 13.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 13.3 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 13.4 Check connectivity - FAIL
• Connectivity is not as expected

Case 14: - FAIL

• 14.1 Add MPLS encapsulation to a vpls network - No Result
• 14.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 14.3 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 14.4 Check connectivity - FAIL
• Connectivity is not as expected

Case 15: - FAIL

• 15.1 Change an encapsulation type - No Result
• 15.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 15.3 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 15.4 Check connectivity - FAIL
• Connectivity is not as expected

Case 16: - FAIL

• 16.1 Remove encapsulation - No Result
• 16.2 Check network configurations for vpls application - FAIL
• Net Cfg not added for vpls
• 16.3 Check vpls app configurations - FAIL
• VPLS not configured correctly
• 16.4 Check connectivity - FAIL
• Connectivity is not as expected

Case 11: - PASS

• 11.1 Clean all vpls configurations - No Result
• 11.2 Check network configurations for vpls application - PASS
• 11.3 Check vpls app configurations - PASS
• 11.4 Check connectivity - PASS