...
commit 7a3b4611c1593afe4648ad427bca9fb80da22cc7 (HEAD -] onos-1.14, origin/onos-1.14)
Author: psneha [sneha.prem@infosys.com]
AuthorDate: Thu Aug 2 01:16:46 2018 -0400
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Tue Aug 21 17:20:06 2018 +0000
Added one more Component Config REST API; for specified component and variable.
--
(cherry picked from commit f31ac6ff9f72d040b2da80b6ee5c630ccf9dcc55)
Case 1: Starting
...
up
...
7 node(s
...
- 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 Starting Mininet - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing Atomix - PASS
- 1.8 Installing ONOS package - PASS
- 1.9 Set up ONOS secure SSH - PASS
- 1.10 Checking ONOS service - PASS
- 1.11 Starting ONOS CLI sessions - PASS
- 1.12 Checking ONOS nodes - PASS
- 1.13 Checking ONOS applications - PASS
- 1.14 Checking ONOS nodes - PASS
- 1.15 Activate apps defined in the params file - No Result
- 1.16 Set ONOS configurations - PASS
- 1.17 Check app ids - PASS
- 1.18 Set logging levels - 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 - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 21: Assigning Controller roles for switches - PASS
Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'
- 21.1 Assign mastership of switches to specific controllers - PASS
- 21.2 Check mastership was correctly assigned - PASS
Case 3: Adding host Intents - PASS
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 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
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 - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 5: Setting up and gathering data for current state - PASS
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - PASS
- 5.16 Comparing ONOS topology to MN - PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - PASS
- 5.19 Hosts are correct - PASS
Case 14: Start Leadership Election app - PASS
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - PASS
- 14.3 Active node was elected leader? - PASS
Case 15: Check that Leadership Election is still functional - PASS
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Check that a new node was elected leader - PASS
- 15.5 Check that that new leader was the candidate of old leader - PASS
- 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - No Result
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - PASS
Case 17: Check for basic functionality with distributed primitives - FAIL
Test the methods of the distributed primitives (counters and sets) throught the cli
...
- Set clear was incorrect
...
)
...
- Error getting atomic Value None, found: ['baz', 'baz', 'baz', 'baz', 'baz', 'baz', 'baz']
...
- Work Queue stats incorrect
...
ONOS cluster
...
- 6.1 Checking ONOS Logs for errors - No Result
- 6.2 Checking ONOS service - PASS
- 6.3 Starting ONOS CLI sessions - FAIL
- Failed to rerun for election
...