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.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCnetconf_master_20-builds_graph.jpg", alt="FUNCnetconf", style="width:525px;height:350px;border:0"> |
commit e0eaf5c7bfaacca5f03a188bc9d33df532b768fa 9417e13b3d9d764f9ec94691ef6d5c1ff902a3d8 (HEAD, origin/master, origin/HEAD, master)
Author: Jian Li [pyguni@gmail.com]
AuthorDate: Mon Tue Sep 6 107 15:0213:13 42 2021 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Mon Wed Sep 6 088 00:2855:48 09 2021 +0000
Check node init status when probing node health through REST API
Support to inject controller IP address to API config for tenant NW
--
(cherry picked from commit 6a08072a2c1c3094818268ebf22ffa82f97131250a05d6fe81c13ddffa4aba674d33103df8e5121b)
Case 1: Pull onos branch and build onos on Teststation. - PASS
...
- 1.1 Constructing test variables - PASS
Case 2: Starting up 1 node(s) ONOS cluster - PASS
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 - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
Case 100: Start up NETCONF app in all nodes Test - 1 NODE(S) - FAIL
- 100.1 Starting NETCONF app - FAIL
- Assertion result for starting NETCONF app
- 100.2 Starting OFC-Server - PASS
Case 200: Assemble the configuration Test - 1 NODES(S) - PASS
- 200.1 Assembling configuration file - PASS
Case 300: Uploading the configuration Test - 1 NODES(S) - No Result
- 300.1 Sending the configuration file - PASS