| commit | 4acbd4c0ff8537bed05ddc8d40f2c7fd73bb6847 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Thu May 18 08:24:43 2017 -0700 |
| committer | Scott Baker <scottb@onlab.us> | Thu May 18 15:34:04 2017 -0700 |
| tree | 65d56a39973be9fb7705fbc806accd67c0365817 | |
| parent | ae0b359cfec41624f035b3b317817c45c31adde5 [diff] |
CORD-1337 use content_type strings instead of ids Change-Id: Ie23e2aae0a3165e7d43c2804704b3e9e6f64819c
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