| commit | 3ccd44f33356ab42db104c3b0a752121c668cf70 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Mon Sep 25 15:21:48 2017 -0700 |
| committer | Scott Baker <scottb@onlab.us> | Sat Oct 07 07:53:19 2017 -0700 |
| tree | 17e7f54c11202da92874dcb81f6fb35bae340535 | |
| parent | 8fa1a614877cdb235cf53c2ae0226660035238e3 [diff] |
CORD-1923: Eliminate hardcoded dependencies between VTR and VSG Change-Id: I25017fa8f03e3ca9a160b6ff7d5074ce9320ac8a (cherry picked from commit 80cfb40f7a5354456043d4cf7331d27521a9fb8e)
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