commit 4124bc365f7abe0c4271e0b09065e66d88a0241c (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani [madan.jampani@gmail.com]
AuthorDate: Sat Jan 30 23:53:56 2016 -0800
Commit: Madan Jampani [madan.jampani@gmail.com]
CommitDate: Sat Jan 30 23:53:56 2016 -0800
LEADER_ELECTOR distributed primitive enum type
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 topology - 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
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 - No Result
- 5.3 Get the intents from each controller - No Result
- 5.4 Get the flows from each controller - No Result
- 5.5 Get the OF Table entries - No Result
- 5.6 Collecting topology information from ONOS - No Result
- 5.7 Each host has an IP address - PASS
- 5.8 There is only one dataplane cluster - PASS
- 5.9 Comparing ONOS topology to MN - PASS
- 5.10 Device information is correct - PASS
- 5.11 Links are correct - PASS
- 5.12 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
Case 15: Check that Leadership Election is still functional - No Result
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - PASS