| commit | d64e8c47b50ed1903fc6e03ca9f5b526a199f86a | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <teo@opennetworking.org> | Tue Apr 24 12:59:28 2018 +0200 |
| committer | Matteo Scandolo <teo@opennetworking.org> | Tue Apr 24 12:59:28 2018 +0200 |
| tree | 731c6cc34878a08a3fe712f3297b7fc35e667d5c | |
| parent | a3c3fd8eff101168f0053dcccf6d375d980f5612 [diff] |
[CORD-2938] Moving convenience methods in the synchronizer containers Change-Id: I2c777ddad38659e96cb37521a346830735e0e483
The vTR service is designed to perform a connectivity test in place of the subscriber. It will save you time and costs of sending a truck to the subscriber premises to perform the same kind of test.
To onboard this service in your system, you can execute the onboard-vtr.yaml playbook, using this command:
ansible-playbook -i /etc/maas/ansible/pod-inventory --extra-vars=@/opt/cord/build/genconfig/config.yml onboard-vtr-playbook.yaml