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/FUNCovsdbtest_master_20-builds_graph.jpg", alt="FUNCovsdbtest", style="width:525px;height:350px;border:0"> |
commit 3039bdbb06f426bf06c59b6d25b0847a73fab8e7 46d557f868c4a1d904de7669f7bff0241e7b709f (HEAD -] master, origin/master, origin/HEAD)
Author: alessio pier [alessiopier@opennetworking.giorgetti@gmail.comorg]
AuthorDate: Thu Tue Nov 29 1427 11:1223:32 50 2018 +0100-0800
Commit: Pier Luigi Ventre [pier@opennetworking.org]
CommitDate: Thu Fri Dec 6 7 21:3720:20 07 2018 +0000
[ONOS-7839] suggestedPath for optical connectivity intent with optical-rest support
Provides a separate executor to handle map events.
Case 1: Starting up 1 node(s) ONOS cluster - PASS
...
- 3.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS
- 3.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 3.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS
- 3.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS
- 3.5 Check default br-int bridge on ovsdb node 10.192.19.229 - FAIL
- onos add default bridge on the node 1 failed
- 3.6 Check default br-int bridge on ovsdb node 10.192.19.231 - FAIL
- onos add default bridge on the node 2 failed
- 3.7 Check default vxlan port on ovsdb node 10.192.19.229 - FAIL
- onos add default vxlan port on the node 1 failed
- 3.8 Check default vxlan port on ovsdb node 10.192.19.231 - FAIL
- onos add default vxlan port on the node 2 failed
Case 4: -
...
PASS
- 4.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS
- 4.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 4.3 Check ovsdb node 1 manager is 10.192.19.231 - PASS
- 4.4 Check ovsdb node 2 manager is 10.192.19.231 - PASS
- 4.5 Check ovsdb node 1 bridge br-int controller set to 10.192.19.231 - FAIL
- sudo ovs-vsctl show
- 69d75e74-ec31-40a6-9908-c1fc20d9faab
- is_connected: true
- PASS
- 4.6 Check ovsdb node 2 bridge br-int controller set to 10.192.19.231 - PASS
- 4.7 Check onoscli devices have ovs 10.192.19.229 - PASS
- 4.8 Check onoscli devices have ovs 10.192.19.231 - PASS
...
- 7.1 ovsdb node 1 set ovs manager to 10.192.19.231 - PASS
- 7.2 ovsdb node 2 set ovs manager to 10.192.19.231 - PASS
- 7.3 Create host1 on node 1 10.192.19.229 - PASS
- 7.4 Create host2 on node 2 10.192.19.231 - PASS
- 7.5 Create port on host1 on the node 10.192.19.229 - PASS
- 7.6 Create port on host2 on the node 10.192.19.231 - PASS
- 7.7 Add port to ovs br-int and host go-online on the node 10.192.19.229 - PASS
- 7.8 Add port to ovs br-int and host go-online on the node 10.192.19.231 - PASS
- 7.9 Check onos set host flows on the node 10.192.19.229 - FAIL PASS
- 7.10 Check onos set host flows on the node 10.192.19.231 - PASS
- 7.11 Check hosts can ping each other - FAIL
...