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.
...
commit 71d85bcc94d8e77228828a44db073c38f8ea30d2 19bd1301c278edfc91a00d2cb1eb2aae9130965a (HEAD, origin/onos-1.6, onos-1.6)
Author: Simon Hunt [simon@onlab.usBharat saraswal [bharat.saraswal@huawei.com]
AuthorDate: Fri Sat May 27 1128 17:5450:02 57 2016 -0700+0530
Commit: Simon Hunt [simon@onlab.usbharat saraswal-huawei [bharat.saraswal@huawei.com]
CommitDate: Fri Sat May 27 28 13:3009:08 14 2016 -0700
GUI -- topo - fix incorrect function reference.
--
(cherry picked from commit 356da76)
Case 101: Setting up ONOS environment - PASS
- 101.1 Copying config files - PASS
- 101.2 Create cell file - No Result
- 101.3 Applying cell variable to environment - PASS
- 101.4 Verify cell connectivity - PASS
- 101.5 Creating ONOS package - PASS
- 101.6 Installing ONOS package - PASS
- 101.7 Checking if ONOS is up yet - PASS
- 101.8 Checking if ONOS CLI is ready - PASS
- 101.9 Checking if ONOS CLI is ready for issuing commands - PASS
Case 100: Setup the Mininet testbed - PASS
- 100.1 Starting Mininet Topology - PASS
- 100.2 Connect switches to controllers - PASS
Case 200: Activate sdn-ip application - PASS
- 200.1 Get links in the network - PASS
- 200.2 Activate sdn-ip application - PASS
Case 102: Load methods from other Python file and create tunnels - PASS
- 102.1 Set up tunnel from Mininet node 1.1.1.2:2000 to ONOS node 10.254.1.201:2000 - PASS
- 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254.1.202:2000 - PASS
- 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254.1.203:2000 - PASS
Case 1: Ping between BGP peers and speakers - PASS
- 1.1 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.2 BGP speakers ping peers, expect all tests to succeed - PASS
Case 2: Check point-to-point intents - PASS
- 2.1 Check P2P intents number from ONOS CLI - PASS
Case 3: Check routes and M2S intents to all BGP peers - FAIL
- 3.1 Check routes installed - PASS
- 3.2 Check M2S intents installed - FAIL
- MultiPointToSinglePoint Intent Num is wrong!
- 3.3 Check whether all flow status are ADDED - PASS
Case 4: Ping test for each route, all hosts behind BGP peers - FAIL
- 4.1 Check ping between each host pair, expect all to succede=True - FAIL
- Ping test results are Not expected
Case 5: Bring down links and check routes/intents - FAIL
- 5.1 Bring down the link between sw32 and peer64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.4 Bring down the link between sw8 and peer64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.7 Bring down the link between sw28 and peer64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - PASS
- 5.10 Check whether all flow status are ADDED - PASS
- 5.11 BGP speakers ping peers, expect all tests to fail - PASS
- 5.12 Check ping between each host pair, expect all to succede=False - PASS
Case 6: Bring up links and check routes/intents - FAIL
...
- M2S intent number is wrong!
...
- M2S intent number is wrong!
...
- M2S intent number is wrong!
...
+0000
[ONOS-4627] Rpc empty folder structure issue fixed.