| commit | bba581a4455151e4b50d1adfe57b3f889d3c7ad1 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Tue May 09 14:38:31 2017 -0700 |
| committer | Scott Baker <scottb@onlab.us> | Wed May 10 08:50:37 2017 -0700 |
| tree | 71021fd67a86f45dadb4a51da985aa968af5dc6f | |
| parent | 6cc514744884aba55199696126790ba4745cc01d [diff] |
CORD-1130 remove onboarding artifacts from vtr Change-Id: Ic640da822dca431387dd8ca0d58b1a04d23336db (cherry picked from commit ae0b359cfec41624f035b3b317817c45c31adde5)
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