Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
HAsanity at 11 May 2016 15:37:07
commit 072ee2f6f6a571bd61eff11fc2b0b3f569e05e93 (HEAD, origin/master, origin/HEAD, master)
Author: HIGUCHI Yuta [y-higuchi@ak.jp.nec.com]
AuthorDate: Wed May 11 11:56:22 2016 -0700
Commit: HIGUCHI Yuta [y-higuchi@ak.jp.nec.com]
CommitDate: Wed May 11 11:56:22 2016 -0700
Remove unnecessary CHECKSTYLE comment
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 Checking ONOS nodes - PASS
- 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 - No Result
- 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