| commit | 825cd732b87a9ef885b0998c94f1b49dad20eec9 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Fri May 19 08:40:30 2017 -0700 |
| committer | Scott Baker <smbaker@gmail.com> | Thu May 25 19:44:35 2017 -0700 |
| tree | 990188e29599b6b466c85336d4c888a336b6c564 | |
| parent | 7c0ed0f38d9724388942c631f6a9f1cc193e6e41 [diff] |
CORD-1337 Fix legacy VTR Admin Change-Id: I6ce99eb1cad283cf7869fe1189ef8b0f0e14b914
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