| commit | cd2caa7a78ec7e0a6e91f478661078cb2672e685 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <matteo.scandolo@gmail.com> | Thu Sep 28 14:19:21 2017 -0700 |
| committer | Matteo Scandolo <teo@opennetworking.org> | Thu Sep 28 16:40:05 2017 -0700 |
| tree | 67415bbe819bcb480d44782b6f53da8898f58a29 | |
| parent | 4c30cf0b9f91e5d054627b48acfdbbae8611abee [diff] |
Fixing vTR dashboard Change-Id: I4183b2303708484288eebc8f32e319f0d9b07a42 (cherry picked from commit 945f536e2b3180dbb63aa4099bc5d0e17a90a3e5)
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