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.
...
The parameter "-ENV_DEFAULT*" is used to specify the default environment.
2.2.
...
1) net-setup-odtn
The same as net-setup-odtn in the single onos instance scenario, the output is shown below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
2019-04-08 21:47:05 ODTN-Net-Setup started 2019-04-08 21:47:05 ODTN-Net-Setup.Wipe-Out-Data-Before started -- onos-wipe-out 2019-04-08 21:47:06 ODTN-Net-Setup.Wipe-Out-Data-Before completed 2019-04-08 21:47:06 ODTN-Net-Setup.Initial-Summary-Check started -- onos-check-summary 172.17.0.5 [0-9]* 0 0 0 2019-04-08 21:47:06 ODTN-Net-Setup.Initial-Summary-Check completed 2019-04-08 21:47:06 ODTN-Net-Setup.Activate-Apps started -- onos 172.17.0.5 app activate odtn-service 2019-04-08 21:47:39 ODTN-Net-Setup.Activate-Apps completed 2019-04-08 21:47:39 ODTN-Net-Setup.Verify-Apps started 2019-04-08 21:47:39 Check-Apps-2 started -- onos-check-apps 172.17.0.6 optical-model,yang,config,configsync,faultmanagement,netconf,configsync-netconf,drivers,drivers.netconf,drivers.optical,restconf,protocols.restconfserver,odtn-api,drivers.odtn-driver,odtn-service,models.tapi,models.ietf,models.openconfig,models.openconfig-infinera,models.openconfig-odtn includes 2019-04-08 21:47:39 Check-Apps-3 started -- onos-check-apps 172.17.0.7 optical-model,yang,config,configsync,faultmanagement,netconf,configsync-netconf,drivers,drivers.netconf,drivers.optical,restconf,protocols.restconfserver,odtn-api,drivers.odtn-driver,odtn-service,models.tapi,models.ietf,models.openconfig,models.openconfig-infinera,models.openconfig-odtn includes 2019-04-08 21:47:39 Check-Apps-1 started -- onos-check-apps 172.17.0.5 optical-model,yang,config,configsync,faultmanagement,netconf,configsync-netconf,drivers,drivers.netconf,drivers.optical,restconf,protocols.restconfserver,odtn-api,drivers.odtn-driver,odtn-service,models.tapi,models.ietf,models.openconfig,models.openconfig-infinera,models.openconfig-odtn includes 2019-04-08 21:48:10 Check-Apps-3 completed 2019-04-08 21:48:10 Check-Apps-1 completed 2019-04-08 21:48:10 Check-Apps-2 completed 2019-04-08 21:48:10 ODTN-Net-Setup.Verify-Apps completed 2019-04-08 21:48:10 ODTN-Net-Setup.Tapi-context started 2019-04-08 21:48:10 ODTN-Net-Setup.Tapi-context-1 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkUntilSucc.sh /home/sdn/onos/tools/test/scenarios/bin/execute-tapi-context-get-call.py+172.17.0.5+empty 2019-04-08 21:48:10 ODTN-Net-Setup.Tapi-context-3 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkUntilSucc.sh /home/sdn/onos/tools/test/scenarios/bin/execute-tapi-context-get-call.py+172.17.0.7+empty 2019-04-08 21:48:10 ODTN-Net-Setup.Tapi-context-2 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkUntilSucc.sh /home/sdn/onos/tools/test/scenarios/bin/execute-tapi-context-get-call.py+172.17.0.6+empty 2019-04-08 21:48:19 ODTN-Net-Setup.Tapi-context-1 completed 2019-04-08 21:48:19 ODTN-Net-Setup.Tapi-context-2 completed 2019-04-08 21:48:20 ODTN-Net-Setup.Tapi-context-3 completed 2019-04-08 21:48:20 ODTN-Net-Setup.Tapi-context completed 2019-04-08 21:48:20 ODTN-Net-Setup.Tapi-connectivity started -- /home/sdn/onos/tools/test/scenarios/odtn/checkUntilSucc.sh /home/sdn/onos/tools/test/scenarios/bin/execute-tapi-post-call.py+172.17.0.5+tapi-connectivity:get-connectivity-service-list+empty 2019-04-08 21:48:20 ODTN-Net-Setup.Tapi-connectivity completed 2019-04-08 21:48:20 ODTN-Net-Setup.Verify-Logs-1 started 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-3 started -- onos-check-logs 172.17.0.7 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-2 started -- onos-check-logs 172.17.0.6 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-1 started -- onos-check-logs 172.17.0.5 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-1 completed 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-3 completed 2019-04-08 21:48:20 Check-Logs-Odtn-Setup-1-2 completed 2019-04-08 21:48:20 ODTN-Net-Setup.Verify-Logs-1 completed 2019-04-08 21:48:20 ODTN-Net-Setup.Init-network started 2019-04-08 21:48:20 ODTN-Net-Setup.Start-emulators started -- docker-compose -f /home/sdn/emulator/docker-compose.yaml up -d 2019-04-08 21:48:23 ODTN-Net-Setup.Start-emulators completed 2019-04-08 21:48:23 ODTN-Net-Setup.Generate-cfg-files started -- /home/sdn/onos/tools/test/scenarios/odtn/createNetCfg.sh 2019-04-08 21:48:53 ODTN-Net-Setup.Generate-cfg-files completed 2019-04-08 21:48:53 ODTN-Net-Setup.Put-nodes started -- onos-netcfg 172.17.0.5 /tmp/odtn/openconfig-devices.json 2019-04-08 21:48:53 ODTN-Net-Setup.Put-nodes completed 2019-04-08 21:48:53 ODTN-Net-Setup.Wait-nodes started 2019-04-08 21:48:53 ODTN-Net-Setup.Wait-node-1 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh device 172.17.0.5 2019-04-08 21:48:53 ODTN-Net-Setup.Wait-node-2 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh device 172.17.0.6 2019-04-08 21:48:53 ODTN-Net-Setup.Wait-node-3 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh device 172.17.0.7 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-node-1 completed 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-port-1 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh port 172.17.0.5 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-node-2 completed 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-port-2 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh port 172.17.0.6 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-node-3 completed 2019-04-08 21:49:05 ODTN-Net-Setup.Wait-port-3 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh port 172.17.0.7 2019-04-08 21:49:38 ODTN-Net-Setup.Wait-port-1 completed 2019-04-08 21:49:38 ODTN-Net-Setup.Wait-port-2 completed 2019-04-08 21:49:39 ODTN-Net-Setup.Wait-port-3 completed 2019-04-08 21:49:39 ODTN-Net-Setup.Wait-nodes completed 2019-04-08 21:49:39 ODTN-Net-Setup.Verify-Logs-2 started 2019-04-08 21:49:39 Check-Logs-Odtn-Setup-2-3 started -- onos-check-logs 172.17.0.7 2019-04-08 21:49:40 Check-Logs-Odtn-Setup-2-2 started -- onos-check-logs 172.17.0.6 2019-04-08 21:49:40 Check-Logs-Odtn-Setup-2-1 started -- onos-check-logs 172.17.0.5 2019-04-08 21:49:40 Check-Logs-Odtn-Setup-2-3 completed 2019-04-08 21:49:40 Check-Logs-Odtn-Setup-2-1 completed 2019-04-08 21:49:40 Check-Logs-Odtn-Setup-2-2 completed 2019-04-08 21:49:40 ODTN-Net-Setup.Verify-Logs-2 completed 2019-04-08 21:49:40 ODTN-Net-Setup.Put-links started -- onos-netcfg 172.17.0.5 /tmp/odtn/openconfig-device-link.json 2019-04-08 21:49:40 ODTN-Net-Setup.Put-links completed 2019-04-08 21:49:40 ODTN-Net-Setup.Wait-links started 2019-04-08 21:49:40 ODTN-Net-Setup.Wait-link-1 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh link 172.17.0.5 2019-04-08 21:49:40 ODTN-Net-Setup.Wait-link-2 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh link 172.17.0.6 2019-04-08 21:49:40 ODTN-Net-Setup.Wait-link-3 started -- /home/sdn/onos/tools/test/scenarios/odtn/checkNetInit.sh link 172.17.0.7 2019-04-08 21:50:11 ODTN-Net-Setup.Wait-link-2 completed 2019-04-08 21:50:11 ODTN-Net-Setup.Wait-link-3 completed 2019-04-08 21:50:11 ODTN-Net-Setup.Wait-link-1 completed 2019-04-08 21:50:11 ODTN-Net-Setup.Wait-links completed 2019-04-08 21:50:11 ODTN-Net-Setup.Verify-Logs-3 started 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-2 started -- onos-check-logs 172.17.0.6 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-1 started -- onos-check-logs 172.17.0.5 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-3 started -- onos-check-logs 172.17.0.7 2019-04-08 21:50:11 ODTN-Net-Setup.Init-network completed 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-1 completed 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-3 completed 2019-04-08 21:50:11 Check-Logs-Odtn-Setup-3-2 completed 2019-04-08 21:50:11 ODTN-Net-Setup.Verify-Logs-3 completed 2019-04-08 21:50:11 ODTN-Net-Setup completed 3:06 Passed! 41 steps succeeded |
2.2.2) net-odtn-restconf
The same as net-odtn-restconf in the single onos instance scenario, the output is shown below:
...