| commit | 15f11b9e0dc178ad070090fce853d62ed920dad5 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <matteo.scandolo@gmail.com> | Tue May 30 17:31:02 2017 -0700 |
| committer | Matteo Scandolo <matteo.scandolo@gmail.com> | Fri Jun 02 14:43:39 2017 -0700 |
| tree | 542f6e141a1c509572e1ea5f5e9123e5d15f1426 | |
| parent | aa0372a1a3e5b2b21fe64ff36aa20db75d03173a [diff] |
[CORD-1360] Using new config Change-Id: Iee7c2c456cf45e131fef0330a6f657ad0080449f
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