commit ef2e63998b679c456cbb3f641cec8307263e262b (HEAD, origin/master, origin/HEAD, master)
Author: Bharat saraswal [bharat.saraswal@huawei.com]
AuthorDate: Tue Apr 19 19:50:32 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Apr 19 17:17:49 2016 +0000
YANG augment's generated file name resolver implementation and UT fixes.
Case 1: Setting up test environment - FAIL
Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.
- 1.1 Create cell file - No Result
- 1.2 Applying cell variable to environment - No Result
- 1.3 Starting Mininet - PASS
- 1.4 Git checkout and pull master - No Result
- 1.5 Using mvn clean install - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing ONOS package - PASS
- 1.8 Checking if ONOS is up yet - PASS
- 1.9 Checking ONOS nodes - FAIL
- Nodes check NOT successful
- 1.10 Activate apps defined in the params file - No Result
- 1.11 Set ONOS configurations - PASS
- 1.12 App Ids check - PASS
Case 2: Assigning devices to controllers - PASS
Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.
- 2.1 Assign switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - FAIL
- ONOS nodes have different views of hosts
- 8.3 Hosts information is correct - FAIL
- Host information is incorrect
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Hosts are correct - FAIL
- Hosts are incorrect
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
Case 3: Adding host Intents - FAIL
Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - FAIL
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - FAIL
- ONOS nodes have different views of hosts
- 8.3 Hosts information is correct - FAIL
- Host information is incorrect
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Hosts are correct - FAIL
- Hosts are incorrect
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
Case 4: Verify connectivity by sending traffic across Intents - FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 5: Setting up and gathering data for current state - No Result
- 5.1 Check that each switch has a master - FAIL
- Some devices don't have a master assigned
- 5.2 Get the Mastership of each switch from each controller - FAIL
- Error in reading roles from ONOS
- 5.3 Check for consistency in roles from each controller - FAIL
- ONOS nodes have different views of switch roles
- 5.4 Get the intents from each controller - FAIL
- Error in reading intents from ONOS
- 5.5 Check for consistency in Intents from each controller - FAIL
- ONOS nodes have different views of intents
- 5.6 Get the flows from each controller - FAIL
- Error in reading flows from ONOS