commit ca20bb57f420966384d45c6817bcae7fc90d4aa1 (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey [ray@onlab.us]
AuthorDate: Tue Nov 10 13:59:16 2015 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Nov 11 03:22:46 2015 +0000
Unit tests for OpenFlowControllerImplTest
Case 1: Setting up test environment - PASS
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 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 - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - 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 4: Verify connectivity by sendind traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS