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.
FUNCflow at 16 Aug 2018 21:15:38
commit 7981a32f37d64225a5b641725ba172cdc32e2f0d (HEAD -] master, origin/master, origin/HEAD)
Author: Ray Milkey [ray@opennetworking.org]
AuthorDate: Thu Aug 16 14:55:46 2018 -0700
Commit: Ray Milkey [ray@opennetworking.org]
CommitDate: Thu Aug 16 23:52:44 2018 +0000
Fix NPE when component can't be found
Case 1: Pull onos branch and build onos on Teststation. - PASS
For loading from params file, and pull and build the latest ONOS package
- 1.1 Constructing test variables - PASS
Case 2: Starting up 1 node(s) ONOS cluster - FAIL
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - FAIL
- Test step FAIL
- 2.8 Checking ONOS service - FAIL
- ONOS service did not start properly on all nodes
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - FAIL
- Not all ONOS nodes are in READY state
- 2.11 Checking ONOS applications - FAIL
- Not all ONOS apps are activated
Case 10: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology elements between Mininet and ONOS
- 10.1 Setup Mininet Topology - PASS
- 10.2 Assign switch to controller - PASS
- 10.3 Comparing Mininet topology to ONOS topology - FAIL
- ONOS incorrectly discovered the topology
Case 11: Starting scapy with Mininet - PASS
- 11.1 Creating Host component - No Result
- 11.2 Start scapy components - PASS